Re: I would like to introduce myself!

Some questions:

– How much effort is it for you to do a test with my file? (… just to get an idea about the amount of work. I don’t want to block your capacities …)

– In which .po file should I make the changes? If I make changes in the .po file which is stored under „S3_0/“, are the changes synced into the other files as well? Or do I have to make the same changes in the files under „S3_1/“ and „S3_2/“? 

– In order to make a build myself, I would need a detailed step-by-step manual. I really don’t know, if someone wants to give me such a crashcourse! Besides, I really don't know if I even want to venture into such uncharted waters! :-) 


- - 
Mathias


> Am 04.03.2022 um 21:05 schrieb Marko Lindqvist <[email protected]>:
> 
> On Thu, 3 Mar 2022 at 21:35, Mathias (GER, Freeciv)
> <[email protected] <mailto:[email protected]>> wrote:
>> 
>> Hi Marko!
>> 
>> Thanks for your answer.
>> 
>> I have downloaded the free version of „Poedit".
>> 
>> I opened the file „de.po“, which I had downloaded from here:
>> http://files.freeciv.org/translations/S3_0/core/
>> 
>> Is that correct so far?
>> 
>> In Poedit, I can see the English texts on the left and the German texts on the right. I did a first test and translated three texts and saved the file.
> 
> If you want to confirm your workflow, you can send your modified
> translation to me for testing.
> 
>> You mentioned, that I could „test your translations in their natural habitat.“ How would I do that? Would I have to download the Freeciv code and somehow „join" it with the new translation?
> 
> That would require getting the latest freeciv source code from git,
> and building freeciv yourself, with your translations included. While
> MacOS is unixy, and one would assume that building freeciv would work
> there as easily as in other such systems, from the reports of some
> users it's not so trivial, and I don't have Mac to experiment myself.
> OTOH: We do have MacOS doing building test for all the changes that
> go in to the codebase for the later development branches (S3_1 &
> master) and the script for making that build doesn't seem to making
> too exotic.
> 
> 
> - ML