Hi Ivo,
I want to discuss inclusion of Serbian translation of OpenOffice.org
2.0. We're doing it using PO files, and I'm creating SDF file for my
translators. We're already at 90% of the UI translation with only
officecfg and instsetoo_native unfinished (not counting helpcontent,
which we haven't tackled just yet). We'll certainly have this
complete by August 5th.
"We" here is mostly Serbian Gnome translation team (I'm the
coordinator), with one member (co-coordinator) of Serbian
KDE translation team (both Gnome and KDE have complete Serbian
translations for two years now). I have experience with all l10n and
i18n stuff, having done sr_CS locales for GNU libc, sr keyboard
layouts for X11, worked on fonts such as DejaVu, gsfonts/urwcyr,
FreeFont and done a lot of translations.
I have talked to Branko Tanovic (sr.openoffice.org maintainer and team
leader: [EMAIL PROTECTED]) on the phone, and he's agreed that we can
take over the translation since he's currently overwhelmed with work
and can't dedicate much time to this.
If I understood correctly, I need to take the following steps:
- get all (five or six of them) translators to sign
http://www.openoffice.org/licenses/jca.pdf
and fax and snail-mail this to you: can I send scans over e-mail
instead of faxing (it would be much cheaper for me)?
- submit SDF file to you (I've put current, m121-based version at
http://prevod.org/ftp/oo/sr-CS.sdf.bz2)
- look over anything else there is (locales, font defaults,...)
Cheers,
Danilo
Last Friday at 15:29, Ivo Hinkelmann wrote:
> 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]
