The firefox translation should actually be provided by language-pack-crh-base.
Although the .xpi was imported on the 8th, firefox translation still wasn't
provided by language-pack-crh-base after last Friday's full export from
launchpad.
If it's still possible to fix up language-pack-crh-base p
I am now aware that apparently language-support-crh package isn't
related to gdm languages list, but the following is probably still
related to this bug:
The firefox .xpi import has succeeded, but apparently it's not been released w/
04/10 full export from launchpad. The following package is stil
I was kinda tilted to thinking in that direction after seeing this bug upstream:
https://alioth.debian.org/tracker/index.php?func=detail&aid=311588&group_id=30316&atid=413077
I guess what you mean is that that bug refers to another distro, where
gdm uses iso-codes, and it doesn't apply to Ubuntu y
Reşat SABIQ wrote:
> I wonder whether upgrading
> http://packages.ubuntu.com/jaunty/iso-codes
> which is currently based on 3.6, to 3.7 or 3.8 would resolve the gdm
> languages list issue, although the only additional relevant thing provided w/
> those releases is crh.po files.
>
> P.S.
> I don
I wonder whether upgrading
http://packages.ubuntu.com/jaunty/iso-codes
which is currently based on 3.6, to 3.7 or 3.8 would resolve the gdm languages
list issue, although the only additional relevant thing provided w/ those
releases is crh.po files.
P.S.
I don't know whether it matters, but I d
I forgot to mention: i'm wondering if ; character in language name spelling
might be causing such hard to diagnose side effects, because it appears to be a
"reserved" character at least in one the files involved.
Please feel free to change ; to another character, which should be OK
temporarily,
I'm wondering if there is any way to get the gdm languages list issue resolved
before final jaunty release, for which apparently the time is running out.
I'm busy trying to do some last minute translations, but if there's anything i
can do to help resolve the gdm issue, please let me know.
Than
** Changed in: langpack-o-matic
Status: In Progress => Triaged
--
Please enable language support for Crimean Tatar (Crimean Turkish) locale (crh)
https://bugs.launchpad.net/bugs/335307
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Despite my inability to manually get it to work, as mentioned in my last
comment, Martin might well be right about /etc/gdm/locale.conf being the
roadblock, and it might start working when the package is built in a manner
that addresses this.
I hope this can be addressed in gdm in time for jaun
FYI, i have tried adding the following manually to this apparently generated
file, but it did NOT resolve the gdm issue:
Crimean_Tatar;_Crimean_Turkish(Ukraine) crh_UA
Crimean_Tatar;_Crimean_Turkish(Ukraine) crh_UA.UTF-8
I gave it about 30 minutes, maybe i missed something, but it doesn't
appear
Indeed, crh needs to be added to /etc/gdm/locale.conf .
** Also affects: gdm (Ubuntu)
Importance: Undecided
Status: New
--
Please enable language support for Crimean Tatar (Crimean Turkish) locale (crh)
https://bugs.launchpad.net/bugs/335307
You received this bug notification because y
Reşat SABIQ wrote:
> Btw., i don't think .orth could be causing gdm language selection issues, but
> is there any chance that it could be a factor?
> https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/339396
I don't think that's related.
It seems to be a gdm bug, I'm currently trying to co
Btw., i don't think .orth could be causing gdm language selection issues, but
is there any chance that it could be a factor?
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/339396
Thanks.
--
Please enable language support for Crimean Tatar (Crimean Turkish) locale (crh)
https://bugs.l
I see that language-support-crh doesn't appear to affect the remaining
gdm issue, but after spending many hours on it today, i still see that
the following issue is outstanding:
crh isn't listed among available languages in the gdm login screen, even
after adding language support for crh locale. S
The non-GNOME package exists now: https://launchpad.net/ubuntu/+source
/language-pack-crh
So this should be working for crh now.
** Changed in: language-pack-gnome-crh (Ubuntu)
Status: Confirmed => Fix Released
--
Please enable language support for Crimean Tatar (Crimean Turkish) locale
Reşat SABIQ wrote:
> Turns out when i posted my last update on 03-21, 2 out of 3 packages
> were already available since 03-16. This was a good news, because now
> language support can be added as user-default language once the user is
> logged on.
>
> However, the following package is still not a
Turns out when i posted my last update on 03-21, 2 out of 3 packages
were already available since 03-16. This was a good news, because now
language support can be added as user-default language once the user is
logged on.
However, the following package is still not available:
language-support-crh
> OK, the issue is, that the -base package is not generated. We will fix this
> in langpack-o-matic, which builds the
> packages.
Pleaease tell me that this is on track for Crimean Tatar (Crimean
Turkish) language support to be available with the Jaunty release? I
hope very much to be able to tes
Just a bit more info, in case it's relevant. Alacarte package for some
reason doesn't have a .po import from upstream, although gnome-panel,
which upstream was translated later than alacarte, does have a .po
import from upstream. If this tells you anything, please take it into
account. If not, then
** Changed in: langpack-o-matic
Status: New => In Progress
--
Please enable language support for Crimean Tatar (Crimean Turkish) locale (crh)
https://bugs.launchpad.net/bugs/335307
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
OK, the issue is, that the -base package is not generated. We will fix
this in langpack-o-matic, which builds the packages.
** Also affects: langpack-o-matic
Importance: Undecided
Status: New
** Changed in: langpack-o-matic
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed
Also, will users be able to add Crimean Tatar (Crimean Turkish) support from
Language Support menu item once 1 or more of the following packages are
released:
language-pack-crh
language-pack-crh-base
language-support-crh
Just want to make sure whether this is the only "missing link".
Thanks.
-
Hi Arne,
Did you mean you this would be released in mid-March? I tried it today, and no
changes yet: crh is still not available in language selector. Which l10n
packages are available also hasn't changed since Feb. 27:
Available (these packages started to get built in October of last year):
lang
Arne Goetje wrote:
> Anyways, it will be fixed with the next full export, which might happen
> tonight UTC time. We will probably have language packs for crh available
> at the beginning of next week.
OK, make that "end of next week"... there is currently some trouble on
the Launchpad side and I n
Please no patch!
Language packs are generated entirely automatic.
The reason why crh is missing, is that it either didn't have any
translations in Launchpad when the first -base packages were built, or
that they were missing in the full export from Launchpad.
Anyways, it will be fixed with the n
Please let me know if i should attach a patch for this. I could easily make
both packages by tweaking a currently supported locale, and attaching a .tar.
Just 1 question:
Should the contents of
language-pack-crh-base:data/crh/LC_MESSAGES
be included in such a patch?
Thanks.
--
Please enable l
Linking to language selector: that's the best i can think of at the
moment.
** Changed in: language-selector (Ubuntu)
Sourcepackagename: None => language-selector
--
Please enable language support for Crimean Tatar (Crimean Turkish) locale (crh)
https://bugs.launchpad.net/bugs/335307
You receive
27 matches
Mail list logo
