Skip to content

Commit deec9f1

Browse files
committed
Merge pull request bitcoin#130 from bip39JP/master
BIP39: Clarify necessity for ideographic spaces.
2 parents 272d9cf + 144ef37 commit deec9f1

File tree

2 files changed

+650
-648
lines changed

2 files changed

+650
-648
lines changed

bip-0039/bip-0039-wordlists.md

+6-4
Original file line numberDiff line numberDiff line change
@@ -11,10 +11,12 @@
1111

1212
###Japanese
1313

14-
1. Users will most likely separate the words with UTF-8 ideographic space.
15-
(UTF-8 bytes: 0xE38080) When generating the seed, normalization as per the spec will
16-
automatically change these into normal ASCII spaces. Depending on the font, displaying the
17-
words should use the UTF-8 ideographic space if it looks like the symbols are too close.
14+
1. **Developers implementing phrase generation or checksum verification must separate words using ideographic spaces / accommodate users inputting ideographic spaces.**
15+
(UTF-8 bytes: **0xE38080**; C/C+/Java: **"\u3000"**; Python: **u"\u3000"**)
16+
However, code that only accepts Japanese phrases but does not generate or verify them should be fine as is.
17+
This is because when generating the seed, normalization as per the spec will
18+
automatically change the ideographic spaces into normal ASCII spaces, so as long as your code never shows the user an ASCII space
19+
separated phrase or tries to split the phrase input by the user, dealing with ASCII or Ideographic space is the same.
1820

1921
2. Word-wrapping doesn't work well, so making sure that words only word-wrap at one of the
2022
ideographic spaces may be a necessary step. As a long word split in two could be mistaken easily

0 commit comments

Comments
 (0)