Enabling languages

Developing ICT and web solutions for lesser used and minority languages.

[Enabling languages @enablelanguages]

@zenodotus But the new lib sector specs don't leverage the I18N improvements in W3C specs.

[Enabling languages @enablelanguages]

@zenodotus Not that I am aware of. The library specific standards fall outside of W3C. There were some library sector people involved in linked data specs but honestly, I18N was an uphill battle with those specs. But horizontal reviews make it easier these days.

[Enabling languages @enablelanguages]

@zenodotus Well, if it's broken, it's broken, part or whole. But you know my position is, it's the system. The real question is can it be fixed. And the following question is whether there is anyone in a position to take responsibility for fixing it.

[Enabling languages @enablelanguages]

@zenodotus Systemic as in it is categorised as a marginal consideration so less resources? Or systemic as in an artefact of colonialism and néocolonialisme?

[Enabling languages @enablelanguages]

@zenodotus And vendors are a problem more than a help

[Enabling languages @enablelanguages]

@zenodotus Part of the problem is resourcing. Individual institutions aren't necessarily in a position to have an I18N specialist, and there isn't anyone to provide guidance and assistance.

[Enabling languages @enablelanguages]

@zenodotus My gut reaction is that existing momentum is built on flawed approaches.

[Enabling languages @enablelanguages]

@zenodotus Not familiar with the Dr

[Enabling languages @enablelanguages]

@zenodotus I was thinking also in terms of new records as well. The meta framework. Native first, romanisation as an assist. Which is the reversal of a costing practice

[Enabling languages @enablelanguages]

@zenodotus Yes and no, that is an attempt to convert from romanised to native. But considering how much of a sieve tables can be, more robust mechanisms are needed. Data is lacking.

[Enabling languages @enablelanguages]

@zenodotus Doesn't address versioning which is a key element.

[Enabling languages @enablelanguages]

@zenodotus W3C I18N WG has done a lot of work in this area. What libraries are lacking is people with the knowledge, skills and experience to apply it to this domain

[Enabling languages @enablelanguages]

@zenodotus Unfortunately full bcp-47 is needed. Iso-639-3 by itself doesn't cut it.

[Enabling languages @enablelanguages]

@zenodotus There quite a few other things but that's a start. Once interesting area would be getting bidi and vertical text working correctly in UIs, but getting bibframe up to speed with yhos would be the first step.

[Enabling languages @enablelanguages]

@zenodotus Internationalisation is poorly understood in library sector and few have the knowledge or skills, and little interest in supporting it.

[Enabling languages @enablelanguages]

@zenodotus Bibliographic data cleaning tools that can handle the various I18N issues that n existing records

[Enabling languages @enablelanguages]

@zenodotus Sort out the bad encodings mess with Cyrillic romanisations

[Enabling languages @enablelanguages]

@zenodotus PyMARC equivalent for Bibframe