On [[wikt:nl:Egypte]] I have two things that I would like your comments for.
* Under the header for pronounciation, it says on a line: * Geluid: Egypte
When pressing the template for sound ( {{-sound-}}translates to
Geluid ), you get a sound.howto
When pressing on Egypte, the process of letting you hear Egypte will
start (media)
*Under the header for Translations, there are three lines for Portugese;
* Indicating Portugese
One line with Brazilian Portugese and the word
One line with Portugese Portugese and the word
With the first thing I think I give ample attention to the potential
problems with sound. When there is a SAMPA transliteration, it would be
on a seperate line and the SAMPA would get you to something about SAMPA,
With the second thing I think I have a proper way of presenting
alternate standard translations within one language. the templates used
are {{pr br}} and {{pt pt}}
Thanks,
GerardM
Over the last few days, I've had an intermittent problem where my
watchlists on both w:en: and meta: come up as though I was loading the
page a day or so ago. As in, it says "..the last X changes in the last
3 days" but then begins with "29 Sep 2004" and goes back from there.
Does anyone know why this is? Is it a result of overloaded servers? Or
just some on-going maintenance? Or is there something more serious - a
server with an incorrect internal clock, for instance?
Just thought I'd ask because a) it's a bit annoying and b) if nobody
who had the power to fix it knew about it, it would carry on being
annoying on and off for ages. So I apologise if this is something
you're already working on.
--
Rowan Collins BSc
[IMSoP]
Hoi,
To celebrate the 5000th word of nl:wiktionary, I have uploaded 100 .ogg
files to Commons. These are Dutch words pronounced by me. While doing
this excercise, I have written a blurp about sound and how to handle it
on Wikimedia. The piece is still in Dutch, it is still in nl:wiktionary,
but I have asked the nl:wikipedia crowd to review it. When this is done,
I will translate it in English and post it in Meta ? en:Wikipedia ?
Please let me know..
One thing that is non obvious is that a sound file is supposed to be an
image; the name for a *sound* file is: "Image:Title.ogg". Can this be
changed to be Sound or something ??
I have read the posts about Firefox and the problems that we have
supporting Internet Explorer. Would it be an idea to suggest that
Wikimedia is best experienced with Firefox / Opera / .. I am myself a
fan of Firefox, it really increases my productivity using two screens
with 9 tabs on average. That is what the Firefox experience is for me :)
Seriously though, when we do not allow MP3, would it not make equally
good sense to suggest that our content is best experienced not using IE
?? Needless to say, we would continue the support for IE !!
It only needs to be a small statement on our main page or on our user
portal ...
Thanks,
GerardM
Hoi,
One difference with pictures is, that when you save a screen with a
picture on it, you save the picture at the same time. When you save an
"image" with a sound, you do NOT save the sound at the same time. The
problem is that when people prepare their computer to use .ogg files.
One stage is to check if you can hear .ogg files locally. This means
that you have to HAVE an .ogg file.
Yesterday I mentioned that sounds being "Image"s for wikimedia is
counterintuitive, today I ask for a Sound detail screens which has the
option to download the sound,
Thanks,
GerardM
On the English Wikipedia, I have been trying to upload the latest
version of wikipedia-mode.el, an Emacs lisp mode for editing wikipedia
articles. After submitting the file, I end up at a page that says
"Warning: .el is not a recommended file format". There used to be two
buttons underneath this, labelled "Upload anyway" and "Cancel", but
these have disappeared, which means I'm no longer able to proceed.
Can someone fix this?
-- CYD
My idea: http://bugzilla.wikipedia.org/show_bug.cgi?id=607 was denied
because its similar to a fix thats in 1.4 CVS:
http://bugzilla.wikipedia.org/show_bug.cgi?id=143
This 143 fix is not sufficient because it makes links to templates
available from the editing screen. My proposal is for a backlink (to
the template itself or its edit page) to be rendered in directly in a
standard article (not only on its edit page).
I write this argument to the list now because if we have a link in the
actual page for editing sections, then we should surely have a link
helping us quickly get back to a template.
For the third time, this message:
:Due to the ever-increasing number of people visiting Wikipedia and its sister
Wikimedia projects, we have a constant need to buy new hardware to keep the
site running. If you'd like to help, please
[http://wikimediafoundation.org/wiki/fundraising donate].
is ''completely'' useless when the database server is down since the
[http://wikimediafoundation.org/wiki/fundraising donate] link brings up the
same damn message. ''Please'' create a static copy of the old fundraising page
and link to that from a failsafe server.
-- mav
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
We're tightening up security on the uploads due to exploitable Internet
Explorer and Safari bugs that allow for scripting attacks to steal
session and saved password cookies.
For the moment uploads are limited to the default extension whitelist:
'png', 'gif', 'jpg', 'jpeg', 'ogg'. Other types of files can't be
uploaded to the wikis until we expand it again, but files already
uploaded remain accessible.
-- brion vibber (brion @ pobox.com)
The basic functionality of switching the UI language is in CVS HEAD. I
see test.wp is already running it, so please take a look.
The current implementation is largely suggested by Tim Starling (at
least I heard it from him...): We explicitly separate the UI language
and the content language, and create two language objects: wgContLang
and wgLang. wgLang is for the UI and wgContLang is for the content.
The original wfMsg* functions will specifically fetch message for the
UI, and wfMsgForContent() and wfMsgNoDBForContent() should be used for
content.
Only messages of the content language (and supported variants, such as
zh-cn and zh-tw for zh) are stored in the MediaWiki: namespace. All
message keys are suffixed by the language code in the namespace. For
example, 'mainpage' will be 'mainpage/en' in the en site, and
'mainpage/fr' in the fr site, etc. This is mainly for the purpose of
supporting multiple variants (e.g. zh-tw and zh-cn) in the namespace.
Right now the UI language option is only accessible for registered
users through the preference page. I think we should also place a
selection box somewhere in the mainpage for anonymous users so they
can choose the UI language as well.
--
zhengzhu
Dear members-of-the-list
and especially Hans-Juergen, Nick and Chris and of course Markus:
if you are interested in E-mail notification on page and user_talk page
changes - we call it "enotif" -
please feel kindly invited to visit the first release
- the patch itself at http://bugzilla.wikipedia.org/show_bug.cgi?id=454
- the documentation at http://meta.wikipedia.org/Enotif
Tom and Markus
September 2004