[RELEASE]: new languages for AOO 3.4.1

[Jürgen Schmidt <jo...@gmail.com>]

Hi,

we all know that the number of volunteers helping with translation is
growing and we would like to make new languages as soon as possible
available. This is important for two reason, first to make AOO available
in further languages to reach more users. Second to show our volunteers
that their work is appreciated and become integrated as soon as
possible. We don't have a well defined process for doing it at moment
but we will find a working way that will be ok for all of us. And we can
improve it over time when see demand for changes or improvements, means
we don't have to find a 100% perfect solution from the beginning.

The most important part is how we do the naming of the different parts
of such a release.

I see two different scenarios:

1. Only new languages, no bugfixes, no other code changes
We add the new languages on top of the existing AOO34 branch, build the
office with the new languages and release the new languages as
convenience binary packages. We also build a new src release package and
add the revision number in the name to identify a respin of the orginal
3.4.1.

For example: aoo-3.4.1-rev1372282-src.tar.bz2

This new src release becomes the default for 3.4.1 because it is a
respin only (no functional changes)

The revision number is part of the about dialog as well and it is
possible to identify the respin.


2. New languages + bug-fixes or security fixes
The micro number will be increased and we do a normal release cycle.
The src release will contain the revision number in future always.



Concrete proposal for 3.4.1 and new languages:

1. set a deadline for new translations, for exmaple December 31, 2012
2. integrate the new languages and provide the builds until January 10, 2013
3. test and verify the new language builds asap
4. release the new languages at the end of January


Why a deadline until December:
The reason is quite simply, we have 22 languages with an UI coverage of
more than 95% (ok Turkish 93%). My plan is to prepare a blog entry and
call again for volunteers for these languages where the effort is
moderate. My hope is that we can integrate a few of the important ones.

UI coverage with more than 93%
==============================
100%: Danish
98%: Korean, Polish, Asturian, Uighur, Icelandic, Indonesian, Welsh,
Catalan, Bulgarian, Latvian
97%: Greek, Basque
96%: English (South Africa)
95%: Portuguese, Swedish, Marathi, Kannada, Gujarati, Irish, Oriya
93%: Turkish


Juergen

Fwd: [RELEASE]: new languages for AOO 3.4.1

[Rob Weir <ro...@apache.org>]

Hello Dhrubajyoti,

I am forwarding your note to our Localization mailing list.   I urge
you to subscribe to that list by sending an email to
L10n-subscribe@openoffice.apache.org.

We have a partial Assamese translation -- 85% complete -- so if you
have some additional volunteers it should be possible to complete the
translation quickly.

Some more information on translation is here:
http://incubator.apache.org/openofficeorg/translate.html

We can discuss more how to get started on the L10n list.

Regards,

-Rob

---------- Forwarded message ----------
From: Dhrubajyoti Gogoi <dh...@gmail.com>
Date: Sun, Nov 25, 2012 at 3:12 AM
Subject: Re: [RELEASE]: new languages for AOO 3.4.1
To: dev@openoffice.apache.org


I would like to add support for Assamese language. It is widely used in the
state of Assam, India. Please guide me the steps on how to get it started.
I have a couple of willing volunteers.

On 24 November 2012 04:51, Kay Schenk <ka...@gmail.com> wrote:

> On Fri, Nov 23, 2012 at 12:39 AM, Jürgen Schmidt <jo...@gmail.com>
> wrote:
> > Hi,
> >
> > we all know that the number of volunteers helping with translation is
> > growing and we would like to make new languages as soon as possible
> > available. This is important for two reason, first to make AOO available
> > in further languages to reach more users. Second to show our volunteers
> > that their work is appreciated and become integrated as soon as
> > possible. We don't have a well defined process for doing it at moment
> > but we will find a working way that will be ok for all of us. And we can
> > improve it over time when see demand for changes or improvements, means
> > we don't have to find a 100% perfect solution from the beginning.
> >
> > The most important part is how we do the naming of the different parts
> > of such a release.
> >
> > I see two different scenarios:
> >
> > 1. Only new languages, no bugfixes, no other code changes
> > We add the new languages on top of the existing AOO34 branch, build the
> > office with the new languages and release the new languages as
> > convenience binary packages. We also build a new src release package and
> > add the revision number in the name to identify a respin of the orginal
> > 3.4.1.
> >
> > For example: aoo-3.4.1-rev1372282-src.tar.bz2
> >
> > This new src release becomes the default for 3.4.1 because it is a
> > respin only (no functional changes)
> >
> > The revision number is part of the about dialog as well and it is
> > possible to identify the respin.
> >
> >
> > 2. New languages + bug-fixes or security fixes
> > The micro number will be increased and we do a normal release cycle.
> > The src release will contain the revision number in future always.
>
> If we have outstanding security fixes, I would favor #2. Thus we would
> release 3.4.2 I guess.
>
> >
> >
> >
> > Concrete proposal for 3.4.1 and new languages:
> >
> > 1. set a deadline for new translations, for exmaple December 31, 2012
> > 2. integrate the new languages and provide the builds until January 10,
> 2013
> > 3. test and verify the new language builds asap
> > 4. release the new languages at the end of January
> >
> >
> > Why a deadline until December:
> > The reason is quite simply, we have 22 languages with an UI coverage of
> > more than 95% (ok Turkish 93%). My plan is to prepare a blog entry and
> > call again for volunteers for these languages where the effort is
> > moderate. My hope is that we can integrate a few of the important ones.
> >
> > UI coverage with more than 93%
> > ==============================
> > 100%: Danish
> > 98%: Korean, Polish, Asturian, Uighur, Icelandic, Indonesian, Welsh,
> > Catalan, Bulgarian, Latvian
> > 97%: Greek, Basque
> > 96%: English (South Africa)
> > 95%: Portuguese, Swedish, Marathi, Kannada, Gujarati, Irish, Oriya
> > 93%: Turkish
> >
> >
> > Juergen
>
>
>
> --
>
> ----------------------------------------------------------------------------------------
> MzK
>
> “How wrong is it for a woman to expect the man to build the world
>  she wants, rather than to create it herself?”
>
>      -- Anais Nin
>

Fwd: [RELEASE]: new languages for AOO 3.4.1

[Rob Weir <ro...@apache.org>]

Hello Dhrubajyoti,

I am forwarding your note to our Localization mailing list.   I urge
you to subscribe to that list by sending an email to
L10n-subscribe@openoffice.apache.org.

We have a partial Assamese translation -- 85% complete -- so if you
have some additional volunteers it should be possible to complete the
translation quickly.

Some more information on translation is here:
http://incubator.apache.org/openofficeorg/translate.html

We can discuss more how to get started on the L10n list.

Regards,

-Rob

---------- Forwarded message ----------
From: Dhrubajyoti Gogoi <dh...@gmail.com>
Date: Sun, Nov 25, 2012 at 3:12 AM
Subject: Re: [RELEASE]: new languages for AOO 3.4.1
To: dev@openoffice.apache.org


I would like to add support for Assamese language. It is widely used in the
state of Assam, India. Please guide me the steps on how to get it started.
I have a couple of willing volunteers.

On 24 November 2012 04:51, Kay Schenk <ka...@gmail.com> wrote:

> On Fri, Nov 23, 2012 at 12:39 AM, Jürgen Schmidt <jo...@gmail.com>
> wrote:
> > Hi,
> >
> > we all know that the number of volunteers helping with translation is
> > growing and we would like to make new languages as soon as possible
> > available. This is important for two reason, first to make AOO available
> > in further languages to reach more users. Second to show our volunteers
> > that their work is appreciated and become integrated as soon as
> > possible. We don't have a well defined process for doing it at moment
> > but we will find a working way that will be ok for all of us. And we can
> > improve it over time when see demand for changes or improvements, means
> > we don't have to find a 100% perfect solution from the beginning.
> >
> > The most important part is how we do the naming of the different parts
> > of such a release.
> >
> > I see two different scenarios:
> >
> > 1. Only new languages, no bugfixes, no other code changes
> > We add the new languages on top of the existing AOO34 branch, build the
> > office with the new languages and release the new languages as
> > convenience binary packages. We also build a new src release package and
> > add the revision number in the name to identify a respin of the orginal
> > 3.4.1.
> >
> > For example: aoo-3.4.1-rev1372282-src.tar.bz2
> >
> > This new src release becomes the default for 3.4.1 because it is a
> > respin only (no functional changes)
> >
> > The revision number is part of the about dialog as well and it is
> > possible to identify the respin.
> >
> >
> > 2. New languages + bug-fixes or security fixes
> > The micro number will be increased and we do a normal release cycle.
> > The src release will contain the revision number in future always.
>
> If we have outstanding security fixes, I would favor #2. Thus we would
> release 3.4.2 I guess.
>
> >
> >
> >
> > Concrete proposal for 3.4.1 and new languages:
> >
> > 1. set a deadline for new translations, for exmaple December 31, 2012
> > 2. integrate the new languages and provide the builds until January 10,
> 2013
> > 3. test and verify the new language builds asap
> > 4. release the new languages at the end of January
> >
> >
> > Why a deadline until December:
> > The reason is quite simply, we have 22 languages with an UI coverage of
> > more than 95% (ok Turkish 93%). My plan is to prepare a blog entry and
> > call again for volunteers for these languages where the effort is
> > moderate. My hope is that we can integrate a few of the important ones.
> >
> > UI coverage with more than 93%
> > ==============================
> > 100%: Danish
> > 98%: Korean, Polish, Asturian, Uighur, Icelandic, Indonesian, Welsh,
> > Catalan, Bulgarian, Latvian
> > 97%: Greek, Basque
> > 96%: English (South Africa)
> > 95%: Portuguese, Swedish, Marathi, Kannada, Gujarati, Irish, Oriya
> > 93%: Turkish
> >
> >
> > Juergen
>
>
>
> --
>
> ----------------------------------------------------------------------------------------
> MzK
>
> “How wrong is it for a woman to expect the man to build the world
>  she wants, rather than to create it herself?”
>
>      -- Anais Nin
>

Re: [RELEASE]: new languages for AOO 3.4.1

[Dhrubajyoti Gogoi <dh...@gmail.com>]

I would like to add support for Assamese language. It is widely used in the
state of Assam, India. Please guide me the steps on how to get it started.
I have a couple of willing volunteers.

On 24 November 2012 04:51, Kay Schenk <ka...@gmail.com> wrote:

> On Fri, Nov 23, 2012 at 12:39 AM, Jürgen Schmidt <jo...@gmail.com>
> wrote:
> > Hi,
> >
> > we all know that the number of volunteers helping with translation is
> > growing and we would like to make new languages as soon as possible
> > available. This is important for two reason, first to make AOO available
> > in further languages to reach more users. Second to show our volunteers
> > that their work is appreciated and become integrated as soon as
> > possible. We don't have a well defined process for doing it at moment
> > but we will find a working way that will be ok for all of us. And we can
> > improve it over time when see demand for changes or improvements, means
> > we don't have to find a 100% perfect solution from the beginning.
> >
> > The most important part is how we do the naming of the different parts
> > of such a release.
> >
> > I see two different scenarios:
> >
> > 1. Only new languages, no bugfixes, no other code changes
> > We add the new languages on top of the existing AOO34 branch, build the
> > office with the new languages and release the new languages as
> > convenience binary packages. We also build a new src release package and
> > add the revision number in the name to identify a respin of the orginal
> > 3.4.1.
> >
> > For example: aoo-3.4.1-rev1372282-src.tar.bz2
> >
> > This new src release becomes the default for 3.4.1 because it is a
> > respin only (no functional changes)
> >
> > The revision number is part of the about dialog as well and it is
> > possible to identify the respin.
> >
> >
> > 2. New languages + bug-fixes or security fixes
> > The micro number will be increased and we do a normal release cycle.
> > The src release will contain the revision number in future always.
>
> If we have outstanding security fixes, I would favor #2. Thus we would
> release 3.4.2 I guess.
>
> >
> >
> >
> > Concrete proposal for 3.4.1 and new languages:
> >
> > 1. set a deadline for new translations, for exmaple December 31, 2012
> > 2. integrate the new languages and provide the builds until January 10,
> 2013
> > 3. test and verify the new language builds asap
> > 4. release the new languages at the end of January
> >
> >
> > Why a deadline until December:
> > The reason is quite simply, we have 22 languages with an UI coverage of
> > more than 95% (ok Turkish 93%). My plan is to prepare a blog entry and
> > call again for volunteers for these languages where the effort is
> > moderate. My hope is that we can integrate a few of the important ones.
> >
> > UI coverage with more than 93%
> > ==============================
> > 100%: Danish
> > 98%: Korean, Polish, Asturian, Uighur, Icelandic, Indonesian, Welsh,
> > Catalan, Bulgarian, Latvian
> > 97%: Greek, Basque
> > 96%: English (South Africa)
> > 95%: Portuguese, Swedish, Marathi, Kannada, Gujarati, Irish, Oriya
> > 93%: Turkish
> >
> >
> > Juergen
>
>
>
> --
>
> ----------------------------------------------------------------------------------------
> MzK
>
> “How wrong is it for a woman to expect the man to build the world
>  she wants, rather than to create it herself?”
>
>      -- Anais Nin
>

