Last modified: 2014-10-15 20:25:32 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T47672, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 45672 - Separate English and qqq messages from others
Separate English and qqq messages from others
Status: RESOLVED WORKSFORME
Product: MediaWiki extensions
Classification: Unclassified
WikidataRepo (Other open bugs)
unspecified
All All
: Low minor (vote)
: ---
Assigned To: Wikidata bugs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-03-03 20:44 UTC by Daniel A. R. Werner
Modified: 2014-10-15 20:25 UTC (History)
6 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Daniel A. R. Werner 2013-03-03 20:44:07 UTC
English and qqq messages should have their own file since editing the file directly gets slower and slower. Perhaps we should even have one file per language. Not sure what translatewiki can support.

Splitting the file would make editing of messages during development significantly faster and clearer.
Comment 1 Niklas Laxström 2013-03-03 20:53:55 UTC
Translate extension does not support this unless someone starts coding. The alternative is to use multiple i18n files partitioned by set of messages.
Comment 2 jeblad 2013-03-05 10:32:39 UTC
Eclipse 3.7 was veeeery slow on this, 3.8 is nearly normal in speed. The merge conflicts on old changesets can be horrible due to changes in other languages, if we could avoid them, then that would be a reason for changing the file layout.
Comment 3 Nemo 2014-10-15 20:25:32 UTC
WONTFIX is giving en, qqq a special treatment; but the bug summary was satisfied by the new [[mw:Localisation file format]] in JSON files (one per language).

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links