home.social

#babelstonehan — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #babelstonehan, aggregated by home.social.

fetched live
  1. @jlhwung

    Perfect, thanks!

    At first, while comparing the new HTML version with the previous one, I thought that there was something odd about the IDSes for U+8846, i.e., two occurrences of ⿱罒𧰨 being both incorrect and duplicated, but then I realized that this was not a new issue. And although IDSes for variations are certainly useful information, they don't appear in the charts of registered collections anyway (same goes for the the first variant being also the default)…

    #BabelStoneHan

  2. @jlhwung

    Perfect, thanks!

    At first, while comparing the new HTML version with the previous one, I thought that there was something odd about the IDSes for U+8846, i.e., two occurrences of ⿱罒𧰨 being both incorrect and duplicated, but then I realized that this was not a new issue. And although IDSes for variations are certainly useful information, they don't appear in the charts of registered collections anyway (same goes for the the first variant being also the default)…

    #BabelStoneHan

  3. @jlhwung

    Perfect, thanks!

    At first, while comparing the new HTML version with the previous one, I thought that there was something odd about the IDSes for U+8846, i.e., two occurrences of ⿱罒𧰨 being both incorrect and duplicated, but then I realized that this was not a new issue. And although IDSes for variations are certainly useful information, they don't appear in the charts of registered collections anyway (same goes for the the first variant being also the default)…

    #BabelStoneHan

  4. @jlhwung

    Perfect, thanks!

    At first, while comparing the new HTML version with the previous one, I thought that there was something odd about the IDSes for U+8846, i.e., two occurrences of ⿱罒𧰨 being both incorrect and duplicated, but then I realized that this was not a new issue. And although IDSes for variations are certainly useful information, they don't appear in the charts of registered collections anyway (same goes for the the first variant being also the default)…

    #BabelStoneHan

  5. @jlhwung

    To add the *unregistered* BabelStone collection to my CJK Variations utility, at first I had to "scrape" its data from the BSH_IVS.html page then, later on, Andrew added a plain text BSH_IVS.TXT data file, much more convenient to parse.

    I currently use the .html as a reference, and sometimes switch to the .TXT to see if I get the same result, and I recently noticed that the two versions are now in sync, except for the VS ordering of U+3515 and U+8846.

    HTH…

    #BabelStoneHan #IVS #IVD

  6. @jlhwung

    To add the *unregistered* BabelStone collection to my CJK Variations utility, at first I had to "scrape" its data from the BSH_IVS.html page then, later on, Andrew added a plain text BSH_IVS.TXT data file, much more convenient to parse.

    I currently use the .html as a reference, and sometimes switch to the .TXT to see if I get the same result, and I recently noticed that the two versions are now in sync, except for the VS ordering of U+3515 and U+8846.

    HTH…

    #BabelStoneHan #IVS #IVD

  7. @jlhwung

    To add the *unregistered* BabelStone collection to my CJK Variations utility, at first I had to "scrape" its data from the BSH_IVS.html page then, later on, Andrew added a plain text BSH_IVS.TXT data file, much more convenient to parse.

    I currently use the .html as a reference, and sometimes switch to the .TXT to see if I get the same result, and I recently noticed that the two versions are now in sync, except for the VS ordering of U+3515 and U+8846.

    HTH…

    #BabelStoneHan #IVS #IVD

  8. @jlhwung

    To add the *unregistered* BabelStone collection to my CJK Variations utility, at first I had to "scrape" its data from the BSH_IVS.html page then, later on, Andrew added a plain text BSH_IVS.TXT data file, much more convenient to parse.

    I currently use the .html as a reference, and sometimes switch to the .TXT to see if I get the same result, and I recently noticed that the two versions are now in sync, except for the VS ordering of U+3515 and U+8846.

    HTH…

    #BabelStoneHan #IVS #IVD

  9. @jlhwung

    In the current BabelStone Han Extra font, the glyphs for U+23E86 𣺆 and U+2B46C 𫑬 don't match their G-source representative glyph: U+7540 畀 vs. U+2233F 𢌿...

    #Unicode #BabelStoneHan

  10. @jlhwung

    In the current BabelStone Han Extra font, the glyphs for U+23E86 𣺆 and U+2B46C 𫑬 don't match their G-source representative glyph: U+7540 畀 vs. U+2233F 𢌿...

    #Unicode #BabelStoneHan

  11. @jlhwung

    In the current BabelStone Han Extra font, the glyphs for U+23E86 𣺆 and U+2B46C 𫑬 don't match their G-source representative glyph: U+7540 畀 vs. U+2233F 𢌿...

    #Unicode #BabelStoneHan

  12. @jlhwung

    In the current BabelStone Han Extra font, the glyphs for U+23E86 𣺆 and U+2B46C 𫑬 don't match their G-source representative glyph: U+7540 畀 vs. U+2233F 𢌿...

    #Unicode #BabelStoneHan

  13. @jlhwung

    In the BabelStone Han font, the glyph for U+283E1 𨏡 is currently ⿰車𤴡 (duplicate of U+4879(TP) 䡹) but its right part should be ⿳⿱士冖田⿱厶龰 instead, like for U+4D91(GH) 䶑 and also U+27036 𧀶 at bottom.

    #BabelStoneHan

  14. @jlhwung

    In the BabelStone Han font, the glyph for U+283E1 𨏡 is currently ⿰車𤴡 (duplicate of U+4879(TP) 䡹) but its right part should be ⿳⿱士冖田⿱厶龰 instead, like for U+4D91(GH) 䶑 and also U+27036 𧀶 at bottom.

    #BabelStoneHan

  15. @jlhwung

    In the BabelStone Han font, the glyph for U+283E1 𨏡 is currently ⿰車𤴡 (duplicate of U+4879(TP) 䡹) but its right part should be ⿳⿱士冖田⿱厶龰 instead, like for U+4D91(GH) 䶑 and also U+27036 𧀶 at bottom.

    #BabelStoneHan

  16. @jlhwung

    In the BabelStone Han font, the glyph for U+283E1 𨏡 is currently ⿰車𤴡 (duplicate of U+4879(TP) 䡹) but its right part should be ⿳⿱士冖田⿱厶龰 instead, like for U+4D91(GH) 䶑 and also U+27036 𧀶 at bottom.

    #BabelStoneHan

  17. Thanks to @jlhwung, the so beautifully crafted 'BabelStone Han' font by Andrew West (魏安), is alive and well!

    The latest version 17.0.0, made of 'BabelStoneHanBasic.ttf' and 'BabelStoneHanExtra.ttf', is available from:

    🔗 github.com/babelstone/babelsto

    #BabelStone #BabelStoneHan #Unicode #Unihan #CJK #CJKV

  18. Thanks to @jlhwung, the so beautifully crafted 'BabelStone Han' font by Andrew West (魏安), is alive and well!

    The latest version 17.0.0, made of 'BabelStoneHanBasic.ttf' and 'BabelStoneHanExtra.ttf', is available from:

    🔗 github.com/babelstone/babelsto

    #BabelStone #BabelStoneHan #Unicode #Unihan #CJK #CJKV

  19. Thanks to @jlhwung, the so beautifully crafted 'BabelStone Han' font by Andrew West (魏安), is alive and well!

    The latest version 17.0.0, made of 'BabelStoneHanBasic.ttf' and 'BabelStoneHanExtra.ttf', is available from:

    🔗 github.com/babelstone/babelsto

    #BabelStone #BabelStoneHan #Unicode #Unihan #CJK #CJKV

  20. Thanks to @jlhwung, the so beautifully crafted 'BabelStone Han' font by Andrew West (魏安), is alive and well!

    The latest version 17.0.0, made of 'BabelStoneHanBasic.ttf' and 'BabelStoneHanExtra.ttf', is available from:

    🔗 github.com/babelstone/babelsto

    #BabelStone #BabelStoneHan #Unicode #Unihan #CJK #CJKV

  21. Thanks to @jlhwung, the so beautifully crafted 'BabelStone Han' font by Andrew West (魏安), is alive and well!

    The latest version 17.0.0, made of 'BabelStoneHanBasic.ttf' and 'BabelStoneHanExtra.ttf', is available from:

    🔗 github.com/babelstone/babelsto

    #BabelStone #BabelStoneHan #Unicode #Unihan #CJK #CJKV