Re: [RELEASE]: new languages for AOO 3.4.1

[Kay Schenk <ka...@gmail.com>]

On Fri, Nov 23, 2012 at 12:39 AM, Jürgen Schmidt <jo...@gmail.com> wrote:
> Hi,
>
> we all know that the number of volunteers helping with translation is
> growing and we would like to make new languages as soon as possible
> available. This is important for two reason, first to make AOO available
> in further languages to reach more users. Second to show our volunteers
> that their work is appreciated and become integrated as soon as
> possible. We don't have a well defined process for doing it at moment
> but we will find a working way that will be ok for all of us. And we can
> improve it over time when see demand for changes or improvements, means
> we don't have to find a 100% perfect solution from the beginning.
>
> The most important part is how we do the naming of the different parts
> of such a release.
>
> I see two different scenarios:
>
> 1. Only new languages, no bugfixes, no other code changes
> We add the new languages on top of the existing AOO34 branch, build the
> office with the new languages and release the new languages as
> convenience binary packages. We also build a new src release package and
> add the revision number in the name to identify a respin of the orginal
> 3.4.1.
>
> For example: aoo-3.4.1-rev1372282-src.tar.bz2
>
> This new src release becomes the default for 3.4.1 because it is a
> respin only (no functional changes)
>
> The revision number is part of the about dialog as well and it is
> possible to identify the respin.
>
>
> 2. New languages + bug-fixes or security fixes
> The micro number will be increased and we do a normal release cycle.
> The src release will contain the revision number in future always.

If we have outstanding security fixes, I would favor #2. Thus we would
release 3.4.2 I guess.

>
>
>
> Concrete proposal for 3.4.1 and new languages:
>
> 1. set a deadline for new translations, for exmaple December 31, 2012
> 2. integrate the new languages and provide the builds until January 10, 2013
> 3. test and verify the new language builds asap
> 4. release the new languages at the end of January
>
>
> Why a deadline until December:
> The reason is quite simply, we have 22 languages with an UI coverage of
> more than 95% (ok Turkish 93%). My plan is to prepare a blog entry and
> call again for volunteers for these languages where the effort is
> moderate. My hope is that we can integrate a few of the important ones.
>
> UI coverage with more than 93%
> ==============================
> 100%: Danish
> 98%: Korean, Polish, Asturian, Uighur, Icelandic, Indonesian, Welsh,
> Catalan, Bulgarian, Latvian
> 97%: Greek, Basque
> 96%: English (South Africa)
> 95%: Portuguese, Swedish, Marathi, Kannada, Gujarati, Irish, Oriya
> 93%: Turkish
>
>
> Juergen



-- 
----------------------------------------------------------------------------------------
MzK

“How wrong is it for a woman to expect the man to build the world
 she wants, rather than to create it herself?”

     -- Anais Nin

Re: [RELEASE]: new languages for AOO 3.4.1

[jan iversen <ja...@apache.org>]

On 23 November 2012 09:39, Jürgen Schmidt <jo...@gmail.com> wrote:

> Hi,
>
> we all know that the number of volunteers helping with translation is
> growing and we would like to make new languages as soon as possible
> available. This is important for two reason, first to make AOO available
> in further languages to reach more users. Second to show our volunteers
> that their work is appreciated and become integrated as soon as
> possible. We don't have a well defined process for doing it at moment
> but we will find a working way that will be ok for all of us. And we can
> improve it over time when see demand for changes or improvements, means
> we don't have to find a 100% perfect solution from the beginning.
>
> The most important part is how we do the naming of the different parts
> of such a release.
>
> I see two different scenarios:
>
> 1. Only new languages, no bugfixes, no other code changes
> We add the new languages on top of the existing AOO34 branch, build the
> office with the new languages and release the new languages as
> convenience binary packages. We also build a new src release package and
> add the revision number in the name to identify a respin of the orginal
> 3.4.1.
>
> For example: aoo-3.4.1-rev1372282-src.tar.bz2
>
> This new src release becomes the default for 3.4.1 because it is a
> respin only (no functional changes)
>
> The revision number is part of the about dialog as well and it is
> possible to identify the respin.
>
+1 I would favour this version, because it is the least amount of work, and
we can use the resources to focus on the next major release.

I assume, that we will not only provide source, but also binaries.


>
>
> 2. New languages + bug-fixes or security fixes
> The micro number will be increased and we do a normal release cycle.
> The src release will contain the revision number in future always.
>
>
>
> Concrete proposal for 3.4.1 and new languages:
>
> 1. set a deadline for new translations, for exmaple December 31, 2012
>
1a QA the translations (by local translators, and e.g. pootle review)

> 2. integrate the new languages and provide the builds until January 10,
> 2013
> 3. test and verify the new language builds asap
>
3a QA the build with local translators

> 4. release the new languages at the end of January
>

Since the release does not include formal testing, I would like to have the
QA steps, so it is apparent to everybody that translation itself is only
part of the whole.

>
>
> Why a deadline until December:
> The reason is quite simply, we have 22 languages with an UI coverage of
> more than 95% (ok Turkish 93%). My plan is to prepare a blog entry and
> call again for volunteers for these languages where the effort is
> moderate. My hope is that we can integrate a few of the important ones.
>
> UI coverage with more than 93%
> ==============================
> 100%: Danish
> 98%: Korean, Polish, Asturian, Uighur, Icelandic, Indonesian, Welsh,
> Catalan, Bulgarian, Latvian
> 97%: Greek, Basque
> 96%: English (South Africa)
> 95%: Portuguese, Swedish, Marathi, Kannada, Gujarati, Irish, Oriya
> 93%: Turkish
>
Sounds like a lot of movements in the po files, If you need help with
managing just tell me.


>
>
> Juergen
>

Re: [RELEASE]: new languages for AOO 3.4.1

[Rob Weir <ro...@apache.org>]

On Sun, Nov 25, 2012 at 8:45 PM, 胡其图 <hu...@163.com> wrote:
> Hi there,
> I am a mongolian where living in inner mongolia, china. and I want to build a traditional mongolian AOO if it possible.
> and I know there have a slav mongolian AOO, but this is not similar to traditional mongolian.
> tell me how to add about a language for traditional mongolian?
>

The first step is to join our localization mailing list by sending an
email to L10n-subscribe@openoffice.apache.org.  This will generate a
confirmation email that you will need to respond to.

As you mention, we have a Cyrillic/Mongolian translation of OpenOffice
3.0.0, but no traditional Mongolian translation.

Starting a new translation is a lot of work, but is manageable if you
can find some other volunteers to help.

But a linguistics question for you:  Is traditional Mongolian just a
change of script compared to the Cyrillic script?  If so, is it
possible to transform the scripts from one to another by a program,
and then clean up the results?  I've seen this done for Traditional
versus Simplified Chinese, for example.  Or will this require a
complete new translation?

If you start from scratch, then the translation/localization
considerations include:

1) Develop a glossary of common terminology related to the application
and the user interface.  This helps ensure consistency.

2) Translate the user interface

3) In-product localization, for things like calendar systems, counting
conventions for numbered lists, etc.

4) Creating a spell checking dictionary

5) Translation of help files

As you see, this is a big effort, but it can be very rewarding.

Are you able to find other Mongolian volunteers to help with this?

Regards,

-Rob

>
>
>
>
>
>
>
> At 2012-11-23 16:39:46,"Jürgen Schmidt" <jo...@gmail.com> wrote:
>>Hi,
>>
>>we all know that the number of volunteers helping with translation is
>>growing and we would like to make new languages as soon as possible
>>available. This is important for two reason, first to make AOO available
>>in further languages to reach more users. Second to show our volunteers
>>that their work is appreciated and become integrated as soon as
>>possible. We don't have a well defined process for doing it at moment
>>but we will find a working way that will be ok for all of us. And we can
>>improve it over time when see demand for changes or improvements, means
>>we don't have to find a 100% perfect solution from the beginning.
>>
>>The most important part is how we do the naming of the different parts
>>of such a release.
>>
>>I see two different scenarios:
>>
>>1. Only new languages, no bugfixes, no other code changes
>>We add the new languages on top of the existing AOO34 branch, build the
>>office with the new languages and release the new languages as
>>convenience binary packages. We also build a new src release package and
>>add the revision number in the name to identify a respin of the orginal
>>3.4.1.
>>
>>For example: aoo-3.4.1-rev1372282-src.tar.bz2
>>
>>This new src release becomes the default for 3.4.1 because it is a
>>respin only (no functional changes)
>>
>>The revision number is part of the about dialog as well and it is
>>possible to identify the respin.
>>
>>
>>2. New languages + bug-fixes or security fixes
>>The micro number will be increased and we do a normal release cycle.
>>The src release will contain the revision number in future always.
>>
>>
>>
>>Concrete proposal for 3.4.1 and new languages:
>>
>>1. set a deadline for new translations, for exmaple December 31, 2012
>>2. integrate the new languages and provide the builds until January 10, 2013
>>3. test and verify the new language builds asap
>>4. release the new languages at the end of January
>>
>>
>>Why a deadline until December:
>>The reason is quite simply, we have 22 languages with an UI coverage of
>>more than 95% (ok Turkish 93%). My plan is to prepare a blog entry and
>>call again for volunteers for these languages where the effort is
>>moderate. My hope is that we can integrate a few of the important ones.
>>
>>UI coverage with more than 93%
>>==============================
>>100%: Danish
>>98%: Korean, Polish, Asturian, Uighur, Icelandic, Indonesian, Welsh,
>>Catalan, Bulgarian, Latvian
>>97%: Greek, Basque
>>96%: English (South Africa)
>>95%: Portuguese, Swedish, Marathi, Kannada, Gujarati, Irish, Oriya
>>93%: Turkish
>>
>>
>>Juergen

Re: [RELEASE]: new languages for AOO 3.4.1

[Rob Weir <ro...@apache.org>]

On Sun, Nov 25, 2012 at 8:45 PM, 胡其图 <hu...@163.com> wrote:
> Hi there,
> I am a mongolian where living in inner mongolia, china. and I want to build a traditional mongolian AOO if it possible.
> and I know there have a slav mongolian AOO, but this is not similar to traditional mongolian.
> tell me how to add about a language for traditional mongolian?
>

The first step is to join our localization mailing list by sending an
email to L10n-subscribe@openoffice.apache.org.  This will generate a
confirmation email that you will need to respond to.

As you mention, we have a Cyrillic/Mongolian translation of OpenOffice
3.0.0, but no traditional Mongolian translation.

Starting a new translation is a lot of work, but is manageable if you
can find some other volunteers to help.

But a linguistics question for you:  Is traditional Mongolian just a
change of script compared to the Cyrillic script?  If so, is it
possible to transform the scripts from one to another by a program,
and then clean up the results?  I've seen this done for Traditional
versus Simplified Chinese, for example.  Or will this require a
complete new translation?

If you start from scratch, then the translation/localization
considerations include:

1) Develop a glossary of common terminology related to the application
and the user interface.  This helps ensure consistency.

2) Translate the user interface

3) In-product localization, for things like calendar systems, counting
conventions for numbered lists, etc.

4) Creating a spell checking dictionary

5) Translation of help files

As you see, this is a big effort, but it can be very rewarding.

Are you able to find other Mongolian volunteers to help with this?

Regards,

-Rob

>
>
>
>
>
>
>
> At 2012-11-23 16:39:46,"Jürgen Schmidt" <jo...@gmail.com> wrote:
>>Hi,
>>
>>we all know that the number of volunteers helping with translation is
>>growing and we would like to make new languages as soon as possible
>>available. This is important for two reason, first to make AOO available
>>in further languages to reach more users. Second to show our volunteers
>>that their work is appreciated and become integrated as soon as
>>possible. We don't have a well defined process for doing it at moment
>>but we will find a working way that will be ok for all of us. And we can
>>improve it over time when see demand for changes or improvements, means
>>we don't have to find a 100% perfect solution from the beginning.
>>
>>The most important part is how we do the naming of the different parts
>>of such a release.
>>
>>I see two different scenarios:
>>
>>1. Only new languages, no bugfixes, no other code changes
>>We add the new languages on top of the existing AOO34 branch, build the
>>office with the new languages and release the new languages as
>>convenience binary packages. We also build a new src release package and
>>add the revision number in the name to identify a respin of the orginal
>>3.4.1.
>>
>>For example: aoo-3.4.1-rev1372282-src.tar.bz2
>>
>>This new src release becomes the default for 3.4.1 because it is a
>>respin only (no functional changes)
>>
>>The revision number is part of the about dialog as well and it is
>>possible to identify the respin.
>>
>>
>>2. New languages + bug-fixes or security fixes
>>The micro number will be increased and we do a normal release cycle.
>>The src release will contain the revision number in future always.
>>
>>
>>
>>Concrete proposal for 3.4.1 and new languages:
>>
>>1. set a deadline for new translations, for exmaple December 31, 2012
>>2. integrate the new languages and provide the builds until January 10, 2013
>>3. test and verify the new language builds asap
>>4. release the new languages at the end of January
>>
>>
>>Why a deadline until December:
>>The reason is quite simply, we have 22 languages with an UI coverage of
>>more than 95% (ok Turkish 93%). My plan is to prepare a blog entry and
>>call again for volunteers for these languages where the effort is
>>moderate. My hope is that we can integrate a few of the important ones.
>>
>>UI coverage with more than 93%
>>==============================
>>100%: Danish
>>98%: Korean, Polish, Asturian, Uighur, Icelandic, Indonesian, Welsh,
>>Catalan, Bulgarian, Latvian
>>97%: Greek, Basque
>>96%: English (South Africa)
>>95%: Portuguese, Swedish, Marathi, Kannada, Gujarati, Irish, Oriya
>>93%: Turkish
>>
>>
>>Juergen

