Showing posts with label UNICODE. Show all posts
Showing posts with label UNICODE. Show all posts

Thursday, July 23, 2026

SignWriting 2025 - A response to a Wiktionary initiative.

On Diff, the aggregator for Wikimedia news, a case was made to support sign languages particularly for Wiktionary. Sign languages are used to communicate, there are many hundreds of sign languages, only half the people who know how to sign are deaf. There is one writing system, SignWriting that can be used for all sign languages.

There are a few misconceptions in the Wiktionary proposal; with over 300 sign languages, there is a potential for over 300 translations for each concept. Sign languages are not to be linked to countries; there are countries with multiple indigenous sign languages. All languages have their own ISO-639 language code the same, ase for instance is the code for American Sign Language. 

The characters of the SignWriting script are included in the same standard that includes all other scripts like Cyrillic or Devangari. The consequence is that as your computer supports UNICODE, your computer will be able to show texts written in SignWriting when you have a supporting font. At that Google may be your friend with its Noto Sans font and the Wikimedia Foundation may provision readers of its projects content.

A decade ago, there was a concerted effort from within the SignWriting movement to have Wikipedias in multiple sign languages. Much of what transpired can still be read on my blog. At the time the Wikimedia Foundation did not have the bandwidth to support the technical requirements in MediaWiki. It is why the deaf who express themselves with their sign language have no platform within the Wikimedia Foundation.

Thanks,

        GerardM

Thursday, December 25, 2014

Season greetings


Every year there is a SignWriting card like this one. It is send to the people subscribed to the SignWriting mailinglist. They are created by the list members themselves, this time by Stefan and Elfriede Wöhrmann.

There is no card they can buy from Hallmark but the need for cards for the seasons greetings is as high as for anyone else. Most years I put the card on my blog and this year is no exception. Each year I hope for at least one Wikipedia in a sign language. Maybe in 2015. This is what Steven Slevinsky has to say about it. It explains the challenges and the hope for the future really well.
I believe that 2015 will be the year of the sign language Wikipedia.  I believe the ASL Wikipedia activity will increase and other sign language Wikipedia projects will start. 
The new TrueType fonts are a great step forward: pages are 30 times smaller and SignWriting can be displayed without an internet connection.  Each page is reduced to a single connection, elimination a unique connection for each sign/symbol on the page. 
The new editors based on the TrueType fonts are nearing completion.  This will increase the spread of written sign language all over the Internet. 
Written sign language will also spread because of the inclusion of the SignWriting symbols in Unicode 8. 
So 2015 will be an amazing year for SignWriting.  We'll have TrueType fonts, new editors, Unicode, and Wikipedia.  A great combination for success.
Regards,-Steve

Sunday, March 23, 2014

Mark Davis is the co-founder and president of the #Unicode Consortium

Mark is one of those persons who is associated with what is now "basic functionality". He is still working in the field of Unicode and language support and is therefore one of the movers and shakers in the computer industry.

When you search for Mark Davis, he is one of 28 items that show up. They are many people, a house, two computer games and a movie made by a Mark Davis. These 28 items represent the combined knowledge of Wikipedia, Wikisource and Wikivoyage.

When you hover over any of the items in the list, you will get a box with pertinent information. When available, a picture shows up. I asked Mark if I could use a picture of him to be used in Wikidata and Wikipedia. I could and have the chat log to prove it.

When I told Mark that Wikidata is harvested, among others, by DBpedia, he realised that the picture used will have an impact on the semantic web. He was impressed and, is now considering if he has an even better picture to share.
Thanks,
      GerardM

Monday, February 17, 2014

The place of #language support in #MediaWiki support

At this moment #Wikipedia has 280+ versions. They represent 280+ different languages. Every language is written in a script. This script may be from right to left (eg Latin), from left to right (eg Arabic). Top down is not yet supported.

All these languages use Unicode to represent the characters in their script. As a consequence it is "just" a matter of configuring a language correctly and it will work in a wiki. The characters used in a script have to be defined in Unicode. Without this supporting a language is problematic. An example of this is the SignWriting script and all the sign languages. They are not supported by the Wikimedia Foundation and they are developing their software themselves.

When people want to have their own Wikipedia, they have to localise the MediaWiki software at translatewiki.net. This is a requirement for the people that request a new project to fulfil. All that is required to support another language is some configuration.  To support all languages other than English, MediaWiki developers have to internationalise their software. This is a well established process, there is nothing special in there for "small languages", it is the same process for any language.

