Translations

[iPott]

Hi one question... is there the possibility to translate opensync?

if there is no translation... i would like to translate opensync into german.... sorry my english is bad, but i'm better in translation (i have some projects like truecyrpt)

Hi,
> Hi one question... is there the possibility to translate opensync?
>
> if there is no translation... i would like to translate opensync into
> german.... sorry my english is bad, but i'm better in translation (i have
> some projects like truecyrpt)
There is a ticket about translating opensync at
http://opensync.org/ticket/14

HTH
Felix Möller

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Opensync-devel mailing list
Opensync-devel@...
https://lists.sourceforge.net/lists/listinfo/opensync-devel

[Daniel Gollub]

On Friday 25 April 2008 10:43:43 iPott wrote:
> Hi one question... is there the possibility to translate opensync?

Not yet. But there is a very old ticket about this:
http://opensync.org/ticket/14

Maybe it's time to make this finally possibly....

> if there is no translation... i would like to translate opensync into
> german.... sorry my english is bad, but i'm better in translation (i have
> some projects like truecyrpt)

No worry, my English is bad as well.

I wonder if you're familiar with gettext? And could help us in setting this up
for OpenSync

First we would have to setup some i18n like gettext or the wrapper from glib.
Another thing before starting the translation would be to cleanup/rephrase
some of the strings. Since in OpenSync itself it's mostly about error
messages - and most of them are very funny for non OpenSync developer i
guess:

"Failed creating the XSLT context. Run out of memory?"
"This engine was not in state initialized: %i"
"At least one object engine failed within sync_done. Aborting"
"Entries got changed at the same time. Can't decide."
"Unable to find engine which can handle objtype %s"

grep -r osync_error_set opensync/*| grep -v svn | grep OSYNC_ERROR | wc -l
187

grep -r osync_error_set opensync/*| grep -v svn | grep OSYNC_ERROR | uniq |
wc -l
166

Since those strings might appear in UI we should first sum up all those bad
strings and rephrase them. And declare how to rephrase certain internal terms
like "objtype", "engine", "sink", "xmlformat" ...

AFAIK, the only strings we have to look at are in osync_error_set().
osync_trace() is not worth to translate.

Maybe it's also possible to get rid of most error strings, and avoid similar
but different error strings - and replace them by more values of
OSyncErrorType. And have only those OSyncErrorType values one corresponding
error string.


Thoughts?
Volunteers?! ;)

best regards,
Daniel

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Opensync-devel mailing list
Opensync-devel@...
https://lists.sourceforge.net/lists/listinfo/opensync-devel