7 Nov
2007
7 Nov
'07
4:27 p.m.
Hi Timo,
(.)
Another advantage of Marc's solution is that it
would make it possible to
compile only those languages that you want. If you
don't want a translation
for some languages, switch them off in the
config.rbuild.
Exacly . that's one of the planed features , if you take a look at my branch
you will see I introduced a new element "language" that complements the also
new "localization" element we are discussing. The "language" element
is used
to explicitly declare what languages is reactos available (meaning at least
one rc is available somewhere in that language) , this functionality is
required to validate the "isoname" attribute on "localization"
elements but
also in the future to fill part of the languages information on txtsetup.sif
(see http://www.reactos.org/bugzilla/show_bug.cgi?id=2635) . so you will be
able to just comment the languages you don't want to include in the build in
languages.rbuild (see
http://svn.reactos.org/svn/reactos/branches/rbuild/reactos/languages.rbuild?
revision=30209
<http://svn.reactos.org/svn/reactos/branches/rbuild/reactos/languages.rbuild
?revision=30209&view=markup> &view=markup ) and apart from not being
compiled and included in your OS image they will disappear from setup
automatically.
Regards,
/Marc
Colin Finck schrieb:
The open question would be: What happens with the already planned/prepared
online translation service?
It also had a plan to improve the whole translation process, but as far as I
know it differs much from your solution.
Klemens, Magnus, any comments on this?
Regards,
Colin