Re: Refresh Pootle for Translation 4.2

[Andrea Pescetti]

Mechtilde wrote:

as already wrote, I try to work on translation update.
Now I could get an actual *.sdf file from source code.


Thanks, Mechtilde! Could you please start from my notes at 
https://s.apache.org/Dukc and copy them to a wiki page (or, if you don't 
like wiki, to a text file to be then copied to a wiki page) so that you 
can take advantage of what I already wrote and fix it?



After preparing a build directory there I could start localize successful.


OK, so for example my item 1 from the link above
   ---
1. A full checkout of trunk; I believe some of the tools are built
during the build process, but I'm using a fully built tree anyway.
   ---
should be improved to say that you don't actually need a full build (but 
you still need to initialize the build process).



I could also create *.pot file with oo2po from *.sdf file. There I get
many *.pot files in different directories.


I assume you will be looking at German with more attention, right? I 
recommend to just start with one language, since having all SDF files is 
useless anyway (Pootle has only a selection of languages).


Once we get a few languages working, generalizing won't be hard.


Now I downloaded a *.zip file from Pootle with the previous German
translation. Must I do it for every language manually? How can I do it
effectivly?


I would suggest this: do the same steps as I did for French and 
Portuguese in the discussion above. Let's check if we get to the same 
conclusions, i.e., that Pootle is in a bad state that does not 
correspond to any release.



Then I can look for the next steps.


Please note that, as I wrote, we need to go the opposite direction: from 
Pootle to SDF. But we need to re-learn both flows, so it's really good 
if you repeat all the process from my earlier notes.


So your next major steps would be:
- Exporting German from Pootle (not to Pootle) and build 4.1.6 (not 
4.2.0) based on it
- Understanding the "malformed string" error messages when doing the 
above and their impact on the resulting build; this is where I stopped 
on 31 Dec last year, and I think nobody has done further work ever since.


Regards,
  Andrea.

-
To unsubscribe, e-mail: l10n-unsubscr...@openoffice.apache.org
For additional commands, e-mail: l10n-h...@openoffice.apache.org

Re: Refresh Pootle for Translation 4.2

[Mechtilde]

Hello,

as already wrote, I try to work on translation update.

Now I could get an actual *.sdf file from source code.

After preparing a build directory there I could start localize successful.

I could also create *.pot file with oo2po from *.sdf file. There I get
many *.pot files in different directories.

Now I downloaded a *.zip file from Pootle with the previous German
translation. Must I do it for every language manually? How can I do it
effectivly?

Then I can look for the next steps.

Please help!

Kind regards

-- 
Mechtilde Stehmann
## Apache OpenOffice
## Freie Office Suite für Linux, MacOSX, Windows
## Debian Developer
## Loook, calender-exchange-provider, libreoffice-canzeley-client
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F



signature.asc
Description: OpenPGP digital signature

Re: Refresh Pootle for Translation 4.2

[Dick Groskamp]

Op 13-11-2018 om 13:48 schreef Mechtilde:

Hello Dick,

the solution is more easier.

you have to prepare a build without doing "build --all".

Esp. you have to do configure and bootstrap - then it works.

Kind regards

Am 13.11.18 um 13:34 schrieb Dick Groskamp:

Mechtilde,

[cut]

Kind regards


Good for you !

Good luck on the further path to new sdf's


--
DiGro
___
Apache OpenOffice 4.1.5 (Dutch) and scanned with Ziggo Safe Online (F-Secure)


-
To unsubscribe, e-mail: l10n-unsubscr...@openoffice.apache.org
For additional commands, e-mail: l10n-h...@openoffice.apache.org

Re: Refresh Pootle for Translation 4.2

[Matthias Seidel]

Hi Mechtilde,

Am 13.11.18 um 13:48 schrieb Mechtilde:
> Hello Dick,
>
> the solution is more easier.
>
> you have to prepare a build without doing "build --all".
>
> Esp. you have to do configure and bootstrap - then it works.

Maybe configure and bootstrap isn't even needed, but it doesn't hurt. ;-)

Glad, that it works for you now...

Regards,

   Matthias

