ODK Aggregate uses GWT 2.5.x for its web page rendering. At the time we
began development, internationalization support was not yet built into GWT.
It now is ( http://www.gwtproject.org/doc/latest/DevGuideI18n.html ).
However, to enable it, we would need a developer to go through the client
code and extract the display strings into a translatable-strings dictionary
and make the simple changes to the code to access that dictionary for the
display string.
We lack the resources to do this at this time. If anyone has a strong
desire for this, and can contribute a developer's time to sift through the
code and extract the translatable strings, we'd be happy to begin
supporting internationalized ODK Aggregate web pages.
···
----------------------
I don't know what would be necessary for ODK Build (I'm not familiar with
that tool or the internationalization support available).
Not sure what you are asking, but to reiterate what Mitch said...
Since you are a developer, you can go through the client code and
extract the display strings into a translatable-strings dictionary and
make the simple changes to the code to access that dictionary for the
display string. http://www.gwtproject.org/doc/latest/DevGuideI18n.html
will help with this.
I was not sure if I need to open an issue, or I if I should clone and
submit a pull request.
Thanks for your help.
Josemando
···
On Thu, Aug 15, 2013 at 11:31 AM, Yaw Anokwa wrote:
Jose,
Not sure what you are asking, but to reiterate what Mitch said...
Since you are a developer, you can go through the client code and
extract the display strings into a translatable-strings dictionary and
make the simple changes to the code to access that dictionary for the
display string. http://www.gwtproject.org/doc/latest/DevGuideI18n.html
will help with this.
[attempting to switch this thread to the -developers list]
Create a public clone on the googlecode site.
When you have changes that should be merged back, tag the check-in of your
googlecode clone that should be examined, and create an issue with the tag
to be merged.
Prod me if it sits idle.
Please make the changes on the ui_experiment branch.
It will make merges easier for us.
Note that the Maven scripts on that branch use updated GAE libraries. Your
.m2/settings.xml will need to be updated with the corresponding gae sdk
path.
In many cases, the exceptions that are thrown are displayed directly to the
user ( e.toString() ). I would leave these as-is during your first pass
through the code.
If you want to tackle these later, we will need to add an coded prefix
(e.g., 'ERR-102') to yield errors like (e.g., 'ERR-102 Bad credentials -
OAuth2 credentials are invalid when publishing to Google Fusion Tables')
so that we can understand screen shots showing a translation of those
errors.
If you reach a point where there is no obvious choice for how to proceed
with i18n, we can set up a Skype chat to discuss what you've found and what
the tradeoffs are.
Mitch
···
On Thu, Aug 15, 2013 at 10:46 AM, Josemando Sobral wrote:
Yaw,
I was not sure if I need to open an issue, or I if I should clone and
submit a pull request.
Thanks for your help.
Not sure what you are asking, but to reiterate what Mitch said...
Since you are a developer, you can go through the client code and
extract the display strings into a translatable-strings dictionary and
make the simple changes to the code to access that dictionary for the
display string. http://www.gwtproject.org/doc/latest/DevGuideI18n.html
will help with this.