Forum for English speaking Miranda NG users > Localization

Serbian Translation - In Progress

<< < (5/6) > >>

Robyer:
watcher, I see. To provide my points:

1) My way is MUCH easier for translator/maintainer to write and update translation.

* file references are useful way to understand what's being translated and where in code we can found this string. Your way completely removes them even from Untranslated folder which makes generating them completely useless in first place.
* keeping untranslated strings (and empty lines) in same file makes it MUCH easier to use with SVN/Git revision compare, because these strings doesn't jump between files but are still on same line in same file. You can easily spot the useful changes in log ( = changes done in original english translation) and when there are changed only english typos, you can "revert" the translated line (which was correctly translated without typo) with one single click.
* translating inside Untranslated and then copying the content back into translated file is useless and time wasting. Working on same file is better and faster.
* when some user wants to help with translation of single plugin, I can give him link to svn to this partially translated file (with empty lines), then he can fill it and/or fix existing translations and then send it back to me. I can simply replace file on SVN with his file and easily see what he changed, what he translated (blank lines are filled). I don't need to copy his strings manually and refresh langpack and he doesn't need to work on more files.
* when translating, it often contains similar strings like these which are already translated and I can easily see or Find existing translations to compare or inspire me. Also you can see in context of what other translations this untranslated thing is, which is helpful too.
2) These files on SVN aren't and shouldn't be the "clean result". It is the "raw" stuff which gets "compiled" into release clean form and only this is clean result that is being published.

3) You don't need to use translate.js for "compiling" release format, because yeah, it's slow (due to parsing, translating, and doing again). I don't know where/what Mataes' tool is, but it could and should easily provide stripping comments and empty lines from result file and do it very quickly. It doesn't need the already cleaned files (unless it just simple append whole files together).

I recommend to trying to solve issues at correct place. If your problem is that tool you use to generate langpack keeps comments and blank translations, then we should fix that tool. Not the way raw langpack files are saved.

watcher:
Robyer, this is your opinion, i stay with mine, this is how we kept things for years and years before any scripts and our lang was the only one that wasn't abandoned. Let the serbian guy decide how he wants to work. Maybe your way works better for him too - i'm not saying that mine is perfect, this is just how we prefer to do things. Maybe this is harder for rest of the guys, well, than switching to Refresh.bat takes 1 minute  ;D

watcher:
Robyer,  even better way - http://trac.miranda-ng.org/changeset/12447

I provide 2 batch files - one leaves empty lines and references, second do not, so vultures can try both ways, choose the most comfortable one, or even use both  ;D First - generate files with empty lines, translate whatever you want, then use the second batch file to leave it all clean while keeping freshly translated lines  ;D

Robyer:
watcher, yeah, ok, whatever floats his goat  ;D

watcher:
My goat was brutally murdered :(

Navigation

[0] Message Index

[#] Next page

[*] Previous page