You are viewing a plain text version of this content. The canonical link for it is here.
Posted to l10n@openoffice.apache.org by jan iversen <ja...@gmail.com> on 2012/10/15 01:17:59 UTC

first draft of l10n process document.

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

Re: first draft of l10n process document.

Posted by Alexandro Colorado <jz...@oooes.org>.
On 10/15/12, jan iversen <ja...@gmail.com> wrote:
> I give in...I will do the rest in wiki :-)
>
> I have a lot at flow diagrams in my document (easy done with draw), and
> that seems quite difficult in mediaWiki, but I will find a way.

Is only a matter of upload and link to the images:
http://www.mediawiki.org/wiki/Images#Format

We use a very conservative editor, not sure if we want to upgrade to a
more feature rich one like FckEditor, EtherEditor or fancy Ajax-Inline
editors. But usually this community has been very conservative and
happy with the default settings.

Here is more information on external editors for graphics and text:
http://www.mediawiki.org/wiki/Manual:External_editors

and on Feature rich web editors (on the latest version of Mediawiki):
http://www.mediawiki.org/wiki/Extension:WikiEditor

>
> By the way, the documentation says that there is a 4 day blocking before I
> can add pages, that might be the reason why the "new page" button is
> nowhere to find.
>
> rgds.
> Jan I
>
> On 15 October 2012 18:52, Alexandro Colorado <jz...@oooes.org> wrote:
>
>> On Mon, Oct 15, 2012 at 4:01 AM, jan iversen <jancasacondor@gmail.com
>> >wrote:
>>
>> > so you are saying, that I should simply do so much qualified work that
>> the
>> > committers get tired of committing my work, and vote me in as a
>> > committer
>> > :-)
>> >
>> > time will show...!!!
>> >
>> > I have created a wiki account, and are able to edit pages, I have
>> installed
>> > the mediaWiki extension to openOffice, but it cannot upload the page,
>> > it
>> > says my user is not known. Do you know if that a real problem, or am I
>> > doing something wrong ?
>> >
>>
>> Most people simply just work within the wiki, is not a pre-requisite to
>> edit the OpenOffice wiki with OpenOffice. That said, I think is a good
>> testing practice, in case something in mediawiki changes and break the
>> extension.
>>
>> But I am not sure how reliable is to use it in the long road specially
>> with
>> multiple edits and access to history and other matters. Also there is
>> certain convention on the wiki that is good to follow like Categories,
>> and
>> subfolders. Formating is not such a big deal, but you might want to read
>> the Mediawiki help page every now and then.
>>
>> The localization page was unique since it used it's Category page as its
>> main page, this makes it somewhat easier to locate its content related
>> pages. Most other project has a main page and could work within a
>> subfolder
>> (usually is just a prefix to your page). Is another way of encapsulating
>> the content, like JA/MainPage as opposed to JA_MainPage. Even in the past
>> most editors didnt make much use of this way of working and "commited to
>> root".
>>
>> Also there is the issue of hyperlinking, since inside project links are
>> usually just relative links and its convention is different from external
>> links. OpenOffice wont help you locating other wikipages.
>>
>> So yeah is a bit unpractical, so you might want to try to do it within
>> Mediawiki.
>>
>>
>> >
>> > jan I
>> >
>> > On 15 October 2012 10:23, Jürgen Schmidt <jo...@gmail.com> 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.orgwhere
>> > > 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.
>> > >
>> > > Juergen
>> > >
>> > > >
>> > > > jan I
>> > > >
>> > > > On 15 October 2012 02:32, Rob Weir <ro...@apache.org> wrote:
>> > > >
>> > > >> On Sun, Oct 14, 2012 at 8:13 PM, Keith N. McKenna
>> > > >> <me...@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
>> > > >>>
>> > > >>>
>> > > >>
>> > > >
>> > >
>> >
>>
>


-- 
Alexandro Colorado
PPMC Apache OpenOffice
http://es.openoffice.org

Re: first draft of l10n process document.

Posted by jan iversen <ja...@gmail.com>.
I give in...I will do the rest in wiki :-)

I have a lot at flow diagrams in my document (easy done with draw), and
that seems quite difficult in mediaWiki, but I will find a way.

By the way, the documentation says that there is a 4 day blocking before I
can add pages, that might be the reason why the "new page" button is
nowhere to find.

rgds.
Jan I

On 15 October 2012 18:52, Alexandro Colorado <jz...@oooes.org> wrote:

