#ISO - the shame that is in #standards behind a #paywall

The International Organisation for Standardisation exists for one reason and one reason alone. It is to define and promote standards. On the one hand it does a wonderful job and on the other hand it has been set up to fail miserably.

Defining a standard is hard work and a political process. Once it has been defined, it is ratified, it has to be adopted. The politicians, that make the process extra hard have for reasons that are ... political, decided that ISO has to pay for itself and consequently it was told to raise funds by charging people for learning about standards.

The consequence is that people make do with other standards or substandard descriptions of the standard like this one for the ISO 8601. Substandard because it is not the standard.

Wikidata includes information about events, it knows about a start date and an end date. This is what the ISO 8601 is about: date, time, calculation of periods and obviously the presentation of all that. Obviously, it is easy enough to buy one copy of the text of the standard.  But at the same time, there are many people, projects that are not as fortunate. They are anxious about implementing what is already defined in a standard, an ISO standard.

It is wrong headed politicians that ruin what is important. The politics of standards should be about the macro effects; the adoption of standards. It should not be about micro managing a system and breaking the system in the process.
Thanks,
       GerardM

#ImpactOCR - Digital publications and the national libraries

According to the #ISBN standard, the "format/means of delivery are irrelevant in deciding whether a product requires an ISBN". However, it is often assumed that a publication requiring an ISBN number is a commercial publication. In the USA and the UK for instance you have to buy your ISBN number or bar code while in Canada they are free because Canada stimulates Canadian culture.

When a standard is not universally applied, it loses application. When all publications are not registered a national library will have to maintain its own system when it is to collect a copy of all publications. As a result the ISBN is dysfunctional as a standard because it does not function as a standard.

When the Wikisourcerers finish the transliteration of a book, it deserves an ISBN number and, national libraries should be aware of these publications. This recognises and registered the work done in the Open Content world. When these books are registered, all the Open Content projects may know that they can concentrate on another book or source.

As the ISBN does not register all publications, it does not do what it is expected to do; function as a standard. 
Thanks,
       GerardM

#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.

Getting the knack of Narayam

Narayam provides input methods to several languages of India. This is seen with keen interest by many Wikimedia communities. Their need for an input method is no less profound then for their language.

At the India hackathon people expressed interest to create an input method for Marathi or Panjabi. At the WikiConference India there was interest to create an input method for the Angika language.

When technical people and language people get together, they can do awesome stuff. The language people know what it should look like while the technical people can make it happen. Doing this in an organised way however is the difference between a hack and a solution.

To create solutions we have our language support teams; once hacks are tried and tested, when it meets with all the initial requirements hacks can become a solution when they are passed on to downstream applications. When a Marathi keyboard method has been defined, why not have it also in a Linux distribution or defined in the applicable ISO standard.

Yes, it is great to start with hacks but our languages are not only used in MediaWiki for Wikipedia.
Thanks,
      GerardM

A #keyboard to enter "foreign" characters ..

#Google announced new functionality for people who search text in a different script.. "ISO 9995" is the ISO standard defining layouts of computer keyboards. It is a great and honest way of enabling people to enter search items..

Russian keyboard layout

The idea is lovely and, when this "virtual" keyboard is available not only on their search bar but also as an entry method for where the cursor is.

I would love for Google to go overboard and support scripts like the one for  Javanese, for Malayalam, Kannada and Nepali.. As the list goes on and on, I will not go overboard but, you get the idea..
Thanks,
      GerardM

Beer, free wifi and standards

Today is a day to reflect on the days that went before. I am in Milan and yesterday there was this wonderful meeting where ISO contemplated how it will continue to evolve in the 21th century. I was asked to present about Wikis, and I am very happy with the opportunity that was given to me.

I must admit that I was exceedingly nervous, I hardly slept the day before I flew, and when I arrived at Bergamo airport I found that I had left my itinerary at home. Luckily there was an Internet cafe, and I had no problem reconstructing this all important list. There was one other person there, we got to talk and it turned out that Mz Otto had to wait until 15:00 for her travel partner to fly in. This allowed us to have a pleasant day in Bergamo, we drank coffee had some gelatto and visited the botanic garden after a nice walk in the old city. A great way to ease the nerves.

That evening I had a nice meal with the other people presenting; it was great because it eased my nerves. The meeting was held in a state of the art conference room, there was a nice opening speech by Mr Bob Sutor, he presented well what technologies are maturing and how they could be used by an international organisation that ISO is.

My presentation was a mix of the technical but most importantly also the social aspects that are necessary to make a Wiki approach a success. Wikis are considered as a viable way forward by ISO. It is definetly recognition for the relevance and the vitality as perceived outside of our wiki world :)

The one glitch was the Internet availability; at the meeting it just did not work. When I got near the hotel, I found this bar, and happily drank two bears not even starting to make an inroad of all the mail and other things. Today, I am back at this bar, I have had my coffees, a beer and something to eat. It is truly a busman's holiday and I could not be more content :)
Thanks,
GerardM