[Bug 28661] U+2212 in shift_jis encoder

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28661

--- Comment #24 from Jungshik Shin <jshin@chromium.org> ---
(In reply to Kent Tamura from comment #23)
> (In reply to Jungshik Shin from comment #20)
> > tkent@ : I couldn't enter U+2212 on Mac OS 10.10 with Japanese IME -
> > Hiragana, Romaji, Katakana (in both English UI and Japanese UI). Can you
> > tell me how to enter U+2212? 
> 
> Enable Hiragana with Kotoeri, or Hiragana with Google Japanese Input, then
> type "1-2-3".  It puts U+FF11 U+2212 U+FF12 U+2212 U+FF13.

Thank you. I couldn't get U+2212 because I just tried typing '-' by itself and
none of candidates was U+2212. In the context of '1-2-3', I do get U+2212 as
well as full-width digits. 

> > What I got is U+30FC (Hiragana-Katakana prolonged sound mark), which is
> > rather strange. 
> > 
> > BTW, one of choices I got for '~' with 'Hiragana' is  U+301C (Wave Dash),
> > which is not included in the current table for Shift_JIS although there's a
> > fallback mapping (encoding-only) in ICU's converter. (see the previous
> > comment).  Obviously, wave dash won't be used as often as U+2212 in postal
> > code.
> 
> Other one-way mapping characters are not important at all.  I have no idea
> of use cases in web forms.


Thank you for the answer. 

> (In reply to Jungshik Shin from comment #22)
> > While we're at it, I propose that we do the same for EUC-JP and ISO-2022-JP.
> > (add an one-way encoding-only mapping for U+2212). 
> 
> It's very reasonable.

I'll go ahead adding a one-way mapping (encoding-only) for U+2212 to all the
Japanese legacy encodings (ISO-2022-JP automatically gets it from Shift_JIS) in
Chrome's copy of ICU. (all these tables for the encoding spec will be
contributed back to ICU eventually along with the aliases table per spec.).

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Tuesday, 2 June 2015 17:27:38 UTC