From: mose <mo...@ti...> - 2004-10-24 13:40:14
|
le Sun, Oct 24, 2004 at 09:13:25AM -0400 par Sylvie Greverend : > My concern about moving existing code to the mods is the lost of the > translated strings. > Has something being done about this? How do you organize translated strings > in mods? For the moment I have the impression that > mods is an English feature. I think there is no sense to put the mods > strings in language.php, It will slow down an already slow process. > FOr instance tikisheet, now, the translated strings will go in the unused > strings and at the first cleaning they will be lost. - yes there is something to do there, and optimaly mods should be able to embed their own translation, and in the same context been available to transversal transaltion without running everywhere to find things to be translated. The get_strings file is already a huge and powerful tool, and it needs an evolution to be able to : * collect strings from mods and detect those strings come from mods. * split the language file in parts for embeding in the mods distribution system, maybe by reading the mods control files to get the list of what file is used in what mod. Maybe the split can be done by an extra arg, so the file that holds all translation can still be unique for translation comfort. Not sure what could be the best. * modification of the language inclusion system for including not only the language.php that is in lang/fr/ for example, but all *.language.php (or any conventional way, maybe *.lang.php) that are present in that dir, and merge the $language array. The order of array merge can be an issue, as some strings can be used in more than one place. Another similar work is needed for styles, to modularize it properly (by the use of @import and mini-css declaration). Help and ideas are welcome. Ideas are not readable by apache, and usually are only useful if delivered with effective code, but that language evolution is a huge things that could deserve some talking. cheers, mose |