Oneiric reached EOL.
** Changed in: gedit (Ubuntu Oneiric)
Status: Confirmed = Won't Fix
** No longer affects: gedit (Ubuntu Oneiric)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
Since this bug:
- Is valid.
- Is well described.
- Is reported in the upstream project.
- Is ready to be worked on by a developer.
It's already triaged.
** Changed in: gedit (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
** Changed in: gedit (Ubuntu)
Status: Incomplete = Confirmed
** Changed in: gedit (Ubuntu Oneiric)
Status: Incomplete = Confirmed
** Tags added: precise quantal raring
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
This problem is partially worked around by not-so-recent translation change in
upstream.
https://git.gnome.org/browse/gedit/tree/po/zh_CN.po#n424
Such translation is included in 3.6.1 tarball already but Unfortunately
Ubuntu 12.10, even claim to have Gedit 3.6.1, doesn't seem to get that
from
The link http://people.canonical.com/~ycmiao/lp819714/ is broken.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/819714
Title:
Can not display GB2312/GB18030 encoded chinese files
Well, I'd say an ideal solution would be for gedit to detect the
encoding by itself, and thus avoid all these tricky configurations. I've
experimented a bit with universalchardet, which comes with Mozilla
project, and its separate library libuchardet. I found it to be smart
enough in most cases.
I've uploaded testing packages to
http://people.canonical.com/~ycmiao/lp819714/, please help test.
Note it's for precise, and one needs to install libuchardet0 firstly.
$ sudo apt-get install libuchardet0
$ sudo dpkg --install gedit*~lp819714_*.deb
--
You received this bug notification
The attachment uchardet.diff of this bug report has been identified as
being a patch. The ubuntu-reviewers team has been subscribed to the bug
report so that they can review the patch. In the event that this is in
fact not a patch you can resolve this situation by removing the tag
'patch' from
** Changed in: gedit (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/819714
Title:
Can not display GB2312/GB18030 encoded chinese files
To
** Tags added: qin
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/819714
Title:
Can not display GB2312/GB18030 encoded chinese files
To manage notifications about this bug go to:
Not sure how gedit3 is supposed to work, it seems the old gconf key
which has the encoding order got deprecated
** Also affects: gedit
Importance: Undecided
Status: New
** Changed in: gedit (Ubuntu)
Importance: Undecided = High
** Also affects: gedit (Ubuntu Oneiric)
Importance:
Ok, in fact they are still there, could you run that on Oneiric with a Chinese
installation:
gsettings get org.gnome.gedit.preferences.encodings auto-detected
** Changed in: gedit (Ubuntu Oneiric)
Status: New = Incomplete
--
You received this bug notification because you are a member of
The key should be set to something similar to what was pointed before,
i.e [CURRENT,GB18030,GBK,GB2312,UTF-8,UTF-16] so GB18030 encoding is
used before UTF ones
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
I just tested opening the gb180130.txt file in oneiric alpha3. Here are
my findings:
For auto detect of a new encoding to work in gedit, one must do two things:
* Add the encoding in gedit (Open Character Encodings Add/Remove add
desired encoding)
- Note that after this step the value of
Hi Hou,
I just tested the default setting in the gedit package,
[CURRENT,GB18030,GBK,GB2312,UTF-8,UTF-16]
All of GB18030,GBK,GB2312,UTF-8 and UTF-16 characters can be displayed.
[UTF-8,CURRENT,ISO-8859-15,UTF-16,GB2312,GBK,GB18030]
Your config maybe have some problem, did you test the case, if
http://bazaar.launchpad.net/~ubuntu-china-devs/ubuntu-chinese/ubuntu-
chinese-default-settings/view/head:/debian/gconf-defaults
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/819714
Gedit indeed can display all gb18030 encoded files, it support gb18030 encoding
very well.
But gedit in ubuntu can not do this -:(
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
The file opens fine on my Oneiric installation if I do this:
- run gedit
- click open
- select in the encoding combo add and add GB18030
- select that encoding in the combo
- select the file
it renders like it is on the screenshot then
is there a way to detect that a file is GB18030 in a
Sebastien,
Yes, you are right, if the user know the encoding of the file, they can open it
with gedit.
But not all of them know what's the encoding, so automatic detect mode is the
most user case.
Gedit has a auto detect sequence recorded in gconf, the correct value is
I'm sorry, typing mistaken, the correct value is
[CURRENT,GB18030,GBK,GB2312,UTF-8,UTF-16]
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/819714
Title:
Can not display
can encoding be automatically be detected though? the gconf key you list
is by local and suggest that chinese install should use gb encoding
before utf8 so the example should open fine?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
In /usr/share/gconf/schemas/gedit.schemas, it can set different key
value of auto_detected according to the local settings.
For example, when the LANG=zh_CN, the following will be set:
locale name=zh_CN
default[CURRENT,GB18030,GBK,GB2312,UTF-8,UTF-16]/default
/locale
postinst scripts of
So I guess, if the LANG environment were set to zh_CN, you can create a
release CD with the right settings of gedit.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/819714
Title:
Can
right, that's getting confusing though, what issue do you try to solve
or what are you asking for there? gedit should already do the right
thing when using a zh_CN locale and open files in gb encoding which is
rated before utf for that locale
--
You received this bug notification because you are
Sebastien,
I just want to contribute to Qin-ubuntu project(a Chinese locale edition
of ubuntu), but I do not know who is the right person should notice this
problem, Martin Pitti or somebody else?
And of cause, this bug should influence on any other local editions of
ubuntu, I hope the guy there
The default value of auto_detected is [UTF-8,CURRENT,ISO-8859-15,UTF-16], no
matter which language were used.
I think something is wrong in ubuntu, but I don't know who sould be involved.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
is the issue specific to the liveCD or also on the installed system?
What version of Ubuntu do you use?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/819714
Title:
Can not display
I tested it from lucid to natty, no matter CD or DVD edition, no matter
x86 or x86_64 edition, all of them have this bug.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/819714
Title:
is the issue specific to liveCD sessions or also on the installed
system?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/819714
Title:
Can not display GB2312/GB18030 encoded chinese
both of them.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/819714
Title:
Can not display GB2312/GB18030 encoded chinese files
To manage notifications about this bug go to:
** Attachment added: gb18030.txt
https://bugs.launchpad.net/bugs/819714/+attachment/2249112/+files/gb18030.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/819714
Title:
Can
My local settings:
LANG=zh_CN.UTF-8
LANGUAGE=zh_CN:en_US:en
LC_CTYPE=zh_CN.UTF-8
LC_NUMERIC=zh_CN.UTF-8
LC_TIME=zh_CN.UTF-8
LC_COLLATE=zh_CN.UTF-8
LC_MONETARY=zh_CN.UTF-8
LC_MESSAGES=zh_CN.UTF-8
LC_PAPER=zh_CN.UTF-8
LC_NAME=zh_CN.UTF-8
LC_ADDRESS=zh_CN.UTF-8
LC_TELEPHONE=zh_CN.UTF-8
The content of gb18030.txt should like this picture.
** Attachment added: Screenshot-gb18030.txt
(~-文档-unicode-chinese-encoding-examples) - gedit.png
Hi,
Is it possible that the characters do not display simply because there
is no font installed that provides a glyph for the code point?
(I notice when looking in the character map application, there are many
Chinese characters that appear to have no glyph, for example UFACE has
a glyph but
在 2011-08-02二的 19:41 +，Kyle Nitzsche写道：
Hi,
Is it possible that the characters do not display simply because there
is no font installed that provides a glyph for the code point?
Sure, It's possible.
But wqy fonts include all glyphs in CJK UNIFIED IDEOGRAPHs and extension
B.
It's enough
I'm sorry, wqy fonts include all glyphs in CJK UNIFIED IDEOGRAPHs and extension
A.
CJK UNIFIED IDEOGRAPHs extension B/C is optional.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
36 matches
Mail list logo