When people use MediaWiki it can be assumed that they use any of these 280+ languages. It cannot be assumed that they know any other language than their own. The Universal Language Selector allows people to select the language they need for their user interface. They can choose a language by typing in the name of their language in their own language.

Once a languages is selected, MediaWiki supports both input methods and web fonts. This is necessary because most devices do not support all the languages MediaWiki supports. At this point a user can read and write in MediaWiki. A special case is the OpenDyslexic font; is enables 7% of a population to read their language with less effort. This font works only for many languages that are written in the Latin script like English.

One other aspect of language support is in enabling search in all the 280+ languages. This is where Wikimedia engineers may have to do special things for a single language. When they do this well, they only have to do this once. Typically however, setting up search for a language is well documented, it is part of international standards.

Language support for MediaWiki is nothing but internationalising the software and for being mindful that MediaWiki is used by people representing over 300 cultures and languages. There is no special consideration for small or big languages.
Thanks,
        GerardM

Thursday, June 28, 2012

#ImpactOCR - A #font using #unicode private use characters

When really old historic texts are digitised and OCR-ed, the images of letters found are mapped to the correct characters. Characters are defined in Unicode and when a character is NOT defined, it is possible to define them in the "private use" space.

As part of the Impact project, really old texts have been digitised, texts in many languages. At the recent presentation it was mentioned by two speakers that there were characters used in the Slovenian and Polish language that are not (yet) defined in Unicode. As part of their project, the missing characters were defined in the Unicode private use area and the scanning software was taught to use them.

With the research completed, with the need for all these characters and their shape defined, it will be great when these characters find their way in Unicode proper. When the code points for the missing characters are defined and agreed, the OCR software can learn to recognise the characters at the new code points, a conversion program can be written for the existing texts and it will be more inviting to include these characters in fonts.

Now that the project is at its end, it is the right moment to extend the Latin script in Unicode even further.
Thanks,
     GerardM

Monday, June 18, 2012

#Batak - getting a #script ready for the #Internet

Several languages from Sumatra, #Indonesia were originally written in the Batak script. This script was encoded in Unicode and the waiting was for a freely licensed font. Thanks to a grant by the Wikimedia Foundation, a project is under way that will produce a font for Batak and will transcribe sources from Dutch museums like the Tropenmuseum.

For a script to be encoded into Unicode, a lot of research goes into describing the font and how it functions. For Batak you can find this documentation here.

When you read this, you find details like how the combination of a consonant and a vowel is expressed in the Batak script. When smart algorithms are used only the valid combinations will be expressed.

Given that multiple languages use the Batak script, the rules that are implemented in a font need to allow for every Batak language.

The first iterations of the Unicode font for Batak are being tested. When this is done, the font will be available and it will be possible to transcribe original Batak sources including a book on sorcery.
Thanks,
       GerardM



Tuesday, June 12, 2012

#Gutenberg; #Unicode is the new #ASCII

Project Gutenberg is the original project that makes books that are out of copyright available for reading to you. At this time they made some 39,000 books available for you to read. Through affiliated organisations, including Wikibooks and project Runeberg, there are some 100,000 books to read.

When the project started in 1971, ASCII was how text was digitally stored on a computer. It has been a guiding principle of project Gutenberg to store text in ASCII ever since.

When a book was written in Greek, the characters of the Greek alphabet were transliterated into ASCII and, at the time this made perfect sense. It made sense because ASCII represented the standard every computer understood.

Nowadays, modern computers use Unicode for the encoding of text. The first notions of Unicode came into being sixteen years after the start of project Gutenberg. Most scripts are defined in Unicode and modern software expects Unicode. Now, twenty five years later there are free fonts for all the important scripts. Transliteration into ASCII for all these languages makes the resulting product unusable for many people. Most people do not know how to read a text that is transliterated.

Is there still a point to stick to ASCII or can ASCII be safely replaced by Unicode?
Thanks,
     GerardM

Monday, May 28, 2012

#Language, #script, #Unicode, #font and web fonts

Making the Internet globally accessible is more then running cables. It is also about making sure that you can read and write any language. Once all this is in place, people enabled in this way can share in the sum of all knowledge.

