Hi Alberto,
there is no policy that requires a minimum amount of translated strings,
if you think you have something to integrate, then feel free to submit.
But keep in mind that the integration causes work, I propose that you
don't send me a file that is not yet worth.
The question is:
-How much percent have been translation in the Jambo OpenOffice 1.1.3 ?
-Do you only migrate the 1.1.3 release or also did some translation work ?
As most UI moved into the officecfg xml files you should at least
translate that module, or the users see a English office with Swahili
dialogs ;)
Cheers,
Ivo
Alberto Escudero wrote:
Hi Ivo,
Long time no hear. I have migrated our translation of Jambo
OpenOffice.org (1.1.3) to OOo 2.0 m118, i think i will be able to
migrate the translation to OOo 2.0 m121 before the deadline. The SDF
will be uncompleted by the Writer will be almost complete.
Some stats of the migration from 1.1.x to 2.0 m118 are here
http://www.it46.se/downloads/migration/migration_stats_m118.html
A OOo policy question:
- Do you rather get a full SDF for 2.0.1? or want to integrate the
existing/migrated one anyway?
/aep
Hi all,
The OOo 2.0 release is coming closer and there are new or changed
strings in the source code since the last l10n collection, what was
arround milestone m104 . Those new / changed strings force us to collect
another time, but this is also a chance for you to submit latest
corrections and updates.
The deadline for providing GSI / SDF files is 2005/08/05
Please update to milestone m121, because that milestone contains a new
readme section.
As handling full gsi files will cause work and consume a lot of time, it
would be perfect if you can provide me with a difference between your
previous submissing and your current sdf file ,so the provided file is a
smaller. I don't mean a patch, but a file only containing new / updated
strings. If this don't work for you, because you provided me with a ftp
link to a constantly updated file or you are unfamiliar with unix tools
and don't know how to create such a file, just provide me with your full
sdf file. No problem.
And as usual please:
- File an issuezilla bug to me ( [EMAIL PROTECTED] ). Please don't
attach your file directly to that issue, better provide a URL / link
pointing to your file. Only attach if you don't have any webspace available.
( http://qa.openoffice.org/issue_handling/project_issues.html )
- Please take care that the GSI / SDF file format is not violated (
format errors like wrong amount of tabs, shifted columns, ... ). You can
use the tool "gsicheck" to perform basic checks on your file. "gsicheck"
is located in the transex3 module.
usage: gsicheck -c -l "" myfile.sdf
- We try to correctly update our database status information which would
later help to improve the overall quality of the translation. If
possible please provide a GSI / SDF file containing both, your language
and the corresponding en-US source string. This is only nice to have and
not (yet) required ! Please note that the en-US string have to be the
same milestone like your translation.
Cheers,
Ivo
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
