Siebrand Mazeland schrieb: > 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 hade a look, it seems realtively straight forward to me > 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. I would suggest to use TSV as supported by MySQLs LOAD INFILE command. That would make importing very easy. > 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. My idea was to dump TSV files to a web-readable directory, and have a cron-job on the toolserver that loads that file and imports it into MySQL using LOAD INFILE. > 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. Yes, I'll be there. Looking forward to seeing you all :) -- daniel _______________________________________________ Toolserver-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/toolserver-l
