[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [babel-dev] translatable string freeze date for all Eclipseprojects
|
Title: Message
I
wholeheartedly agree with Bjorn that community involvement should be a major
objective of Babel. My vision is that text can be translated by end-users
at any time from within the runtime RCP application, even if they don't know
what a Java resource bundle or a plug-in is. End-users may have no idea
which plug-in contributed a piece of text; they just want to translate or
correct the text.
This
is what we have done in our own application, and I have re-packaged the plug-in
so it works with the Eclipse IDE as well as any other RCP application. It
is well past time to get this plug-in contributed to the Babel project. To
get this process moving, I have attached the plug-in, and also some
documentation that I have started to put together. If the concensus is
that this is a direction that Babel should take then I will submit the code to
IPZilla.
I will
be on today's call so hopefully we can include this in the
agenda.
Nigel
Westbury
My thoughts have been a little different:
I see Babel as a way to get the community involved in translations rather than
as a way to provide tools for professional translators. Not that the
professional translators couldn't use the tools, but rather the focus is on
ways to get the community involved. The consequence of "get the community
involved" is that it's unlikely that we'll get 100% translation coverage
before GA. Thus I was working towards NL packs that users can download at any
time. If they download the one on the GA day, they'll get, perhaps 80% of the
strings. If they wait until August, they'll get 90%. And maybe in December
they'll get 98%. Something like that.
- Bjorn
--
[end of
message]
|
Attachment:
org.eclipse.babel.runtime_1.0.0.jar
Description: Binary data
Attachment:
babel-runtime.rtf
Description: Binary data