Re: [libreoffice-l10n] Re: Global site release page and translation

On Sat, Aug 11, 2012 at 5:12 AM, Marc Paré <marc@marcpare.com> wrote:
> Hi Cor and Martin
>
> Le 2012-08-11 04:06, Cor Nouws a écrit :
>
> > Hi Martin,
> >
> > Martin Srebotnjak wrote (11-08-12 09:36)
> > > I am more worried about the procedure of localizing. I had to manually
> > > create this page for Slovenian and to copy and paste the English
> > > content from the live version of the page.
> >
> >
> > I copied the whole html code, saved it local, and added most of the
> > Dutch (privided by some other members) there, then pasted it in the
> > empty Dutch that I made.
> >
> > > Could you not create a translated version of it for those language
> > > sites that want it (and make it invisible for the localization team to
> > > finish it off?
> >
> >
> > Adding to the navigation menu was the last step. Before that, it was not
> > 'visible' ;-)
> >
> > Ciao,
>
> I would imagine that this is what most groups would do (if they find the
> preferences page to their liking). If you are the person maintaining the
> site and translating, then it would be easiest to copy the html code
> directly into your SilverStripe page and then do the translation from the
> English text.
>
> BTW ... you can also publish the page without it appearing in the menu line
> and also turn off the search so that search engines cannot find them -- this
> allows you to have other community members verify the page before adding it
> to the menu line.
>
> As far as creating a translated version, I am not sure how the SilverStripe
> translation would work, but yes, it does look like this could be done for
> individual languages that ask for this ... but ... I think Christian would
> know how this would work (I am copying this to him). Not sure how well it
> would translate the page. Maybe there would be a way to test this.

Marc,

I believe what might help with getting these pages localized would be
an automated workflow that converted the desired text into PO file
format (and back again).  I think this might be what Martin is
referencing when he says "procedure for localizing" and "make it
invisible for the localization team to finish it off".

It would be desirable if something like inlttool

http://freedesktop.org/wiki/Software/intltool/

were employed to offer a method that presented this work in a format
that a localizer would consider properly internationalized (e.g.
produces PO files posted on your Pootle instance that are synched with
templates).  Not every language community is led by an HTML source
hacker or a wiki master.

As an example, the Gnome project uses Mallard and intltool to make it
possible for their language teams to localize the Gnome docs in PO
format.  It is quite enough work for most language teams to perform
the translation without having to master multiple mark-up languages
(i.e. either HTML or wiki).

Do you think it would be possible for the documentation team to
perform the i18n task and take that step to meet the localizer
half-way by providing PO files to work on in Pootle?

cjl

-- 
Unsubscribe instructions: E-mail to l10n+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted