![[TEST] Document Foundation Community](https://communitytest.documentfoundation.org/images/discourse-logo-sketch.png){kind=logo}
Thanks everyone for their reply
Sveinn those are the exact folders that I was looking for.
Also, I do find it a bit weird that I couldn't even find the 'gn' package
on the pre-release packages.
Is there anything I can do?
It might be a different issue on Ubuntu. Or indeed, two.
1) As far as I remember, Ubuntu is usually several versions behind the latest LO
releases, something about stability before they release into Ubuntu. So it may
be some time before LO on Ubuntu progresses to the version you're working on.
2) We had a problem with gd which had to do with Debian (I think, I'll check
when I'm back on my desktop). If I recall rightly, in order for your langpacks
to be included on Ubuntu, the locale has to be added to Debian in some way. So
it may be the case that gn (like gd previously) is missing in some Debian list
of locales.
I'll check my emails and follow up on 2) unless someone else can remember in
more detail and/or check for gn.
Michael
Ok, back home, found it. Here's the exchange which finally solved the headache of why it wasn't getting into Ubuntu for gd:
Hi,
Why is our locale (gd) missing?
Ubuntu essentially ships the same l10n as debian does:
Usually both of us consider shipping a locale when it is reasonably complete.
... if we notice.
As gd seems reasonably complete:
Ah, 100% in 4.1.x and 4.2.x.
we might add it to the shipped locales.
@Rene: Any objections here?
I checked gn using the same links someone eventually threw at me:
http://packages.ubuntu.com/search?keywords=libreoffice-l10n-gn
https://packages.debian.org/search?keywords=libreoffice-l10n-gn
Neither place seems to 'have' gn. I tried but I never found out what exactly the 'cutoff' is for 'reasonably complete'.
I just checked the 4.3.5. Windows installer, which doesn't have Guaraní yet. I would probably get it into Windows builds to begin with as that seems an easier first step and then look into Ubuntu?
Michael
Hello Michael
I don't think its a Ubuntu issue. I was checking the languages available
for the 4.4 version (
http://www.libreoffice.org/download/libreoffice-fresh/?lang=pick) and it
doesn't show up there either nor on
http://dev-builds.libreoffice.org/pre-releases/
I am not quite sure what the problem might be.
Hi Giovanni,
Hello Michael
I don't think its a Ubuntu issue. I was checking the languages available
for the 4.4 version (
http://www.libreoffice.org/download/libreoffice-fresh/?lang=pick) and it
doesn't show up there either nor on
http://dev-builds.libreoffice.org/pre-releases/I am not quite sure what the problem might be.
Have you read https://wiki.documentfoundation.org/LibreOffice_Localization_Guide/Adding_a_New_Language_or_Locale
? Source code modifications are required to add a new language. Please
submit locale data.
Best regards,
Andras
Hello Andras
Thanks for the tip. I just finished and uploaded to bugzilla.
Hi 
So is the problem is solved for now? I think if Andras' tip didn't
work then it would be a new issue and worthy of a new thread in a
month or so or whenever the translation should appear.
Regards from
Tom
Bugzilla already claims they have a Guarani Locale.
*"We already have gug-PY locale data, see
https://gerrit.libreoffice.org/gitweb?p=core.git;a=blob;f=i18npool/source/localedata/data/gug_PY.xml;hb=HEAD
<https://gerrit.libreoffice.org/gitweb?p=core.git;a=blob;f=i18npool/source/localedata/data/gug_PY.xml;hb=HEAD>*
That looks like Guaraní-Paraguay
If I remember rightly, Guaraní is used across several countries so the question is, are you translating into a 'generic' Guaraní that anyone can understand irrespective of the country or are you doing a specific variety such as Paraguayan G, Argentinian G or Bolivian G?
If you're doing an over-regional localization into Guaraní then I think we should get gn added rather than using the specific gug-PY.
Michael
Sgrìobh Giovanni Caligaris na leanas 23/01/2015 aig 13:01:
I am only doing a Paraguayan-Guarani translation.
In this case it would be good to use the specific "gug" language code
everywhere. I was looking fog "gn" in locale data, that's why I asked
you, if you have had it submitted.
I can add Guarani translations to the build (to master for the time
being) in the next days.
Regards,
Andras
Thanks a lot Andras
Hi Giovanni,
> I am only doing a Paraguayan-Guarani translation.
In this case it would be good to use the specific "gug" language code
everywhere. I was looking fog "gn" in locale data, that's why I asked
you, if you have had it submitted.I can add Guarani translations to the build (to master for the time
being) in the next days.Regards,
AndrasThanks a lot Andras
I added Guarani UI translation to the build. See
https://gerrit.libreoffice.org/gitweb?p=core.git;a=commit;h=b68ecae158c327c3fd85de9d2babb657ae97da1d
Now you can configure master to build Guarani UI with the following
autogen.sh switch:
--with-lang=en-US gug
I think it is enough to have it in master only, because only 15% is
translated. Localized betas of LibreOffice 4.5 will be released in
May.
Also I renamed language code 'gn' to 'gug' in translations module:
https://gerrit.libreoffice.org/gitweb?p=translations.git;a=commit;h=b88d2877688f4d01d3f054a4fd0246b2159136c3
Cloph, can you please rename 'gn' to 'gug' in Pootle, too? 'gn' is the
code of Guarani macrolanguage, and 'gug' is specifically Guarani in
Paraguay. We use the 'gug' code at all places in source code (it was
added earlier).
Best regards,
Andras
Hi,
couple questions.
Shouldn't we use the short locale code when it is available (in this case, gn instead of gug)?
Also, shouldn't we treat one of the Guarani locales as the base one (that is, use only the language code for it, without specifying the region code)? I'm not speaking with absolute certainty here, but I only know one exception to this rule of thumb so far (Chinese).
Either way, gug-PY looks superfluous: gug already means "Paraguayan Guarani", according to ISO 639-3.
Rimas