Re: translations (let's use Transifex or Pootle)

2017-04-28 Thread Thomas Åkesson

> On 16 Mar 2017, at 16:36, Bert Huijben  wrote:
> 
> For some reason Transifex doesn't want me to update Swedish 'sv' resources, 
> but does allow Swedish-Sweden 'sv_SE' rersources.

Strange, they list 'sv' as a supported:
https://www.transifex.com/explore/languages/

Being Swedish I can't think of any reason to disallow 'sv' when accepting for 
example 'de'. 

/Thomas Å. 

RE: translations (let's use Transifex or Pootle)

2017-03-16 Thread Bert Huijben


> -Original Message-
> From: Julian Foad [mailto:jul...@foad.me.uk]
> Sent: vrijdag 10 februari 2017 12:48
> To: Andreas Stieger 
> Cc: Branko Čibej ; dev@subversion.apache.org
> Subject: Re: translations (let's use Transifex or Pootle)
> 
> > Andreas Stieger wrote:
> >> [Pootle] worked sufficiently well for strings that have no special
> >> formatting requirements. It also worked well for out-of-band changes,
> >> e.g. merging items translated locally with those translated in Pootle.
> >>
> >> For anything that includes non-trivial help output and special
> >> formatting, I found it to be cumbersome.
> [...]
> >> You would not use the .pot but the .po, so as to not loose existing
> >> translations.
> >> For other translations: setting them up in Pootle, I did not want to
> >> presume that other po maintainers would want to do that.
> >>
> >> Pootle has automation opportunities of scanning the code base, have not
> >> explored.
> >>
> >> Is that something we want to kick off for the next release?
> 
> Andreas, thanks for your thoughts. It sounds like your overall
> experience of using Pootle was that it was useful but not great.
> 
> Also I see that OpenOffice is the *only* project really using Apache's
> Pootle: other than that and Subversion (German only), there is just
> JMeter (French only) and two projects that have no major activity.
> 
> So the major reason I assumed we should use it -- because I assumed it
> was the standard tool for Apache projects -- evaporates. How about we
> use transifex (https://www.transifex.com/) then, because it's what
> TortoiseSVN is using?

For some initial testing I uploaded the current set of resources on trunk to 
transifex.
They are now available on: 
https://www.transifex.com/apache-subversion/apache-subversion/

Feel free to request an account to play with these.

I'm still working on automating the update system two ways, but for now it 
appears to work... After fixing a few plural form problems in our existing po 
files all languages except Swedish are now stored as they should be.

For some reason Transifex doesn't want me to update Swedish 'sv' resources, but 
does allow Swedish-Sweden 'sv_SE' rersources.

Bert

> 
> Branko Čibej wrote:
> > It wouldn't hurt to bring Subversion into the 20th century, at least as
> > far as translations are concerned. :)
> 
> +1
> 
> > I can help with any scripting but can't promise to lead this effort ...
> > NoTimeTM.
> 
> Thanks! (And me too.)
> 
> - Julian



Re: translations (let's use Transifex or Pootle)

2017-02-10 Thread Julian Foad

Andreas Stieger wrote:

[Pootle] worked sufficiently well for strings that have no special
formatting requirements. It also worked well for out-of-band changes,
e.g. merging items translated locally with those translated in Pootle.

For anything that includes non-trivial help output and special
formatting, I found it to be cumbersome.

[...]

You would not use the .pot but the .po, so as to not loose existing
translations.
For other translations: setting them up in Pootle, I did not want to
presume that other po maintainers would want to do that.

Pootle has automation opportunities of scanning the code base, have not
explored.

Is that something we want to kick off for the next release?


Andreas, thanks for your thoughts. It sounds like your overall 
experience of using Pootle was that it was useful but not great.


Also I see that OpenOffice is the *only* project really using Apache's 
Pootle: other than that and Subversion (German only), there is just 
JMeter (French only) and two projects that have no major activity.


So the major reason I assumed we should use it -- because I assumed it 
was the standard tool for Apache projects -- evaporates. How about we 
use transifex (https://www.transifex.com/) then, because it's what 
TortoiseSVN is using?


Branko Čibej wrote:

It wouldn't hurt to bring Subversion into the 20th century, at least as
far as translations are concerned. :)


+1


I can help with any scripting but can't promise to lead this effort ...
NoTimeTM.


Thanks! (And me too.)

- Julian