Gnome bug was migrated to Gitlab (over at
https://gitlab.gnome.org/GNOME/glib/issues/54 ) and the bug number
changed as a result. Currently the close bug (due to being migrated)
seems to result in it being set expired all the time.
** Changed in: gvfs
Importance: Low => Undecided
** Changed in
Upstream bug URL changed to
https://gitlab.gnome.org/GNOME/glib/issues/54
Unable to edit it...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/378783
Title:
xdg-open *.desktop opens text
I haven't reported it to Debian, I did not have a test system to confirm
that it is present there as well (I'm quite sure it would be present, it
is the same package source) (And https://www.debian.org/Bugs/Reporting
for manual reporting seems quite scary...)
--
You received this bug notification
@Roland: Incorrect upstream, that is python-html2text /
python3-html2text. This is from http://www.mbayer.de/html2text/ (And
that won't have the issue, since it was introduced in Debian's UTF-8
patch) (Debian might also be affected though)
--
You received this bug notification because you are a m
Also affects 1.3.2a-18 on Ubuntu 16.04.
** Description changed:
When running html2text on a file with incorrect encoding (e.g. indicated
as us-ascii, but actually UTF-8), it fails with an error message but
returns a successful result code (0).
Actual output:
-
$ htm
Note: This is probably also present in Debian, since it seems like the
Ubuntu package is mostly unmodified.
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to htm
My attempt at an actual patch.
The other method, of actually changing all the error handling to save
that there have been an error and returning the code at the end might
still make sense for later.
** Patch added: "Patch to modify patches to return an error code on recoding
errors"
https://
Diffs for patch files: (for simple fix - return 2 for recoding error,
don't attempt to continue to other files) (The problem seems to be
present to at least the precise version)
--- 611-recognize-input-encoding.patch.orig 2016-03-31 18:25:01.914598768
+0200
+++ 611-recognize-input-encoding.pa
The simplest fix is to replace the "continue" in the recode error
handlers with "exit(1)" (Patched html2text.C lines 595 and 555). (Using
a different value for encoding errors might be useful)
This makes the error handling consistent with other cases, like failing
to open a file. (See line 482)
A
Quick method to test:
sudo apt-get install html2text
curl -s https://launchpadlibrarian.net/250515419/test.html | html2text; echo $?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to html2text in Ubuntu.
https://bugs.launchpad.net/bugs/1564
Public bug reported:
When running html2text on a file with incorrect encoding (e.g. indicated
as us-ascii, but actually UTF-8), it fails with an error message but
returns a successful result code (0).
Actual output:
-
$ html2text test.html; echo $?
Input recoding failed due to inv
11 matches
Mail list logo