> On Mon, Oct 15, 2012 at 4:01 AM, jan iversen <jancasacondor@gmail.com
> >wrote:
>
> > so you are saying, that I should simply do so much qualified work that
> the
> > committers get tired of committing my work, and vote me in as a committer
> > :-)
> >
> > time will show...!!!
> >
> > I have created a wiki account, and are able to edit pages, I have
> installed
> > the mediaWiki extension to openOffice, but it cannot upload the page, it
> > says my user is not known. Do you know if that a real problem, or am I
> > doing something wrong ?
> >
>
> Most people simply just work within the wiki, is not a pre-requisite to
> edit the OpenOffice wiki with OpenOffice. That said, I think is a good
> testing practice, in case something in mediawiki changes and break the
> extension.
>
> But I am not sure how reliable is to use it in the long road specially with
> multiple edits and access to history and other matters. Also there is
> certain convention on the wiki that is good to follow like Categories, and
> subfolders. Formating is not such a big deal, but you might want to read
> the Mediawiki help page every now and then.
>
> The localization page was unique since it used it's Category page as its
> main page, this makes it somewhat easier to locate its content related
> pages. Most other project has a main page and could work within a subfolder
> (usually is just a prefix to your page). Is another way of encapsulating
> the content, like JA/MainPage as opposed to JA_MainPage. Even in the past
> most editors didnt make much use of this way of working and "commited to
> root".
>
> Also there is the issue of hyperlinking, since inside project links are
> usually just relative links and its convention is different from external
> links. OpenOffice wont help you locating other wikipages.
>
> So yeah is a bit unpractical, so you might want to try to do it within
> Mediawiki.
>
>
> >
> > jan I
> >
> > On 15 October 2012 10:23, Jürgen Schmidt <jo...@gmail.com> 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.orgwhere
> > > 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.
> > >
> > > Juergen
> > >
> > > >
> > > > jan I
> > > >
> > > > On 15 October 2012 02:32, Rob Weir <ro...@apache.org> wrote:
> > > >
> > > >> On Sun, Oct 14, 2012 at 8:13 PM, Keith N. McKenna
> > > >> <me...@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
> > > >>>
> > > >>>
> > > >>
> > > >
> > >
> >
>

Re: first draft of l10n process document.

Posted by Alexandro Colorado <jz...@oooes.org>.
On Mon, Oct 15, 2012 at 4:01 AM, jan iversen <ja...@gmail.com>wrote:

> so you are saying, that I should simply do so much qualified work that the
> committers get tired of committing my work, and vote me in as a committer
> :-)
>
> time will show...!!!
>
> I have created a wiki account, and are able to edit pages, I have installed
> the mediaWiki extension to openOffice, but it cannot upload the page, it
> says my user is not known. Do you know if that a real problem, or am I
> doing something wrong ?
>

Most people simply just work within the wiki, is not a pre-requisite to
edit the OpenOffice wiki with OpenOffice. That said, I think is a good
testing practice, in case something in mediawiki changes and break the
extension.

But I am not sure how reliable is to use it in the long road specially with
multiple edits and access to history and other matters. Also there is
certain convention on the wiki that is good to follow like Categories, and
subfolders. Formating is not such a big deal, but you might want to read
the Mediawiki help page every now and then.

The localization page was unique since it used it's Category page as its
main page, this makes it somewhat easier to locate its content related
pages. Most other project has a main page and could work within a subfolder
(usually is just a prefix to your page). Is another way of encapsulating
the content, like JA/MainPage as opposed to JA_MainPage. Even in the past
most editors didnt make much use of this way of working and "commited to
root".

Also there is the issue of hyperlinking, since inside project links are
usually just relative links and its convention is different from external
links. OpenOffice wont help you locating other wikipages.

So yeah is a bit unpractical, so you might want to try to do it within
Mediawiki.


>
> jan I
>
> On 15 October 2012 10:23, Jürgen Schmidt <jo...@gmail.com> 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.
> >
> > Juergen
> >
> > >
> > > jan I
> > >
> > > On 15 October 2012 02:32, Rob Weir <ro...@apache.org> wrote:
> > >
> > >> On Sun, Oct 14, 2012 at 8:13 PM, Keith N. McKenna
> > >> <me...@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
> > >>>
> > >>>
> > >>
> > >
> >
>



-- 
Alexandro Colorado
PPMC Apache OpenOffice
http://es.openoffice.org

Re: first draft of l10n process document.

Posted by jan iversen <ja...@gmail.com>.
so you are saying, that I should simply do so much qualified work that the
committers get tired of committing my work, and vote me in as a committer
:-)

time will show...!!!

I have created a wiki account, and are able to edit pages, I have installed
the mediaWiki extension to openOffice, but it cannot upload the page, it
says my user is not known. Do you know if that a real problem, or am I
doing something wrong ?

jan I

On 15 October 2012 10:23, Jürgen Schmidt <jo...@gmail.com> 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.
>
> Juergen
>
> >
> > jan I
> >
> > On 15 October 2012 02:32, Rob Weir <ro...@apache.org> wrote:
> >
> >> On Sun, Oct 14, 2012 at 8:13 PM, Keith N. McKenna
> >> <me...@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
> >>>
> >>>
> >>
> >
>

Re: first draft of l10n process document.

Posted by Jürgen Schmidt <jo...@gmail.com>.
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 <ro...@apache.org> wrote:
>>
>>> On Sun, Oct 14, 2012 at 8:13 PM, Keith N. McKenna
>>> <me...@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
>>>>
>>>>
>>>
>>
> 


Re: first draft of l10n process document.

Posted by Jürgen Schmidt <jo...@gmail.com>.
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.

Juergen

> 
> jan I
> 
> On 15 October 2012 02:32, Rob Weir <ro...@apache.org> wrote:
> 
>> On Sun, Oct 14, 2012 at 8:13 PM, Keith N. McKenna
>> <me...@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
>>>
>>>
>>
> 


Re: first draft of l10n process document.

Posted by jan iversen <ja...@gmail.com>.
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).

jan I

On 15 October 2012 02:32, Rob Weir <ro...@apache.org> wrote:

> On Sun, Oct 14, 2012 at 8:13 PM, Keith N. McKenna
> <me...@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
> >
> >
>

Re: first draft of l10n process document.

Posted by Rob Weir <ro...@apache.org>.
On Sun, Oct 14, 2012 at 8:13 PM, Keith N. McKenna
<me...@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
>
>

Re: first draft of l10n process document.

Posted by "Keith N. McKenna" <me...@yahoo.com>.
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.

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 <http://jandorte.wordpress.com>
>