>
> Kind regards
>
> Am 13.11.18 um 13:34 schrieb Dick Groskamp:
>> Mechtilde,
>>
>> I'v also been searching for setsolar and I suspect it has to do with a
>> variable in the configure (whatever that may be :-)  )
>>
>> In /main should be a file named "set_soenv" I suspect it means "set
>> solar environment"
>> It is mentioned in the Building guide in the paragraph Building:
>>
>> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO
>> ""
>>
>> Start by including the environment variables prepared by configure into
>> your current environment with
>>
>>   source 
>>
>> where  depends on your platform:
>>
>> platform id 
>> wntmsci12 winenv.set.sh
>> unxlngi6 LinuxX86Env.Set.sh
>> unxlngx6 LinuxX86-64Env.Set.sh
>> unxmacci MacOSXX64Env.Set.sh
>>
>> Look into main/set_soenv for more platforms. (search for lines |$OUTPATH
>> = "";| and the nearby line |$outfile =
>> "";|. Add the suffix |.sh| for the bash variant.""
>>
>> Found an old reference to set_soenv in :
>>
>> Old Building_Guide/Building_on_Windows
>> 
>>
>>
>> ""If you experiment with the newest sources, mind that it can happen
>> sometimes that |configure.in| was updated, but it was forgotten to
>> update configure too. The configure script itself is created from
>> |configure.in| using the |autoreconf| command. The perl script
>> |set_soenv| is created when you run configure from |set_soenv.in|.""
>>
>> Hope this helps somehow
>>
>> Op 12-11-2018 om 21:19 schreef Mechtilde:
>>> Hello
>>>
>>> Am 11.11.18 um 09:37 schrieb Mechtilde:
 Hello,

 after doing a successful building of Apache OpenOffice I want to help
 working on a better translation (process)

 My first problem is to extract an actual SDF Template

 I followed the intructions in the wiki and the slides from FOSDEM 2018.
 No success.

 localize -e -l en-US -f en-US.sdf

 I execute it in  and get the message bash: localize: command
 not found

 Are there some requirements to install?
>>> I did some further search for "setsolar" and found that it must be a
>>> function of Visual Studio.
>>>
>>> Does someone use Visual Studio for building and can provide an actual
>>> *.sdf file.
>>>
>>> Kind regards
>>>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Refresh Pootle for Translation 4.2

[Mechtilde]

Hello Dick,

the solution is more easier.

you have to prepare a build without doing "build --all".

Esp. you have to do configure and bootstrap - then it works.

Kind regards

Am 13.11.18 um 13:34 schrieb Dick Groskamp:
> Mechtilde,
> 
> I'v also been searching for setsolar and I suspect it has to do with a
> variable in the configure (whatever that may be :-)  )
> 
> In /main should be a file named "set_soenv" I suspect it means "set
> solar environment"
> It is mentioned in the Building guide in the paragraph Building:
> 
> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO
> ""
> 
> Start by including the environment variables prepared by configure into
> your current environment with
> 
>   source 
> 
> where  depends on your platform:
> 
> platform id 
> wntmsci12 winenv.set.sh
> unxlngi6 LinuxX86Env.Set.sh
> unxlngx6 LinuxX86-64Env.Set.sh
> unxmacci MacOSXX64Env.Set.sh
> 
> Look into main/set_soenv for more platforms. (search for lines |$OUTPATH
> = "";| and the nearby line |$outfile =
> "";|. Add the suffix |.sh| for the bash variant.""
> 
> Found an old reference to set_soenv in :
> 
> Old Building_Guide/Building_on_Windows
> 
> 
> 
> ""If you experiment with the newest sources, mind that it can happen
> sometimes that |configure.in| was updated, but it was forgotten to
> update configure too. The configure script itself is created from
> |configure.in| using the |autoreconf| command. The perl script
> |set_soenv| is created when you run configure from |set_soenv.in|.""
> 
> Hope this helps somehow
> 
> Op 12-11-2018 om 21:19 schreef Mechtilde:
>> Hello
>>
>> Am 11.11.18 um 09:37 schrieb Mechtilde:
>>> Hello,
>>>
>>> after doing a successful building of Apache OpenOffice I want to help
>>> working on a better translation (process)
>>>
>>> My first problem is to extract an actual SDF Template
>>>
>>> I followed the intructions in the wiki and the slides from FOSDEM 2018.
>>> No success.
>>>
>>> localize -e -l en-US -f en-US.sdf
>>>
>>> I execute it in  and get the message bash: localize: command
>>> not found
>>>
>>> Are there some requirements to install?
>> I did some further search for "setsolar" and found that it must be a
>> function of Visual Studio.
>>
>> Does someone use Visual Studio for building and can provide an actual
>> *.sdf file.
>>
>> Kind regards
>>

-- 
Mechtilde Stehmann
## Apache OpenOffice
## Freie Office Suite für Linux, MacOSX, Windows
## Debian Developer
## Loook, calender-exchange-provider, libreoffice-canzeley-client
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F



signature.asc
Description: OpenPGP digital signature

Re: Refresh Pootle for Translation 4.2

[Dick Groskamp]

Mechtilde,

I'v also been searching for setsolar and I suspect it has to do with a 
variable in the configure (whatever that may be :-)  )


In /main should be a file named "set_soenv" I suspect it means "set 
solar environment"

It is mentioned in the Building guide in the paragraph Building:

https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO
""

Start by including the environment variables prepared by configure into 
your current environment with


  source 

where  depends on your platform:

platform id 
wntmsci12   winenv.set.sh
unxlngi6LinuxX86Env.Set.sh
unxlngx6LinuxX86-64Env.Set.sh
unxmacciMacOSXX64Env.Set.sh

Look into main/set_soenv for more platforms. (search for lines |$OUTPATH 
= "";| and the nearby line |$outfile = 
"";|. Add the suffix |.sh| for the bash variant.""


Found an old reference to set_soenv in :

Old Building_Guide/Building_on_Windows 



""If you experiment with the newest sources, mind that it can happen 
sometimes that |configure.in| was updated, but it was forgotten to 
update configure too. The configure script itself is created from 
|configure.in| using the |autoreconf| command. The perl script 
|set_soenv| is created when you run configure from |set_soenv.in|.""


Hope this helps somehow

Op 12-11-2018 om 21:19 schreef Mechtilde:

Hello

Am 11.11.18 um 09:37 schrieb Mechtilde:

Hello,

after doing a successful building of Apache OpenOffice I want to help
working on a better translation (process)

My first problem is to extract an actual SDF Template

I followed the intructions in the wiki and the slides from FOSDEM 2018.
No success.

localize -e -l en-US -f en-US.sdf

I execute it in  and get the message bash: localize: command not found

Are there some requirements to install?

I did some further search for "setsolar" and found that it must be a
function of Visual Studio.

Does someone use Visual Studio for building and can provide an actual
*.sdf file.

Kind regards


--
DiGro
___
Apache OpenOffice 4.1.5 (Dutch) and scanned with Ziggo Safe Online (F-Secure)