28. KDE kwidgetsaddons ????? ??
Sorry, I did not notice this review request earlier.
I have to reject addition of new fields for now, because this will break distributions that update the data file separately from the
library code. There is unfortunately no version number information in the data file to be able to handle additions (or reject the
file). In worst case, the code can simply crash when mixing incompatible versions.
The current vision that I am working on is:
- new data format that allows us to include missing blocks, e.g. the CJK Extension B-F and ancient scripts
- split the data files into multiple files, e.g. one for Unihan data, one for ancient scripts, one for ConScript etc.
- allow selection of Unihan code points ordered by KangXi radicals and stroke count (kRSUnicode field)
- filter by kIICore or other useful properties
If you have additional ideas which other k* fields from Unihan.txt for CJK languages are useful to be included in KCharSelect,
your input is welcome either on kde-utils-devel list, or on kde-frameworks list.
??: https://git.reviewboard.kde.org/r/129245/
35. GNOME Gucharmap ??? ?? ?? ??
? Refer Link: https://github.com/GNOME/gucharmap/pull/1?
Forked My Github repository: https://github.com/studioego/gucharmap
? Unihan_Readings.txt included in Unihan.zip defines the notation and pronunciation of East Asian languages such as Chinese, Japanese, Korean, Vietnamese.
? Unihan_Readings.txt’ has some properties.Such askCantonese, kDefinition, kHangul, kHanyuPinlu, kHanyuPinyin, kJapaneseKun, kJapaneseOn, kKorean, kMandarin, kTang,
kVietnamese, kXHC1983.
? I add Unihan_Readings.txt defined kVietnamese property and kHangul property in this program.
? Unihan_Readings.txt’s property kVietnamese describe Vietnamese character(Qu?c ng?) pronunciation. this property defined Unihan version 3.1.1. Now Unihan database
version is 9.0.0.
? Unihan_Readings.txt’s property kHangul describe Korean character(??,Hangul) describe Korean pronunciation for this character in hangul.(Hangul is Korean Alphabet) this
property defined Unihan version 5.0. Now Unihan database version is 9.0.0.
? Why do I add kHangul(Korean Alphabet[Hangul]) property? Because, Unicode Consortium presented kHangul property on Unihan version 5. Unicode Unihan database
document ( http://www.unicode.org/reports/tr38/ ) describe “kKorean” property. “kKorean property’s description” The Korean pronunciation(s) of this character, using the
Yale romanization system. (See http://en.wikipedia.org/wiki/Korean_romanization for a discussion of the various Korean romanization systems.) Use of the kKorean field is
not recommended. The kHangul field, which is aligned to the KS X 1001 and KS X 1002 standards, is recommended to be used instead.
? Now, Revised Romanization of Korean (RR, also called South Korean or Ministry of Culture (MC) 2000) is the most commonly used and widely accepted system of
romanization for Korean instead of "Yale romanization system"[kKorean property] in Unihan database.
? So, I add kHangul property and add “Korean Alphabet(Hangul)” notation.
? Why do i add kVietnamese(Vietnamese pronunciation[Qu?c ng?]) property? “Unicode Consortium’s version9 guide chapter18. East Asia shows these paragraph. In Vietnam,
a set of native ideographs was created for Vietnamese based on the same principles used to create new ideographs for Chinese. These Vietnamese ideographs were used
through the beginning of the 20th century and are occasionally used in more recent signage and other limited contexts.
? Although the term “CJK”—Chinese, Japanese, and Korean—is used throughout this text to describe the languages that currently use Han ideographic characters, it should be
noted that earlier Vietnamese writing systems were based on Han ideographs. Consequently, the term “CJKV” would be more accurate in a historical sense. Han ideographs
are still used for historical, religious, and pedagogical purposes in Vietnam. “
? So I read Unihan documentation specification, then support Vietnamese language
46. GNOME Gucharmap ??? ?? ?? ??
? [Proposal, Enhancement] Add Hangul jamo representation for Hangul Syllables on
gucharmap
? This is not bug, but I think that feature enhance gucharmap for Korean learners and
Korean users.
? I add new feature, “Add Hangul jamo representation for selected Hangul Syllables
features on gucharmap”
? Hangul elements are commonly referred to as jamo(??/字母), meaning “alphabet”
? Korean has special term for the jamo that are used to construct hangul syllable,
depending on where in the syllable they appear:
? - Choseong(??/初聲) for the initial sound, usually a consonant
? - Jungseong(??/中聲) for the middle sound, usually a vowel
? - Jongseong(??/終聲) for the final sound, usually a consonant
? Hangul syllables are the characters that are used to express contemporary Korean texts
in writing.
? Gucharmap’s canonical decomposition Notation appear Hangul jamo for Selected
Hangul syllables.
? example)
? Canonical decomposition: U+1100 HANGUL CHOSEONG KIYEOK + U+1161
HANGUL JUNGSEONG A
? But these jamo name and representation is not appear, so I add “Hangul jamo names
and representation for selected hangul syllable” feature on gucharmap.
? example)
? Canonical decomposition: U+1100 HANGUL CHOSEONG KIYEOK + U+1161
HANGUL JUNGSEONG A
? Hangul Choseong:?
? Hangul Jungseong:?
? ex1) Decomposition of hangul syllable
? Unicode codepoint: U+AC00?
Hangul(??) ‘?’ ?
jamo(??/字母): ? plus ??
choseong(??/初聲): ? (codepoint: U+1100)?
jungseong(??/中聲): ?(codepoint: U+1161)?
Selected Hangul syllable ‘?’(U+AC00)
? AS-IS ?
Canonical decomposition: U+1100 HANGUL CHOSEONG KIYEOK +
U+1161 HANGUL JUNGSEONG A
? TO-BE?
Canonical decomposition: U+1100 HANGUL CHOSEONG KIYEOK +
U+1161 HANGUL JUNGSEONG A
? Hangul Choseong:??
Hangul Jungseong:?
? ex2) Decomposition of hangul syllable
? Unicode code point: U+AC01?
Hangul(??) ‘?’?
jamo(??/字母): ‘?’ plus ‘?’ plus ‘?’ ?
choseong(??/初聲):? (codepoint: U+1100)?
jungseong(??/中聲):?(codepoint: U+1161)?
jongseong(??/終聲):? (codepoint: U+11A8)?
Selected Hangul syllable ‘?’(U+AC01)
? AS-IS ?
Canonical decomposition: U+1100 HANGUL CHOSEONG KIYEOK +
U+1161 HANGUL JUNGSEONG A + U+11A8 HANGUL JONGSEONG
KIYEOK
? TO-BE?
Canonical decomposition: U+1100 HANGUL CHOSEONG KIYEOK +
U+1161 HANGUL JUNGSEONG A + U+11A8 HANGUL JONGSEONG
KIYEOK?
Hangul Choseong:??
Hangul Jungseong:??
Hangul Jongseong:?
47. GNOME Gucharmap(?? ???) 9.0.3
?? ??!?
http://git.net/ml/commits.gnome/2017-03/msg07073.html
Subject: [gucharmap] Created tag 9.0.3
The unsigned tag '9.0.3' was created.
Tagger: Christian Persch <chpe@xxxxxxxxxxxxx>
Date: Mon Mar 20 23:32:30 2017 +0100
Version 9.0.3
Git-EVTag-v0-SHA512:
26eec441630fc43d9c239b57bbe727fa0a799a0f7ccc9968c82c08346375385cb02e12d5d1a802bee02f093583e8bd77c35a68e85ff5a23cf4e75e22ae6a134a
Changes since the last tag ‘9.0.2':
(??)
Christian Persch (6):
Post release version bump
charmap: Conditionalise forcing the light theme on gtk < 3.22
build: Remove obsolete README file
charmap: Also show compatibility decomposition
charmap: Parse compatibility formatting tags
charmap: Only add non-space printable character to codepoint link
DaeHyun Sung (2):
charmap: Show characters in the canonical decomposition
Update Korean translation
(??)
_______________________________________________
commits-list mailing list (read only)
https://mail.gnome.org/mailman/listinfo/commits-list
53. ProposalAdd Hangul jamo representation for Hangul Syllables on KDE kcharselect
[Proposal, Enhancement] Add Hangul jamo representation for Hangul Syllables on KDE
kcharselect
This is not bug, but I think that feature enhance KDE kcharselect for Korean learners and Korean
users.
I add new feature, “Add Hangul jamo representation for selected Hangul Syllables features on
KDE kcharselect”
Hangul elements are commonly referred to as jamo(??/字母), meaning “alphabet”
Korean has special term for the jamo that are used to construct hangul syllable, depending on
where in the syllable they appear:
- Choseong(??/初聲) for the initial sound, usually a consonant
- Jungseong(??/中聲) for the middle sound, usually a vowel
- Jongseong(??/終聲) for the final sound, usually a consonant
Examples of Canonical Equivalence
Hangul & conjoining jamo ? ? ? +?
Hangul syllables are the characters that are used to express contemporary Korean texts in writing.
KDE kcharselect canonical decomposition Notation not appear Hangul jamo for Selected Hangul
syllable.
so I add “Hangul jamo names and representation for selected hangul syllable” feature on KDE
kcharselect.
example)
Hangul Syllable decomposition:
? U+1100 HANGUL CHOSEONG KIYEOK
? U+1161 HANGUL JUNGSEONG A
ex1) Decomposition of hangul syllable
Unicode codepoint: U+AC00
Hangul(??) ‘?’
jamo(??/字母): ? plus ?
choseong(??/初聲): ? (codepoint: U+1100)
jungseong(??/中聲): ?(codepoint: U+1161)
Selected Hangul syllable ‘?’(U+AC00)
TO-BE
Hangul Syllable decomposition:
? U+1100 HANGUL CHOSEONG KIYEOK
? U+1161 HANGUL JUNGSEONG A
ex2) Decomposition of hangul syllable
Unicode code point: U+AC01
Hangul(??) ‘?’
jamo(??/字母): ‘?’ plus ‘?’ plus ‘?’
choseong(??/初聲):? (codepoint: U+1100)
jungseong(??/中聲):?(codepoint: U+1161)
jongseong(??/終聲):? (codepoint: U+11A8)
Selected Hangul syllable ‘?’(U+AC01)
TO-BE
Hangul Syllable decomposition:
? U+1100 HANGUL CHOSEONG KIYEOK
? U+1161 HANGUL JUNGSEONG A
? U+11A8 HANGUL JONGSEONG KIYEOK
ex3) Decomposition of hangul syllable
Unicode code point: U+C633
Hangul(??) ‘?’
jamo(??/字母): ‘?’ plus ‘?’ plus ‘?’
choseong(??/初聲):? (codepoint: U+110B)
jungseong(??/中聲):?(codepoint: U+1169)
jongseong(??/終聲):? (codepoint: U+11B6)
Selected Hangul syllable ‘?’ (U+C633)
TO-BE
Hangul Syllable decomposition:
? U+110B HANGUL CHOSEONG IEUNG
? U+1169 HANGUL JUNGSEONG O
? U+11B6 HANGUL JONGSEONG RIEUL-HIEUH
Reference
KS X 1026-1:2007 Information Technology - Universal Multiple-Octet Coded Character Set(UCS) - Hangul
Part1 Hangul processing guide for information interchanges
http://std.dkuug.dk/jtc1/sc2/wg2/docs/n3422.pdf
Unicode Normalization forms http://unicode.org/reports/tr15/
Unicode Normalization forms #14.1.4. Hangul Decomposition and Composition
http://unicode.org/reports/tr15/#Hangul_Composition
Hangul Jamo (Range: U+1100-U+11FF) http://www.unicode.org/charts/PDF/U1100.pdf
Hangul Syllables (Range: U+AC00-U+D7AF) http://www.unicode.org/charts/PDF/UAC00.pdf
72. Unicode 10.0? 2017? 6? ?? ??
??: UTC #148, Extension F & Unicode Version 10.0?
https://blogs.adobe.com/CCJKType/2016/08/utc148-extf-unicode10.html
Unicode Character Database data files for Version 10.0.0 beta review?
http://www.unicode.org/Public/10.0.0/ucd/