I did not delete in HU or CZ - only made new translations with previously 0%
and I did not delete untranslated strings
with transifex you must distinguish between files for translation and files for use
files for use contain english-english for non-translated
files for translation contain english-empty for non-translated
if you use the original files from the latest trunk, you have a file for use - so english-english, which are mostly commented with double slash at start of the line
so when I start a new language to first import into transifex, I open lang/XY/language.php
delete everything between $lang = array( and );
and paste the result from Calc
Then I have a clean file in transifex with only translated strings english-translated + english-empty and the percentage is matching the reality
if I do not do this way, but instead would just paste the original "for use" version (without deleting // lines) I'd have 99% for German, French, Italian, etc., but most of the strings in fact translated english-english, what we do not want
I made the fault first and just wondered why we have IT, FR and DE all 99%
So I looked into it and figered the above out
If you download HU and CZ "for translatione" you will see !
you will have nearly no english-empty but a lot of english-english besides a few english hungarian or english-czech
so lets say we switch to transifex, than this script needs to update only the english languages, which then gets updated automatically in transifex
i think i need to wrtie this down on a wikipage
I think, all files are compared to the base file which is English-English in our case (the top in the list with logically 100%
would be great if you write it down
just at the very first openingof a new language - if we have an existing non-empty file in our Tiki code - we have to do the sort and delete with Calc or Excel
I'll do that with japanes and korean later aswell - it is just sort, delete, use the rest. no need to understand the language itself, once the encoding (unicode) is alright
gezza next thing:
we should take care to use the right (in Tiki commonly used) languages first
example: German we use (and translated so far) mainly German de, Not German (Germany) de_DE
same with French
in the German Language Tiki User Group there is nobody translating or caring about country specific German variations, so we should use the general version and only this one in Transifex
same for French and others
Hungarian (Hungary) you know better ... are there different variations used and which one is generally used in other software or in Tiki?
the workflow needs some thinking
how do new strings get into transifex?
and how do the translations go back into svn
i think there is no way to edit the translations files directly and commit, all must go through transifex
maybe you restart - create hu and use the existing hu from trunk => then filter and delete * // english-english * and then put the result into Transifex
I think the workflow to SVN or maybe in future GIT is not the major thing, as with Transifex a larger number of people has access to the translated files - could become a subresponsibility of a then larger release team
I do not see a problem to download and commit a language once it got added another 10%
the problem would be how to merge, in case People would commit to SVN aswell
but I can imagine, that Transifex could handle doubling of lines
then I'd need only a local shell script to delete all lines starting with // and batch rename them to the Transifex naming
upload there
download for "use variations" and recommit
OK ... the more often and the more languages, the more we'd need kind of an API to handle automatisation
or we remove all the other translations from the codebase and keep it transifex
and deploy them only at release time
so there is no chance for a conflict
i think wee need to use the demo infrastructure for various releases
ahhaaaha no, many of us run sites directly from the versioning system - no point to not having the lang files there
svn (or maybe future git) must be complete
maybe Tikis online translation could be helpful together with Transifex, when a nice coordianated workflow is in place
I am thinking about some combination
right now there is no easy way to figure out where online translated strings (with Tiki own tool) go to
Yes gezza, I did see this, I know the guy (did chat with him frequently) and did import to the dev version
let's think => I see a string or a few untranslated in my Tiki => I online translate this directly in my own Tiki => I copy the result from the resulting file, maybe accessible from my Tiki webinterface (tiki-admin.php?page=i18n => I login to Transifex, download the "for translation" version of my language, simply add my strings, save and upload back to transifex. ... later every Xhours or days this will be
autocommitted to the Tiki's versioning system
loooool
changing Tiki's feature's names to comply with a companies individual setup
that is funny
they just need to label their menu items and use mainly wikipages instead of admin views of galleries and trackers
I'll answer him
they should get a consultant
instead of "contributing" a change of naming "file galleries" to "form", just because they store downloadable forms in the file galleries
what if you start to store not only forms, but aswell images
find images in the feature "forms" ?
oh I'll write him that ...
good luck with redoing your hungarian translation which will then leave only CZ near 100%
we need to inform Luci before he starts over to translate strings (which then caused a lot of extra work for him)