Talk:㌬
Latest comment: 7 years ago by Daniel Carrero in topic ㌬
㌬
[edit]I have reverted your edit. I don’t think redirect can cover the information in this case. — TAKASUGI Shinji (talk) 08:15, 28 January 2017 (UTC)
- @TAKASUGI Shinji And do you see the page パーツ yet? I already move info there. --Octahedron80 (talk) 15:07, 28 January 2017 (UTC)
- I didn’t check it, but why should ㌬ be redirected to パーツ knowing it is an error? — TAKASUGI Shinji (talk) 15:24, 28 January 2017 (UTC)
- Because Unicode maps the symbol to the decomposition: 30D1 30FC 30C4 = パーツ paatsu, as shown in the glyph. And it has never changed since version 1. --Octahedron80 (talk) 15:32, 28 January 2017 (UTC)
- Prima facie, I'd support redirecting ㌬ to パーツ (with pa instead of ba), because the single character appears to be just another way to present the characters "パーツ". I also support having usage notes at パーツ to convey the intended use of the single character as バーツ (with ba).
- But, I'm curious if there are 3 citations with ㌬ meaning baht in running text. Maybe that would justify having a separate sense in some way. --Daniel Carrero (talk) 15:37, 28 January 2017 (UTC)
- Because of the error, no one uses the Unicode character ㌬, but on newspaper you can find the square character バーツ (baht). It is a common practice on newspaper to use square characters for currency units, like ㌦ and ㍀. It will take time to find one because you have to check scanned paper, not digital texts. As far as I know, there is no square character for パーツ (parts) on printed media. — TAKASUGI Shinji (talk) 01:27, 29 January 2017 (UTC)
- At this moment, the entry ㌬ has only one sense: "baht. Note: this character is erroneously registered as パーツ." It gives the impression that people use a square パーツ for that unit, which seems like a mistake. Someone learning Japanese might have the impression that it's OK to use ㌬ for the currency unit. If the entry ㌬ were discussed in an RFV, I'd specifically like to see a few citations with ㌬ used as a currency unit. If we find three citations for a square バーツ, in my opinion they won't serve the purpose of citing ㌬.
- If we find three citations for a square バーツ (which apparently does not exist in Unicode), will we want to create a separate entry for it regardless? Correct me if I'm wrong, but it seems just a specific arrangement and size of letters, so it seems like we shouldn't have a separate entry for it.
- In my opinion, the entry パーツ should mention the existence of the Unicode character ㌬ regardless of whether the ㌬ is citable or not, just because it's a different way to write the same word. --Daniel Carrero (talk) 02:06, 29 January 2017 (UTC)
- Because of the error, no one uses the Unicode character ㌬, but on newspaper you can find the square character バーツ (baht). It is a common practice on newspaper to use square characters for currency units, like ㌦ and ㍀. It will take time to find one because you have to check scanned paper, not digital texts. As far as I know, there is no square character for パーツ (parts) on printed media. — TAKASUGI Shinji (talk) 01:27, 29 January 2017 (UTC)
- Because Unicode maps the symbol to the decomposition: 30D1 30FC 30C4 = パーツ paatsu, as shown in the glyph. And it has never changed since version 1. --Octahedron80 (talk) 15:32, 28 January 2017 (UTC)
- I didn’t check it, but why should ㌬ be redirected to パーツ knowing it is an error? — TAKASUGI Shinji (talk) 15:24, 28 January 2017 (UTC)
I have a question but you don't need to answer. When Japaneses realize that the symbol ㌬ is made by error, but why don't they propose the Unicode Consortium to correct it since 1991 and do leave it until today? --Octahedron80 (talk) 02:02, 29 January 2017 (UTC)
- From what I remember, the name of Unicode characters can't be changed or corrected. --Daniel Carrero (talk) 02:08, 29 January 2017 (UTC)
- Characters can be changed if they have consensus. Many characters are changed in their names since version 1.1.5. (and also their properties). Unicode have ever moved a script to another range. --Octahedron80 (talk) 02:16, 29 January 2017 (UTC)
- Please say one Unicode character that got its name changed. --Daniel Carrero (talk) 02:21, 29 January 2017 (UTC)
- ㄱ U+3131 HANGUL LETTER KIYEOK is firstly named as HANGUL LETTER GIYEOG, for example. --Octahedron80 (talk) 02:24, 29 January 2017 (UTC)
- ij U+0133 LATIN SMALL LIGATURE IJ is firstly named as LATIN SMALL LETTER I J, for example. --Octahedron80 (talk) 02:26, 29 January 2017 (UTC)
- Having a lot of them ([1]). You can check with BabelMap (its creator). --Octahedron80 (talk) 02:29, 29 January 2017 (UTC)
- They have simply decided not using it: [2]. This character should probably be RFVed. No one would find its usage for “parts”. — TAKASUGI Shinji (talk) 02:48, 29 January 2017 (UTC)
- ^ And they don't even produce the correct 'baht' character in Unicode either. OMG. However, the 'parts' is commented in Unicode's document. --Octahedron80 (talk) 02:52, 29 January 2017 (UTC)
- @TAKASUGI Shinji: If the RFV of ㌬ meaning "parts" passes (hypothetically), what happens? It's OK if we want to keep separate entries for these katakana boxes, but personally I'd rather redirect them to the main entries like パーツ, as I said above. That way, apparently it doesn't matter if that RFV passes or fails. --Daniel Carrero (talk) 02:59, 29 January 2017 (UTC)
- Technically, it is acceptable to redirect ㌬ to パーツ based on Unicode specification. But we have to explain that it is a ghost character never used, and it has nothing to do with the word パーツ. — TAKASUGI Shinji (talk) 09:12, 29 January 2017 (UTC)
- @TAKASUGI Shinji: I'm okay with that. --Daniel Carrero (talk) 09:24, 29 January 2017 (UTC)
- Technically, it is acceptable to redirect ㌬ to パーツ based on Unicode specification. But we have to explain that it is a ghost character never used, and it has nothing to do with the word パーツ. — TAKASUGI Shinji (talk) 09:12, 29 January 2017 (UTC)
- @TAKASUGI Shinji: If the RFV of ㌬ meaning "parts" passes (hypothetically), what happens? It's OK if we want to keep separate entries for these katakana boxes, but personally I'd rather redirect them to the main entries like パーツ, as I said above. That way, apparently it doesn't matter if that RFV passes or fails. --Daniel Carrero (talk) 02:59, 29 January 2017 (UTC)
- Please say one Unicode character that got its name changed. --Daniel Carrero (talk) 02:21, 29 January 2017 (UTC)
- Characters can be changed if they have consensus. Many characters are changed in their names since version 1.1.5. (and also their properties). Unicode have ever moved a script to another range. --Octahedron80 (talk) 02:16, 29 January 2017 (UTC)