My friend Amir wrote twice ([1], [2]) about the need for the localisation of names. The need for localisation is rather obvious when the original name is in another script. But names written in the Latin script can be as foreign. Take for instance the Czech author and screenwriter Jiří Růžička, I do not know how to type his name and, I am sure 98% of the users of Wikidata will be able to do so either.
When a name uses characters that are not in use in a language, it follows that the name is unlikely to be found in a language and consequently transliteration is in order. The name as originally written is not an alias. It is something different. It probably needs an attribute of the type "multilingual text" for support in Wikidata.
Thanks,
GerardM
Showing posts with label script. Show all posts
Showing posts with label script. Show all posts
Tuesday, November 19, 2013
Saturday, August 17, 2013
A challenge: 20.248 #Wikipedia articles with script errors
When you add references to #Wikidata of relevant images, by magic they will appear on the Occitan Wikipedia. I did that by adding a picture to the Wikidata entry for Ahmad Tajuddin, the 27th Sultan of Brunei.
It was a random selection of a person mentioned on a list with 20.248 articles with script errors. The number is big but it is probably only one template that is generating all those errors. The edit page says:
Some say that Wikidata is about big numbers and I am impressed that all these articles probably refer to Wikidata. The one thing I am curious about is how long it will take for the list to clear once the script has been fixed.
First things first; who is going to fix the script.
Thanks,
GerardM
It was a random selection of a person mentioned on a list with 20.248 articles with script errors. The number is big but it is probably only one template that is generating all those errors. The edit page says:
{{Infobox|tematica=|carta=}}{{Intro}}I checked out a small number of other articles on this list and they all include this same template.
Some say that Wikidata is about big numbers and I am impressed that all these articles probably refer to Wikidata. The one thing I am curious about is how long it will take for the list to clear once the script has been fixed.
First things first; who is going to fix the script.
Thanks,
GerardM
Tuesday, July 02, 2013
Writing #Cuneiform on #Wikipedia
When you always wanted to write in the cuneiform script on Wikipedia, now you can. Technically there is not that much to it.
{{Cuneiform|{{linktext|𒄖|𒉈|𒅁|𒌨|𒅎}}}}
This is what it took to get the text you see on the infobox of the cuneiform article.
....
This is fun, nice but not all there is to it. What is really exciting is that you can now write in many, many scripts and expect that the person will see the text properly.
It is no longer necessary to create a screenshot. If anything, this is the time to find all those screenshots and replace them with the proper text and invoke the ULS and its webfonts.
Thanks,
GerardM
{{Cuneiform|{{linktext|𒄖|𒉈|𒅁|𒌨|𒅎}}}}
This is what it took to get the text you see on the infobox of the cuneiform article.
....
This is fun, nice but not all there is to it. What is really exciting is that you can now write in many, many scripts and expect that the person will see the text properly.
It is no longer necessary to create a screenshot. If anything, this is the time to find all those screenshots and replace them with the proper text and invoke the ULS and its webfonts.
Thanks,
GerardM
Tuesday, July 31, 2012
Learning a new #script .. #Arabic
As I am learning a new language with a script that is new to me, I find the Internet not yet the resource it is in languages for the Latin script.
There are several obstacles; I have to configure my computing devices for the Arabic script and keyboard. I have to find the characters on my keyboard and only when I do will I get the facility that I need.
The one thing that would make my day is to have a typing tutor that is ready for an international public. This means that the instructions are available in multiple languages for the same input method for the same language. When these parts are separated from the code, there are three specific parts.
There are several obstacles; I have to configure my computing devices for the Arabic script and keyboard. I have to find the characters on my keyboard and only when I do will I get the facility that I need.
The one thing that would make my day is to have a typing tutor that is ready for an international public. This means that the instructions are available in multiple languages for the same input method for the same language. When these parts are separated from the code, there are three specific parts.
- the user interface
- the exercises
- the input method or keyboard layout itself
This allows the same software to be used for multiple input methods and scripts / languages. The software can be localised at translatewiki.net and the typing tutor can be distributed with the input methods themselves.
Thanks,
GerardM
Sunday, July 22, 2012
Levels of competence for #Arabic in #Wikipedia
As my competence in the Arabic language is growing, I added Arabic in my Babel information. To my amazement what I read is wrong. The "ba" is written on its own while it should be connected with the following "aliph". It is one of those peculiarities of the Arabic script that a character like the "ba" is expressed depending on its position in a word.
I had a look at translatewiki.net to understand why it is wrong; as you can see the "ba" or ب is
connected to a wiki link and the word is not formatted after what is in the variable.
It is fun to learn other languages. What is really amazing is that I can find glaring issues like this one.
Thanks,
GerardM
It is fun to learn other languages. What is really amazing is that I can find glaring issues like this one.
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
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
Monday, May 28, 2012
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
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
Tuesday, May 08, 2012
A #font for ancient scripts
#Wikipedia refers to and #Wikisource includes sources that were written millennia ago. Sources that inform us about when what is now the western culture was centred in places like Athens, Crete or Karnak. The scripts used were different from modern scripts but like modern scripts many of them can and did make the transition into the digital age. They were encoded in Unicode and there are fonts available for these scripts.
George Douras has been really active in the creation of fonts for ancient scripts. There are many available from his website. The message about licensing is plain and simple and is probably all that is required. George is happy to see his fonts used as webfonts and is willing to help when there are issues with his font.
The list of what he has on offer is impressive:
Aegean Numbers, Alchemical Symbols, Anatolian Hieroglyphs, Ancient Greek Musical Notation, Ancient Greek Numbers, Ancient Roman Symbols, Arkalochori Axe, Arrows, Basic Latin, Block Elements, Box Drawing, Braille Patterns, Byzantine Musical Symbols, Carian, Combining Diacritical Marks, Combining Diacritical Marks for Symbols, Combining Half Marks, Control Pictures, Coptic, Counting Rod Numerals, Cretan Hieroglyphs, Cuneiform, Cuneiform Numbers and Punctuation, Currency Symbols, Cypriot Syllabary, Cypro-Minoan, Cyrillic, Cyrillic Supplement, Deseret, Dingbats, Dispilio tablet, Domino Tiles, Egyptian Hieroglyphs, Egyptian Transliteration characters, Emoticons, Gardiner set of Egyptian Hieroglyphs, General Punctuation, Geometric Shapes, Gothic, Greek and Coptic, Greek Extended, Hieratic alphabet, IPA Extensions, Last Resort font glyphs, Letterlike Symbols, Linear A, Linear B Ideograms, Linear B Syllabary, Local variants of Ancient Greek and Old Italic alphabets, Lycian, Lydian, Mahjong Tiles, Mathematical Alphanumeric Symbols, Mathematical Operators, Maya Hieroglyphs, Meroitic, Miscellaneous Mathematical Symbols-A, Miscellaneous Mathematical Symbols-B, Miscellaneous Symbols, Miscellaneous Symbols and Arrows, Miscellaneous Symbols And Pictographs, Miscellaneous Technical, Musical Symbols, Number Forms, Old Italic, Old Persian, Optical Character Recognition, Phaistos Disc, Phoenician, Phrygian, Playing Cards, Sidetic, Spacing Modifier Letters, Specials, Superscripts and Subscripts, Supplemental Arrows-A, Supplemental Arrows-B, Supplemental Mathematical Operators, Supplemental Punctuation, Tai Xuan Jing Symbols, Transport And Map Symbols, Troy vessels’ signs, Ugaritic, Yijing Hexagram Symbols, Text Fonts based on the work of Firmin Didot (1764-1836), Richard Porson (1757-1808), Victor Julius Scholderer (1880-1971), Alexander Wilson (1714-1786), Claude Garamond (1480-1561), Demetrios Damilas (c. 1493), Robert Granjon (1513-1589) et al.The MediaWiki WebFonts extension is enabled on Wikisource. It is therefore for the Wikisourcers to make their pick and ask on Bugzilla for a specific font.
Thanks,
GerardM
Friday, May 04, 2012
Font subsets III
#Google web fonts is important. A major player makes freely licensed fonts available for general use. They allow people to be more expressive because the right font adds to the message. They allow people to contribute to existing fonts and make new fonts available.
Both Google and the Wikimedia Foundation invest in freely licensed web fonts and because of this, an opportunity for cooperation exists. The Wikimedia Foundation supports all languages in all scripts particularly for use in its projects and Google supports the world with its Google docs where people can use web fonts in their own documents and in their own language.
As the two organisations complement each other so well, it would be great when they share their web fonts. Wikipedia can become more expressive and for Google docs usable fonts can be associated with the languages that they support. A combined outreach of Google and the WMF will make web fonts even more visible and it will make the effort of both organisations even more relevant.
Thanks,
GerardM
Both Google and the Wikimedia Foundation invest in freely licensed web fonts and because of this, an opportunity for cooperation exists. The Wikimedia Foundation supports all languages in all scripts particularly for use in its projects and Google supports the world with its Google docs where people can use web fonts in their own documents and in their own language.
As the two organisations complement each other so well, it would be great when they share their web fonts. Wikipedia can become more expressive and for Google docs usable fonts can be associated with the languages that they support. A combined outreach of Google and the WMF will make web fonts even more visible and it will make the effort of both organisations even more relevant.
Thanks,
GerardM
#Font subsets II
Arguments to support Junicode:
- it is a freely licensed font
- it has a clearly defined use case
Arguments against the use of Junicode as a web font:
- it is really big
- it does not target one script
- it is only one font for a script
When you read the Wikipedia article on the Runic script, it becomes abundantly clear that the Runic script evolved over time. Not only does the shape of characters change, the number of characters used is different as well. This is perfectly normal and it argues against the use of a single font for a single script.
As Junicode is freely licensed, it is possible to break the font up in pieces and have a separate font to be used for Runic and another for Gothic. When other fonts for Runic are available as well, we can show sources with a font that resembles the original best and provide a more familiar font for easy reading as well.
Thanks,
GerardM
Thursday, May 03, 2012
#Font subsets
A font with all the characters for the Latin or Cyrillic script is big. Over a mega byte big. This is considered too big for use in a web font particularly when mobile devices are targeted as well. For this reason, moves are under way to split mega fonts in subsets.
At SIL they are working on font subsets. Their criteria is to include all the characters used in a given "region". In this way they explicitly target a range of languages. It does reduce the size and one font can be used as a web font for all these languages. When they are to be used on Wikipedia, it will still be necessary to identify the specific language and have the language associated with a particular region.
Typically a font does not include all characters anyway. It is created with a language in mind and when another language needs extra characters, it is tough. Many languages do use the same subset of characters and when a font is identified as complete for one language, it follows that it is complete for all other languages as well.
SIL needs a way to subset its existing fonts. Google in contrast provides many fonts as web fonts that provide subsets of the Latin script. As it is not made obvious if these fonts support languages like German, French or Dutch, it is not really attractive when English is not your language.
Both Google and SIL provide solutions. The key question they do not explicitly answer is: does it support my language.
Thanks,
GerardM
At SIL they are working on font subsets. Their criteria is to include all the characters used in a given "region". In this way they explicitly target a range of languages. It does reduce the size and one font can be used as a web font for all these languages. When they are to be used on Wikipedia, it will still be necessary to identify the specific language and have the language associated with a particular region.
Typically a font does not include all characters anyway. It is created with a language in mind and when another language needs extra characters, it is tough. Many languages do use the same subset of characters and when a font is identified as complete for one language, it follows that it is complete for all other languages as well.
SIL needs a way to subset its existing fonts. Google in contrast provides many fonts as web fonts that provide subsets of the Latin script. As it is not made obvious if these fonts support languages like German, French or Dutch, it is not really attractive when English is not your language.
Both Google and SIL provide solutions. The key question they do not explicitly answer is: does it support my language.
Thanks,
GerardM
Saturday, March 31, 2012
#WebFonts for the #French #Wikisource
Following the deployment of the WebFonts extension on the English Wikisource, it is now the French who asked for WebFonts. With WebFonts it is possible to show selected texts in a specific font. At this time the selected texts will not be in French because no fonts are available for the Latin script.Once content is labelled as being in a different language, it is obvious what texts are in French or in another language. This will not only trigger WebFonts for the languages with a default font, it will also help people analysing the content of the French Wikisource.
WebFonts is a tool that delivers fonts where needed. So far we have not really considered supporting languages in the Latin script with WebFonts. When there are fonts that serve a purpose and are freely licensed, adding support will certainly be considered.
One of the issues that we will have to consider is how to support the really big fonts. When they support multiple scripts it does affect the time it takes to send a font to the user. This is one area where local fonts and web fonts substantially differ.
Historic scripts like Runic and Cuneiform but also modern scripts like the Latin script have evolved a lot over time. To do justice to this and to differences in different places, it will be important to have fonts that reflect these differences.With the interest of the Wikisourcerers we may learn from them about the fonts available under a free license that do justice to all such considerations.
Thanks,
GerardM
Sunday, March 18, 2012
The #Santali language and the Ol Chiki script
At first the Santali language was hardly written and when it was, it was written in the Bengali alphabet, Oriya alphabet, or the Latin alphabet. As Santali is not an Indo-Aryan language (like most other languages in the north of India), Indic scripts do not have letters for all of Santali's phonemes, especially its stop consonants and vowels, which made writing the language accurately in an unmodified Indic script difficult.
The Ol Cemet', Ol Chiki or simply Ol was created in 1925 by Raghunath Murmu specifically for the Santali script one letter is assigned to each phoneme.
A Wikipedia has been requested for the Santali language and it will be localised in the script that is popular with most people. Apparently this is the Latin script. This does not mean that the Ol Chiki script is not relevant for use within a Santali Wikipedia.
There is a font that is available for free. Sadly it is not available under a free license. Finding the copyright holder for these fonts allows us to request a change of the license. Once the license is changed, we can make the font available as a web font.
Thanks,
GerardM
The Ol Cemet', Ol Chiki or simply Ol was created in 1925 by Raghunath Murmu specifically for the Santali script one letter is assigned to each phoneme.
A Wikipedia has been requested for the Santali language and it will be localised in the script that is popular with most people. Apparently this is the Latin script. This does not mean that the Ol Chiki script is not relevant for use within a Santali Wikipedia.
There is a font that is available for free. Sadly it is not available under a free license. Finding the copyright holder for these fonts allows us to request a change of the license. Once the license is changed, we can make the font available as a web font.
Thanks,
GerardM
Friday, March 09, 2012
It is all #Malayalam to me
When you give me a text to read in a script like the Malayalam script, it is all the same to me. Like in the example below, I can recognised different elements; I recognise the user interface, I notice an introductory text followed by the text that is introduced. It is likely this way because it is after all text in the Malayalam Wikisource.
For automated systems like the ones employed by Google, recognising a script is easy; all characters of a script have their own number and it is just a matter of looking them up. This is what automated systems do really well.
They are, like me, not able to recognise that the bottom text in the example below is written in Sanskrit.
Automated systems can be helped by identifying texts using labels embedded in the text. Something like this: <div lang="sa">സംസ്കൃതം</div>. It helps Google but it will confuse its systems. The default script for Sanskrit is Devanagari and this is implied when you only use the language code.
When the embedded label is like this <div lang="sa-Mlym">സംസ്കൃതം</div>, it will be clear that it is Sanskrit written in the Malayalam script. It will not only be clear to Google, it will also be clear to the WebFonts extension because it can be configured to use fonts for the Malayalam script in a Sanskrit text.
Thanks,
GerardM
For automated systems like the ones employed by Google, recognising a script is easy; all characters of a script have their own number and it is just a matter of looking them up. This is what automated systems do really well.
They are, like me, not able to recognise that the bottom text in the example below is written in Sanskrit.
Automated systems can be helped by identifying texts using labels embedded in the text. Something like this: <div lang="sa">സംസ്കൃതം</div>. It helps Google but it will confuse its systems. The default script for Sanskrit is Devanagari and this is implied when you only use the language code.
When the embedded label is like this <div lang="sa-Mlym">സംസ്കൃതം</div>, it will be clear that it is Sanskrit written in the Malayalam script. It will not only be clear to Google, it will also be clear to the WebFonts extension because it can be configured to use fonts for the Malayalam script in a Sanskrit text.
Thanks,
GerardM
The #Mongolian #script
Have a look at the article "Mongolian script". Now do the same thing with another browser or use Chrome as your browser.
The blocks represent the Unicode characters and I do not have a Mongolian font on my system yet. What is really cool is that Chrome shows Mongolian correctly from top to bottom. So far the lack of support for top down text in browsers is what prevents us from figuring out what we need to do in MediaWiki.
It will be cool when top down scripts are supported in most modern browsers. It enables us to support the people who read the top down scripts as well and consequently it brings us closer to what we aim to achieve.
Thanks,
GerardM
The blocks represent the Unicode characters and I do not have a Mongolian font on my system yet. What is really cool is that Chrome shows Mongolian correctly from top to bottom. So far the lack of support for top down text in browsers is what prevents us from figuring out what we need to do in MediaWiki.
It will be cool when top down scripts are supported in most modern browsers. It enables us to support the people who read the top down scripts as well and consequently it brings us closer to what we aim to achieve.
Thanks,
GerardM
Friday, February 24, 2012
Relevant historic texts
The Cyrus cylinder is arguably one important piece of world heritage. It consists of a text written in the cuneiform script. The text is still relevant after two thousand year so much so, that there is a TED presentation about it.
The text is in translation available at Wikisource. Given that the English Wikisource will support WebFonts next week, having a freely licensed font to do justice to the Cyrus cylinder is the next step before we can reliably show the text as it exists on the cylinder. Having a translation adds value to the source.
Thanks,
GerardM
Monday, February 20, 2012
#MediaWiki supports #Amharic
Having a #font for the Ge'ez script allows you to see what a language like the Amharic or the Tigrinya language look like. Chances are that many people who have the font on their system can also read a language that uses the script.
For those people who do not have a font for this script on their computer, the Amharic Wikipedia now supports the AbyssinicaSIL font. For the people who do not know this, Amharic is spoken in Ethiopia.
When you use the current Firefox, you will get an experience like the one below. We already know that a next version of Chrome will properly support it. I do not know about the other browsers. What I do know is that Firefox is doing a sterling job for me.
Thanks,
GerardM
For those people who do not have a font for this script on their computer, the Amharic Wikipedia now supports the AbyssinicaSIL font. For the people who do not know this, Amharic is spoken in Ethiopia.
When you use the current Firefox, you will get an experience like the one below. We already know that a next version of Chrome will properly support it. I do not know about the other browsers. What I do know is that Firefox is doing a sterling job for me.
Thanks,
GerardM
Thursday, February 16, 2012
Some texts are more equal then others
In #Ubuntu, the fonts for #Malayalam and several other scripts are a bit broken. As you can see in the Google+ screenshot, headers are not displayed. This is probably because the font provided by Ubuntu does not support bold or something.
Obviously, the best solution is when the fonts used by Ubuntu provide the full support applications expect. When these fonts fail as they do, it is possible to provide web fonts. Google is very much into web fonts but it seems that they have a preoccupation with the one script that is already so well supported.
It would be so cool when the people who develop fonts would concentrate their efforts where they provide the most benefit. Enabling the full functionality of a script and its associated languages on the Internet is arguably more relevant then prettifying single webpages.
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;
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
Subscribe to:
Posts (Atom)



















