Closed
Bug 1068510
Opened 11 years ago
Closed 11 years ago
React to the removal of ARMSCII8
Categories
(MailNews Core :: Internationalization, defect)
MailNews Core
Internationalization
Tracking
(Not tracked)
RESOLVED
FIXED
Thunderbird 37.0
People
(Reporter: hsivonen, Assigned: mkmelin)
Details
Attachments
(1 file)
|
3.83 KB,
patch
|
jcranmer
:
review+
|
Details | Diff | Splinter Review |
Bug 1067911 removed ARMSCII8. My understanding is that non-Gecko-based software has never supported this encoding except unknowingly via font hacks, so even though Thunderbird previously offered this encoding in the message compose encoding menu, I think Thunderbird should not keep this encoding.
comm-central should either
1) Remove this encoding form charsetalias.properties and the like. (Preferred.)
OR
2) Import the removed encoding into comm-central.
| Reporter | ||
Updated•11 years ago
|
Blocks: cc-backlog
| Reporter | ||
Comment 1•11 years ago
|
||
| Assignee | ||
Comment 2•11 years ago
|
||
There's no refs to this in comm-central anymore. And I agree we shouldn't import the encoder.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 36.0
| Assignee | ||
Comment 3•11 years ago
|
||
I was wrong - mxr lied.
Leave out the 8 and you get some hits, add the -8 and there are none:
<http://mxr.mozilla.org/comm-central/search?string=ARMSCII&find=&findi=&filter=^[^\0]*%24&hitlimit=&tree=comm-central>
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Target Milestone: Thunderbird 36.0 → ---
| Assignee | ||
Comment 4•11 years ago
|
||
Attachment #8529258 -
Flags: review?(Pidgeot18)
| Assignee | ||
Updated•11 years ago
|
Assignee: nobody → mkmelin+mozilla
Status: REOPENED → ASSIGNED
Updated•11 years ago
|
Attachment #8529258 -
Flags: review?(Pidgeot18) → review+
| Assignee | ||
Comment 5•11 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 37.0
Updated•11 years ago
|
No longer blocks: cc-backlog
You need to log in
before you can comment on or make changes to this bug.
Description
•