Op maandag 19 oktober 2015 01:09:01 schreef Carlos E. R.:
On 2015-10-19 00:24, Freek de Kruijf wrote:
Op zondag 18 oktober 2015 17:50:46 schreef Carlos E. R.:
Then after a few months, Tumbleweed and Leap will diverge, and every month more. We need a separate branch for Leap because if it doesn't exist we can't handle any bugzilla after release.
Not necessary. These texts can be made more general with parameters that represent the distribution or the release version. This last information is already present somewhere in the system
So your idea is to have a generic .pot file with %s all over the place to replace with "Leap" or "TW" at runtime? More work for the developers? Or you propose to run a script to generate both texts, by someone, and then save both texts somewhere, at the SVN or GIT?
Why not then, have two separate files?
You still can have separate files and have these parameter used. So yes it is work for the developers, but it also saves work for the translators. Less items to translate.
What if the marketing team want to create different slide shows for each version, highlighting the advantages of whatever one the user is installing?
And that only covers the slide show.
What about, for instance, the developers adding the switch "--heuristic" for "TW", which is not present in Leap? The help text and the error messages for "TW" would be different than on "Leap". How would you cover that?
That's why different branches for each release are needed.
I am a simpleminded person who suggests simpleminded solutions. No must. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org