There are few people as intimately involved in supporting languages than Michael Everson. He is known for encoding scripts into Unicode, this requires both technical and linguistic expertise and finally he is a publisher of books written in minority languages.
Enjoy,
     GerardM

Michael at Chogh Zanbil - Cuneiform .. :)
Are all scripts registered yet ... do we know them all in ISO 15924?
No, not at all. The best-known scripts have been given four-letter codes in ISO 15924, but we tend to be conservative for lesser-used scripts, and try to co-ordinate with proposals for encoding them in the Universal Character Set (a.k.a. ISO/IEC 10646 or Unicode).

Several scripts are not yet encoded in Unicode. Many of them are used by living languages.. How do languages cope?
A script (or character) not encoded can't be used in interchange. People can either use the Private Use Area or hack an existing encoding.

What does it do to the cultures involved ?
The lack of an encoded script prevents a language from using its script effectively in any computer environment.

Is it known how many scripts used by living languages are not yet encoded ?
I don't think we have kept a quantitative inventory. And we always discover something new. I know of a number of specialist scripts like SignWriting and Blissymbols which have not been encoded. We are working on some other scripts, like Woleai and Afáka, and a number of West African scripts, but it is very difficult to contact the user communities to get feedback. There is a huge technological divide. (Not for SignWriting or Blissymbols: for those the problem is a lack of funding to do the work.)

Is it known how many scripts used by dead languages are not yet encoded ?
Again, we don't keep a quantitative inventory. The Roadmaps on the Unicode site are as good a checklist as anything.

Several scripts are encoded but there is no freely licensed font for them. Why is this not part of the process of encoding for Unicode ??
The Universal Character Set is a character set. Both ISO/IEC JTC1/SC2/WG2 and the Unicode Technical Committee work to study character and script proposals, give the characters the right properties, and get them encoded. It is not the function of either committee to establish implementations, or to give them away. The work is already voluntary (and expensive).

MediaWiki supports web fonts ... What relevance does this have for you, what opportunities are there for the Wikimedia communities
It is a great opportunity for Wikimedia to exploit some of the generosity of the many people who have donated to the foundation, and to make good use of the skills of people who have expertise in the Universal Character Set and in font design.

What impact will the availability of freely licensed fonts have on the availability of information in those scripts
For instance, right now anyone viewing any Wikipedia in any language may encounter text in Ol Chiki, or in Runic, or in the simple International Phonetic Alphabet, and pages have to apologize to the reader because their computer may not display the material correctly. This is *bad* for the encyclopaedia.

What difference would it make if the Wikimedia Foundation were to become a player in the development of fonts
People using the encyclopaedia would be able to see the information without worrying about seeing ☐☐☐☐☐☐ ☐☐☐☐☐! From a personal point of view, I can say that at various conferences over the past two years, I have spoken with people in the Wikimedia Foundation, and with people from another very large organization, about this matter -- specifically about exploiting my own expertise in the Universal Character Set and in the provision of rare scripts and characters in web fonts -- yet nothing has resulted. I think the message has got through. But so far no one in either organization has decided to take the necessary principled decision that in order to ensure that the information in the Free Encyclopaedia is actually available to people who use it, complete UCS support should be provided in a suite of freely-available and maintained webfonts.

Provenance is the basis for the establishment of facts. Is transcription in the original script essential ?
Why wouldn't it be? That's the source text. Encoding it correctly means that it can be interpreted by the reader if he or she wishes to consult the primary source. Anything else obliges the reader to use someone else's interpretation. Of course expertise is needed, but the closer one can get to the primary source, the better.


Michael, why "Alice's Adventures in Wonderland" ?
I love languages, and it has been a great honour for me to publish Alice for the first time in a number of minority languages which might otherwise never have seen the text. Alice is available in the following languages: Cornish, English, Esperanto (Kearney), Esperanto (Broadribb), French, German, Hawaiian, Irish, Italian, Jèrriais, Latin, Lingua Franca Nova, Low German, Manx, Mennonite Low German, Borain Picard, Scots, Swedish, Ulster Scots and Welsh  and several others translations are being prepared.

Reading #Arabic

Learning to pronounce texts in classic Arabic is an adventure. It is a challenge for me and I have been promised that I will be able to vocalise at the end of four day sessions and a month of practising at home.