Re: [RELEASE]: new languages for AOO 3.4.1

[Johanne Mathisen Tandberg <jm...@hotmail.no>]

Cancel me from the maling list

Johanne

Den 26. nov. 2012 kl. 04:51 skrev "Shenfeng Liu" <li...@gmail.com>:

> Welcome to join AOO!
> I suggest you can start from our New Volunteer Orientation page for how to
> do translation: http://incubator.apache.org/openofficeorg/translate.html .
> And besides the dev@openoffice.apache.org mail group, you should also
> subscript to l10n@openoffice.apache.org, by sending an email to
> L10N-subscribe@openoffice.apache.org. In I10n, translation related
> topics/questions will be discussed in more details.
> 
> - Shenfeng (Simon)
> 
> 
> 2012/11/26 胡其图 <hu...@163.com>
> 
>> Hi there,
>> I am a mongolian where living in inner mongolia, china. and I want to
>> build a traditional mongolian AOO if it possible.
>> and I know there have a slav mongolian AOO, but this is not similar to
>> traditional mongolian.
>> tell me how to add about a language for traditional mongolian?
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> At 2012-11-23 16:39:46,"Jürgen Schmidt" <jo...@gmail.com> wrote:
>>> Hi,
>>> 
>>> we all know that the number of volunteers helping with translation is
>>> growing and we would like to make new languages as soon as possible
>>> available. This is important for two reason, first to make AOO available
>>> in further languages to reach more users. Second to show our volunteers
>>> that their work is appreciated and become integrated as soon as
>>> possible. We don't have a well defined process for doing it at moment
>>> but we will find a working way that will be ok for all of us. And we can
>>> improve it over time when see demand for changes or improvements, means
>>> we don't have to find a 100% perfect solution from the beginning.
>>> 
>>> The most important part is how we do the naming of the different parts
>>> of such a release.
>>> 
>>> I see two different scenarios:
>>> 
>>> 1. Only new languages, no bugfixes, no other code changes
>>> We add the new languages on top of the existing AOO34 branch, build the
>>> office with the new languages and release the new languages as
>>> convenience binary packages. We also build a new src release package and
>>> add the revision number in the name to identify a respin of the orginal
>>> 3.4.1.
>>> 
>>> For example: aoo-3.4.1-rev1372282-src.tar.bz2
>>> 
>>> This new src release becomes the default for 3.4.1 because it is a
>>> respin only (no functional changes)
>>> 
>>> The revision number is part of the about dialog as well and it is
>>> possible to identify the respin.
>>> 
>>> 
>>> 2. New languages + bug-fixes or security fixes
>>> The micro number will be increased and we do a normal release cycle.
>>> The src release will contain the revision number in future always.
>>> 
>>> 
>>> 
>>> Concrete proposal for 3.4.1 and new languages:
>>> 
>>> 1. set a deadline for new translations, for exmaple December 31, 2012
>>> 2. integrate the new languages and provide the builds until January 10,
>> 2013
>>> 3. test and verify the new language builds asap
>>> 4. release the new languages at the end of January
>>> 
>>> 
>>> Why a deadline until December:
>>> The reason is quite simply, we have 22 languages with an UI coverage of
>>> more than 95% (ok Turkish 93%). My plan is to prepare a blog entry and
>>> call again for volunteers for these languages where the effort is
>>> moderate. My hope is that we can integrate a few of the important ones.
>>> 
>>> UI coverage with more than 93%
>>> ==============================
>>> 100%: Danish
>>> 98%: Korean, Polish, Asturian, Uighur, Icelandic, Indonesian, Welsh,
>>> Catalan, Bulgarian, Latvian
>>> 97%: Greek, Basque
>>> 96%: English (South Africa)
>>> 95%: Portuguese, Swedish, Marathi, Kannada, Gujarati, Irish, Oriya
>>> 93%: Turkish
>>> 
>>> 
>>> Juergen
>> 

Re: [RELEASE]: new languages for AOO 3.4.1

[Johanne Mathisen Tandberg <jm...@hotmail.no>]

Cancel me from the maling list

Johanne

Den 26. nov. 2012 kl. 04:51 skrev "Shenfeng Liu" <li...@gmail.com>:

> Welcome to join AOO!
> I suggest you can start from our New Volunteer Orientation page for how to
> do translation: http://incubator.apache.org/openofficeorg/translate.html .
> And besides the dev@openoffice.apache.org mail group, you should also
> subscript to l10n@openoffice.apache.org, by sending an email to
> L10N-subscribe@openoffice.apache.org. In I10n, translation related
> topics/questions will be discussed in more details.
> 
> - Shenfeng (Simon)
> 
> 
> 2012/11/26 胡其图 <hu...@163.com>
> 
>> Hi there,
>> I am a mongolian where living in inner mongolia, china. and I want to
>> build a traditional mongolian AOO if it possible.
>> and I know there have a slav mongolian AOO, but this is not similar to
>> traditional mongolian.
>> tell me how to add about a language for traditional mongolian?
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> At 2012-11-23 16:39:46,"Jürgen Schmidt" <jo...@gmail.com> wrote:
>>> Hi,
>>> 
>>> we all know that the number of volunteers helping with translation is
>>> growing and we would like to make new languages as soon as possible
>>> available. This is important for two reason, first to make AOO available
>>> in further languages to reach more users. Second to show our volunteers
>>> that their work is appreciated and become integrated as soon as
>>> possible. We don't have a well defined process for doing it at moment
>>> but we will find a working way that will be ok for all of us. And we can
>>> improve it over time when see demand for changes or improvements, means
>>> we don't have to find a 100% perfect solution from the beginning.
>>> 
>>> The most important part is how we do the naming of the different parts
>>> of such a release.
>>> 
>>> I see two different scenarios:
>>> 
>>> 1. Only new languages, no bugfixes, no other code changes
>>> We add the new languages on top of the existing AOO34 branch, build the
>>> office with the new languages and release the new languages as
>>> convenience binary packages. We also build a new src release package and
>>> add the revision number in the name to identify a respin of the orginal
>>> 3.4.1.
>>> 
>>> For example: aoo-3.4.1-rev1372282-src.tar.bz2
>>> 
>>> This new src release becomes the default for 3.4.1 because it is a
>>> respin only (no functional changes)
>>> 
>>> The revision number is part of the about dialog as well and it is
>>> possible to identify the respin.
>>> 
>>> 
>>> 2. New languages + bug-fixes or security fixes
>>> The micro number will be increased and we do a normal release cycle.
>>> The src release will contain the revision number in future always.
>>> 
>>> 
>>> 
>>> Concrete proposal for 3.4.1 and new languages:
>>> 
>>> 1. set a deadline for new translations, for exmaple December 31, 2012
>>> 2. integrate the new languages and provide the builds until January 10,
>> 2013
>>> 3. test and verify the new language builds asap
>>> 4. release the new languages at the end of January
>>> 
>>> 
>>> Why a deadline until December:
>>> The reason is quite simply, we have 22 languages with an UI coverage of
>>> more than 95% (ok Turkish 93%). My plan is to prepare a blog entry and
>>> call again for volunteers for these languages where the effort is
>>> moderate. My hope is that we can integrate a few of the important ones.
>>> 
>>> UI coverage with more than 93%
>>> ==============================
>>> 100%: Danish
>>> 98%: Korean, Polish, Asturian, Uighur, Icelandic, Indonesian, Welsh,
>>> Catalan, Bulgarian, Latvian
>>> 97%: Greek, Basque
>>> 96%: English (South Africa)
>>> 95%: Portuguese, Swedish, Marathi, Kannada, Gujarati, Irish, Oriya
>>> 93%: Turkish
>>> 
>>> 
>>> Juergen
>> 

Re: [RELEASE]: new languages for AOO 3.4.1

[Shenfeng Liu <li...@gmail.com>]

Welcome to join AOO!
I suggest you can start from our New Volunteer Orientation page for how to
do translation: http://incubator.apache.org/openofficeorg/translate.html .
And besides the dev@openoffice.apache.org mail group, you should also
subscript to l10n@openoffice.apache.org, by sending an email to
L10N-subscribe@openoffice.apache.org. In I10n, translation related
topics/questions will be discussed in more details.

- Shenfeng (Simon)


2012/11/26 胡其图 <hu...@163.com>

> Hi there,
> I am a mongolian where living in inner mongolia, china. and I want to
> build a traditional mongolian AOO if it possible.
> and I know there have a slav mongolian AOO, but this is not similar to
> traditional mongolian.
> tell me how to add about a language for traditional mongolian?
>
>
>
>
>
>
>
>
> At 2012-11-23 16:39:46,"Jürgen Schmidt" <jo...@gmail.com> wrote:
> >Hi,
> >
> >we all know that the number of volunteers helping with translation is
> >growing and we would like to make new languages as soon as possible
> >available. This is important for two reason, first to make AOO available
> >in further languages to reach more users. Second to show our volunteers
> >that their work is appreciated and become integrated as soon as
> >possible. We don't have a well defined process for doing it at moment
> >but we will find a working way that will be ok for all of us. And we can
> >improve it over time when see demand for changes or improvements, means
> >we don't have to find a 100% perfect solution from the beginning.
> >
> >The most important part is how we do the naming of the different parts
> >of such a release.
> >
> >I see two different scenarios:
> >
> >1. Only new languages, no bugfixes, no other code changes
> >We add the new languages on top of the existing AOO34 branch, build the
> >office with the new languages and release the new languages as
> >convenience binary packages. We also build a new src release package and
> >add the revision number in the name to identify a respin of the orginal
> >3.4.1.
> >
> >For example: aoo-3.4.1-rev1372282-src.tar.bz2
> >
> >This new src release becomes the default for 3.4.1 because it is a
> >respin only (no functional changes)
> >
> >The revision number is part of the about dialog as well and it is
> >possible to identify the respin.
> >
> >
> >2. New languages + bug-fixes or security fixes
> >The micro number will be increased and we do a normal release cycle.
> >The src release will contain the revision number in future always.
> >
> >
> >
> >Concrete proposal for 3.4.1 and new languages:
> >
> >1. set a deadline for new translations, for exmaple December 31, 2012
> >2. integrate the new languages and provide the builds until January 10,
> 2013
> >3. test and verify the new language builds asap
> >4. release the new languages at the end of January
> >
> >
> >Why a deadline until December:
> >The reason is quite simply, we have 22 languages with an UI coverage of
> >more than 95% (ok Turkish 93%). My plan is to prepare a blog entry and
> >call again for volunteers for these languages where the effort is
> >moderate. My hope is that we can integrate a few of the important ones.
> >
> >UI coverage with more than 93%
> >==============================
> >100%: Danish
> >98%: Korean, Polish, Asturian, Uighur, Icelandic, Indonesian, Welsh,
> >Catalan, Bulgarian, Latvian
> >97%: Greek, Basque
> >96%: English (South Africa)
> >95%: Portuguese, Swedish, Marathi, Kannada, Gujarati, Irish, Oriya
> >93%: Turkish
> >
> >
> >Juergen
>

Re: [RELEASE]: new languages for AOO 3.4.1

[Shenfeng Liu <li...@gmail.com>]

Welcome to join AOO!
I suggest you can start from our New Volunteer Orientation page for how to
do translation: http://incubator.apache.org/openofficeorg/translate.html .
And besides the dev@openoffice.apache.org mail group, you should also
subscript to l10n@openoffice.apache.org, by sending an email to
L10N-subscribe@openoffice.apache.org. In I10n, translation related
topics/questions will be discussed in more details.

- Shenfeng (Simon)


2012/11/26 胡其图 <hu...@163.com>

