Talk:Toolserver:Translatewiki.net interface
Add topic
This page was moved from the Toolserver wiki.
Toolserver has been replaced by Toolforge. As such, the instructions here may no longer work, but may still be of historical interest.
Please help by updating examples, links, template links, etc. If a page is still relevant, move it to a normal title and leave a redirect.
# All files in that directory that have the extension ".yml" and do not start with "." are considered message files.
What's this for? Only files with match valid language code + .yml are read by the extension.
# The root node uses the language code (see above) as a key.
Isn't this redundant?
This import script shall be run from cron on a regular basis, perhaps daily.
Perhaps more often, if we want to export more often or do some quick fixes. It should then check if it has changed. In normal use then the exports we do would happen more seldom than you try to import. – Nikerabbit 10:07, 18 September 2009 (UTC)
- the thing about all files being message files basically tells people to to put other yaml files into the same dir, to avoid confusion. together with the next item (ther root node being the language code), this allows you to simply reads all yml files, ignore their file names, and use the root nodes as the language code. Having the code in the root node would also allow us to relax the first requirement and allow all languages to be in a single file. Basically, these two items are about flexibility/robustness.
- So be it then. – Nikerabbit 15:11, 18 September 2009 (UTC)
- How often you run which job is up to you - change it if you like. -- Daniel 10:18, 18 September 2009 (UTC)
- In case of errors it would be nice to have fixes propagated quite fast even if we can't contact anyone from Toolserver side to do this. But this is all hypothetical, I don't know if there is real need for that. – Nikerabbit 15:11, 18 September 2009 (UTC)
Why going via the DB and not comiting back directly into the source SVN? Bryan 21:07, 18 September 2009 (UTC)
- Because that requires interaction from the tool's maintainers. And they tend to be lazy (I'm extremly bad about putting new localizations live myself). And automating it is *not* an option. I don't want anyone writing into my repo, much less updating a live tool's code. -- Daniel 22:05, 18 September 2009 (UTC)