openoffice-l10n mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jürgen Schmidt <jogischm...@gmail.com>
Subject Re: first draft of l10n process document.
Date Mon, 15 Oct 2012 08:26:15 GMT
On 10/15/12 10:23 AM, Jürgen Schmidt wrote:
> On 10/15/12 10:10 AM, jan iversen wrote:
>> I totally agree.
>>
>> My document just aims at the ongoing build process for existing languages.
>>
>> For sure I hope that it is not nearly 100% UI changes, hopefully there are
>> nearly just as many help changes, otherwise we are slowly getting a big
>> documentation problem.
>>
>> I will have a new draft ready later today, and find a place to upload it.
>> It is too bad that there are no upload.apache.org for such things (or more
>> importantly for translations).
> 
> committers at Apache have their own directory on people.apache.org where
> it is possible to share such files.
> 
> But I would create a wiki page which is easier to maintain over time and
> where collaboration is easier.

well a reminder that we also have an IRC channel where we can discuss
some things quite fast. The good things with mailing lists is that the
info becomes archived. But to push things forward IRC is often quite useful.

I am on #dev.openoffice.org at freenode

Juergen


> 
> Juergen
> 
>>
>> jan I
>>
>> On 15 October 2012 02:32, Rob Weir <robweir@apache.org> wrote:
>>
>>> On Sun, Oct 14, 2012 at 8:13 PM, Keith N. McKenna
>>> <meriodoc_brandybuck@yahoo.com> wrote:
>>>> Hi Jan;
>>>>
>>>> I suspect that you attached the document to your mail to the list.
>>>> Unfortunately most of the lists strip attachments. The best bet is to
>>> upload
>>>> it to your website or something like sky drive and post a link to it
>>> back to
>>>> the mailing list. I look forward to seeing what you have come up with and
>>>> though I am not a translator, hopefully my process engineering background
>>>> can make some useul comments.
>>>>
>>>
>>> +1.
>>>
>>> And we'll probably need to make some distinction between updating an
>>> existing localization and creating one from scratch.  For a new
>>> localization, like the Uighur one, there are many tasks, from
>>> developing the basic glossary, to translation, but also other aspects
>>> of localization, like collation/sorting order, numeration, decimal
>>> formats, spell checkers, etc.  But updating an existing translation
>>> for a new release is almost 100% UI string translation.  And then
>>> there are the rarer cases of language/spelling reforms such as in
>>> German, which are of intermediate difficulty.  The most common case is
>>> the updated translation, and it might make sense to focus the initial
>>> process documentation on that case.
>>>
>>> -Rob
>>>
>>>> Regards
>>>> Keith
>>>>
>>>> jan iversen wrote:
>>>>
>>>> Hi.
>>>>
>>>> I have just finished the first draft of the l10n process document.
>>>>
>>>> Please feel free to give me feedback, especially on the commands in the
>>>> workflows which I can only hope I have described correctly.
>>>>
>>>> During the next days I will integrate any comments I receive as well as
>>> make
>>>> some extensions to the document like:
>>>>   - Data flow
>>>>   - List of issues
>>>>   - cross check tool and file format list
>>>>
>>>> I will later put it on the wiki server.
>>>>
>>>> have a nice night
>>>>
>>>> --
>>>> Jan Iversen
>>>> ________________________________________________
>>>> Tel. no. +34 622 87 66 19
>>>> jandorte.wordpress.com
>>>>
>>>>
>>>
>>
> 


Mime
View raw message