change status to Fix released (see gnome-bug)
** Changed in: evolution (Ubuntu)
Status: Triaged => Invalid
** Changed in: evolution (Ubuntu)
Status: Invalid => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assign
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/21000144/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/21000145/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/21000146/ProcStatus.txt
--
couldn
** Bug watch added: GNOME Bug Tracker #559282
http://bugzilla.gnome.org/show_bug.cgi?id=559282
** Also affects: evolution via
http://bugzilla.gnome.org/show_bug.cgi?id=559282
Importance: Unknown
Status: Unknown
--
couldn't change character encoding set for the subject of the mess
** Changed in: evolution
Status: Unknown => New
--
couldn't change character encoding set for the subject of the message sended by
evolution
https://bugs.launchpad.net/bugs/314953
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to ev
thanks for the report, that's known upstream you can track it here:
http://bugzilla.gnome.org/show_bug.cgi?id=559282
** Changed in: evolution (Ubuntu)
Importance: Undecided => Low
Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
Status: New => Triaged
--
couldn't chang
Although they seem related, it seems Evolution has specified which
characters are allowed in a http link. I feel better programming would
be to specify which characters are NOT allowed.
i.e: Only space should mark the end of a http link
--
couldn't change character encoding set for the subject o
Am I only one that thinks that upstream bug report
https://bugzilla.gnome.org/show_bug.cgi?id=442934 is unrelated to this
bug report ? This bug report is about message headers created by
Evolution. The upstream bug report is about wrongly formatted headers
received by Evolution.
--
You received t
** Changed in: evolution
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/314953
Title:
couldn't change character encoding set for the subject of the message
send
Still present in Evolution 2.26.1 Jaunty, making impossible to
communicate with other Czech enterprises and do not look like a dork.
Seriously, Czech text in subject may look strange for a stranger, but
not _this_ strange: "ZŘUD - už je to lepš�"
--
couldn't change character encoding set for
Upstream bug has been marked as duplicate of bug
https://bugzilla.gnome.org/show_bug.cgi?id=442934
** Bug watch added: GNOME Bug Tracker #442934
http://bugzilla.gnome.org/show_bug.cgi?id=442934
** Changed in: evolution
Status: New => Unknown
** Changed in: evolution
Remote watch: GNOM
** Changed in: evolution
Status: Unknown => New
--
couldn't change character encoding set for the subject of the message sended by
evolution
https://bugs.launchpad.net/bugs/314953
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
** Changed in: evolution
Importance: Unknown => Medium
--
couldn't change character encoding set for the subject of the message sended by
evolution
https://bugs.launchpad.net/bugs/314953
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assigne
12 matches
Mail list logo
