Front-end translation tool
williamv.anderson
localization could be the perfect project for non-technical end users
to contribute to Sahana but that, as currently configured, the process
is a bit intimidating for the non-technical.
After two quick twitter conversations (one with Eduardo Jezierski of
InSTEDD, the other with Jeff Sonstein-Professor at Rochester Institute
of Technology) we thought an interactive front end translation tool
would be useful and might be accomplished using Grease Monkey. A wiki-
style front end localization tool would allow the translation to be
context aware and provide a lower barrier to entry for the non-
technical. Eduardo suggested looking at Grease Monkey and Jeff added
a reference to Platypus.
Rough cut for basic requirements:
Front end interface that allows double click editing of any text
Supports multiple character sets
Allows the user to save a local copy of the changes that creates a
portable patch copy
What do you think?
-Will
Dominic König
I think such a feature already exists in Sahana (interactive translation, in
Admin->Language/Locale).
Dominic
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups
> "Sahana Localization" group. To post to this group, send email to
> sahana-lo...@googlegroups.com To unsubscribe from this group, send
> email to sahana-localiza...@googlegroups.com For more options,
> visit this group at
> http://groups.google.com/group/sahana-localization?hl=en
> -~----------~----~----~----~------~----~------~--~---
Dominic König
there are in fact multiple ways to contribute to the Sahana translation, even
one similar to what you suggest. In doubt you can do it as you like it, if
only you can provide computer-readable lists of pairs of "Original String"
<-> "Translated String" (except paper-based translations, though).
Using the Pootle server is just one possible way, especially for collaborative
translation, but you can as well use any other tool you want, even your local
Sahana installation itself - just do as follows:
1. Give write permission to your web server to the whole res subdirectory.
2. Start Sahana, go to the Admin menu -> Language/Locale -> Interactive
Translation (this requires the gettext utilities to be installed properly)
3. Follow the instructions shown for this function
4. Extract the PO file in the "Translation" menu
To submit a PO file to the Pootle site (regardless of how you have translated
it), just send it to webm...@nursix.org and comment about its origin. It
will then be merged into the Pootle server files, so that you (or the
translation maintainers) can do further review/correction of the translation.
Please be aware that the existing translation at the Pootle site always has
higher priority than translations submitted from elsewhere (reverse merging).
So if you wish to correct an existing translation, please use the Pootle site
and make your suggestion/overwrite existing translations. If this is to
tricky for you, just contact me to do it for you.
In case anyone wants to send me Sahana translations, he will not necessarily
have to send original Sahana PO files, I can even deal with any
portion/aggregation of PO files, CSV lists, Excel sheets, XML files and other
formats (as long as a Linux desktop system can read it somehow). The only
thing required is that the particular translator registers itself at the
Sahana Localization Group, and the translation is provided in
computer-readable pairs of "Original String" - "Translated String".
Furthermore, I have created some shell scripts to extract any desired portion
of the Sahana UI strings from the sources and create PO templates (and other
list formats) of it - so you can have translation templates for any
modified/customized Sahana version (as long as it uses GNU/gettext for
localization) as well.
I will however take a look at Grease Monkey.
Kind regards,
Dominic
måndag, 22. december 2008 17:45 skrev williamv.anderson:
williamv.anderson
Ahh, I didn't realize I had to enable the write access. I couldn't
figure out why the functionality would be there but not work. Is that
process on the wiki anywhere? I can't seem to find it.
One additional (hopefully non-silly) question. Is there an instance
that's sole purpose is to do in-application translation or should I
set one up for myself?
Thanks,
Will
On Dec 22, 1:23 pm, Dominic König <domi...@nursix.org> wrote:
> Hello Will,
>
> there are in fact multiple ways to contribute to the Sahana translation, even
> one similar to what you suggest. In doubt you can do it as you like it, if
> only you can provide computer-readable lists of pairs of "Original String"
> <-> "Translated String" (except paper-based translations, though).
>
> Using the Pootle server is just one possible way, especially for collaborative
> translation, but you can as well use any other tool you want, even your local
> Sahana installation itself - just do as follows:
>
> 1. Give write permission to your web server to the whole res subdirectory.
> 2. Start Sahana, go to the Admin menu -> Language/Locale -> Interactive
> Translation (this requires the gettext utilities to be installed properly)
> 3. Follow the instructions shown for this function
> 4. Extract the PO file in the "Translation" menu
>
> To submit a PO file to the Pootle site (regardless of how you have translated
> < 1KViewDownload- Hide quoted text -
>
> - Show quoted text -
Dominic König
there are no silly questions ;-)
The interactive translation process is documented on the wiki somewhere, but
not yet on the translation pages - perhaps it should be moved there. I'm a
little short in time right now, so will do it later (or someone else does
it).
I don't know about a public instance for interactive translation, and due to
the necessity of file system write access I would rather suggest that you set
up your own locally.
Kind regards,
thanks for prodding,
Dominic
GlennP
Done, content of Dominic's letter rewritten and added as third section
of http://wiki.sahana.lk/doku.php?id=translate:home
Except I didn't say anything about Grease Monkey or other potential
tools.
Glenn
> < 1KViewDownload
Dominic König
looks good so far.
Glenn - I assigned the StyleGuide issue to you, because I don't have the time
at the moment (because I'm moving to a new residence). Please eliminate the
_t() function from this guide - there are only 4 calls to _t() in the current
release, the whole rest calls _() directly and this is ok.
Furthermore, please correct my english in the translation wiki as necessary
(but keep it as simple as possible).
Kind regards,
and a merry christmas to all,
Dominic
GlennP
I just replaced all _t( ) instances with _( ). BTW, I would like to
encourage people, particularly developers, to look over the style
guide at
http://wiki.sahana.lk/doku.php?id=translate:styleguide .
Just to pose one question that arose: is it better for developers to
use double quotes, e.g. _("..."), or single quotes, e.g., _('...') ?
If we can achieve consensus, then I can rewrite the examples
accordingly.
- Glenn
On Dec 23, 1:51 pm, Dominic König <domi...@nursix.org> wrote:
> Thank you very much,
>
> looks good so far.
>
> Glenn - I assigned the StyleGuide issue to you, because I don't have the time
> at the moment (because I'm moving to a new residence). Please eliminate the
> _t() function from this guide - there are only 4 calls to _t() in the current
> release, the whole rest calls _() directly and this is ok.
>
> Furthermore, please correct my english in the translation wiki as necessary
> (but keep it as simple as possible).
>
> Kind regards,
> and a merry christmas to all,
> Dominic
>
> tisdag, 23. december 2008 19:23 skrev GlennP:
>
> > Done, content of Dominic's letter rewritten and added as third section
> > Except I didn't say anything about Grease Monkey or other potential
> > tools.
> > Glenn
>
>
>
> < 1KViewDownload