The Wikimedia Language Engineering team is pleased to announce the
first release of the MediaWiki Language Extension Bundle. The bundle
is a collection of selected MediaWiki extensions needed by any wiki
which desires to be multilingual.
This first bundle release (2012.11) is compatible with MediaWiki 1.19,
1.20 and 1.21alpha.
Get it from https://www.mediawiki.org/wiki/MLEB
The Universal Language Selector is a must have, because it provides an
essential functionality for any user regardless on the number of
languages he/she speaks: language selection, font support for
displaying scripts badly supported by operating systems and input
methods for typing languages that don't use Latin (a-z) alphabet.
Maintaining multilingual content in a wiki is a mess without the
Translate extension, which is used by Wikimedia, KDE and
translatewiki.net, where hundreds of pieces of documentation and
interface translations are updated every day; with Localisation Update
your users will always have the latest translations freshly out of the
oven. The Clean Changes extension keeps your recent changes page
uncluttered from translation activity and other distractions.
Don't miss the chance to practice your rusty language skills and use
the Babel extension to mark the languages you speak and to find other
speakers of the same language in your wiki. And finally the cldr
extension is a database of language and country translations.
We are aiming to make new releases every month, so that you can easily
stay on the cutting edge with the constantly improving language
support. The bundle comes with clear installation and upgrade
installations. The bundle is tested against MediaWiki release
versions, so you can avoid most of the temporary breaks that would
happen if you were using the latest development versions instead.
Because this is our first release, there can be some rough edges.
Please provide us a lot of feedback so that we can improve for the
next release.
-Niklas
--
Niklas Laxström
Hi,
after a user reported a discrepancy between two versions of the autonym for
the Czech language used in different contexts in MediaWiki, I noticed it
comes from a difference between the MediaWiki core Names.php and CLDR data
(via the CLDR extension’s CldrNames). Originally, I just intended to submit
a patch to Names.php unifying those two to the CLDR version, but then I
thought the problem might exist in other languages, too.
So, I compiled a list [1][2] of 39 differences in language names between MW
core and the CLDR extension. Some of those differences are just case
changes, some of them might be errors in one of the sources, some of them
just random choices between two equally valid versions (like in the Czech
case, it’s not like one of them is generally better than the other, it’s
just that consistency would be better).
I definitely do not intend to change all those languages I do not
understand, but maybe other people could be interested in checking their
language in the list…
-- [[cs:User:Mormegil | Petr Kadlec]]
[1]
http://translatewiki.net/wiki/User:Mormegil/CLDR_language_names_differences
[2] https://gist.github.com/mormegil-cz/7240262
Hello,
I would like to announce the release of MediaWiki Language Extension
Bundle 2014.01. This bundle is compatible with MediaWiki 1.22.2 and
MediaWiki 1.21.5 releases.
* Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.01.tar…
* sha256sum: 2dc673ba0bbc43a3d69237c15600171e85d3c56d9ff520e5bdb3eda0f2fdc74a
Quick links:
* Installation instructions are at: https://www.mediawiki.org/wiki/MLEB
* Announcements of new releases will be posted to a mailing list:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n
* Report bugs to: https://bugzilla.wikimedia.org
* Talk with us at: #mediawiki-i18n @ Freenode
Release notes for each extension are below.
-- Kartik Mistry
== Babel, CLDR, CleanChanges and LocalisationUpdate ==
* Only localisation updates.
== Translate ==
=== Noteworthy changes ===
* Bug 45695: Added plural support for Android file format.
* Bug 46831: Fixed HTML validation error which caused broken layout in
especially in the Monobook skin when language is blacklisted.
* Bug 59199: Regression in the previous MLEB release: Message groups
without changes were listed on Special:ManageMessageGroups.
* Bug 59241: MediaWiki plural syntax checker no longer warns about
false positives.
* Bug 60128: Fixed statsbar for subgroups in the message group
selector for correct statistics.
* Bug 60198: Preserve whitespace in review mode. In review mode,
whitespace was not preserved and new lines were being displayed as
single spaces, which was messing up the messages.
* Fixed a regression caused by Alt shortcuts introduced in the
previous MLEB release: Can again access special characters with AltGr.
* Translation editor now reacts better to page scrolling and resizing.
* Set directory and language of insertables to the source messages' values.
* Special:SupportedLanguages is now faster.
* Translate can be installed via Composer now.
== UniversalLanguageSelector ==
=== Noteworthy changes ===
* Bug 59175: When clicking a regions in the map in ULS, scroll only
the list of languages and not the entire page.
* Bug 59239: Fixed an alignment issue of ULS personal toolbar trigger.
* Bug 59958: Fixed an issue where web fonts were sometimes loaded for
elements that use the Autonym font.
=== Fonts ===
* Added new font RailwaysSans.
* Updated AbyssinicaSIL font to latest upstream (1.500) version.
* Fix name of Scheherazade to properly target locally installed font on system.
--
Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_
{kartikm, 0x1f1f}.wordpress.com
Hello,
Now Lua has access to the internal fallback sequences of MediaWiki [1], so
this can be used to gracefully degrade the translation of the templates
included in a page, by the means of {{Translatable template}} (also called
{{TNT}}) or auto-translated templates which use {{Fallback}}, mainly on
Commons. I worked on this yesterday [2].
But I send this message mainly to show the comparison between the fallback
sequences of Commons vs MediaWiki [3].
I guess some fallback sequences of Commons could be added to MediaWiki:
* af -> nl
* br -> fr (not sure)
* ckb -> fa
* en-gb -> en
* fy -> nl
There is one conflicting fallback sequence:
* co -> fr (Commons) or it (MediaWiki)
And some differences:
* pdt -> nds, de (Commons) or de (MediaWiki)
* nds -> nds-nl, de (Commons) or de (MediaWiki)
* nds-nl -> nds, nl (Commons) or nl (MediaWiki)
And more importantly, the purposes of the fallback sequences are a bit
different inside a same language family/variant family: MediaWiki
specializes from general to variants (often by script), but Commons does
the opposite: degrades from variants to general. I find a feature could be
added in the Translate extension to give access to these "reverse fallback
sequences" by comparison to MediaWiki’s ones. This could be implemented
either by creating a small database (perhaps add the opposite parameter of
$fallback in the MessagesXX.php) either by computing these. This could be
used for the translation of the templates, in Special:MyLanguage [bug
48292], and to redirect the translators to the general language (the
messages "Translate in zh please." in $wgTranslateBlacklist of
CommonSettings.php in Wikimedia config).
[1] https://gerrit.wikimedia.org/r/101910
[2]
https://meta.wikimedia.org/wiki/Module_talk:Template_translation#Fallback
[3]
https://commons.wikimedia.org/wiki/Template_talk:Fallback#Comparison_of_the…
[bug 48292] https://bugzilla.wikimedia.org/48292
~ Seb35
Dear all,
My apologies up front for the long e-mail that follows. In this e-mail you
will find a comprehensive status overview of the recent WebFonts deployment.
On Monday December 12 at 18:00 UTC we deployed the extension WebFonts[1] to
40 wikis in 11 Indic languages and Wikimedia Incubator -- all wikis in
Assamese, Bengali, Gujarati, Hindi, Kannada, Marathi, Nepali, Oriya,
(Eastern) Punjabi, Sankrit and Telugu have WebFonts now. WebFonts was not
deployed on Malayalam and Tamil projects. The reason for this was that
community members had requested us not to. We are confident that in time,
the communities will request that WebFonts is enabled on their projects.
WebFonts aims to resolve the issue that users see incomplete web pages,
because the fonts to properly render the page is not present in the local
system by downloading the font through the browser.
One of our great challenges developing this functionality is the multitude
of scripts and the low availability of freely licensed fonts that may be
modified and redistributed.
Over the past few months we have tried to build out a collection of fonts
in the extension mainly for Indic languages, and we have performed many
tests. We have solicited community involvement through messaging in village
pumps, e-mails on mailing lists, blog posts on personal blogs as well as on
the Wikimedia Foundation blog, at developer events, through personal
e-mails and through our bug tracker, and gotten some feedback, although
unfortunately not for all the languages we would like to have gotten it
for. We will of course continue our efforts in this area. Next to the
community involvement, we have had a two day session with the Red Hat
Localisation team in Pune, India.
Since the deployment, we have been criticised for not communicating enough
-- or not through the right channels, not with the right people, not in
time, or too soon, or not with the right messages. I'm not really sure how
to respond to that, except for uttering a general "mea culpa, mea maxima
culpa". We are working really hard in continuously improving the work that
we do, and the way that we do it. We make mistakes, we are human after all,
and when we become aware of our mistakes, we will do everything in our
power to make it better.
With our team we support the mission of the Wikimedia Foundation to
"imagine a world in which every single human being can freely share in the
sum of all knowledge." I care about that -- a lot. We all care, and I am
pretty certain that we're not ignorant, dismissive or incapable. I
acknowledge that we as the Localisation team are a relatively new entity
within the MediaWiki development community and within the Wikimedia
Foundation, with a very wide scope, and that we are dealing with a lot of
technical details on which we are simply not able to assess the final
quality; there are after all 7.500 languages in this world of over 7
billion people that we theoretically all cover, some 350 of those languages
are supported in MediaWiki, and 280 within Wikimedia.
I accept that we cannot keep everybody happy -- doesn't keep us from
trying, though. I want to try and work with as many people as possible in a
constructive way. With these numbers, that's not always easy to coordinate.
To channel the input on languages, we have set up "Language Support
Teams"[2]. We do not yet have a language support team for every language.
Please sign up if you care about the technical facilitation of your
language in the Wikimedia movement. Let's use the mediawiki-i18n mailing
list[3] to have constructive discussions about language support. Let's use
the #mediawiki-i18n IRC channel[4] on Freenode to have real-time
discussions. Let's use bugzilla.wikimedia.org to report bugs[5]. Link [5]
explains the bug reporting procedure. If you already know how, report
issues quickly using this link: http://ur1.ca/6ov9a .
Since the deployment, we have been made aware of about 17 issues. Some very
serious in nature, others not requiring immediate attention. Yesterday an
issue with web fonts not loading in Firefox was resolved in the
infrastructure. Today around 15:30 UTC, we have deployed fixes for an
additional hand full of issues[6]: functionality disabled in IE6, IE8 on
Windows XP, selection buttons not working properly in IE7 and hiding the
Samyak fonts in the font selector. During our current sprint, we are
working on a framework for multi-lingual and localised user documentation
as well as feature based feedback functionality for WebFonts, Narayam and
Translate. In the future we will also explore what is known as "dark
launch" by some, a kind of hidden live deployment of a feature, only usable
be for example manipulating a URL. This would allow us to deploy a feature
in a live environment, without having the "full deployment" impact.
Thanks for reading through this. I am looking forward to working with you!
Please read on for details on all the issues that were reported on WebFonts
recently.
Cheers!
Siebrand Mazeland
Product Manager Localisation
Wikimedia Foundation
=======================================
Links
=======================================
[1] https://www.mediawiki.org/wiki/Extension:WebFonts
[2] https://translatewiki.net/wiki/Language_support_team
[3] https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n
[4] https://translatewiki.net/wiki/Special:WebChat
[5] https://www.mediawiki.org/wiki/Bugzilla
[6] https://www.mediawiki.org/wiki/Special:Code/MediaWiki/106204
=======================================
Open issues
=======================================
https://bugzilla.wikimedia.org/33004 -- Old cached pages do not have web
fonts enabled
Priority: HIGH
--------------------------------------------------------------------------------------
Wikimedia is able to serve this many pages with relative few servers
because of very aggressive caching strategies, especially for anonymous
users. WebFonts requires the addition of JavaScript for anonymous users,
which is not being done for pages that are in the squid cache at the moment
WebFonts was enabled. All squid cache objects for wikis on which WebFonts
was deployed need to be purged. An internal RT ticket created for the
Wikimedia Operations team to get anonymous squid caches purged. This may
take up to a week or longer to be resolved.
https://bugzilla.wikimedia.org/33018 -- Firefox 5 on Windows XP has script
time-outs
Priority: MEDIUM
--------------------------------------------------------------------------------------
The Localisation team has tested this report, and was not yet able to
confirm the observation. The reason for using a non-recent version of
Firefox for the report was the alleged lower memory usage. Brion noted that
Mozilla has been actively working on lowering memory usage over the last
year, so the reporter may be better off with the current versions than the
old ones.
https://bugzilla.wikimedia.org/33110 -- Google Crome on Windows XP dispays
gibberish
Priority: LOW
--------------------------------------------------------------------------------------
Observed very rarely on a page on Wikimedia Incubator, and we have not been
able to reproduce this observation, let alone reproduce it reliably. A
screenshot is present in the bug report. Except for reporting upstream, no
action is being taken on this issue at this point in time.
https://bugzilla.wikimedia.org/33054 -- Hinting issues in Lohit fonts
Priority: MEDIUM
--------------------------------------------------------------------------------------
Confirmed in Windows XP. We can do something to the font by adding hinting,
but this is a lot of work if it needs to be done manually. The stem of the
Lohit glyphs could do with more width and darkness. This may not be
desirable for platforms (Linux) which render it perfectly, because it
already has hinting and anti-aliasing on an operating system level. Same
goes got Windows 7.
https://bugzilla.wikimedia.org/33100 -- Page crashes on Webkit browsers
with WebFonts enabled.
Priority: MEDIUM (could be HIGH if we find many occurances)
--------------------------------------------------------------------------------------
A page in Nepali Wikipedia makes a tab on Mac OS X 10.7.2 with Google Crome
crash. This behaviour was also reported for Mac OS X 10.7.2 (11C74) with
Safari 5.1.1 (7534.51.22, r102522) [This is a webkit nightly build] by
thedj. This is most probably related to the WebFonts code, because if, as a
logged in user, web fonts is disabled in preferences, the page does not
crash Chrome.
Developer Derk-Jan Hartman was asked to report this bug in the WebKit.
Please make us aware of any additional pages that would cause this
behaviour in any wiki.
https://bugzilla.wikimedia.org/33102 -- OSX 10.7.2/Opera 11.60 has no
fallback for Latin characters
Priority: MEDIUM
--------------------------------------------------------------------------------------
This is a bug that needs to be reported upstream. No technical measures
have been taken so far to mitigate this issue. One of the Localisation team
members has been in contact with a high level executive of Opera, and will
contact that person again. We're going to wait for a few days for an
outcome -- if there is no expectation of a relatively quick fix, we might
disable WebFonts for Opera completely. Opera unfortunately does not have a
public bug tracker.
https://bugzilla.wikimedia.org/33027 -- Narayam and WebFonts both loading
slows down page
Priority: MEDIUM
--------------------------------------------------------------------------------------
The reporter claims that the functionality is quicker on
translatewiki.netthan it is in Wikimedia wikis. A commenter states
that more functionality
usually means more code, means more data that needs to be transferred, and
without changing bandwidth, that causes longer load times.
This currently isn't our highest priority, but eventually we will look into
this a little deeper. We're inviting volunteers to do some of the data
gathering and analysis for us. What is needed in our opinion is insight in
the data volume added by WebFonts, as well as an assessment of the code
quality with regards to size optimisation. All referenced properly, of
course :). There are alternate EOT conversion tools that have a good
compression ratio. Needs to be explored, but EOT is not required for modern
browsers since they started using WOFF fonts which are compressed OpenType
fonts.
https://bugzilla.wikimedia.org/33085 -- Integration of updated Lohit-Tamil
Font
Priority: MEDIUM
--------------------------------------------------------------------------------------
Request to update WebFonts with a font that is updated upstream. This is
something the Localisation team checks regularly. Will probably be closed
this week, pending issues the have a higher priority.
https://bugzilla.wikimedia.org/32942 -- Provide help page and bug report
link for WebFonts
Priority: HIGH
--------------------------------------------------------------------------------------
More recently developed tools by the Wikimedia Foundation have often
included feedback mechanisms. The Localisation team plans on implementing
these for the functionality of the WebFonts, Narayam and Translate
extension. Besides that, we also want to provide multi-lingual and
localised documentation. This needs some thinking and some work to provide
in a structured and navigable way. We'll keep you posted. It will most
probably involve translatable *user* documentation on MediaWiki.org and
hopefully it is possible to have one feedback location per feature across
the multiple Wikimedia wikis -- this is something we're going to contact
the ArticleFeedback and MoodBar teams for.
=======================================
Closed issues
=======================================
https://bugzilla.wikimedia.org/33025 -- When changing to a non-default web
font, the content does not
--------------------------------------------------------------------------------------
This issue was a side effect of a feature to allow multiple web fonts to be
used using the "lang" attribute. It was resolved in
https://www.mediawiki.org/wiki/Special:Code/MediaWiki/105980 and has been
deployed.
https://bugzilla.wikimedia.org/33034 -- Web fonts not loading in Firefox
--------------------------------------------------------------------------------------
Duplicate reports were 33038 and 33044. This issue originated from
http://www.w3.org/TR/css3-fonts/#same-origin-restriction. Almost all
browsers except for Firefox ignore that specification. A fix was designed
and deployed: https://www.mediawiki.org/wiki/Special:Code/MediaWiki/106092,
https://gerrit.wikimedia.org/r/1501. Thanks to Roan, Brion and Ryan for
their help.
https://bugzilla.wikimedia.org/32775 -- Gibberish in Internet Explorer 8 on
Windows XP
--------------------------------------------------------------------------------------
This is an unexplained phenomenon only observed in Internet Explorer on
Windows XP. It is also hard to reproduce. One of the developers was able to
make something somewhat reproducible on a clean, fully patched installation
of Windows XP with Internet Explorer 8. See bug report for details.
Based on these observations we think it is a bad idea to keep supporting
WebFonts in Internet Explorer 8 on Windows XP and we have disabled it in
https://www.mediawiki.org/wiki/Special:Code/MediaWiki/106172. This fix has
been deployed.
https://bugzilla.wikimedia.org/33096 -- Internet Explorer 6 does not have
font fallback
--------------------------------------------------------------------------------------
IE6 not having font fallback causes Latin characters to display as squares
when a web font is loaded that does not contain glyphs for the Latin
script. A screenshot is available at
http://media.crossbrowsertesting.com/users/34057/screenshots/window/z669002….
Based on this observation, we think it is a bad idea to keep supporting
WebFonts in Internet Explorer 6 and we have disabled it in
https://www.mediawiki.org/wiki/Special:Code/MediaWiki/106172. This fix has
been deployed.
https://bugzilla.wikimedia.org/33024 -- WebFonts menu buttons not working
in IE7
--------------------------------------------------------------------------------------
This was caused by the JavaScript $( '<input type="radio" />' ) . attr(
"name" ,"font"); not working in IE6 and IE7. Updating name attributes once
they have been created is not possible. We think there may be more
occurances of this in our code (one occurance in jQuery has already been
identified: resources/jquery/jquery.validate.js:59). A fix was made in
https://www.mediawiki.org/wiki/Special:Code/MediaWiki/106175. This fix has
been deployed.
https://bugzilla.wikimedia.org/33040 -- Overlap in Samyak font for Hindi
and Sanskrit
--------------------------------------------------------------------------------------
This issue occurs in Windows XP and Windows 7 (possibly also in Windows
Vista) when using Google Chrome. It is not observed when using Chrome with
Mac OS X 10.7.2 or several Linux distributions (Debian and Fedora). Samyak
Devanagari is available as a non-default web font in Hindi, Marathi, and
Sanskrit. Samyak Gujarati is available for Gujarati as a non-default font.
This font needs to be corrected. The maintainers will be notified of the
observed issues, and mean while, the fonts will be removed from the
WebFonts selection list (but can still be used using the font-family
property. A fix was made in
https://www.mediawiki.org/wiki/Special:Code/MediaWiki/106179. This fix has
been deployed.
https://bugzilla.wikimedia.org/33039 -- Overlap in Madan font for Nepali
--------------------------------------------------------------------------------------
This report was invalid. The reporter was not aware of the correct glyph
for the Nepali script.
Comments on this bug report resulted in two odd observations (Crome crash,
Opera font fallback), that have been split off into separate bug reports:
https://bugzilla.wikimedia.org/33100 and
https://bugzilla.wikimedia.org/33102.
https://bugzilla.wikimedia.org/33095 -- WebFonts menu can expand off the
screen
--------------------------------------------------------------------------------------
If the translations for "Select font" and "Login / Register" are really
short, like in http://mr.wiktionary.org, expanding the WebFonts menu for
anonymous users will display a menu that is partially off the screen. It
was resolved in http://www.mediawiki.org/wiki/Special:Code/MediaWiki/106186,
http://www.mediawiki.org/wiki/Special:Code/MediaWiki/106197,
http://www.mediawiki.org/wiki/Special:Code/MediaWiki/106201,
http://www.mediawiki.org/wiki/Special:Code/MediaWiki/106202. These
revisions also depend on a few small UI changes of both WebFonts and
Narayam, and will be deployed on December 19, 2011.
<no bugzilla report> -- WebFonts menu expands under the control for
customised input method in IE6 on transliteration
--------------------------------------------------------------------------------------
There are issues with the z index in IE6. Because of
https://www.mediawiki.org/wiki/Special:Code/MediaWiki/106172, WebFonts is
no longer available in IE6, so this issue is obsolete. Observing that the
Hindi projects Wikipedia and Wiktionary are using an custom input methods
tool, we would like to invite them to test Narayam which contains many
input methods in a MediaWiki extension. We are very open to having the
Hindi input method InScript tested and add a transliteration input method
with some community representatives, as we have done with other Indic
languages. We hope this will eventually lead to Narayam being adopted by
the Hindi community, and the custom input method being abandoned.
Hi, and best wishes for 2014!
This message is sent to the MediaWiki i18n mailing list and to all users of
translatewiki.net that have ever contributed to translations of the
following language codes: ab, av, ba, be-tarask, bxr, ce, crh-cyrl, cv,
inh, koi, krc, kv, lbe, lez, mhr, mrj, myv, ru, sr-ec, sr-el, tt-cyrl, tyv,
udm, uk, xal. 256 people are in BCC for this email.
*Short version of my message:*Your language needs your help. We ask you to
please review outdated messages for your language at
https://translatewiki.net/w/i.php?title=Special:Translate&group=mediawiki&f…
*Longer version:*
MediaWiki's plural <https://translatewiki.net/wiki/Plural> rules have been
updated to CLDR <https://translatewiki.net/wiki/CLDR> 24. We use these to
be standard-compliant. CLDR 24 introduces some changes in the Russian
plural forms. The changes are applicable to all languages that do not
define explicit plural forms in CLDR and fall back to Russian.
Plural forms for Russian and languages which fall back to Russian are now
as follows:
- Form 1: 1, 21, 31, 41, 51, 61, 71, 81, 101, 1001, …
- Form 2: 0, 5, 6, 7,8,...18, 19, 100, 1000, 10000, 100000, 1000000, …
- Form 3: 2, 3, 4, 22, 23, 24, 32, 33, 34, 42, 43, 44, 52, 53, 54, 62,
102, 1002, …
Effectively, form 2 and form 3 have switched places.
For Russian, languages having Russian as fallback, Serbian, Ukrainian and
Belarusian, there used to be a special case where translators could supply
only 2 plural forms. The first one would be used only for the case of 1 and
the second for all other numbers. This special case has been merged with
the explicit number plural forms. From now on, when {{PLURAL}} is uses two
forms, the first form will be used for 1, 21, 31 etc., and the second for
all other numbers.
Everything is explained at
https://translatewiki.net/wiki/Thread:Portal_talk:Ru/Plural_changes_in_many….
Please ask your questions there so everyone can benefit from the discussion.
We have updated current translations as well as we could, and marked all
messages as outdated. You can review them here:
https://translatewiki.net/w/i.php?title=Special:Translate&group=mediawiki&f…
Many thanks in advance for your help.
Cheers!
--
Siebrand Mazeland
Product Manager Language Engineering
Wikimedia Foundation
M: +31 6 50 69 1239
Skype: siebrand
Support Free Knowledge: http://wikimediafoundation.org/wiki/Donate
[x-posted]
Hello,
The Wikimedia Language Engineering team [1] invites everyone to join the
team’s monthly IRC office hour on January 8, 2014 (Wednesday) at 1700 UTC/
0900 PST on #wikimedia-office. During this session we would be talking
about highlights from our team’s activities and updates from ongoing
projects. Event details and agenda are listed below.
Questions can be sent to me directly before the event. See you all at the
IRC office hour!
regards
Runa
[1] http://wikimediafoundation.org/wiki/Language_Engineering_team
== Details: ==
# Event: WMF Language Engineering Office Hour
# Date and Time: Wednesday, January 8, 2014, 1700-1800 UTC, 0900-1000 PST
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140108T1700
# IRC channel: #wikimedia-office on irc.freenode.net
== Agenda: ==
Project Updates
Q/A (questions can be sent to runa at wikimedia dot org before the event)
--
Language Engineering - Outreach and QA Coordinator
Wikimedia Foundation
Flow was supplying an empty string as a parameter to a message, due to a
bug 59198. What surprised me is the rendered HTML turned into a
preformatted (typewriter-style) block. This happens because the
'flow-topic-participants' message goes through parse(), and in wikitext a
leading blank formats the text as a <pre> tag. You can see this using
eval.php:
> echo wfMessage( 'flow-topic-participants', 2, 2, '', 'second person'
)->parse();
(note the empty string for first participant); this prints
<pre>and second person
</pre>
1) Is there a way to turn off this over-aggressive parsing? It's unwanted
for an i18n string you know should just be a span.
2) Is there an idiom to guard against this unintended <pre> tag generation,
without making the message[1] even more complicated? E.g. we could put some
zero-width Unicode character at the start.
Thanks as always in advance,
[1]
'flow-topic-participants' => '{{PLURAL:$1|$3 started this
topic|{{GENDER:$3|$3}}, {{GENDER:$4|$4}}, {{GENDER:$5|$5}} and $2
{{PLURAL:$2|other|others}}|0=No participation yet|2={{GENDER:$3|$3}} and
{{GENDER:$4|$4}}|3={{GENDER:$3|$3}}, {{GENDER:$4|$4}} and {{GENDER:$5|$5}}}}
--
=S Page WMF Features engineer