It is fun as well. The sounds are not only different for me but also for my fellow students. One of them speaks Moroccan Arabic and is also struggling with the difference in pronunciation.

When you are taught about the structure of Arabic, you are taught that the "i" and its associated variations are written under the character it is associated with. In figure 1, it is combined with a "shadda" on a "ya". My teacher explained that he is not able to write it in this way with Microsoft Word and, that you will find it as you can see in figure 2.

The documentation for the Arabic script at Unicode explains: "computer fonts often follow an approach that originated in metal typesetting and combine the kasratan with shadda in a ligature placed above the text".

My teacher wants to control the way the characters show. It makes the study material consistent for his students. Showing the kasratan with shadda above the text is then something that can be taught when the basics are understood. The question is does he need a different font or does he need a different word processor.
Thanks,
      GerardM

Wednesday, May 16, 2012

Turkish Lira is supported in #Unicode

When #Turkey selected a new symbol for its currency, the Lira, it had to make sure that people can actually use it. Given that almost all modern computing is done with Unicode fonts, it was important to have the symbol included as soon as possible in Unicode.

The Turkish Lira will be supported in the Unicode 6.2 release that was just announced for the third quarter of 2012. The next step is to have the symbol included in fonts. A font that includes the new symbol can already be found on the website of the Turkish central bank.

In a previous Unicode release the Indian Rupee was introduced. The question is very much to what extend and at what pace people will have updated fonts that includes such symbols. The Wikipedia article on the Indian Rupee uses an image.

It is possible to create a font that includes characters like these currency symbols and make use of the WebFonts extension. In many ways it is more elegant than using graphics.
Thanks,
      GerardM

Thursday, April 12, 2012

#CLDR is not used solely for locales

#Unicode is best known for its architecture for the digital representation of the characters off scripts. The Unicode consortium also hosts the "common locale data repository" project also known as the CLDR. In this repository you can find how languages are used in different areas. You will find for instance what currency symbol is used. There is also information on what direction is the language written in, the way numbers and dates are written.

Many applications rely on this data. Several Open Source word processors use this data to enable a language for editing. While it is great that this data is used it is problematic because not all languages are spoken let alone in locales.

One great example is Ancient Greek; this language is not a living language but it is taught in schools all over the world. Students are doing their homework and what they write, it is certainly not modern Greek. From a technical perspective, it is only correct when the meta-data of such documents indicates that it is Ancient Greek.

When Ancient Greek and other extinct languages are supported in word processors, surviving texts can be written with modern tools. These transcribed texts will by default have correct meta data and it will be easier to find them when they are placed on the Internet.

For this to happen, the CLDR either embraces that it is used to enable languages in word processors or the word processors who currently use the CLDR allow for alternate sources of primary data.
Thanks.
     GerardM

Saturday, December 31, 2011

Top to bottom

The scripts used by the languages that have a #Wikipedia are written either in a right to left or in a left to right direction, the Arabic script for instance is "rtl" and the Latin script is "ltr". Supporting all these scripts is difficult enough. There has been a constant demand for improvements that make editing in languages like Arabic, Hebrew or Urdu easier.


Mongolian is one language that turns things on its head; it is written top down. Even though it is a living language, it is hard to find documents on the Internet. It is hard because at this time only Internet Explorer supports the Mongolian script in its production versions and applications like MediaWiki do not support it at all.

When Mongolian is to be completely supported by browsers, there are several issues;

  • the shapes of the Mongolian script need to be supported by Harfbuzz and other shaping engines. 
  • supporting versions of the shaping engines need to be included in the browser people use
  • it still needs to be shown in the top down direction
Mongolian is not the only script that is written in a top down direction. SignWriting is another one. SignWriting is used by sign languages, there are several hundreds of these languages  and SignWriting is the only script that can be used realistically for day to day use.

There are several requests for Wikipedias that need SignWriting support. All these requests are waiting because of missing technical infrastructure or other issues
  • SignWriting characters are not yet defined in Unicode
  • there is a freely licensed font based on Unicode specifications but it is not stable by definition
  • browsers do not support top down; for now top down needs support in the application
All this can hardly be considered "low hanging fruit" and as there is so much that needs doing. Supporting top down languages in general and Mongolian and SignWriting in specific is something to wish for. It is technology that needs champions that make it a reality.
Thanks,
       GerardM

Friday, October 14, 2011

