Skip to content
This repository has been archived by the owner on Dec 29, 2022. It is now read-only.

Suggestions for text fallback #142

Closed
GoogleCodeExporter opened this issue Jun 2, 2015 · 7 comments
Closed

Suggestions for text fallback #142

GoogleCodeExporter opened this issue Jun 2, 2015 · 7 comments

Comments

@GoogleCodeExporter
Copy link

These are suggestions for change that a Google contact for NTT docomo 
received from a docomo representative. They are mostly suggestions for text 
fallbacks. The *-ed ones represent a change from an Emoji fallback to text 
fallback.


1. e-043 LEAF FLUTTERING IN WIND: 〓 --> 風に舞う葉
2. e-047 PALM TREE: ビーチ --> ヤシ
3. e-049 EAR OF RICE: 〓 --> 稲穂
4. e-1A0 COUPLE: 〓 --> カップル
5. e-1A6 MAN WITH TURBAN: インド --> インド人
6. e-1B0 EXTRATERRESTRIAL ALIEN: UFO --> 宇宙人
7. e-1B4 INFORMATION DESK PERSON: 〓 --> 案内
8. e-1B5 GUARDSMAN: 〓 --> 衛兵
9. e-1C4 MONKEY FACE: 〓 --> サル
10. e-1CA HAMSTER: 〓 --> ハムスター

* 11. e-1D0 WOLF: docomo has an Emoji for this and is called 犬 (dog). We 
picked up that name from a docomo document. I am not sure if we should deal 
with this case like a text fallback case. The suggestion is change this to 
おおかみ (wolf).

* 12. e-32F FLUSHED FACE: うれしい顔 -->  熱, The same case as 3-1D0: 
WOLF. 
There is an Emoji assigned to this cell for docomo.

13. e-354 SEE NO EVIL MONKEY: 
見ないことを想起できる顔文字にすべきだと思い
ます。顔文字「(/_\)」は一般的に「見ない」ことをあらわ�
��ていますでしょう
か。

  ** should be a text fallback that represents "not seeing". Does the 
current fallback point to "not seeing"? 
  ** I had thought that we picked this up from some docomo publication?

14. e-4C6 STATUE OF LIBERTY: 〓 --> 自由の女神
15. e-4C7 MAP OF JAPAN: 地図 --> 日本地図
* 16. e-4FB FLASHLIGHT: 
#151(ひらめき)ではなく[懐中電灯]にしてはいかがで
しょうか。

