Re: Translation problem

The problem with Rosetta is that it frequently results in a duplication
of effort, and it is very difficult to integrate existing translations
into the system. They also are not contributed upstream in a very
useable manner, or so I've heard. I have also inquired about this, and
this was the response I received. At the moment, the easiest way (and
really, the only recommended way) to localize AbiWord is to find a PO
editing program (this is a standard translation format) and edit these
files. Testing the translation requires running a script in the AbiWord
source tree to convert the PO file, which is translated, to the strings
files actually used by AbiWord during runtime.

Please use the PO files available from the AbiSource web site to
localize, rather than Launchpad/Rosetta. Thanks!

Fabian Rodriguez wrote:
> Renato Pavičić wrote:
>
>> Hi all,
>> [...]
>>
>> This is the reason why I started to localize Opera. It took me 2
>> minutes from import to the translation of the first line! Without any
>> programming knowledge, additional instalations, setups and without
>> days lost in studying programmers instructions. And, WITH my old
>> database! And, with import and export!
>>
>> I have greatest respect for programmers. They do something that I do
>> not know how to. But please, if I could have at least the same ammount
>> of _understanding_ !
>>
>
>
> Hello,
>
> I am new around, lurking for the past few days.
>
> I was wondering if Rosetta/Launchpad is being used for translations ?
> I'd say that would be pretty easy for any translator to use, although
> perhaps not as fast as other tools. I see the Croatian translation there
> is at 0%:
> https://launchpad.net/products/abiword/+translations
>
> Are the other translations there used at all in Abiword ?
>
> Cheers,
>
> Fabian Rodriguez
> Montreal, QC, Canada
>
>

-- 
Ryan Pavlik
AbiWord Win32 Platform Maintainer
www.abisource.com
"Optimism is the father that leads to achievement." - Helen Keller