in #ISO639 bbc stands for Toba #Batak

Artefacts of many "indigenous" cultures only exist in museums. The cultured people who created them have died or dwindled into non-existence and their descendants often do not know their history, their culture.

When the language still exists... it may be that the script is no longer in use because it is replaced by another. Even when the text is transcribed and then transliterated, the terminology and the associated understanding may be lost.

We have a request for a Wikipedia in Toba Batak. This is only one of the languages that is written or used to be written in the Batak script. The characters of the script have been defined in Unicode and the only font available is freeware and does not feature what you expect of a modern font according to the author.

The author of the existing font, a professor in Hawaii, is happy to work with us to establish a fully functional freely licensed font, a keyboard map and possibly a transcription engine from and to the Latin script.

Many of the objects in the Dutch and other western museums are valued far higher then the cost of the creation of a font for the Batak script. Once a script is available it becomes possible to transcribe all the texts that exists in museums and archives and this in turn will allow us to glimpse of the Batak cultures as they survive in its literature.
Thanks,
       GerardM

Monday, September 19, 2011

#Unicode language names found by search engines

#Statistics are a wonderful thing. These numbers compiled by "Kaśyap కశ్యప్" show how often the name of a language can be found when they are written in Unicode characters. This gives a clue about how well a search engine serves a language.

Such numbers also provide an indication how much a language is actually used on the Internet. What is does not say is how much demand there is to use a language on the web.


The Wikimedia Foundation's Localisation team is working hard to make it easier to use MediaWiki wikis. For us it is interesting to compare these numbers with the number of speakers for a language because this may indicate how hard it will be to make a particular Wikipedia more popular on the Internet.
Thanks,
      GerardM

Friday, September 16, 2011

The name is Bon, James Bon II

Santhosh started work on an #Unicode UAX31 implementation.. Good for us because we support all the scripts for all the languages we have projects in. Our best practice has it that people can have a user in their own language.

The UAX31 standard defines the standard rules for our best practice. Writing a reference implementation that will actually be used is a bit different; the Wikimedia Foundation implemented a black list of names for instance.

Once you start writing an implementation, you encounter all the ambiguities, all the issues that are still open. How for instance do you cope with the Arabic script, what to do with a "." or a full stop in the middle of a user?

It makes sense to allow for the characters that are used in a language. This implies that knowing what language to expect is crucial. There are two obvious approaches; you expect a new user in the default language or the languages is defined in the preferences.

When you are interested in this subject have a read of the current version of the code.
Thanks,
       GerardM

Thursday, September 08, 2011

The name is Bon, James Bon

Santhosh is one of the special agents in the fight to bring language support to the Internet. Identifying him in English is easy; all the characters used to transliterate സന്തോഷ് തോട്ടിങ്ങല്‍ are available to identify Santhosh for who he is.

The last character in his name is the "zwj". According to some, this character is not available for identification purposes. Without the "zwj", the name looks different:
  • സന്തോഷ് തോട്ടിങ്ങല്‍
  • സന്തോഷ് തോട്ടിങ്ങല്
Santhosh is a Malayalam name and for Malayalam there is an alternative way of writing Unicode. So technically it is possible to transliterate the "zwj" out of his name for Malayalam.

It becomes more interesting when you write Sri Lankha in Singhala. this cannot be done without a "zwj". From a Wikimedia Foundation point of view, the Unicode report "Unicode Identifier and Pattern Syntax" assumes for many languages that they are "aspirational" or "limited" use, is not really workable. Our aim is to have support for all scripts and identifying people by their name; their real name.

As we do identify people, an implementation of this Unicode specification is important to us. Having people like Mr തോട്ടിങ്ങല്‍ in the drivers seat will surely get us a best result. It may even get us a reference implementation.
Thanks,
       GerardM

Sunday, August 28, 2011

#Arabic characters to display the #Qur'an

Readers of #Wikipedia are still expected to have all the fonts on their system necessary to display the texts they are about to read. The Arabic fonts on Ubuntu for instance are not enough to show all the characters used in printing the Qu'ran.

The technology used in printing is not necessarily the same as the technology used in displaying on a computer screen. The result is that several characters used when printing the Qu'ran are missing in Unicode. The King Fahd Glorious Quran Printing Complex has as one of its ambitions to bring the Qu'ran to the Internet and consequently brought several proposals to the Unicode standard and the ISO/IEC10646.


