Any input/output format requires 'ffs' support in Translate, whichever
format would be chosen as wanted, if not already supported (see
extensions/Translate/ffs/). At the moment there is support for Wiki
(MessagesXx.php), WikiExtension (MediaWiki extension i18n style), gettext,
Java .properties style (key=message), PHP variables ($key="message"), and
XLIFF (untested). One of these supports multiple languages in one file
(WikiExtension).
I think it is unavoidable to develop a new ffs - there is little to no
documentation on ffs development, but I hope the current code can serve as
example. We have to keep in mind that in theory messages can contain both
semi-colons and tabs, so care has to be taken chosing a separator when
designing a xSV format.
If there would be a Subversion or similar repo available to store the output
from Betawiki, I could commit the changes almost on a daily basis back into
toolserver (or even easier, add it somewhere in
svn.wikimedia.org), from
where it could be processed further.
CC-ing Niklas as he knows a tiny bit more about Translate development than I
do.
Daniel, would you happen to be at FOSDEM this weekend? Niklas will be there,
as will I, so that would be a great opportunity to close this deal.
Cheers! Siebrand
-----Oorspronkelijk bericht-----
Van: toolserver-l-bounces(a)lists.wikimedia.org
[mailto:toolserver-l-bounces@lists.wikimedia.org] Namens Daniel Kinzler
Verzonden: maandag 2 februari 2009 13:40
Aan: toolserver-l(a)lists.wikimedia.org
Onderwerp: Re: [Toolserver-l] Betawiki translations
Luxo schrieb:
So I propose a
four field scheme: language, *application*, key, message.
application would be something like the groups in the translatewiki,
right?
yes.
the translatewiki offers a php output for groups, e.g.
for MediaWiki -
Messages
http://translatewiki.net/w/i.php?title=Special%3ATranslate&task=export
-to-file&group=core&language=de&limit=100
.
eventually we can use that to sync?
I would much rather have TSV/CSV output for syncing. Should be trivial to
add that.
-- daniel