(How about changing this to [懐中電灯] "flashlight". 

* 16. e-4FD SCROLL: 
#166(長音記号2)ではなく[スクロール]にしてはいかがで
しょうか。(Suggest a change to [スクロール] "scroll" from 
長音記号2 "macron 
2"

17. e-530 CHEERING MEGAPHONE: 
[スピーカ]ではなく[メガホン]にしてはいかがで
しょうか。

   Change from [スピーカ] "speaker" to [メガホン] "megaphone"

18. e-53C MINI DISC: 
[フロッピー]ではなく[MD]にしてはいかがでしょうか。

  Change from [フロッピー] "floppy" to [MD] "Mini Disc"

19. e-53F ROUND PUSHPIN: 
φではなく[画びょう]にしてはいかがでしょうか。

  Change from φto [画びょう] "push pin"


* 20. e-54D CARD INDEX: 
#70(本)ではなく[回転式名刺ホルダー]にしてはいかが
でしょうか

 Change from #70 本 "book" to [回転式名刺ホルダー] "revolving business card 
index"


21. e-552 BOOKMARK TABS : 
#76(本)ではなく[しおり]にしてはいかがでしょう
か。

  Change this from #76(本)"book" to [しおり] "bookmark"

  ** Note that we have docomo #76 as 'Book' (本)。Need to reconcile the 
difference also.

22. e-815 SAXOPHONE: 〓 --> [サックス]
23. e-81B PART ALTERNATION MARK: [グラフ] --> [歌記号]
24. e-82A WEDDING: 〓 --> 結婚式
25. e-B26 NO ENTRY: 
#Exp.36(NG)ではなく[立ち入り禁止]にしてはいかがでしょ
うか。

  How about changing this from #Exp.36(NG) to [立ち入り禁止] "entry 
prohibited"?

26. Ee-B4C EM SPACE: 〓 --> U+2003
27. e-B4D EN SPACE: 〓 --> U+2002
28. e-B4E FOUR-PER-EM SPACE: 〓 --> U+2005


Original issue reported on code.google.com by katmomoi on 31 Jan 2009 at 11:34

@GoogleCodeExporter
Copy link
Author

Is the fallback string a part of, or relevant to, the proposal ? 

Original comment by kida.ya...@gmail.com on 2 Feb 2009 at 3:36

@GoogleCodeExporter
Copy link
Author

> Is the fallback string a part of, or relevant to, the proposal ? 

No. However, it may be a good idea for us to maintain the definitive 
cross-mapping 
and text fallback tables for all to share. The issues described here can be 
dealt 
with outside of the timelines for the UTC/WG2 proposal.

Original comment by katmomoi on 2 Feb 2009 at 9:08

@GoogleCodeExporter
Copy link
Author

These are generally easy to change, and not part of nor critical for the 
proposal.

I think we should limit text fallbacks to characters that are in standard JIS X 
0208, 
so that they work in a Shift-JIS and ISO-2022-JP environment. For example, the 
spaces 
U+2002/2003/2005 are not in there. I should write a test for this.

Original comment by markus.icu on 2 Feb 2009 at 4:48

  • Added labels: Milestone-WG2-2009apr
  • Removed labels: Type-Defect

@GoogleCodeExporter
Copy link
Author

> No. However, it may be a good idea for us to maintain the definitive 
cross-mapping 
> and text fallback tables for all to share. 

understood.


Original comment by kida.ya...@gmail.com on 2 Feb 2009 at 4:54

@GoogleCodeExporter
Copy link
Author

In r186, I made the following changes:

1. e-043 LEAF FLUTTERING IN WIND: 〓 --> 風に舞う葉
2. e-047 PALM TREE: ビーチ --> ヤシ
3. e-049 EAR OF RICE: 〓 --> 稲穂
4. e-1A0 COUPLE: 〓 --> カップル
5. e-1A6 MAN WITH TURBAN: インド --> インド人
6. e-1B0 EXTRATERRESTRIAL ALIEN: UFO --> 宇宙人
7. e-1B4 INFORMATION DESK PERSON: 〓 --> 案内
8. e-1B5 GUARDSMAN: 〓 --> 衛兵
9. e-1C4 MONKEY FACE: 〓 --> サル
10. e-1CA HAMSTER: 〓 --> ハムスター

14. e-4C6 STATUE OF LIBERTY: 〓 --> 自由の女神
15. e-4C7 MAP OF JAPAN: 地図 --> 日本地図

17. e-530 CHEERING MEGAPHONE: 
[スピーカ]ではなく[メガホン]にしてはいかがで
しょうか。

   Change from [スピーカ] "speaker" to [メガホン] "megaphone"

18. e-53C MINI DISC: 
[フロッピー]ではなく[MD]にしてはいかがでしょうか。

  Change from [フロッピー] "floppy" to [MD] "Mini Disc"

19. e-53F ROUND PUSHPIN: 
φではなく[画びょう]にしてはいかがでしょうか。

  Change from φto [画びょう] "push pin"
22. e-815 SAXOPHONE: 〓 --> [サックス]
23. e-81B PART ALTERNATION MARK: [グラフ] --> [歌記号]
24. e-82A WEDDING: 〓 --> 結婚式

Other changes require additional considerations. I will work on them next but 
in 
another issue report.



Original comment by katmomoi on 3 Nov 2009 at 4:09

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author

Looks Good To Me

Original comment by markus.icu on 3 Nov 2009 at 10:41

  • Changed state: Verified

@GoogleCodeExporter
Copy link
Author

One correction. I did not make the following change:

6. e-1B0 EXTRATERRESTRIAL ALIEN: UFO --> 宇宙人

The reason is that e-1B1 (ALIEN MONSTER) has also the text fallback 宇宙人 
and it may 
be confusing to change e-1B0 to 宇宙人.

No changes will be made for the following:

26. Ee-B4C EM SPACE: 〓 --> U+2003
27. e-B4D EN SPACE: 〓 --> U+2002
28. e-B4E FOUR-PER-EM SPACE: 〓 --> U+2005


Since none of these fallback suggestions are in the Shift_JIS/JIS X 0208 set.


Original comment by katmomoi on 4 Nov 2009 at 7:13

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant