** Changed in: gedit
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/75151
Title:
Refuses to open files where the character encoding is not recognised
To
** Tags added: raring saucy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/75151
Title:
Refuses to open files where the character encoding is not recognised
To manage notifications about this bug
Marking as Fix Released
** Changed in: gedit (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/75151
Title:
Refuses to open files where the character
@Vadim
i've opened a similar bug #930601 you have already reviewed, and this one still
have not been fixed by gnome (still wishlist).
If i've not had such issue with 3.2.3 (it was able to open files without
crashing, even sometimes it was complaining about binaries).
So 3.3.3 is again a
Same issue, with oldish workaround
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/67844
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/75151
Title:
Refuses to open files where the character
Can't reproduce this in gedit 3.3.3, can somebody else confirm?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/75151
Title:
Refuses to open files where the character encoding is not recognised
To
Can't reproduce it In gedit 3.2.3. You can open any file, gedit gives a
warning that continuing may corrupt the file, an edit anyway option
has been added. So yaay!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I get gedit has not been able to detect the character encoding at
first, and then once I choose a character encoding, Could not open the
file %s using the %s character encoding. I cannot attach the files that
trigger the bug due to copyright or confidentiality. Should I make a
stripped-down
I also tried to open a supposed-to-be text file. Apparently it contains
one or more 'illegal' characters. The program should not patronize its
users. A warning is ok, but in the end the decision to open the file
should be up to the user.
--
You received this bug notification because you are a
I've attached one file that is supposed to be a text file, but
apparently has 'nul' characters in it. It's a log from Microsoft IIS
6.0. The thing that really annoys me is that I can see the file for a
little bit when I click Retry.
The error I'm getting is
Could not open the file ftp://---.
Could people experiencing this bug please specify which of these three
error messages you receive when you try to open your file (from gedit-
io-error-message-area.c):
gedit has not been able to detect the character encoding.
Please check that you are not trying to open a binary file.
Select a
The thing is, this probably isn't actually a bug, but rather a
misfeature, and the it's not a bug, it's a feature mentality is
probably responsible for the fact that it has gone unfixed so long. I
see no evidence that the behavior gedit exhibits here wasn't intended.
If it *were* a bug, it would
I have a document which survives unmodified through iconv -c -f UTF-8
-t US-ASCII yet gedit still refuses to open it. Kate opens in read-
only mode, while vim doesn't display any warnings. The file contains
two null bytes. Please change this from an error to a warning.
--
You received this
Alternatively, allow the document to be opened read-only.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/75151
Title:
Refuses to open files where the character encoding is not recognised
--
How do you use that patch?
--
Refuses to open files where the character encoding is not recognised
https://bugs.launchpad.net/bugs/75151
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This is the dumbest damn issue I've ever seen.
I can see the document I want to view before gedit obscures it with a
warning.
gedit, throw me a bone here, I'm working!
--
Refuses to open files where the character encoding is not recognised
https://bugs.launchpad.net/bugs/75151
You received
This is the dumbest damn issue I've ever seen.
I can see the document I want to view before gedit obscures it with a
warning.
gedit, throw me a bone here, I'm working!
--
Refuses to open files where the character encoding is not recognised
https://bugs.launchpad.net/bugs/75151
You received
** Changed in: gedit
Importance: Unknown = Wishlist
--
Refuses to open files where the character encoding is not recognised
https://bugs.launchpad.net/bugs/75151
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Tags added: patch-forwarded-upstream
--
Refuses to open files where the character encoding is not recognised
https://bugs.launchpad.net/bugs/75151
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
That or convert the invalid code units to Unicode private use
characters.
--
Refuses to open files where the character encoding is not recognised
https://bugs.launchpad.net/bugs/75151
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
this is a enhancement request and not a blocker for jaunty, rejecting
the nomination.
--
Refuses to open files where the character encoding is not recognised
https://bugs.launchpad.net/bugs/75151
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This patch replaces NUL bytes with '?' character. This should allow you
to at least view every type of file. There is no warning that the NUL
bytes have been replaced, so be careful not to save over the original.
** Attachment added: gedit-nul-patch.diff
This issue has been open for almost 4 years now upstream, with no
indication of it ever being fixed.
The most annoying thing is that Ubuntu uses gedit as default text
editor, so users get bitten by this usability snafu often. If upstream
is unwilling to fix, perhaps a different text editor should
** Changed in: gedit (Ubuntu)
Status: Confirmed = Triaged
--
Refuses to open files where the character encoding is not recognised
https://bugs.launchpad.net/bugs/75151
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
As pointed by the bug watch opened that's known upstream:
http://bugzilla.gnome.org/show_bug.cgi?id=156199
** Changed in: gedit (Ubuntu)
Importance: Undecided = Wishlist
Assignee: (unassigned) = Ubuntu Desktop Bugs
--
Refuses to open files where the character encoding is not recognised
25 matches
Mail list logo
