Update of bug #15074 (project mhonarc):
Status: None => Confirmed
_______________________________________________________
Follow-up Comment #1:
Not sure if it worth the effort to fix this bug. If TEXTENCODE
is enabled, this problem does not exist since all non-ASCII
encoded text is decoded when messages are read.
When TEXTENCODE is disabled (the default), mhonarc stores
subject text in "raw" form, which may include non-ascii encoding.
The resource variable resolution does not check for non-ascii
encodings. It could be added, but it complicates things and
increases processing overhead. Details of why it complicates
things can be provided if interested.
The work-around solution is to enable TEXTENCODE, or whatever
is processing the subsequent URL is modified to deal
with non-ASCII encoded text.
(Note, DECODEHEADS can provide a partial solution for
selected charsets.)
Unless there is an overwhelming need, I will probably not
fix this bug and call it a limitation instead :)
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?func=detailitem&item_id=15074>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