As you can see, quite a number of characters are missing for me. As reading the Qu'ran, requires a high quality font, it would be a gift to the world when the font as used and developed for displaying the Qu'ran becomes available under a Free license. This will ensure that everyone can see and read the Qu'ran as it has been handed down.
Thanks,
       GerardM

Sunday, August 14, 2011

What makes a #language a living language

The #Wikimedia Foundation provides hosting to any and all languages that are able to comply with the minimal requirements that have been defined in the language policy. For languages that have sufficient vitality and infrastructure this is a godsend; a Wikipedia is seen as recognition for a language.

Wikipedia is well positioned for this because of one early design decision for MediaWiki; the exclusive use of Unicode fonts. All languages that are supported with fonts are in luck. Recent work on for instance right to left languages will percolate into production in the near future, we are working on WebFonts and input methods and all this will be a game changer for many of the existing Wikimedia languages.

The Wikimedia Foundation has always been clear that its primary interest is not in the preservation of languages but in providing information to the people of the world. It has taken its time before the WMF is getting involved in increasing its support for languages. This is driven largely by the lack of growth in the "global north" and an astounding room for growth in the "global south".

When a language is a living language, it will at some stage have a presence on the Internet. Failure to do so will mean it will be increasingly marginalised. There may be mitigating circumstances like the use by a locked in community like the deaf and their many sign languages.

In the WMF language committee there is a big discussion about what to do with the languages that do not have a WMF project. Should we go out and stimulate people to start a WMF project in their language. Should we technically enable languages for the Internet and stimulate its use in the hope of a living WMF project at some later date...

Projects like indigenoustweets.com are very much the kind of projects we can support to further the use of more languages on the Internet. Even the use of Facebook or Google+ is a net gain when people use their language on the Internet. I am all for it, I am even for providing social software at the WMF. When we can help people use the Internet in any way, it will stimulate a language, a culture. First you give them their voice and then we may find a request for a new Wikimedia project. At the same time the chance of finding content about such a culture and language in for instance the English Wikipedia will increase. Now that, the sum of all knowledge, is what the WMF is about.
Thanks,
      GerardM

Saturday, July 30, 2011

#Email in #SignWriting

When it was announced that it is possible to send an e-mail in SignWriting, it was Thorsteinn who posted the first message on a public list as far as I know. He added a message in English saying that he may have selected a wrong sign and he expressed his hope for all the recipients to be able to read it.

When your ability to sign is as good as mine; it is not only a different language, a different script but also a different delivery system, it will be hard to understand what this messages is about. What we have are the different symbols expressing gestures and facial expressions. There are the vertical lanes for the direction of the text. There are the breaks between the sentences.


The hope is that SignWriting will soon become accepted and encoded by Unicode. This will realise much needed momentum for every sign language. The hope is that shaping engines like HarfBuzz will adopt the shaping rules quickly so that Wikipedias in sign languages will no longer be a dream waiting to come true.
Thanks,
      GerardM

Monday, July 25, 2011

#Unicode is not that complicated

When good people associate Unicode with this #XKCD strip, things are wrong, seriously wrong. The value of a standard is in its acceptance. Unicode is best known for its work on scripts and it is this work that makes Wikipedia possible. Without the standardisation brought about by Unicode it would be impossible to support the 270+ languages who have a Wikipedia and, the languages working towards their Wiki in the Incubator.

As there is confusion about Unicode lets analyse what is said. First of all, Unicode is a work in progress. As a consequence there is no guarantee that every script has been encoded and, there is even less of a guarantee that a font is available let alone a freely licensed font. One reason why the situation is not good is because many organisations consider the development of Unicode encodings for scripts and fonts out of scope.

Unicode is developing an additional standard, the CLDR or the Common Locale Data Repository. While this standard is important, many of the languages supported by the Wikimedia Foundation are not represented and languages that are represented do not have complete data. Consequently there is no authoritative source for many a date format, a currency format, the sorting order ...


Unicode is a consortium of companies and organisations. Particularly the companies have an interest in ensuring that the technology represents its investments. When individuals are singled out negatively, particularly people like Michael Everson who does not represent company interests, who is involved in open content, it becomes clear that Unicode should to do what it is supposed to do and provide support for languages, all languages and scripts, all scripts.
Thanks,
      GerardM