6.0.0-beta1
▾
Tasks
New Task
Search
Photos
Wiki
▾
Tickets
New Ticket
Search
dev.horde.org
Toggle Alerts Log
Help
11/7/25
H
istory
A
ttachments
C
omment
W
atch
Download
Comment on [#10054] Subject didn't encode with attachment
*
Your Email Address
*
Spam protection
Enter the letters below:
.__.. .. ..__ .__ | ||\/||\/|[__)[__) |__\| || || [__)
Comment
> I think that it is Big-5 that use double-8it to encode one Chinese > word. Do you think that it is the reason caused this problem?? > In fact, I have thought that it might be the problem of Big-5 > charset. Therefore, i also tested for the UTF-8 charset. > Then, I found the same problem when using the UTF-8 charset. > > >> Is Big-5 one of those charsets that only contains ASCII characters, >> even though it represents an 8+bit representation? That would >> explain this behavior. See, e.g., Horde_mime::is8bit: >> >> /* ISO-2022-JP is a 7bit charset, but it is an 8bit >> representation so >> * it needs to be entirely encoded. */ >> return is_string($string) && >> ((stristr('iso-2022-jp', $charset) && >> (strstr($string, "\x1b\$B"))) || >> preg_match('/[\x80-\xff]/', $string)); >
Attachment
Watch this ticket
N
ew Ticket
M
y Tickets
S
earch
Q
uery Builder
R
eports
Saved Queries
Open Bugs
Bugs waiting for Feedback
Open Bugs in Releases
Open Enhancements
Enhancements waiting for Feedback
Bugs with Patches
Enhancements with Patches
Release Showstoppers
Stalled Tickets
New Tickets
Horde 5 Showstoppers