Hi Rafaella,
Rafaella Braconi wrote:
> Hi Sophie,
>>
>> ok, I miss that part. I think that I will write a FAQ for those very
>> important parts that can be forgot from one localization round to
>> another. Do you think it could be useful ? Something like
>> - Do I submit a complete .sdf
>> - To whom do I assign the issue
>> - when do I open an issue
>> - where is gsicheck
>> - is it possible to gsicheck on Pootle
>> - etc.
>>   
> well, we do have already wikis such as
> http://wiki.services.openoffice.org/wiki/Translation_for_3.1
> where you can find information on how to deliver sdf, where to find
> gsicheck ....
> 
> and a checklist:
> http://wiki.services.openoffice.org/wiki/NLC:ReleaseChecklist
> 
> Instead of creating a new one, we could add the missing information or
> even thinking of restructuring the current ones....

Yes, you're right there is already all the needed information. I guess I
need to put some reminders on my own list ;)
>>>>         
>>> Yes, sure. The current process is far from perfect and I'm thankful for
>>> any idea that can help us simplifying it :-)
>>> Just 3 ideas that come into my mind are:
>>>
>>> 1) the sdf file that needs to be corrected is the sdf file which results
>>> out of the gsi check. In order not to have to fix those errors both in
>>> pootle and in the sdf, I would encourage all teams to use the
>>> verification checks in Pootle. And I am sure that we can ask to
>>> customize these checks...
>>>     
>>
>> ok. However under the Chek option in Pootle there is a lot of check that
>> can be made, and some are shown as errors however it's language
>> dependent. What are the most important?
>>   
> the important verification checks are currently reported in the Pootle
> User Guide:
> http://wiki.services.openoffice.org/wiki/Pootle_User_Guide#Verification_checks

Thank you, I missed also this list it seems.

Kind regards
Sophie


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to