Thanks!
On Sun, Mar 30, 2014 at 8:03 AM, Daniel Narvaez wrote:
> I think upstream should definitely include all the translations. It's up
> to distributions to exclude some languages if they want to... It's even
> supported by image composing tools usually, I think.
>
> I posted pull requests t
I think upstream should definitely include all the translations. It's up to
distributions to exclude some languages if they want to... It's even
supported by image composing tools usually, I think.
I posted pull requests to modernize our setup to use LINGUAS, add the
missing translations and alway
dnarvaez,
Any idea about what should we do with this?
Gonzalo
On Wed, Mar 26, 2014 at 9:23 PM, Gonzalo Odiard wrote:
> Yes, but is not a problem in the rpm, but in the sources repository.
>
> Gonzalo
>
>
> On Wed, Mar 26, 2014 at 8:15 PM, Jerry Vonau wrote:
>
>> The hint was given in the initi
Yes, but is not a problem in the rpm, but in the sources repository.
Gonzalo
On Wed, Mar 26, 2014 at 8:15 PM, Jerry Vonau wrote:
> The hint was given in the initial email, alter ALL_LINGUAS= in
> /configure.ac
>
> Jerry
>
> > On March 26, 2014 at 1:27 PM Gonzalo Odiard
> > wrote:
> >
> >
> >
The hint was given in the initial email, alter ALL_LINGUAS= in
/configure.ac
Jerry
> On March 26, 2014 at 1:27 PM Gonzalo Odiard
> wrote:
>
>
> Maybe the reason is we don't have en_GB in the variable ALL_LINGUAS in
> the
> Makefile.in
> in sugar/po directory.
>
> In my system:
> * we have a fil
Maybe the reason is we don't have en_GB in the variable ALL_LINGUAS in the
Makefile.in
in sugar/po directory.
In my system:
* we have a file en_GB.po sugar-build/sugar/po/
* the file is not copied
in sugar-build/build/out/install/share/locale/en_GB/LC_MESSAGES
not sure how Makefile.in is created
Looks like we need a file po/LINGUAS
Anybody have a idea about why we don't have one?
Gonzalo
On Wed, Mar 26, 2014 at 3:27 PM, Gonzalo Odiard wrote:
> Maybe the reason is we don't have en_GB in the variable ALL_LINGUAS in the
> Makefile.in
> in sugar/po directory.
>
> In my system:
> * we hav
I know there is no translations for en_AU in Pootle therefore not in sugar,
but en_GB was used in the past as a substitute for this shortcoming. There
are languages in Pootle that form the source tar file that becomes part of
the source rpm, however the resulting installable rpm doesn't ship all th
We do not have an en_AU language project in Pootle, so that does not
surprise me.
On Wed, Mar 26, 2014 at 12:10 PM, Jerry Vonau wrote:
> That is strange, I don't see en_AU's translation file when extracting the
> files from the released rpm[1]. The src[2] rpm's tar file only lists en_GB
> and en_
On Wed, Mar 26, 2014 at 7:59 AM, Gonzalo Odiard wrote:
> I think was done to preserve space.
> Not sure if that is a concern now.
>
Yep. It was definitely a concern for XO-1 and for XO-1.5 images for 2GB
machines.
m
--
martin.langh...@gmail.com
- ask interesting questions
- don't get dis
There are not en_AU in http://translate.sugarlabs.org/ neither.
Maybe was just en_GB?
Gonzalo
On Wed, Mar 26, 2014 at 1:10 PM, Jerry Vonau wrote:
> That is strange, I don't see en_AU's translation file when extracting the
> files from the released rpm[1]. The src[2] rpm's tar file only lists e
That is strange, I don't see en_AU's translation file when extracting the
files from the released rpm[1]. The src[2] rpm's tar file only lists en_GB
and en_USA, but those are not in the released rpm and not en_AU at all.
Jerry
1.
http://harvest.one-education.org/public/au1b-updates/RPMS/sugar-0.1
They did when DX4 was used, not now.
Jerry
> On March 26, 2014 at 8:59 AM Chris Leonard
> wrote:
>
>
> I believe AU makes their own build with en_GB.
>
> cjl
>
>
> On Wed, Mar 26, 2014 at 9:33 AM, Jerry Vonau wrote:
> > Just wondering how AU is reacting without having the correct spelling
> > f
We included en_AU, but not en_GB.
Will be in the next image.
Gonzalo
On Wed, Mar 26, 2014 at 10:59 AM, Chris Leonard wrote:
> I believe AU makes their own build with en_GB.
>
> cjl
>
>
> On Wed, Mar 26, 2014 at 9:33 AM, Jerry Vonau wrote:
> > Just wondering how AU is reacting without having th
http://bugs.sugarlabs.org/ticket/4743
Jerry
> On March 26, 2014 at 8:48 AM Gonzalo Odiard
> wrote:
>
>
> Honestly, they didn't complained yet.
> Thanks for pointing that.
>
> Gonzalo
>
>
> On Wed, Mar 26, 2014 at 10:33 AM, Jerry Vonau wrote:
>
> > Just wondering how AU is reacting without havin
I believe AU makes their own build with en_GB.
cjl
On Wed, Mar 26, 2014 at 9:33 AM, Jerry Vonau wrote:
> Just wondering how AU is reacting without having the correct spelling for
> 'favourites', 'neighbourhood' that comes with en_BR. This is a regression
> from DX4 that included such support. I
Honestly, they didn't complained yet.
Thanks for pointing that.
Gonzalo
On Wed, Mar 26, 2014 at 10:33 AM, Jerry Vonau wrote:
> Just wondering how AU is reacting without having the correct spelling for
> 'favourites', 'neighbourhood' that comes with en_BR. This is a regression
> from DX4 that i
Just wondering how AU is reacting without having the correct spelling for
'favourites', 'neighbourhood' that comes with en_BR. This is a regression
from DX4 that included such support. It would be better would really
support en_AU thou.
just my thoughts,
Jerry
> On March 26, 2014 at 6:59 AM Gonz
I think was done to preserve space.
Not sure if that is a concern now.
Gonzalo
On Sun, Mar 9, 2014 at 8:43 PM, me wrote:
> Hi All:
>
> I'm wondering if there is any reason why there are po files generated for
> the source in git, these are included as .mo files in the src rpm, but not
> shippe
Hi All:
I'm wondering if there is any reason why there are po files generated for
the source in git, these are included as .mo files in the src rpm, but not
shipped in the released rpms. Compare the list in git[1] and what becomes
installed in the resulting rpm through "ALL_LINGUAS="[2]. Is there
20 matches
Mail list logo
