Poké Transporter: Difference between revisions
From Bulbapedia, the community-driven Pokémon encyclopedia.
Jump to navigationJump to search
Blueapple128 (talk | contribs) |
Blueapple128 (talk | contribs) |
||
| Line 76: | Line 76: | ||
A name consisting of only spaces, which is only possible in Generation I, will remain unchanged. If a Pokémon has <code>{{PK}}</code>, <code>{{MN}}</code>, <code>[</code>, <code>]</code>, or <code>×</code> in its [[nickname]] or [[original Trainer]], this will be converted to <code>P</code>, <code>M</code>, <code>(</code>, <code>)</code>, or <code>x</code>, respectively, upon being transported. | A name consisting of only spaces, which is only possible in Generation I, will remain unchanged. If a Pokémon has <code>{{PK}}</code>, <code>{{MN}}</code>, <code>[</code>, <code>]</code>, or <code>×</code> in its [[nickname]] or [[original Trainer]], this will be converted to <code>P</code>, <code>M</code>, <code>(</code>, <code>)</code>, or <code>x</code>, respectively, upon being transported. | ||
In Japanese, between September 22, 2017 and November 19, 2017 (after {{game|Gold and Silver|s}} were released on the [[Virtual Console]] but before they were directly compatible with Poké Transporter), transferring a Pokémon from a Virtual Console game with an exclamation point or question mark in its nickname or OT would cause these characters to be converted into spaces. (This required trading the Pokémon to a Generation I Virtual Console game and then transferring through Poké Transporter. The Japanese Generation II games allow entering exclamation points/question marks but the Japanese Generation I games do not. This did not occur in other languages, presumably because it is possible to enter exclamation points/question marks in Generation I in those languages.) Conversely, the kana を / ヲ ''wo'' and small vowel katakana did not have this issue despite also being characters that could be entered in Japanese Generation II but not Japanese Generation I. This was later fixed. | In Japanese, between September 22, 2017 and November 19, 2017 (after {{game|Gold and Silver|s}} were released on the [[Virtual Console]] but before they were directly compatible with Poké Transporter), transferring a Pokémon from a Virtual Console game with an exclamation point or question mark in its nickname or OT would cause these characters to be converted into spaces.<ref>https://twitter.com/QStheSLAYER/status/911462759451189253</ref> (This required trading the Pokémon to a Generation I Virtual Console game and then transferring through Poké Transporter. The Japanese Generation II games allow entering exclamation points/question marks but the Japanese Generation I games do not. This did not occur in other languages, presumably because it is possible to enter exclamation points/question marks in Generation I in those languages.) Conversely, the kana を / ヲ ''wo'' and small vowel katakana did not have this issue despite also being characters that could be entered in Japanese Generation II but not Japanese Generation I. This was later fixed. | ||
In the [[character encoding (Generation I)|Generation I]] and [[Character encoding (Generation II)|Generation II character encoding]]s, several pairs of hiragana and katakana share the same code points due to being rendered the same way in-game; in later generations, this is not the case, with each character having its own code point. These characters are the {{wp|hiragana}} <code>へ</code> (including <code>べ</code> and <code>ぺ</code>) and <code>り</code> and the {{wp|katakana}} <code>ヘ</code> (including <code>ベ</code> and <code>ペ</code>) and <code>リ</code>. Poké Transporter converts the character to hiragana or katakana depending on the first character of the Pokémon's name that is not a space or a {{wp|chōonpu}} (<code>ー</code>). If the first character is hiragana (other than the four kana in question), the character is converted to hiragana <code>へ</code> or <code>り</code>; if the first character is katakana or any of the four kana in question, the character is converted to katakana. | In the [[character encoding (Generation I)|Generation I]] and [[Character encoding (Generation II)|Generation II character encoding]]s, several pairs of hiragana and katakana share the same code points due to being rendered the same way in-game; in later generations, this is not the case, with each character having its own code point. These characters are the {{wp|hiragana}} <code>へ</code> (including <code>べ</code> and <code>ぺ</code>) and <code>り</code> and the {{wp|katakana}} <code>ヘ</code> (including <code>ベ</code> and <code>ペ</code>) and <code>リ</code>. Poké Transporter converts the character to hiragana or katakana depending on the first character of the Pokémon's name that is not a space or a {{wp|chōonpu}} (<code>ー</code>). If the first character is hiragana (other than the four kana in question), the character is converted to hiragana <code>へ</code> or <code>り</code>; if the first character is katakana or any of the four kana in question, the character is converted to katakana. | ||
| Line 252: | Line 252: | ||
|} | |} | ||
This filter is applied after converting characters such as <code>{{PK}}</code>. For unknown reasons, since the Generation VII update, the filter is no longer applied to {{wp|kana}} in nicknames or OTs, and Poké Transporter will not inform the user. (The filter is still applied | This filter is applied after converting characters such as <code>{{PK}}</code>. For unknown reasons, since the Generation VII update, the filter is no longer applied to {{wp|kana}} in nicknames or OTs, and Poké Transporter will not inform the user.<ref>https://twitter.com/SnorlaxMonster/status/826808898816323584</ref><ref>https://twitter.com/SnorlaxMonster/status/827005974196019200</ref> (The filter is still applied to {{wp|Hangul}} and Poké Transporter informs the user.<ref>https://imgur.com/Hd4PkYW</ref>) | ||
===Location data=== | ===Location data=== | ||
