multilingual ontologies - ontology

I'm new to Protege OWL 4 and confused about multilingual ontologies. I want to quickly start a non-english OWL based on an English one. I have three questions:
Which plugins to use? there is an OntoLing http://ainlp.info.uniroma2.it/software/OntoLing/UserManual.html#LinguisticEnrichment
If mapping, how to do it, is there a tutorial?
Labels of the annotation property don't have the language I want
Any guidance would be greatly appreciated.

I would usually approach this by using the original english ontology and add annotion labels. In Protégé 4, you can add custom languages to the labels by simply entering the desired value directly into the Lang field, in the Add Annotation Dialog (see screenshot).

Related

Phonetic translation from Latin (English, German) to Arabic

I read a few papers about machine translation but did not understand them well.
The language models (in Google translate) use phonetics and machine learning as best as I can tell.
My question then becomes is it possible to convert an Arabic word that is phonetically spelled in English to translate the users intended Arabic word?
For instance the word 'Hadith' is an English phonetic of the Arabic word 'حديث'. Can I programmatically go from 'Hadith' to Arabic?
Thanks the Wiki article, there's an entire field of work in the area of Transliteration. There was a Google API for this that was deprecated in 2011 and moved to the Google Input Tools service.
The simplest answer is Buck Walter Transliteration but at first glace a 1:1 mapping doesn't seem like a good enough idea.
I am going to try to see if there's a way to hack the Google Input tools and call it even at CLI level because their online demo works very well

iOS - Country and Language Specific Localization

We are migrating our app from iOS6 to iOS7 and we use programmatic way of creating view (rather from storyboard or nibs).
We are trying to support multiple countries with different languages.
Example,
English for - China, India, US
Simplied Chinese for- Taiwan, China
There can be custom override's for specfic country from the basic language localization set.
Now I need to have a common base for language bundles and country specific bundles.
Common Language Bundles: (base language bundles)
en.lproj
zh_hans.lproj
Country Specific Override Bundles: (if i have custom text for each specific countries)
ch(ina)_en.lproj
ch(ina)_hans.lproj
us_en.lproj
Problem:
Resource files (Translations) have to be duplicated for each countries(chinese, taiwan) with english, chinese. How can we avoid this ?. Images are also duplicated sometimes, it is a maintenance problem, if we start support more than 10 countries.
Android supports delta overrides of translations for each language translation per country, do we have anything in iOS similar to that ?.
I know it is not supported out of the box from iOS. What is the right way to achieve the same without duplicating the resources ?. Any hints or ideas to achieve the same ?.
Thanks,
Alex
I hope I've understood correctly.
1a.Image files will only need to be duplicated per language if they contain text or "imagery" that requires translation otherwise there should only be one version. From memory, you select which image files you want to be translated.
2a.A translation is needed for each language you want to support - there is no way round this (obviously). These usually live in "strings" files which you send off for translation.
2b.If you don't supply a specific translation for a string it defaults to the "base" translation. Unfortunately, I don't know how this would work with two "base" translations or even if this is possible as usually the base translation is the language you developed in. You will need to investigate further.
2c.You will need to manage deltas to your strings file yourself - through GIT perhaps? This is annoying but do-able although there may be third-party products that can do this.

How to make Protege 4.3 display chinese character correctly?

I am using Protege 4.3 to create and organize an Ontology which contains Chinese characters.
As you can see, some Chinese characters are displayed properly, but others are displayed in little squares. The little squares do not always occur, for example: if I click on the []-[]-[]-cheatsheet-[]-[]-[]-[]-[], I can the same Chinese characters are displayed without problem.
Do you know what I can do to make Protege 4.3 display chinese characters correctly and consistently?
I guess I could have done further homework for this question. It's a post close to the final solution. (I have to post this as an answer for the length doesn't fit comment box)
To be specific, I found from Protege Mailing List Archive the following feedback post
[p4-feedback] Protege 4.2.0 Chinese Display Problem:
https://mailman.stanford.edu/pipermail/p4-feedback/2012-June/004721.html
I know this problem and have even fixed it on one occasion. But I don't truly understand it or know what to do about it. I am sorry that I don't have good information on this problem but I will give you my best current understanding.
In my experience, when this happens the character information is correctly encoded in the OWL file. The problem is exclusively a display problem. This is consistent with your description of the problem - in some of the screens the individuals are displaying correctly.
I believe that the problem has to do with the configuration of fonts in the java virtual machine. If you change the instance of java that Protege is using the problem will manifest in different ways or it will go away. When I worked on this problem before (it has happened
a couple of times) I gathered some web pages. Unfortunately only one of them is still valid, but perhaps it is part of the solution.
I will post my own investigation results after trying the suggested approach above.
PS: A useful owl example is provided here - some unicode characters do not display correctly in Protege

Language codes reference

Can someone please give me the official reference to the language (country/region) codes. I'm finding different codes for the same language (es_ES, esp_ESP, etc.) and I can't figure out which one is the right one.
There are several different standards specifying language codes, including ISO-639 with its sub-standards 1-3 and IETF language tags, which describe more of a system of possible codes than the codes themselves.
Which standard is "the right" standard depends on your use case and context. See http://en.wikipedia.org/wiki/Language_codes.
That's because the languages naming coding has different standards, using different number of letters. You might have to chose which standard to use and maybe detect which standard the data source you have is using.
This is a starting point: http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes
These codes are a combination of the specific language as well as the conuntry in which the language is used. So for instance means es_ES spanish_Spain. Another one would be es_AR which would mean spanish_Argentina. For the language code there's the Language Matrix, as for the localisation part you could use the ISO 3166-2 country reference
you can find all the regions code in documentation here

Bypass conditional formatting limitations?

I have to color Calc rows, based on some string condition. So each time some string value appear in B column, the entire column is colored in certain color. It looks like on this image.
I need more strings and more conditions. How can I overcome this limitation?
Use Libreoffice 3.5 which no longer has this limitation.
For older Libreoffice version there should be an extension providing the same functionailty. Check in the Libreoffice extension repository if you can find it.
As the above answer states, LibreOffice 3.5 allows as many conditional formatting rules as you need. You just click the "add" button on the right hand side. To clear up an error in a previous post, VBA is minimally supported in Star/Open/Libre office. They have their own functions and BASIC programming rules that are similar, but most detailed VBA programs from excel spreadsheets need to be rewritten as the syntax is fairly different.
I don't know how long this link will be good for, but this is what I have been using as a guide for programming:
http://198.62.75.4/opt/sun_docs/C/solaris_10/SUNWsodoc/SO7BPG/

Resources