Hi Jordi,
I explain how to make my localize.sdf.
Step1. Download zips and Extract zips.
Extract zips which download from Pootle.
+po *** Extract the openoffice_org-ca.zip here ***
+accessibility
+avmedia
+basctl
...(snip)...
+helpcontent2 *** Create this folder ***
+source *** Create this folder ***
+text *** Extract the helpcontent2-ca.zip here
+sbasic
+scalc
...(snip)...
Step2. Download en-US sdf.
Download en-US sdf, from...
http://download.services.openoffice.org/files/extended/ooomisc/sdf/
and extract full_OOO330_m8_2010-09-16_23-41-37.sdf.bz2, to...
+full_OOO330_m8_2010-09-16_23-41-37.sdf *** Extract the bz2 here ***
+po
+accessibility
+avmedia
+basctl
...(snip)...
Step3. Do po2oo.
$ po2oo -l ca -i po -t full_OOO330_m8_2010-09-16_23-41-37.sdf -o localize.sdf
I think that you can get localize.sdf with this procedure.
Please try it. ^-^
> Hi Dick
>Thanks for your explanation. I tried to get the sdf myself to run
>gsicheck again and see if the Catalan files were fixed, but I did not
>succeed to build the sdf.
>I downloaded the English source .sdf file to specify as template, but
>still it did not work for me.
>Probably I didn't put the files in the correct directory structure.
>
>I'm interested in gsichecks rather that pootle checks because, apart
>from the mentioned false positives, its the gsicheck which decides which
>string makes it to the build and which is discarded...
>
>So, will there be a possibility to get another gsicheck report just in
>case there are outstanding errors?
>
>salut
>jordi s
>
>El 17/09/2010 12:39, en/na Dick Groskamp ha escrit:
>> Op 16-9-2010 23:06, Sophie schreef:
>>> Hi Jordi,
>>> Jordi Serratosa wrote:
>>>> Hi Ivo
>>>> I received the gsicheck log and I'll proceed to fix the errors.
>>>> This is the first time I see such log. I guess the check is based on
>>>> the .sdf file (and not .po files), so if we use Pootle for
>>>> translation we cannot run such check.
>>>
>>> You can do this check using Pootle functionnalities.
>> But that will give you a great amount of false positives (for example
>> on XML-tags)
>>>> Anyway, shouldn't this log always be provided before each language
>>>> build? That would be useful.
>>> If you get the .sdf, you can run gsicheck on it.
>> You can make your own SDF I found out yesterday, and in fact it is
>> quiet simple.
>>
>> Download a zip from the Helpciontent from Pootle.
>> Unpack it as it should be so within the directory text and then put
>> that directory into directory source and then put that into directory
>> helpcontent2
>> (that is the way the tree is build onto the real world app OOo, if you
>> don't follow this build-up everything fails in this case)
>>
>> Run po2oo from the Translate Toolkit on the helpcontent2 directory.
>>
>> That will provide you with the necessary sdf-file since it contains
>> the strings from the POOTLE-download.
>>
>> Run that sdf against gsicheck (this way you can check your own
>> translations)
>>>> By the way, the log is for Help. Is the one for UI available?
>>> If you look at the log, most or the errors pointed are because of
>>> closing tags missing or missmatch betweens tag in the source and
>>> target language. These tags are not present in UI, only in HC2, so
>>> there should be nor errors in the UI.
>> You now should also be able to make your own.
>> Same procedure but without oputting it into separate directories.
>> The UI zip unpacks as it is in the tree for OOo.
>>
>> If you should want a complete SDF then you should put helpcontent2
>> between the directories of the UI and then run po2oo.
>>
>> As I said just figured it out yesterday, having the same problem as
>> you with the originating sdf-file.
>>
>> Good luck and greetings from Dutch NL-team
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [email protected]
>For additional commands, e-mail: [email protected]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
