2005/9/17, Gints Polis <[EMAIL PROTECTED]>:
> Konrad Stobiecki wrote:
> 
> >Dnia 17-09-2005, sob o godzinie 13:58 +0400, Rail Aliev napisał(a):
> >
> >
> >>Maybe we really need centralized GSI/SDF/PO file storage? Every l10n
> >>lead can upload/commit files to separate folder. Everybody can download
> >>fresh files, l10n integrators can pull latest translation from that
> >>storage. Something like i18n.kde.org and kde-i18n packages...
> >>
> >>
> >>
> >
> >Personally, I would be 10 times for!
> >It would be a great idea.
> >
> >Konrad
> >
> >
> >
> Count my 10 votes too.  Also if some contries have problems with foreign
> traffic they could have mirror for they module.  But also in this case
> it will make some standart way on how translations made.
> 

When so, it will be a long term project.
In KDE and Gnome po-files are natural part of application source tree
in CVS, in OO.o there are some intermediate steps more. We need a lot
of server side applications for creating sdf-files, then pot-files,
then merging them to po-files, then making sdf again, then checking
syntax, messaging about syntax errors team leads, or last translators,
etc. Sure I forgot many things. :)
Some teams need all the time pot files with all-strings-unique, some
not at all, some after translation in the QA stage (like me).
Pavel has done a lot for making our current translation process
smoother and simpler. It not very complicated process but at moment it
needs a lot of human intervention. I'm agree, that idea is great, but
someone must make this framework real and it is a lot of work too.
Have we people and have they time for this?
Have we idea, how to bind this with existing source maintaining process?
Are we sure, that our current localization methods in general are most
optimal? (See previous threads from this month). Maybe it is not the
time to start building roof having no basement built? :)
These were just simple questions, not retorical ones, therefore maybe
someone can answer them.

-- 
Ain Vagula

Reply via email to