> Hi there,
> I am a mongolian where living in inner mongolia, china. and I want to
> build a traditional mongolian AOO if it possible.
> and I know there have a slav mongolian AOO, but this is not similar to
> traditional mongolian.
> tell me how to add about a language for traditional mongolian?
>
>
>
>
>
>
>
>
> At 2012-11-23 16:39:46,"Jürgen Schmidt" <jo...@gmail.com> wrote:
> >Hi,
> >
> >we all know that the number of volunteers helping with translation is
> >growing and we would like to make new languages as soon as possible
> >available. This is important for two reason, first to make AOO available
> >in further languages to reach more users. Second to show our volunteers
> >that their work is appreciated and become integrated as soon as
> >possible. We don't have a well defined process for doing it at moment
> >but we will find a working way that will be ok for all of us. And we can
> >improve it over time when see demand for changes or improvements, means
> >we don't have to find a 100% perfect solution from the beginning.
> >
> >The most important part is how we do the naming of the different parts
> >of such a release.
> >
> >I see two different scenarios:
> >
> >1. Only new languages, no bugfixes, no other code changes
> >We add the new languages on top of the existing AOO34 branch, build the
> >office with the new languages and release the new languages as
> >convenience binary packages. We also build a new src release package and
> >add the revision number in the name to identify a respin of the orginal
> >3.4.1.
> >
> >For example: aoo-3.4.1-rev1372282-src.tar.bz2
> >
> >This new src release becomes the default for 3.4.1 because it is a
> >respin only (no functional changes)
> >
> >The revision number is part of the about dialog as well and it is
> >possible to identify the respin.
> >
> >
> >2. New languages + bug-fixes or security fixes
> >The micro number will be increased and we do a normal release cycle.
> >The src release will contain the revision number in future always.
> >
> >
> >
> >Concrete proposal for 3.4.1 and new languages:
> >
> >1. set a deadline for new translations, for exmaple December 31, 2012
> >2. integrate the new languages and provide the builds until January 10,
> 2013
> >3. test and verify the new language builds asap
> >4. release the new languages at the end of January
> >
> >
> >Why a deadline until December:
> >The reason is quite simply, we have 22 languages with an UI coverage of
> >more than 95% (ok Turkish 93%). My plan is to prepare a blog entry and
> >call again for volunteers for these languages where the effort is
> >moderate. My hope is that we can integrate a few of the important ones.
> >
> >UI coverage with more than 93%
> >==============================
> >100%: Danish
> >98%: Korean, Polish, Asturian, Uighur, Icelandic, Indonesian, Welsh,
> >Catalan, Bulgarian, Latvian
> >97%: Greek, Basque
> >96%: English (South Africa)
> >95%: Portuguese, Swedish, Marathi, Kannada, Gujarati, Irish, Oriya
> >93%: Turkish
> >
> >
> >Juergen
>

Re:[RELEASE]: new languages for AOO 3.4.1

[胡其图 <hu...@163.com>]

Hi there,
I am a mongolian where living in inner mongolia, china. and I want to build a traditional mongolian AOO if it possible.
and I know there have a slav mongolian AOO, but this is not similar to traditional mongolian.
tell me how to add about a language for traditional mongolian?








At 2012-11-23 16:39:46,"Jürgen Schmidt" <jo...@gmail.com> wrote:
>Hi,
>
>we all know that the number of volunteers helping with translation is
>growing and we would like to make new languages as soon as possible
>available. This is important for two reason, first to make AOO available
>in further languages to reach more users. Second to show our volunteers
>that their work is appreciated and become integrated as soon as
>possible. We don't have a well defined process for doing it at moment
>but we will find a working way that will be ok for all of us. And we can
>improve it over time when see demand for changes or improvements, means
>we don't have to find a 100% perfect solution from the beginning.
>
>The most important part is how we do the naming of the different parts
>of such a release.
>
>I see two different scenarios:
>
>1. Only new languages, no bugfixes, no other code changes
>We add the new languages on top of the existing AOO34 branch, build the
>office with the new languages and release the new languages as
>convenience binary packages. We also build a new src release package and
>add the revision number in the name to identify a respin of the orginal
>3.4.1.
>
>For example: aoo-3.4.1-rev1372282-src.tar.bz2
>
>This new src release becomes the default for 3.4.1 because it is a
>respin only (no functional changes)
>
>The revision number is part of the about dialog as well and it is
>possible to identify the respin.
>
>
>2. New languages + bug-fixes or security fixes
>The micro number will be increased and we do a normal release cycle.
>The src release will contain the revision number in future always.
>
>
>
>Concrete proposal for 3.4.1 and new languages:
>
>1. set a deadline for new translations, for exmaple December 31, 2012
>2. integrate the new languages and provide the builds until January 10, 2013
>3. test and verify the new language builds asap
>4. release the new languages at the end of January
>
>
>Why a deadline until December:
>The reason is quite simply, we have 22 languages with an UI coverage of
>more than 95% (ok Turkish 93%). My plan is to prepare a blog entry and
>call again for volunteers for these languages where the effort is
>moderate. My hope is that we can integrate a few of the important ones.
>
>UI coverage with more than 93%
>==============================
>100%: Danish
>98%: Korean, Polish, Asturian, Uighur, Icelandic, Indonesian, Welsh,
>Catalan, Bulgarian, Latvian
>97%: Greek, Basque
>96%: English (South Africa)
>95%: Portuguese, Swedish, Marathi, Kannada, Gujarati, Irish, Oriya
>93%: Turkish
>
>
>Juergen

Re: [RELEASE]: new languages for AOO 3.4.1

[Jürgen Schmidt <jo...@gmail.com>]

On 11/26/12 10:54 AM, Andrea Pescetti wrote:
> On 23/11/2012 Jürgen Schmidt wrote:
>> 1. Only new languages, no bugfixes, no other code changes
>> We add the new languages on top of the existing AOO34 branch, build the
>> office with the new languages and release the new languages as
>> convenience binary packages. We also build a new src release package and
>> add the revision number ... aoo-3.4.1-rev1372282-src.tar.bz2
> 
> This is the best solution for me.
> 
>> 2. New languages + bug-fixes or security fixes
>> The micro number will be increased and we do a normal release cycle.
>> The src release will contain the revision number in future always.
> 
> This could still be a possibility, but only if we need to fix a critical
> security bug and 4.0 seems too far away. In that case, of course, we
> would need to release a 3.4.2 with only that security fix and doing so
> we would include all languages that are ready for 3.4.
> 
>> 1. set a deadline for new translations, for exmaple December 31, 2012
>> 2. integrate the new languages and provide the builds until January
>> 10, 2013
>> 3. test and verify the new language builds asap
>> 4. release the new languages at the end of January
> 
> All fine to me. I would honestly have started with what we already have
> and release it as soon as possible, and possibly with another release
> manager (so, Juergen focused on 4.x someone else works on the
> "maintenance" releases of 3.4.x), to test the process and avoid late
> surprises or policy questions. But if for the time being this is the
> best solution for release management, fine. Sure, in future we should
> definitely avoid that it takes this long to get a translation integrated
> and released. So I would try to use this occasion to learn how we can
> streamline the release process as much as possible. But let's start to
> communicate clear deadlines to volunteers,

I have include the deadline end of December already in my blog draft
that I will publish later today.

I will work on some update int eh wiki to reflect this plan in more detail.

Juergen

Re: [RELEASE]: new languages for AOO 3.4.1

[Andrea Pescetti <pe...@apache.org>]

On 23/11/2012 Jürgen Schmidt wrote:
> 1. Only new languages, no bugfixes, no other code changes
> We add the new languages on top of the existing AOO34 branch, build the
> office with the new languages and release the new languages as
> convenience binary packages. We also build a new src release package and
> add the revision number ... aoo-3.4.1-rev1372282-src.tar.bz2

This is the best solution for me.

> 2. New languages + bug-fixes or security fixes
> The micro number will be increased and we do a normal release cycle.
> The src release will contain the revision number in future always.

This could still be a possibility, but only if we need to fix a critical 
security bug and 4.0 seems too far away. In that case, of course, we 
would need to release a 3.4.2 with only that security fix and doing so 
we would include all languages that are ready for 3.4.

> 1. set a deadline for new translations, for exmaple December 31, 2012
> 2. integrate the new languages and provide the builds until January 10, 2013
> 3. test and verify the new language builds asap
> 4. release the new languages at the end of January

All fine to me. I would honestly have started with what we already have 
and release it as soon as possible, and possibly with another release 
manager (so, Juergen focused on 4.x someone else works on the 
"maintenance" releases of 3.4.x), to test the process and avoid late 
surprises or policy questions. But if for the time being this is the 
best solution for release management, fine. Sure, in future we should 
definitely avoid that it takes this long to get a translation integrated 
and released. So I would try to use this occasion to learn how we can 
streamline the release process as much as possible. But let's start to 
communicate clear deadlines to volunteers,

Regards,
   Andrea.

Re: [RELEASE]: new languages for AOO 3.4.1

[Oliver-Rainer Wittmann <or...@googlemail.com>]

Hi,

On 23.11.2012 09:39, Jürgen Schmidt wrote:
> Hi,
>
> we all know that the number of volunteers helping with translation is
> growing and we would like to make new languages as soon as possible
> available. This is important for two reason, first to make AOO available
> in further languages to reach more users. Second to show our volunteers
> that their work is appreciated and become integrated as soon as
> possible. We don't have a well defined process for doing it at moment
> but we will find a working way that will be ok for all of us. And we can
> improve it over time when see demand for changes or improvements, means
> we don't have to find a 100% perfect solution from the beginning.
>
> The most important part is how we do the naming of the different parts
> of such a release.
>
> I see two different scenarios:
>
> 1. Only new languages, no bugfixes, no other code changes
> We add the new languages on top of the existing AOO34 branch, build the
> office with the new languages and release the new languages as
> convenience binary packages. We also build a new src release package and
> add the revision number in the name to identify a respin of the orginal
> 3.4.1.
>
> For example: aoo-3.4.1-rev1372282-src.tar.bz2
>
> This new src release becomes the default for 3.4.1 because it is a
> respin only (no functional changes)
>
> The revision number is part of the about dialog as well and it is
> possible to identify the respin.
>

Yes, let us make a new source release for the new languages and stay with 
version number 3.4.1.
Additionally, let us provide for the convenience of our users installion 
packages for the new languages based on the new source release.

Best regards, Oliver.

>
> 2. New languages + bug-fixes or security fixes
> The micro number will be increased and we do a normal release cycle.
> The src release will contain the revision number in future always.
>
>
>
> Concrete proposal for 3.4.1 and new languages:
>
> 1. set a deadline for new translations, for exmaple December 31, 2012
> 2. integrate the new languages and provide the builds until January 10, 2013
> 3. test and verify the new language builds asap
> 4. release the new languages at the end of January
>
>
> Why a deadline until December:
> The reason is quite simply, we have 22 languages with an UI coverage of
> more than 95% (ok Turkish 93%). My plan is to prepare a blog entry and
> call again for volunteers for these languages where the effort is
> moderate. My hope is that we can integrate a few of the important ones.
>
> UI coverage with more than 93%
> ==============================
> 100%: Danish
> 98%: Korean, Polish, Asturian, Uighur, Icelandic, Indonesian, Welsh,
> Catalan, Bulgarian, Latvian
> 97%: Greek, Basque
> 96%: English (South Africa)
> 95%: Portuguese, Swedish, Marathi, Kannada, Gujarati, Irish, Oriya
> 93%: Turkish
>
>
> Juergen
>

Re: [RELEASE]: new languages for AOO 3.4.1

["Marcus (OOo)" <ma...@wtnet.de>]

Am 11/23/2012 03:30 PM, schrieb jan iversen:
> If it is easier, we could keep the binary, and just release language
> packs....a bit more uncomfortable but still an official release !

Then for these new languages the 1-click-download will not work as the 
full install files are missing.

In the old OOo project we had this behavior and it led to much user 
confusion why this is. IMHO we should really avoid this again.

Marcus



> On 23 November 2012 15:01, Rob Weir<ro...@apache.org>  wrote:
>
>> On Fri, Nov 23, 2012 at 3:39 AM, Jürgen Schmidt<jo...@gmail.com>
>> wrote:
>>> Hi,
>>>
>>> we all know that the number of volunteers helping with translation is
>>> growing and we would like to make new languages as soon as possible
>>> available. This is important for two reason, first to make AOO available
>>> in further languages to reach more users. Second to show our volunteers
>>> that their work is appreciated and become integrated as soon as
>>> possible. We don't have a well defined process for doing it at moment
>>> but we will find a working way that will be ok for all of us. And we can
>>> improve it over time when see demand for changes or improvements, means
>>> we don't have to find a 100% perfect solution from the beginning.
>>>
>>> The most important part is how we do the naming of the different parts
>>> of such a release.
>>>
>>> I see two different scenarios:
>>>
>>> 1. Only new languages, no bugfixes, no other code changes
>>> We add the new languages on top of the existing AOO34 branch, build the
>>> office with the new languages and release the new languages as
>>> convenience binary packages. We also build a new src release package and
>>> add the revision number in the name to identify a respin of the orginal
>>> 3.4.1.
>>>
>>> For example: aoo-3.4.1-rev1372282-src.tar.bz2
>>>
>>> This new src release becomes the default for 3.4.1 because it is a
>>> respin only (no functional changes)
>>>
>>> The revision number is part of the about dialog as well and it is
>>> possible to identify the respin.
>>>
>>
>> If we change the about dialog does this change anything else?  For
>> example, does it change what is written into ODF documents for the
>> creator string?  Does it cause AOO to report a different version to
>> scripts?  If we change anything more than the UI strings we risk
>> breaking 3rd party scripts who have logic tied to 3.4.0 or 3.4.1.
>>
>> -Rob
>>
>>
>>>
>>> 2. New languages + bug-fixes or security fixes
>>> The micro number will be increased and we do a normal release cycle.
>>> The src release will contain the revision number in future always.
>>>
>>>
>>>
>>> Concrete proposal for 3.4.1 and new languages:
>>>
>>> 1. set a deadline for new translations, for exmaple December 31, 2012
>>> 2. integrate the new languages and provide the builds until January 10,
>> 2013
>>> 3. test and verify the new language builds asap
>>> 4. release the new languages at the end of January
>>>
>>>
>>> Why a deadline until December:
>>> The reason is quite simply, we have 22 languages with an UI coverage of
>>> more than 95% (ok Turkish 93%). My plan is to prepare a blog entry and
>>> call again for volunteers for these languages where the effort is
>>> moderate. My hope is that we can integrate a few of the important ones.
>>>
>>> UI coverage with more than 93%
>>> ==============================
>>> 100%: Danish
>>> 98%: Korean, Polish, Asturian, Uighur, Icelandic, Indonesian, Welsh,
>>> Catalan, Bulgarian, Latvian
>>> 97%: Greek, Basque
>>> 96%: English (South Africa)
>>> 95%: Portuguese, Swedish, Marathi, Kannada, Gujarati, Irish, Oriya
>>> 93%: Turkish
>>>
>>>
>>> Juergen

