Re: Translation of Subversion
Karol Szkudlarek wrote on 2018-06-14: > Dear Julian, > > Unfortunately I am unable to continue work for Subversion as a polish > language translator. Thank you for letting me know. I have moved your name to the 'dormant' section of the 'COMMITTERS' file, in r1833511, so you will no longer receive requests to update the translation. Thank you for your work on this in the past. - Julian > As always Subversion is a great tool! > > Thanks and regards, Karol Szkudlarek > > > W dniu 09.02.2018 o 17:21, Julian Foad pisze: >> You are receiving this mail because you are listed as a translator in >> the Subversion COMMITTERS file[1]. [...] If you have no >> intention of continuing to maintain the translation of Subversion, >> we're sorry to see you go, but respect your decision. Please let us >> know so we may recruit other volunteers to continue the maintenance of >> your translation.
Re: Translation of Subversion
6 mars 2018 kl. 14.00 skrev Julian Foad :
>
> > What really needs to be done to make life for translators somewhat bearable
> > is to split the long strings into individual paragraphs; this is standard
> > practice. Right now, even if only a single word has changed in the
> > documentation of "svn merge", for example, all we are told is that
> > something in this 300-line string has changed. One ends up having to go
> > back to the source code and spend quite some time to figure out what part
> > needs updating.
>
> Yes please let's fix this. I am happy to do the grunt work if that helps. Can
> you figure out how to rewrite the source? Try it (if you are able to compile
> and test) or find docs or examples? I could figure it out if necessary but
> would really like some help.
>
> My first guess is
> _("paragraph1 line1\n"
> "paragraph1 line2\n"
> "\n")
> _("paragraph2 line1\n")
Static string concatenation won't work; the strings need to be looked up
separately. This usually means that what was a single string before now becomes
an array of strings.
Thus, instead of
N_("paragraph 1 line 1\n"
"paragraph 1 line 2\n"
"\n"
"paragraph 2 line 1\n"
"paragraph 2 line 2\n")
we would have
{N_("paragraph 1 line 1\n"
"paragraph 1 line 2\n"),
N_("paragraph 2 line 1\n"
"paragraph 2 line 2\n"),
NULL}
assuming the strings are static initialisers. The blank line separating the
paragraphs can either be included in the paragraph strings or be emitted by the
code that translates and prints them.
Re: Translation of Subversion
On 09.02.2018 17:21, Julian Foad wrote: Hello Translators! You are receiving this mail because you are listed as a translator in the Subversion COMMITTERS file[1]. I'm writing on behalf of the Subversion developers to let you know that we're getting close to wrapping up development for Subversion 1.10, and we would like to encourage you to update the translation of Subversion you have volunteered to maintain. The current translation status on trunk is: Translation status report for trunk@r1823672 lang trans untrans fuzzy obs -- de3072 308 248 542 +UU~~~ es2390 990 970 528 UUU~~~ooo fr2713 667 692 124 +++U~~ it225311271047 347 +++UUUoo ja2394 9861031 766 UUo ko2539 841 811 225 ++UU~~o nb2443 937 925 503 +UU~~~ooo pl2479 901 907 306 +UU~~~oo pt_BR222311571101 323 ++oo sv2889 491 555 112 ++UUU~ zh_CN2829 551 599 53 +~ zh_TW216312171135 379 ++oo As you can see, some translations are more complete than others, but all need some work to prepare for the release. If you have no intention of continuing to maintain the translation of Subversion, we're sorry to see you go, but respect your decision. Please let us know so we may recruit other volunteers to continue the maintenance of your translation. What happened to https://www.transifex.com/apache-subversion/apache-subversion/ or https://translate.apache.org/projects/Subversion/ ? I've tried to join on transifex when it was set up, but never got accepted. The state on translate.apache.org only lists one language and is way out of date so I didn't try to join there... Stefan
