Menu
▾
▴
#1159 About "_OBSOLETE" added to some strings in Translation.m
Instead of adding "_OBSOLETE" at the end of string in Translation.m perhaps it would be better jo remove the string.
If not remove the string then perhaps place "OBSOLETE_" at the beginning of the string.
So that when i try to updated a string i dont get to know at the end of the string that i did not needed to update it. If it had say it at the beginning it would be easier to spot.
iirc: the numbers at the beginnnig of each line should stay "fixed" or in "sync" with all other translation files. simply removing them would make it easier to just throw in the next available number and, voila, you have different translations for different things at the same spot.
the currently used translation mechanism is from 16 years ago. and allthough i kind of like the robustness of the .cat files (going with gettext would introduce a new dependency i kind of dislike), i agree it's a major pain in the ass. all the translations are cluttered over a lot of files, it's hare to keep them in sync.
so, maybe one should think about having all the translations in one file ( https://en.wikipedia.org/wiki/XLIFF ), keep all the translations together in that file and create the http://git.fluxbox.org/fluxbox.git/tree/nls/fluxbox-nls.hh file + the .cat files out of it. similar to how the documentation is created right now: change the asciidoc based documents now and then, also create the manpages out of it and commit it into .git as well (so noone uninterested in the translation process needs to have those tools as a build-time dependency).