Re: [RELEASE]: new languages for AOO 3.4.1

[Andrew Rist <an...@oracle.com>]

On 11/23/2012 8:14 AM, Rory O'Farrell wrote:
> On Fri, 23 Nov 2012 17:00:54 +0100
> jan iversen <ja...@apache.org> wrote:
>
>> Good idea, that was basically what I meant...however even microsoft, does
>> provide a slim setup, that then downloads the needed packages.
> There is a disadvantage to that: such an installation has to have on-line access at install time.  There are still many users who do not have on-line access 24/7 at broadband speeds; they may rely for installation on a download on a public library machine or a friend's machine and transfer the file to the target computer by USB key, so a complete package (whether compiled for natice language or as outlined above) would be useful to them,
This point comes up over and over again.  We need to serve both groups, 
but the solution should not force either group into a degraded install 
process.

We can have a 'slim setup' that then loads resources from the same 
location/media it came from.
This approach works for those who need local media due to bandwidth 
constraints  (CD/USB Key/File system)
It also works efficiently for broadband loading the bootstrap ('slim 
setup') over the network, and then collecting additional resources as 
needed.

If it is built correctly, this type of install would also facilitate 
1-click installs without requiring the duplication of bits which is a 
growing problem as we again add languages.   If the bootstrap setup is 
loaded with a configuration file, it could be set to load specific 
language packs, dictionaries, and additional extensions. (The additional 
files would either be downloaded over the network from the same network 
location, or bundled on the same media in the same folder for a CD/USB 
type install)

Let's stop arguing over which of the two scenarios our install will 
support correctly, and agree that we need to support both scenarios 
correctly.


Andrew

>
<snip>

Re: [RELEASE]: new languages for AOO 3.4.1

[Jürgen Schmidt <jo...@gmail.com>]

On 11/23/12 5:14 PM, Rory O'Farrell wrote:
> On Fri, 23 Nov 2012 17:00:54 +0100
> jan iversen <ja...@apache.org> wrote:
> 
>> Good idea, that was basically what I meant...however even microsoft, does
>> provide a slim setup, that then downloads the needed packages.
> 
> There is a disadvantage to that: such an installation has to have on-line access at install time.  There are still many users who do not have on-line access 24/7 at broadband speeds; they may rely for installation on a download on a public library machine or a friend's machine and transfer the file to the target computer by USB key, so a complete package (whether compiled for natice language or as outlined above) would be useful to them,
> 

we have already thought in such a direction and we have taken offline
installation into account as well. But that is much more work and not
possible in the near future.

But volunteers are welcome to think about it and ideas are welcome. We
can only benefit from a smaller download package or a better approach to
reuse the main part that is language independent.

The only thing we should keep in mind is the 1-click installation user
experience.

Juergen

>>
>> jan
>>
>> On 23 November 2012 16:58, Rory O'Farrell <of...@iol.ie> wrote:
>>
>>> On Fri, 23 Nov 2012 16:00:38 +0100
>>> jan iversen <ja...@apache.org> wrote:
>>>
>>>> Following your thought...
>>>>
>>>> Would it not be an idea, if we defined the binary to be en-US always, and
>>>> then modify the installation scripts to include the proper language pack
>>> ??
>>>>
>>>> Please see it as an open question, I do not know if there are other
>>>> implications. I have for some time (years) downloaded the en-US binary
>>> and
>>>> added the language pack, so technically it is possible.
>>>>
>>>> Jan.
>>>>
>>>> On 23 November 2012 15:47, Rob Weir <ro...@apache.org> wrote:
>>>>
>>>>> On Fri, Nov 23, 2012 at 9:30 AM, jan iversen <ja...@apache.org> wrote:
>>>>>> If it is easier, we could keep the binary, and just release language
>>>>>> packs....a bit more uncomfortable but still an official release !
>>>>>>
>>>>>
>>>>> I'm just thinking ahead, to the very real possibility that we're
>>>>> adding new languages on a continual basis until we're shipping 100+ of
>>>>> them.  If that happens we're going to create absolute chaos if we
>>>>> encoding version changes in a way that appears externally to scripts,
>>>>> extensions, in documents, to upgrade servers, etc.  It will lead to a
>>>>> proliferation of version strings that will destroy us all.  This is
>>>>> what the Mayans were warning us about !!!
>>>>>
>>>>> (OK, maybe not that bad, but it would be quite a mess)
>>>>>
>>>>> But if we can consider these new languages to be merely the
>>>>> continuation of the 3.4.1 release, and an keep the external behavior
>>>>> of the program the same, then live is easy.  We can release full
>>>>> versions of Danish, etc., 3.4.1.  All we need to do is vote on a new
>>>>> source tarball which could be called AOO341-danish-patch.tgz or
>>>>> whatever.
>>>>>
>>>>> -Rob
>>>>>
>>>>>
>>>>>> Jan.
>>>>>>
>>>>>> On 23 November 2012 15:01, Rob Weir <ro...@apache.org> wrote:
>>>>>>
>>>>>>> On Fri, Nov 23, 2012 at 3:39 AM, Jürgen Schmidt <
>>> jogischmidt@gmail.com>
>>>>>>> wrote:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> we all know that the number of volunteers helping with
>>> translation is
>>>>>>>> growing and we would like to make new languages as soon as
>>> possible
>>>>>>>> available. This is important for two reason, first to make AOO
>>>>> available
>>>>>>>> in further languages to reach more users. Second to show our
>>>>> volunteers
>>>>>>>> that their work is appreciated and become integrated as soon as
>>>>>>>> possible. We don't have a well defined process for doing it at
>>> moment
>>>>>>>> but we will find a working way that will be ok for all of us. And
>>> we
>>>>> can
>>>>>>>> improve it over time when see demand for changes or improvements,
>>>>> means
>>>>>>>> we don't have to find a 100% perfect solution from the beginning.
>>>>>>>>
>>>>>>>> The most important part is how we do the naming of the different
>>> parts
>>>>>>>> of such a release.
>>>>>>>>
>>>>>>>> I see two different scenarios:
>>>>>>>>
>>>>>>>> 1. Only new languages, no bugfixes, no other code changes
>>>>>>>> We add the new languages on top of the existing AOO34 branch,
>>> build
>>>>> the
>>>>>>>> office with the new languages and release the new languages as
>>>>>>>> convenience binary packages. We also build a new src release
>>> package
>>>>> and
>>>>>>>> add the revision number in the name to identify a respin of the
>>>>> orginal
>>>>>>>> 3.4.1.
>>>>>>>>
>>>>>>>> For example: aoo-3.4.1-rev1372282-src.tar.bz2
>>>>>>>>
>>>>>>>> This new src release becomes the default for 3.4.1 because it is a
>>>>>>>> respin only (no functional changes)
>>>>>>>>
>>>>>>>> The revision number is part of the about dialog as well and it is
>>>>>>>> possible to identify the respin.
>>>>>>>>
>>>>>>>
>>>>>>> If we change the about dialog does this change anything else?  For
>>>>>>> example, does it change what is written into ODF documents for the
>>>>>>> creator string?  Does it cause AOO to report a different version to
>>>>>>> scripts?  If we change anything more than the UI strings we risk
>>>>>>> breaking 3rd party scripts who have logic tied to 3.4.0 or 3.4.1.
>>>>>>>
>>>>>>> -Rob
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> 2. New languages + bug-fixes or security fixes
>>>>>>>> The micro number will be increased and we do a normal release
>>> cycle.
>>>>>>>> The src release will contain the revision number in future always.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Concrete proposal for 3.4.1 and new languages:
>>>>>>>>
>>>>>>>> 1. set a deadline for new translations, for exmaple December 31,
>>> 2012
>>>>>>>> 2. integrate the new languages and provide the builds until
>>> January
>>>>> 10,
>>>>>>> 2013
>>>>>>>> 3. test and verify the new language builds asap
>>>>>>>> 4. release the new languages at the end of January
>>>>>>>>
>>>>>>>>
>>>>>>>> Why a deadline until December:
>>>>>>>> The reason is quite simply, we have 22 languages with an UI
>>> coverage
>>>>> of
>>>>>>>> more than 95% (ok Turkish 93%). My plan is to prepare a blog
>>> entry and
>>>>>>>> call again for volunteers for these languages where the effort is
>>>>>>>> moderate. My hope is that we can integrate a few of the important
>>>>> ones.
>>>>>>>>
>>>>>>>> UI coverage with more than 93%
>>>>>>>> ==============================
>>>>>>>> 100%: Danish
>>>>>>>> 98%: Korean, Polish, Asturian, Uighur, Icelandic, Indonesian,
>>> Welsh,
>>>>>>>> Catalan, Bulgarian, Latvian
>>>>>>>> 97%: Greek, Basque
>>>>>>>> 96%: English (South Africa)
>>>>>>>> 95%: Portuguese, Swedish, Marathi, Kannada, Gujarati, Irish, Oriya
>>>>>>>> 93%: Turkish
>>>>>>>>
>>>>>>>>
>>>>>>>> Juergen
>>>>>>>
>>>>>
>>>
>>> Less well informed users (i.e., the majority of ordinary,
>>> computer-unskilled users) expect to get a complete package for their
>>> language, with no extra downloading or customisation required.  Might it be
>>> possible to package the language packs in such a way that the "complete
>>> pack" consisted of the basic unit (en-US) and the specific Language add-on,
>>> and an "invisible" script automatically installed the Language add-on,
>>> thereby giving the same effect as a compiled national language version?
>>>
>>> --
>>> Rory O'Farrell <of...@iol.ie>
>>>
> 
> 

Re: [RELEASE]: new languages for AOO 3.4.1

[Rory O'Farrell <of...@iol.ie>]

On Fri, 23 Nov 2012 17:00:54 +0100
jan iversen <ja...@apache.org> wrote:

> Good idea, that was basically what I meant...however even microsoft, does
> provide a slim setup, that then downloads the needed packages.

There is a disadvantage to that: such an installation has to have on-line access at install time.  There are still many users who do not have on-line access 24/7 at broadband speeds; they may rely for installation on a download on a public library machine or a friend's machine and transfer the file to the target computer by USB key, so a complete package (whether compiled for natice language or as outlined above) would be useful to them,

> 
> jan
> 
> On 23 November 2012 16:58, Rory O'Farrell <of...@iol.ie> wrote:
> 
> > On Fri, 23 Nov 2012 16:00:38 +0100
> > jan iversen <ja...@apache.org> wrote:
> >
> > > Following your thought...
> > >
> > > Would it not be an idea, if we defined the binary to be en-US always, and
> > > then modify the installation scripts to include the proper language pack
> > ??
> > >
> > > Please see it as an open question, I do not know if there are other
> > > implications. I have for some time (years) downloaded the en-US binary
> > and
> > > added the language pack, so technically it is possible.
> > >
> > > Jan.
> > >
> > > On 23 November 2012 15:47, Rob Weir <ro...@apache.org> wrote:
> > >
> > > > On Fri, Nov 23, 2012 at 9:30 AM, jan iversen <ja...@apache.org> wrote:
> > > > > If it is easier, we could keep the binary, and just release language
> > > > > packs....a bit more uncomfortable but still an official release !
> > > > >
> > > >
> > > > I'm just thinking ahead, to the very real possibility that we're
> > > > adding new languages on a continual basis until we're shipping 100+ of
> > > > them.  If that happens we're going to create absolute chaos if we
> > > > encoding version changes in a way that appears externally to scripts,
> > > > extensions, in documents, to upgrade servers, etc.  It will lead to a
> > > > proliferation of version strings that will destroy us all.  This is
> > > > what the Mayans were warning us about !!!
> > > >
> > > > (OK, maybe not that bad, but it would be quite a mess)
> > > >
> > > > But if we can consider these new languages to be merely the
> > > > continuation of the 3.4.1 release, and an keep the external behavior
> > > > of the program the same, then live is easy.  We can release full
> > > > versions of Danish, etc., 3.4.1.  All we need to do is vote on a new
> > > > source tarball which could be called AOO341-danish-patch.tgz or
> > > > whatever.
> > > >
> > > > -Rob
> > > >
> > > >
> > > > > Jan.
> > > > >
> > > > > On 23 November 2012 15:01, Rob Weir <ro...@apache.org> wrote:
> > > > >
> > > > >> On Fri, Nov 23, 2012 at 3:39 AM, Jürgen Schmidt <
> > jogischmidt@gmail.com>
> > > > >> wrote:
> > > > >> > Hi,
> > > > >> >
> > > > >> > we all know that the number of volunteers helping with
> > translation is
> > > > >> > growing and we would like to make new languages as soon as
> > possible
> > > > >> > available. This is important for two reason, first to make AOO
> > > > available
> > > > >> > in further languages to reach more users. Second to show our
> > > > volunteers
> > > > >> > that their work is appreciated and become integrated as soon as
> > > > >> > possible. We don't have a well defined process for doing it at
> > moment
> > > > >> > but we will find a working way that will be ok for all of us. And
> > we
> > > > can
> > > > >> > improve it over time when see demand for changes or improvements,
> > > > means
> > > > >> > we don't have to find a 100% perfect solution from the beginning.
> > > > >> >
> > > > >> > The most important part is how we do the naming of the different
> > parts
> > > > >> > of such a release.
> > > > >> >
> > > > >> > I see two different scenarios:
> > > > >> >
> > > > >> > 1. Only new languages, no bugfixes, no other code changes
> > > > >> > We add the new languages on top of the existing AOO34 branch,
> > build
> > > > the
> > > > >> > office with the new languages and release the new languages as
> > > > >> > convenience binary packages. We also build a new src release
> > package
> > > > and
> > > > >> > add the revision number in the name to identify a respin of the
> > > > orginal
> > > > >> > 3.4.1.
> > > > >> >
> > > > >> > For example: aoo-3.4.1-rev1372282-src.tar.bz2
> > > > >> >
> > > > >> > This new src release becomes the default for 3.4.1 because it is a
> > > > >> > respin only (no functional changes)
> > > > >> >
> > > > >> > The revision number is part of the about dialog as well and it is
> > > > >> > possible to identify the respin.
> > > > >> >
> > > > >>
> > > > >> If we change the about dialog does this change anything else?  For
> > > > >> example, does it change what is written into ODF documents for the
> > > > >> creator string?  Does it cause AOO to report a different version to
> > > > >> scripts?  If we change anything more than the UI strings we risk
> > > > >> breaking 3rd party scripts who have logic tied to 3.4.0 or 3.4.1.
> > > > >>
> > > > >> -Rob
> > > > >>
> > > > >>
> > > > >> >
> > > > >> > 2. New languages + bug-fixes or security fixes
> > > > >> > The micro number will be increased and we do a normal release
> > cycle.
> > > > >> > The src release will contain the revision number in future always.
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> > Concrete proposal for 3.4.1 and new languages:
> > > > >> >
> > > > >> > 1. set a deadline for new translations, for exmaple December 31,
> > 2012
> > > > >> > 2. integrate the new languages and provide the builds until
> > January
> > > > 10,
> > > > >> 2013
> > > > >> > 3. test and verify the new language builds asap
> > > > >> > 4. release the new languages at the end of January
> > > > >> >
> > > > >> >
> > > > >> > Why a deadline until December:
> > > > >> > The reason is quite simply, we have 22 languages with an UI
> > coverage
> > > > of
> > > > >> > more than 95% (ok Turkish 93%). My plan is to prepare a blog
> > entry and
> > > > >> > call again for volunteers for these languages where the effort is
> > > > >> > moderate. My hope is that we can integrate a few of the important
> > > > ones.
> > > > >> >
> > > > >> > UI coverage with more than 93%
> > > > >> > ==============================
> > > > >> > 100%: Danish
> > > > >> > 98%: Korean, Polish, Asturian, Uighur, Icelandic, Indonesian,
> > Welsh,
> > > > >> > Catalan, Bulgarian, Latvian
> > > > >> > 97%: Greek, Basque
> > > > >> > 96%: English (South Africa)
> > > > >> > 95%: Portuguese, Swedish, Marathi, Kannada, Gujarati, Irish, Oriya
> > > > >> > 93%: Turkish
> > > > >> >
> > > > >> >
> > > > >> > Juergen
> > > > >>
> > > >
> >
> > Less well informed users (i.e., the majority of ordinary,
> > computer-unskilled users) expect to get a complete package for their
> > language, with no extra downloading or customisation required.  Might it be
> > possible to package the language packs in such a way that the "complete
> > pack" consisted of the basic unit (en-US) and the specific Language add-on,
> > and an "invisible" script automatically installed the Language add-on,
> > thereby giving the same effect as a compiled national language version?
> >
> > --
> > Rory O'Farrell <of...@iol.ie>
> >


-- 
Rory O'Farrell <of...@iol.ie>

Re: [RELEASE]: new languages for AOO 3.4.1

[jan iversen <ja...@apache.org>]

Good idea, that was basically what I meant...however even microsoft, does
provide a slim setup, that then downloads the needed packages.

jan

On 23 November 2012 16:58, Rory O'Farrell <of...@iol.ie> wrote:

> On Fri, 23 Nov 2012 16:00:38 +0100
> jan iversen <ja...@apache.org> wrote:
>
> > Following your thought...
> >
> > Would it not be an idea, if we defined the binary to be en-US always, and
> > then modify the installation scripts to include the proper language pack
> ??
> >
> > Please see it as an open question, I do not know if there are other
> > implications. I have for some time (years) downloaded the en-US binary
> and
> > added the language pack, so technically it is possible.
> >
> > Jan.
> >
> > On 23 November 2012 15:47, Rob Weir <ro...@apache.org> wrote:
> >
> > > On Fri, Nov 23, 2012 at 9:30 AM, jan iversen <ja...@apache.org> wrote:
> > > > If it is easier, we could keep the binary, and just release language
> > > > packs....a bit more uncomfortable but still an official release !
> > > >
> > >
> > > I'm just thinking ahead, to the very real possibility that we're
> > > adding new languages on a continual basis until we're shipping 100+ of
> > > them.  If that happens we're going to create absolute chaos if we
> > > encoding version changes in a way that appears externally to scripts,
> > > extensions, in documents, to upgrade servers, etc.  It will lead to a
> > > proliferation of version strings that will destroy us all.  This is
> > > what the Mayans were warning us about !!!
> > >
> > > (OK, maybe not that bad, but it would be quite a mess)
> > >
> > > But if we can consider these new languages to be merely the
> > > continuation of the 3.4.1 release, and an keep the external behavior
> > > of the program the same, then live is easy.  We can release full
> > > versions of Danish, etc., 3.4.1.  All we need to do is vote on a new
> > > source tarball which could be called AOO341-danish-patch.tgz or
> > > whatever.
> > >
> > > -Rob
> > >
> > >
> > > > Jan.
> > > >
> > > > On 23 November 2012 15:01, Rob Weir <ro...@apache.org> wrote:
> > > >
> > > >> On Fri, Nov 23, 2012 at 3:39 AM, Jürgen Schmidt <
> jogischmidt@gmail.com>
> > > >> wrote:
> > > >> > Hi,
> > > >> >
> > > >> > we all know that the number of volunteers helping with
> translation is
> > > >> > growing and we would like to make new languages as soon as
> possible
> > > >> > available. This is important for two reason, first to make AOO
> > > available
> > > >> > in further languages to reach more users. Second to show our
> > > volunteers
> > > >> > that their work is appreciated and become integrated as soon as
> > > >> > possible. We don't have a well defined process for doing it at
> moment
> > > >> > but we will find a working way that will be ok for all of us. And
> we
> > > can
> > > >> > improve it over time when see demand for changes or improvements,
> > > means
> > > >> > we don't have to find a 100% perfect solution from the beginning.
> > > >> >
> > > >> > The most important part is how we do the naming of the different
> parts
> > > >> > of such a release.
> > > >> >
> > > >> > I see two different scenarios:
> > > >> >
> > > >> > 1. Only new languages, no bugfixes, no other code changes
> > > >> > We add the new languages on top of the existing AOO34 branch,
> build
> > > the
> > > >> > office with the new languages and release the new languages as
> > > >> > convenience binary packages. We also build a new src release
> package
> > > and
> > > >> > add the revision number in the name to identify a respin of the
> > > orginal
> > > >> > 3.4.1.
> > > >> >
> > > >> > For example: aoo-3.4.1-rev1372282-src.tar.bz2
> > > >> >
> > > >> > This new src release becomes the default for 3.4.1 because it is a
> > > >> > respin only (no functional changes)
> > > >> >
> > > >> > The revision number is part of the about dialog as well and it is
> > > >> > possible to identify the respin.
> > > >> >
> > > >>
> > > >> If we change the about dialog does this change anything else?  For
> > > >> example, does it change what is written into ODF documents for the
> > > >> creator string?  Does it cause AOO to report a different version to
> > > >> scripts?  If we change anything more than the UI strings we risk
> > > >> breaking 3rd party scripts who have logic tied to 3.4.0 or 3.4.1.
> > > >>
> > > >> -Rob
> > > >>
> > > >>
> > > >> >
> > > >> > 2. New languages + bug-fixes or security fixes
> > > >> > The micro number will be increased and we do a normal release
> cycle.
> > > >> > The src release will contain the revision number in future always.
> > > >> >
> > > >> >
> > > >> >
> > > >> > Concrete proposal for 3.4.1 and new languages:
> > > >> >
> > > >> > 1. set a deadline for new translations, for exmaple December 31,
> 2012
> > > >> > 2. integrate the new languages and provide the builds until
> January
> > > 10,
> > > >> 2013
> > > >> > 3. test and verify the new language builds asap
> > > >> > 4. release the new languages at the end of January
> > > >> >
> > > >> >
> > > >> > Why a deadline until December:
> > > >> > The reason is quite simply, we have 22 languages with an UI
> coverage
> > > of
> > > >> > more than 95% (ok Turkish 93%). My plan is to prepare a blog
> entry and
> > > >> > call again for volunteers for these languages where the effort is
> > > >> > moderate. My hope is that we can integrate a few of the important
> > > ones.
> > > >> >
> > > >> > UI coverage with more than 93%
> > > >> > ==============================
> > > >> > 100%: Danish
> > > >> > 98%: Korean, Polish, Asturian, Uighur, Icelandic, Indonesian,
> Welsh,
> > > >> > Catalan, Bulgarian, Latvian
> > > >> > 97%: Greek, Basque
> > > >> > 96%: English (South Africa)
> > > >> > 95%: Portuguese, Swedish, Marathi, Kannada, Gujarati, Irish, Oriya
> > > >> > 93%: Turkish
> > > >> >
> > > >> >
> > > >> > Juergen
> > > >>
> > >
>
> Less well informed users (i.e., the majority of ordinary,
> computer-unskilled users) expect to get a complete package for their
> language, with no extra downloading or customisation required.  Might it be
> possible to package the language packs in such a way that the "complete
> pack" consisted of the basic unit (en-US) and the specific Language add-on,
> and an "invisible" script automatically installed the Language add-on,
> thereby giving the same effect as a compiled national language version?
>
> --
> Rory O'Farrell <of...@iol.ie>
>

Re: [RELEASE]: new languages for AOO 3.4.1

[Rory O'Farrell <of...@iol.ie>]

On Fri, 23 Nov 2012 16:00:38 +0100
jan iversen <ja...@apache.org> wrote:

> Following your thought...
> 
> Would it not be an idea, if we defined the binary to be en-US always, and
> then modify the installation scripts to include the proper language pack ??
> 
> Please see it as an open question, I do not know if there are other
> implications. I have for some time (years) downloaded the en-US binary and
> added the language pack, so technically it is possible.
> 
> Jan.
> 
> On 23 November 2012 15:47, Rob Weir <ro...@apache.org> wrote:
> 
> > On Fri, Nov 23, 2012 at 9:30 AM, jan iversen <ja...@apache.org> wrote:
> > > If it is easier, we could keep the binary, and just release language
> > > packs....a bit more uncomfortable but still an official release !
> > >
> >
> > I'm just thinking ahead, to the very real possibility that we're
> > adding new languages on a continual basis until we're shipping 100+ of
> > them.  If that happens we're going to create absolute chaos if we
> > encoding version changes in a way that appears externally to scripts,
> > extensions, in documents, to upgrade servers, etc.  It will lead to a
> > proliferation of version strings that will destroy us all.  This is
> > what the Mayans were warning us about !!!
> >
> > (OK, maybe not that bad, but it would be quite a mess)
> >
> > But if we can consider these new languages to be merely the
> > continuation of the 3.4.1 release, and an keep the external behavior
> > of the program the same, then live is easy.  We can release full
> > versions of Danish, etc., 3.4.1.  All we need to do is vote on a new
> > source tarball which could be called AOO341-danish-patch.tgz or
> > whatever.
> >
> > -Rob
> >
> >
> > > Jan.
> > >
> > > On 23 November 2012 15:01, Rob Weir <ro...@apache.org> wrote:
> > >
> > >> On Fri, Nov 23, 2012 at 3:39 AM, Jürgen Schmidt <jo...@gmail.com>
> > >> wrote:
> > >> > Hi,
> > >> >
> > >> > we all know that the number of volunteers helping with translation is
> > >> > growing and we would like to make new languages as soon as possible
> > >> > available. This is important for two reason, first to make AOO
> > available
> > >> > in further languages to reach more users. Second to show our
> > volunteers
> > >> > that their work is appreciated and become integrated as soon as
> > >> > possible. We don't have a well defined process for doing it at moment
> > >> > but we will find a working way that will be ok for all of us. And we
> > can
> > >> > improve it over time when see demand for changes or improvements,
> > means
> > >> > we don't have to find a 100% perfect solution from the beginning.
> > >> >
> > >> > The most important part is how we do the naming of the different parts
> > >> > of such a release.
> > >> >
> > >> > I see two different scenarios:
> > >> >
> > >> > 1. Only new languages, no bugfixes, no other code changes
> > >> > We add the new languages on top of the existing AOO34 branch, build
> > the
> > >> > office with the new languages and release the new languages as
> > >> > convenience binary packages. We also build a new src release package
> > and
> > >> > add the revision number in the name to identify a respin of the
> > orginal
> > >> > 3.4.1.
> > >> >
> > >> > For example: aoo-3.4.1-rev1372282-src.tar.bz2
> > >> >
> > >> > This new src release becomes the default for 3.4.1 because it is a
> > >> > respin only (no functional changes)
> > >> >
> > >> > The revision number is part of the about dialog as well and it is
> > >> > possible to identify the respin.
> > >> >
> > >>
> > >> If we change the about dialog does this change anything else?  For
> > >> example, does it change what is written into ODF documents for the
> > >> creator string?  Does it cause AOO to report a different version to
> > >> scripts?  If we change anything more than the UI strings we risk
> > >> breaking 3rd party scripts who have logic tied to 3.4.0 or 3.4.1.
> > >>
> > >> -Rob
> > >>
> > >>
> > >> >
> > >> > 2. New languages + bug-fixes or security fixes
> > >> > The micro number will be increased and we do a normal release cycle.
> > >> > The src release will contain the revision number in future always.
> > >> >
> > >> >
> > >> >
> > >> > Concrete proposal for 3.4.1 and new languages:
> > >> >
> > >> > 1. set a deadline for new translations, for exmaple December 31, 2012
> > >> > 2. integrate the new languages and provide the builds until January
> > 10,
> > >> 2013
> > >> > 3. test and verify the new language builds asap
> > >> > 4. release the new languages at the end of January
> > >> >
> > >> >
> > >> > Why a deadline until December:
> > >> > The reason is quite simply, we have 22 languages with an UI coverage
> > of
> > >> > more than 95% (ok Turkish 93%). My plan is to prepare a blog entry and
> > >> > call again for volunteers for these languages where the effort is
> > >> > moderate. My hope is that we can integrate a few of the important
> > ones.
> > >> >
> > >> > UI coverage with more than 93%
> > >> > ==============================
> > >> > 100%: Danish
> > >> > 98%: Korean, Polish, Asturian, Uighur, Icelandic, Indonesian, Welsh,
> > >> > Catalan, Bulgarian, Latvian
> > >> > 97%: Greek, Basque
> > >> > 96%: English (South Africa)
> > >> > 95%: Portuguese, Swedish, Marathi, Kannada, Gujarati, Irish, Oriya
> > >> > 93%: Turkish
> > >> >
> > >> >
> > >> > Juergen
> > >>
> >

Less well informed users (i.e., the majority of ordinary, computer-unskilled users) expect to get a complete package for their language, with no extra downloading or customisation required.  Might it be possible to package the language packs in such a way that the "complete pack" consisted of the basic unit (en-US) and the specific Language add-on, and an "invisible" script automatically installed the Language add-on, thereby giving the same effect as a compiled national language version?

-- 
Rory O'Farrell <of...@iol.ie>

Re: [RELEASE]: new languages for AOO 3.4.1

[jan iversen <ja...@apache.org>]

Following your thought...

Would it not be an idea, if we defined the binary to be en-US always, and
then modify the installation scripts to include the proper language pack ??

Please see it as an open question, I do not know if there are other
implications. I have for some time (years) downloaded the en-US binary and
added the language pack, so technically it is possible.

Jan.

On 23 November 2012 15:47, Rob Weir <ro...@apache.org> wrote:

> On Fri, Nov 23, 2012 at 9:30 AM, jan iversen <ja...@apache.org> wrote:
> > If it is easier, we could keep the binary, and just release language
> > packs....a bit more uncomfortable but still an official release !
> >
>
> I'm just thinking ahead, to the very real possibility that we're
> adding new languages on a continual basis until we're shipping 100+ of
> them.  If that happens we're going to create absolute chaos if we
> encoding version changes in a way that appears externally to scripts,
> extensions, in documents, to upgrade servers, etc.  It will lead to a
> proliferation of version strings that will destroy us all.  This is
> what the Mayans were warning us about !!!
>
> (OK, maybe not that bad, but it would be quite a mess)
>
> But if we can consider these new languages to be merely the
> continuation of the 3.4.1 release, and an keep the external behavior
> of the program the same, then live is easy.  We can release full
> versions of Danish, etc., 3.4.1.  All we need to do is vote on a new
> source tarball which could be called AOO341-danish-patch.tgz or
> whatever.
>
> -Rob
>
>
> > Jan.
> >
> > On 23 November 2012 15:01, Rob Weir <ro...@apache.org> wrote:
> >
> >> On Fri, Nov 23, 2012 at 3:39 AM, Jürgen Schmidt <jo...@gmail.com>
> >> wrote:
> >> > Hi,
> >> >
> >> > we all know that the number of volunteers helping with translation is
> >> > growing and we would like to make new languages as soon as possible
> >> > available. This is important for two reason, first to make AOO
> available
> >> > in further languages to reach more users. Second to show our
> volunteers
> >> > that their work is appreciated and become integrated as soon as
> >> > possible. We don't have a well defined process for doing it at moment
> >> > but we will find a working way that will be ok for all of us. And we
> can
> >> > improve it over time when see demand for changes or improvements,
> means
> >> > we don't have to find a 100% perfect solution from the beginning.
> >> >
> >> > The most important part is how we do the naming of the different parts
> >> > of such a release.
> >> >
> >> > I see two different scenarios:
> >> >
> >> > 1. Only new languages, no bugfixes, no other code changes
> >> > We add the new languages on top of the existing AOO34 branch, build
> the
> >> > office with the new languages and release the new languages as
> >> > convenience binary packages. We also build a new src release package
> and
> >> > add the revision number in the name to identify a respin of the
> orginal
> >> > 3.4.1.
> >> >
> >> > For example: aoo-3.4.1-rev1372282-src.tar.bz2
> >> >
> >> > This new src release becomes the default for 3.4.1 because it is a
> >> > respin only (no functional changes)
> >> >
> >> > The revision number is part of the about dialog as well and it is
> >> > possible to identify the respin.
> >> >
> >>
> >> If we change the about dialog does this change anything else?  For
> >> example, does it change what is written into ODF documents for the
> >> creator string?  Does it cause AOO to report a different version to
> >> scripts?  If we change anything more than the UI strings we risk
> >> breaking 3rd party scripts who have logic tied to 3.4.0 or 3.4.1.
> >>
> >> -Rob
> >>
> >>
> >> >
> >> > 2. New languages + bug-fixes or security fixes
> >> > The micro number will be increased and we do a normal release cycle.
> >> > The src release will contain the revision number in future always.
> >> >
> >> >
> >> >
> >> > Concrete proposal for 3.4.1 and new languages:
> >> >
> >> > 1. set a deadline for new translations, for exmaple December 31, 2012
> >> > 2. integrate the new languages and provide the builds until January
> 10,
> >> 2013
> >> > 3. test and verify the new language builds asap
> >> > 4. release the new languages at the end of January
> >> >
> >> >
> >> > Why a deadline until December:
> >> > The reason is quite simply, we have 22 languages with an UI coverage
> of
> >> > more than 95% (ok Turkish 93%). My plan is to prepare a blog entry and
> >> > call again for volunteers for these languages where the effort is
> >> > moderate. My hope is that we can integrate a few of the important
> ones.
> >> >
> >> > UI coverage with more than 93%
> >> > ==============================
> >> > 100%: Danish
> >> > 98%: Korean, Polish, Asturian, Uighur, Icelandic, Indonesian, Welsh,
> >> > Catalan, Bulgarian, Latvian
> >> > 97%: Greek, Basque
> >> > 96%: English (South Africa)
> >> > 95%: Portuguese, Swedish, Marathi, Kannada, Gujarati, Irish, Oriya
> >> > 93%: Turkish
> >> >
> >> >
> >> > Juergen
> >>
>

Re: [RELEASE]: new languages for AOO 3.4.1

[Jürgen Schmidt <jo...@gmail.com>]

On 11/23/12 3:47 PM, Rob Weir wrote:
> On Fri, Nov 23, 2012 at 9:30 AM, jan iversen <ja...@apache.org> wrote:
>> If it is easier, we could keep the binary, and just release language
>> packs....a bit more uncomfortable but still an official release !
>>
> 
> I'm just thinking ahead, to the very real possibility that we're
> adding new languages on a continual basis until we're shipping 100+ of
> them.  If that happens we're going to create absolute chaos if we
> encoding version changes in a way that appears externally to scripts,
> extensions, in documents, to upgrade servers, etc.  It will lead to a
> proliferation of version strings that will destroy us all.  This is
> what the Mayans were warning us about !!!
> 
> (OK, maybe not that bad, but it would be quite a mess)
> 
> But if we can consider these new languages to be merely the
> continuation of the 3.4.1 release, and an keep the external behavior
> of the program the same, then live is easy.  We can release full
> versions of Danish, etc., 3.4.1.  All we need to do is vote on a new
> source tarball which could be called AOO341-danish-patch.tgz or
> whatever.
> 
> -Rob
> 
> 
>> Jan.
>>
>> On 23 November 2012 15:01, Rob Weir <ro...@apache.org> wrote:
>>
>>> On Fri, Nov 23, 2012 at 3:39 AM, Jürgen Schmidt <jo...@gmail.com>
>>> wrote:
>>>> Hi,
>>>>
>>>> we all know that the number of volunteers helping with translation is
>>>> growing and we would like to make new languages as soon as possible
>>>> available. This is important for two reason, first to make AOO available
>>>> in further languages to reach more users. Second to show our volunteers
>>>> that their work is appreciated and become integrated as soon as
>>>> possible. We don't have a well defined process for doing it at moment
>>>> but we will find a working way that will be ok for all of us. And we can
>>>> improve it over time when see demand for changes or improvements, means
>>>> we don't have to find a 100% perfect solution from the beginning.
>>>>
>>>> The most important part is how we do the naming of the different parts
>>>> of such a release.
>>>>
>>>> I see two different scenarios:
>>>>
>>>> 1. Only new languages, no bugfixes, no other code changes
>>>> We add the new languages on top of the existing AOO34 branch, build the
>>>> office with the new languages and release the new languages as
>>>> convenience binary packages. We also build a new src release package and
>>>> add the revision number in the name to identify a respin of the orginal
>>>> 3.4.1.
>>>>
>>>> For example: aoo-3.4.1-rev1372282-src.tar.bz2
>>>>
>>>> This new src release becomes the default for 3.4.1 because it is a
>>>> respin only (no functional changes)
>>>>
>>>> The revision number is part of the about dialog as well and it is
>>>> possible to identify the respin.
>>>>
>>>
>>> If we change the about dialog does this change anything else?  For
>>> example, does it change what is written into ODF documents for the
>>> creator string?  Does it cause AOO to report a different version to
>>> scripts?  If we change anything more than the UI strings we risk
>>> breaking 3rd party scripts who have logic tied to 3.4.0 or 3.4.1.

I don't think so but it is a good point and we have to check it.

Juergen

>>>
>>> -Rob
>>>
>>>
>>>>
>>>> 2. New languages + bug-fixes or security fixes
>>>> The micro number will be increased and we do a normal release cycle.
>>>> The src release will contain the revision number in future always.
>>>>
>>>>
>>>>
>>>> Concrete proposal for 3.4.1 and new languages:
>>>>
>>>> 1. set a deadline for new translations, for exmaple December 31, 2012
>>>> 2. integrate the new languages and provide the builds until January 10,
>>> 2013
>>>> 3. test and verify the new language builds asap
>>>> 4. release the new languages at the end of January
>>>>
>>>>
>>>> Why a deadline until December:
>>>> The reason is quite simply, we have 22 languages with an UI coverage of
>>>> more than 95% (ok Turkish 93%). My plan is to prepare a blog entry and
>>>> call again for volunteers for these languages where the effort is
>>>> moderate. My hope is that we can integrate a few of the important ones.
>>>>
>>>> UI coverage with more than 93%
>>>> ==============================
>>>> 100%: Danish
>>>> 98%: Korean, Polish, Asturian, Uighur, Icelandic, Indonesian, Welsh,
>>>> Catalan, Bulgarian, Latvian
>>>> 97%: Greek, Basque
>>>> 96%: English (South Africa)
>>>> 95%: Portuguese, Swedish, Marathi, Kannada, Gujarati, Irish, Oriya
>>>> 93%: Turkish
>>>>
>>>>
>>>> Juergen
>>>

Re: [RELEASE]: new languages for AOO 3.4.1

[Rob Weir <ro...@apache.org>]

On Fri, Nov 23, 2012 at 9:30 AM, jan iversen <ja...@apache.org> wrote:
> If it is easier, we could keep the binary, and just release language
> packs....a bit more uncomfortable but still an official release !
>

I'm just thinking ahead, to the very real possibility that we're
adding new languages on a continual basis until we're shipping 100+ of
them.  If that happens we're going to create absolute chaos if we
encoding version changes in a way that appears externally to scripts,
extensions, in documents, to upgrade servers, etc.  It will lead to a
proliferation of version strings that will destroy us all.  This is
what the Mayans were warning us about !!!

(OK, maybe not that bad, but it would be quite a mess)

But if we can consider these new languages to be merely the
continuation of the 3.4.1 release, and an keep the external behavior
of the program the same, then live is easy.  We can release full
versions of Danish, etc., 3.4.1.  All we need to do is vote on a new
source tarball which could be called AOO341-danish-patch.tgz or
whatever.

-Rob


> Jan.
>
> On 23 November 2012 15:01, Rob Weir <ro...@apache.org> wrote:
>
>> On Fri, Nov 23, 2012 at 3:39 AM, Jürgen Schmidt <jo...@gmail.com>
>> wrote:
>> > Hi,
>> >
>> > we all know that the number of volunteers helping with translation is
>> > growing and we would like to make new languages as soon as possible
>> > available. This is important for two reason, first to make AOO available
>> > in further languages to reach more users. Second to show our volunteers
>> > that their work is appreciated and become integrated as soon as
>> > possible. We don't have a well defined process for doing it at moment
>> > but we will find a working way that will be ok for all of us. And we can
>> > improve it over time when see demand for changes or improvements, means
>> > we don't have to find a 100% perfect solution from the beginning.
>> >
>> > The most important part is how we do the naming of the different parts
>> > of such a release.
>> >
>> > I see two different scenarios:
>> >
>> > 1. Only new languages, no bugfixes, no other code changes
>> > We add the new languages on top of the existing AOO34 branch, build the
>> > office with the new languages and release the new languages as
>> > convenience binary packages. We also build a new src release package and
>> > add the revision number in the name to identify a respin of the orginal
>> > 3.4.1.
>> >
>> > For example: aoo-3.4.1-rev1372282-src.tar.bz2
>> >
>> > This new src release becomes the default for 3.4.1 because it is a
>> > respin only (no functional changes)
>> >
>> > The revision number is part of the about dialog as well and it is
>> > possible to identify the respin.
>> >
>>
>> If we change the about dialog does this change anything else?  For
>> example, does it change what is written into ODF documents for the
>> creator string?  Does it cause AOO to report a different version to
>> scripts?  If we change anything more than the UI strings we risk
>> breaking 3rd party scripts who have logic tied to 3.4.0 or 3.4.1.
>>
>> -Rob
>>
>>
>> >
>> > 2. New languages + bug-fixes or security fixes
>> > The micro number will be increased and we do a normal release cycle.
>> > The src release will contain the revision number in future always.
>> >
>> >
>> >
>> > Concrete proposal for 3.4.1 and new languages:
>> >
>> > 1. set a deadline for new translations, for exmaple December 31, 2012
>> > 2. integrate the new languages and provide the builds until January 10,
>> 2013
>> > 3. test and verify the new language builds asap
>> > 4. release the new languages at the end of January
>> >
>> >
>> > Why a deadline until December:
>> > The reason is quite simply, we have 22 languages with an UI coverage of
>> > more than 95% (ok Turkish 93%). My plan is to prepare a blog entry and
>> > call again for volunteers for these languages where the effort is
>> > moderate. My hope is that we can integrate a few of the important ones.
>> >
>> > UI coverage with more than 93%
>> > ==============================
>> > 100%: Danish
>> > 98%: Korean, Polish, Asturian, Uighur, Icelandic, Indonesian, Welsh,
>> > Catalan, Bulgarian, Latvian
>> > 97%: Greek, Basque
>> > 96%: English (South Africa)
>> > 95%: Portuguese, Swedish, Marathi, Kannada, Gujarati, Irish, Oriya
>> > 93%: Turkish
>> >
>> >
>> > Juergen
>>

Re: [RELEASE]: new languages for AOO 3.4.1

[jan iversen <ja...@apache.org>]

If it is easier, we could keep the binary, and just release language
packs....a bit more uncomfortable but still an official release !

Jan.

On 23 November 2012 15:01, Rob Weir <ro...@apache.org> wrote:

> On Fri, Nov 23, 2012 at 3:39 AM, Jürgen Schmidt <jo...@gmail.com>
> wrote:
> > Hi,
> >
> > we all know that the number of volunteers helping with translation is
> > growing and we would like to make new languages as soon as possible
> > available. This is important for two reason, first to make AOO available
> > in further languages to reach more users. Second to show our volunteers
> > that their work is appreciated and become integrated as soon as
> > possible. We don't have a well defined process for doing it at moment
> > but we will find a working way that will be ok for all of us. And we can
> > improve it over time when see demand for changes or improvements, means
> > we don't have to find a 100% perfect solution from the beginning.
> >
> > The most important part is how we do the naming of the different parts
> > of such a release.
> >
> > I see two different scenarios:
> >
> > 1. Only new languages, no bugfixes, no other code changes
> > We add the new languages on top of the existing AOO34 branch, build the
> > office with the new languages and release the new languages as
> > convenience binary packages. We also build a new src release package and
> > add the revision number in the name to identify a respin of the orginal
> > 3.4.1.
> >
> > For example: aoo-3.4.1-rev1372282-src.tar.bz2
> >
> > This new src release becomes the default for 3.4.1 because it is a
> > respin only (no functional changes)
> >
> > The revision number is part of the about dialog as well and it is
> > possible to identify the respin.
> >
>
> If we change the about dialog does this change anything else?  For
> example, does it change what is written into ODF documents for the
> creator string?  Does it cause AOO to report a different version to
> scripts?  If we change anything more than the UI strings we risk
> breaking 3rd party scripts who have logic tied to 3.4.0 or 3.4.1.
>
> -Rob
>
>
> >
> > 2. New languages + bug-fixes or security fixes
> > The micro number will be increased and we do a normal release cycle.
> > The src release will contain the revision number in future always.
> >
> >
> >
> > Concrete proposal for 3.4.1 and new languages:
> >
> > 1. set a deadline for new translations, for exmaple December 31, 2012
> > 2. integrate the new languages and provide the builds until January 10,
> 2013
> > 3. test and verify the new language builds asap
> > 4. release the new languages at the end of January
> >
> >
> > Why a deadline until December:
> > The reason is quite simply, we have 22 languages with an UI coverage of
> > more than 95% (ok Turkish 93%). My plan is to prepare a blog entry and
> > call again for volunteers for these languages where the effort is
> > moderate. My hope is that we can integrate a few of the important ones.
> >
> > UI coverage with more than 93%
> > ==============================
> > 100%: Danish
> > 98%: Korean, Polish, Asturian, Uighur, Icelandic, Indonesian, Welsh,
> > Catalan, Bulgarian, Latvian
> > 97%: Greek, Basque
> > 96%: English (South Africa)
> > 95%: Portuguese, Swedish, Marathi, Kannada, Gujarati, Irish, Oriya
> > 93%: Turkish
> >
> >
> > Juergen
>

Re: [RELEASE]: new languages for AOO 3.4.1

[Rob Weir <ro...@apache.org>]

On Fri, Nov 23, 2012 at 3:39 AM, Jürgen Schmidt <jo...@gmail.com> wrote:
> Hi,
>
> we all know that the number of volunteers helping with translation is
> growing and we would like to make new languages as soon as possible
> available. This is important for two reason, first to make AOO available
> in further languages to reach more users. Second to show our volunteers
> that their work is appreciated and become integrated as soon as
> possible. We don't have a well defined process for doing it at moment
> but we will find a working way that will be ok for all of us. And we can
> improve it over time when see demand for changes or improvements, means
> we don't have to find a 100% perfect solution from the beginning.
>
> The most important part is how we do the naming of the different parts
> of such a release.
>
> I see two different scenarios:
>
> 1. Only new languages, no bugfixes, no other code changes
> We add the new languages on top of the existing AOO34 branch, build the
> office with the new languages and release the new languages as
> convenience binary packages. We also build a new src release package and
> add the revision number in the name to identify a respin of the orginal
> 3.4.1.
>
> For example: aoo-3.4.1-rev1372282-src.tar.bz2
>
> This new src release becomes the default for 3.4.1 because it is a
> respin only (no functional changes)
>
> The revision number is part of the about dialog as well and it is
> possible to identify the respin.
>

If we change the about dialog does this change anything else?  For
example, does it change what is written into ODF documents for the
creator string?  Does it cause AOO to report a different version to
scripts?  If we change anything more than the UI strings we risk
breaking 3rd party scripts who have logic tied to 3.4.0 or 3.4.1.

-Rob


>
> 2. New languages + bug-fixes or security fixes
> The micro number will be increased and we do a normal release cycle.
> The src release will contain the revision number in future always.
>
>
>
> Concrete proposal for 3.4.1 and new languages:
>
> 1. set a deadline for new translations, for exmaple December 31, 2012
> 2. integrate the new languages and provide the builds until January 10, 2013
> 3. test and verify the new language builds asap
> 4. release the new languages at the end of January
>
>
> Why a deadline until December:
> The reason is quite simply, we have 22 languages with an UI coverage of
> more than 95% (ok Turkish 93%). My plan is to prepare a blog entry and
> call again for volunteers for these languages where the effort is
> moderate. My hope is that we can integrate a few of the important ones.
>
> UI coverage with more than 93%
> ==============================
> 100%: Danish
> 98%: Korean, Polish, Asturian, Uighur, Icelandic, Indonesian, Welsh,
> Catalan, Bulgarian, Latvian
> 97%: Greek, Basque
> 96%: English (South Africa)
> 95%: Portuguese, Swedish, Marathi, Kannada, Gujarati, Irish, Oriya
> 93%: Turkish
>
>
> Juergen

Re: [RELEASE]: new languages for AOO 3.4.1

["Marcus (OOo)" <ma...@wtnet.de>]

Am 11/23/2012 09:39 AM, schrieb Jürgen Schmidt:
> Hi,
>
> we all know that the number of volunteers helping with translation is
> growing and we would like to make new languages as soon as possible
> available. This is important for two reason, first to make AOO available
> in further languages to reach more users. Second to show our volunteers
> that their work is appreciated and become integrated as soon as
> possible. We don't have a well defined process for doing it at moment
> but we will find a working way that will be ok for all of us. And we can
> improve it over time when see demand for changes or improvements, means
> we don't have to find a 100% perfect solution from the beginning.

Yes, let's start with this. Thanks for your proposal. I've some 
additional comments inline.

> The most important part is how we do the naming of the different parts
> of such a release.
>
> I see two different scenarios:
>
> 1. Only new languages, no bugfixes, no other code changes
> We add the new languages on top of the existing AOO34 branch, build the
> office with the new languages and release the new languages as
> convenience binary packages.

Please make sure to build not only langpacks but also full install 
builds. Otherwise the 1-click-download doesn't work for these new languages.

And they have to contain the same version number than the old files. 
Otherwise the download won't work, too. The DL scripts uses a single 
version number for all files.

 > We also build a new src release package and
> add the revision number in the name to identify a respin of the orginal
> 3.4.1.
>
> For example: aoo-3.4.1-rev1372282-src.tar.bz2
>
> This new src release becomes the default for 3.4.1 because it is a
> respin only (no functional changes)
>
> The revision number is part of the about dialog as well and it is
> possible to identify the respin.

I had a timpestamp in mind but the SVN rev. is much better.

> 2. New languages + bug-fixes or security fixes
> The micro number will be increased and we do a normal release cycle.
> The src release will contain the revision number in future always.

IMHO the src file should *always* contain the rev as an unique reference.

> Concrete proposal for 3.4.1 and new languages:
>
> 1. set a deadline for new translations, for exmaple December 31, 2012
> 2. integrate the new languages and provide the builds until January 10, 2013
> 3. test and verify the new language builds asap
> 4. release the new languages at the end of January

Sounds good to me.

Just to make sure to avoid any misunderstandings:
+1 for scenario 1.

> Why a deadline until December:
> The reason is quite simply, we have 22 languages with an UI coverage of
> more than 95% (ok Turkish 93%). My plan is to prepare a blog entry and
> call again for volunteers for these languages where the effort is
> moderate. My hope is that we can integrate a few of the important ones.
>
> UI coverage with more than 93%
> ==============================
> 100%: Danish
> 98%: Korean, Polish, Asturian, Uighur, Icelandic, Indonesian, Welsh,
> Catalan, Bulgarian, Latvian
> 97%: Greek, Basque
> 96%: English (South Africa)
> 95%: Portuguese, Swedish, Marathi, Kannada, Gujarati, Irish, Oriya
> 93%: Turkish

Good. Many more "nearly-perfect-languages" to come. :-)

Marcus