gedit l10n schemas is not registered

Bug #531155 reported by Nobuto Murata on 2010-03-03
22
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gconf (Ubuntu)
Medium
Unassigned
Declined for Lucid by Sebastien Bacher
Maverick
Medium
Unassigned
gedit (Ubuntu)
Low
Unassigned
Declined for Lucid by Sebastien Bacher
Maverick
Undecided
Unassigned

Bug Description

Binary package hint: casper

Expected result:
 1. boot from LiveCD
 2. choose language "日本語" (Japanese)
 3. execute the below line in terminal
  $ gconftool --get /apps/gedit-2/preferences/encodings/auto_detected
 4. get the value below
  [UTF-8,CURRENT,ISO-2022-JP,SHIFT_JIS,EUC-JP]

Actual result:
 4. get the value below
  [UTF-8,CURRENT,ISO-8859-15,UTF-16]

The value is defined in /usr/share/gconf/schemas/gedit.schemas.
But "$ gconftool --get" returns C locale's value in any locales because the schemas is not registered.

The schemas is necessary for auto detect encodings in each locale.

Last tested:
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110210)
both cases Live session and full-installed system.

ProblemType: Bug
Architecture: i386
Date: Wed Mar 3 06:52:00 2010
DistroRelease: Ubuntu 10.04
LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100302)
Package: casper 1.224
ProcEnviron:
 LANG=ja_JP.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
SourcePackage: casper
Uname: Linux 2.6.32-14-generic i686

Nobuto Murata (nobuto) wrote :
Emmet Hikory (persia) wrote :

Note that with this value set to the more limited character sets, many common text files distributed in Japan cannot be read by gedit.

Nobuto Murata (nobuto) wrote :

This bug might be related with Bug #531184.

Emmet Hikory (persia) wrote :

gedit should determine the filter set based on the user locale at runtime, rather than based on the system locale at install-time. In addition to fixing this issue, this would resolve issues where users need to open text files from foreign locales with appropriate locale variable adjustments being passed to gedit on initialisation.

affects: casper (Ubuntu) → gedit (Ubuntu)
Changed in gedit (Ubuntu):
status: New → Confirmed
Nobuto Murata (nobuto) wrote :

@Emmet
gedit has the function to determines the filter on the user locale at runtime via gconf,
if gedit.shemas is registered properly.

For example, if you install locales, English, Japanese, Bulgarian,
when you login with Japanese,
$ gconf --get /apps/gedit-2/preferences/encodings/auto_detected
returns [UTF-8,CURRENT,ISO-2022-JP,SHIFT_JIS,EUC-JP].
when you login with Bulgarian,
you get [UTF-8,WINDOWS-1251,CURRENT,ISO-8859-15,UTF-16].

Even if you login with Japanese,
$ LANG=bg_BG.UTF-8 gconf --get /apps/gedit-2/preferences/encodings/auto_detected
returns Bulgarian value.

Thus gedit can determine the filter by each user's locale.
With alternate CD this feature works perfectly.
So I assume that this bug is not gedit one.

Nobuto Murata (nobuto) on 2010-03-15
description: updated
tags: added: regression-potential
Nobuto Murata (nobuto) on 2010-03-15
description: updated
Sebastien Bacher (seb128) wrote :

you mean it broken between alpha2 and alpha3 in lucid?

Changed in gedit (Ubuntu):
importance: Undecided → Low
Nobuto Murata (nobuto) wrote :

> you mean it broken between alpha2 and alpha3 in lucid?

Yes.

Nobuto Murata (nobuto) wrote :

As I described in Bug #531184 (marked as duplicate),
This bug also takes effect after ubiquity install.
So users cannot use encoding auto detection unless executing dpkg-reconfigure.

Nobuto Murata (nobuto) on 2010-03-27
Changed in gedit (Ubuntu):
status: Confirmed → Invalid
Nobuto Murata (nobuto) wrote :

I customized LiveCD based on Lucid Alpha2 along the below instruction.
https://help.ubuntu.com/community/LiveCDCustomization

Then I found that upgrading gconf2 cause this bug.
I would assume that gconf2 between 2.28.0-1ubuntu2 and 2.28.0-1ubuntu4 breaks auto-detection feature.

Sebastien Bacher (seb128) wrote :

subscribing pitti to the bug who did the change which introduced the issue

Martin Pitt (pitti) wrote :

Do you have the Japanese language packs installed at that time?

Changed in gconf (Ubuntu):
assignee: nobody → Martin Pitt (pitti)
importance: Undecided → Medium
status: New → In Progress
status: In Progress → Triaged
Martin Pitt (pitti) wrote :

Note to self: Check if install-language-pack needs to call update-schemas --all

Nobuto Murata (nobuto) wrote :

> Do you have the Japanese language packs installed at that time?

Live session: NO
After Ubiquity install: YES

Japanese language packs is installed during Ubiquity install.
Though after reboot, gedit's schemas not registered.

Pedro Villavicencio (pedro) wrote :

This is still an issue? can you please confirm ? thanks.

Changed in gconf (Ubuntu):
status: Triaged → Incomplete
Nobuto Murata (nobuto) on 2010-10-08
summary: - gedit schemas is not registered during live session
+ gedit l10n schemas is not registered
description: updated
Nobuto Murata (nobuto) wrote :

This issue is still reproducible in Maverick latest build. (sorry for late testing)
http://cdimage.ubuntu.com/daily-live/20101007/maverick-desktop-i386.iso

gedit l10n schemas is not registered both in LiveCD and after ubuntu-installation with language-packs.

Changed in gconf (Ubuntu):
status: Incomplete → Confirmed
tags: added: regression-release
removed: regression-potential
Changed in gconf (Ubuntu Maverick):
status: New → Confirmed
importance: Undecided → Medium
Nobuto Murata (nobuto) on 2011-02-15
description: updated
Martin Pitt (pitti) on 2011-03-18
Changed in gconf (Ubuntu):
assignee: Martin Pitt (pitti) → nobody
Nobuto Murata (nobuto) wrote :

Maverick is no longer supported and gedit now uses gsettings not gconf. Closing.

Changed in gedit (Ubuntu Maverick):
status: New → Invalid
Changed in gconf (Ubuntu):
status: Confirmed → Invalid
Changed in gconf (Ubuntu Maverick):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers