Increased Unicode Support for Historical Scripts | World Anvil

Remove these ads. Join the Worldbuilders Guild

Increased Unicode Support for Historical Scripts

Feature Upgrade · Api · Created by Tarn_IV
closed
API -scripts language unicode

WorldAnvil currently supports a great deal of Unicode characters, including obscure scripts like Vai, Syriac, and traditional Mongolian, but lacks support for other, historical scripts, such as Old Italic, Lydian, Gothic, Phoenician, and Cuneiform.

   

For people who enjoy creating languages and a diverse breadth of languages in their worlds, a panoply of different scripts can be quite helpful in differentiating languages and helping to illustrate a language's history and relations between languages and cultures through their use of certain scripts.

   

Those who wish to embed spellings of actual historical words in their articles would also benefit. For example, perhaps in explaining the historicity of the Trojan War, someone wants to include the names of the Greeks (akhaiwoí in Greek, and ahhiyawa in Hittite) and wishes to embed the original spellings in Linear B and Hittite Cuneiform, respectively.

Current score

15/300 Votes · +1910 points

Votes Cast

  • +300

    by sebasoft
    on 2021-10-19 20:40
  • +300

    by aidanbird
    on 2021-10-17 06:30
  • +50

    by Nomminus
    on 2021-10-13 04:41
  • +10

    by Vantaj
    on 2021-10-10 13:26
  • +200

    by CrazyEddie
    on 2021-10-06 19:22
  • +20

    by DarkJediPrincess
    on 2021-10-05 15:49
  • +200

    by aetherith
    on 2021-10-05 04:51
  • +200

    by pdearmen
    on 2021-10-03 03:06
  • +100

    by Wahnsinnik
    on 2021-10-02 12:30
  • +50

    by theaaronw0
    on 2021-10-02 10:16
  • +50

    by NESz
    on 2021-10-02 07:24
  • -100

    by A Rambunctious Hobbit
    on 2021-10-01 08:34
    This is an issue of character sets, would probably need some editor hack to accomplish (stored with special flags then the editor "decodes" them or something like that) since the db character set is unlikely to be able to store these, but then you need to manually engineer this stuff as the dev.   I think this would take way too much time to accomplish for very little gain. To include absolutely everything is also a question of manpower, the team would have to hire someone to do this exclusively, and it is also very bug prone   Maybe everything I'm saying is stupid, so don't take my words as gospel. For now I'd suggest circumventing this issue by using pictures with transparent background for the specific texts, if possible. Drawn text over typed text also has a more historical feel to it.
  • +10

    by SoulLink
    on 2021-10-01 08:01
    This is really a database problem and can't be solved easily.   An idea I had could be to implement a variable for these kinds of texts, which are stored with support for the full range of Unicode. Would of course limit the accessibility, but would make it possible.
  • +20

    by A Goodhearted Hobbit
    on 2021-10-01 00:52
  • +200

    by amelianite
    on 2021-10-01 00:03
  • +300

    by Tarn_IV
    on 2021-09-30 16:14