Search Mailing List Archives
[protege-discussion] protege with other languages
Timothy Redmond
tredmond at stanford.edu
Sat Apr 17 09:30:13 PDT 2010
This exception actually makes a bit of sense. Though I would usually
say that this is an unlikely theory, it looks like this is a problem
with Sun Java. Perhaps there is some other more plausible explanation.
Could you send your platform printout? E.g. the console prints out
Starting Protege 4 OWL Editor (Version 4.1.0, Build = 102)
Platform:
Java: JVM 1.6.0_17-b04 Memory: 466M
Language: en, Country: US
Framework: Apache Software Foundation (1.5)
OS: linux (2.6.31-20-generic)
Processor: x86-64
I don't actually know how to proceed with this issue yet but it might
give me some ideas of where to go from here.
-Timothy
On 04/17/2010 02:54 AM, Alex Shkotin wrote:
> and I have the same in P4.1_alpha.
>
> well, if it is not the same on all PCs then here is a log from my one:
>
>
> Error 1 Logged at Sat Apr 17 13:49:09 MSD 2010
> NullPointerException: null
> java.util.Hashtable.put(Hashtable.java:394)
> sun.font.PhysicalStrike.getGlyphPoint(PhysicalStrike.java:112)
> sun.font.SunLayoutEngine.nativeLayout(Native Method)
> sun.font.SunLayoutEngine.layout(SunLayoutEngine.java:133)
> sun.font.GlyphLayout$EngineRecord.layout(GlyphLayout.java:648)
> sun.font.GlyphLayout.layout(GlyphLayout.java:447)
>
> sun.font.ExtendedTextSourceLabel.createGV(ExtendedTextSourceLabel.java:308)
>
> sun.font.ExtendedTextSourceLabel.getGV(ExtendedTextSourceLabel.java:294)
>
> sun.font.ExtendedTextSourceLabel.createCharinfo(ExtendedTextSourceLabel.java:563)
>
> sun.font.ExtendedTextSourceLabel.getCharinfo(ExtendedTextSourceLabel.java:492)
>
> sun.font.ExtendedTextSourceLabel.getLineBreakIndex(ExtendedTextSourceLabel.java:438)
> java.awt.font.TextMeasurer.calcLineBreak(TextMeasurer.java:308)
> java.awt.font.TextMeasurer.getLineBreakIndex(TextMeasurer.java:544)
> java.awt.font.LineBreakMeasurer.nextOffset(LineBreakMeasurer.java:340)
> java.awt.font.LineBreakMeasurer.nextLayout(LineBreakMeasurer.java:422)
> javax.swing.text.TextLayoutStrategy.sync(TextLayoutStrategy.java:298)
>
> javax.swing.text.TextLayoutStrategy.insertUpdate(TextLayoutStrategy.java:52)
> javax.swing.text.FlowView.loadChildren(FlowView.java:126)
> javax.swing.text.CompositeView.setParent(CompositeView.java:122)
> javax.swing.text.FlowView.setParent(FlowView.java:272)
> javax.swing.text.CompositeView.replace(CompositeView.java:200)
> javax.swing.text.BoxView.replace(BoxView.java:164)
> javax.swing.text.CompositeView.loadChildren(CompositeView.java:97)
> javax.swing.text.CompositeView.setParent(CompositeView.java:122)
>
> javax.swing.plaf.basic.BasicTextUI$RootView.setView(BasicTextUI.java:1316)
> javax.swing.plaf.basic.BasicTextUI.setView(BasicTextUI.java:678)
> javax.swing.plaf.basic.BasicTextUI.modelChanged(BasicTextUI.java:667)
>
> javax.swing.plaf.basic.BasicTextUI$UpdateHandler.insertUpdate(BasicTextUI.java:1842)
>
> javax.swing.text.AbstractDocument.fireInsertUpdate(AbstractDocument.java:185)
>
> javax.swing.text.AbstractDocument.handleInsertString(AbstractDocument.java:734)
>
> javax.swing.text.AbstractDocument.insertString(AbstractDocument.java:693)
> javax.swing.text.DefaultEditorKit.read(DefaultEditorKit.java:254)
> javax.swing.JEditorPane.setText(JEditorPane.java:1499)
>
> org.protege.editor.owl.ui.renderer.OWLCellRenderer.prepareTextPane(OWLCellRenderer.java:637)
>
> org.protege.editor.owl.ui.renderer.OWLCellRenderer.prepareRenderer(OWLCellRenderer.java:469)
>
> org.protege.editor.owl.ui.renderer.OWLCellRenderer.getTreeCellRendererComponent(OWLCellRenderer.java:361)
>
> org.protege.editor.owl.ui.tree.OWLObjectTreeCellRenderer.getTreeCellRendererComponent(OWLObjectTreeCellRenderer.java:34)
>
> javax.swing.plaf.basic.BasicTreeUI$NodeDimensionsHandler.getNodeDimensions(BasicTreeUI.java:2712)
>
> javax.swing.tree.AbstractLayoutCache.getNodeDimensions(AbstractLayoutCache.java:475)
>
> javax.swing.tree.VariableHeightLayoutCache$TreeStateNode.updatePreferredSize(VariableHeightLayoutCache.java:1342)
>
> javax.swing.tree.VariableHeightLayoutCache$TreeStateNode.expand(VariableHeightLayoutCache.java:1478)
>
> javax.swing.tree.VariableHeightLayoutCache$TreeStateNode.expand(VariableHeightLayoutCache.java:1270)
>
> javax.swing.tree.VariableHeightLayoutCache.ensurePathIsExpanded(VariableHeightLayoutCache.java:966)
>
> javax.swing.tree.VariableHeightLayoutCache.setExpandedState(VariableHeightLayoutCache.java:164)
>
> javax.swing.plaf.basic.BasicTreeUI.updateExpandedDescendants(BasicTreeUI.java:1643)
>
> javax.swing.plaf.basic.BasicTreeUI$Handler.treeExpanded(BasicTreeUI.java:3716)
> javax.swing.JTree.fireTreeExpanded(JTree.java:2656)
> javax.swing.JTree.setExpandedState(JTree.java:3427)
> javax.swing.JTree.expandPath(JTree.java:2163)
>
> javax.swing.plaf.basic.BasicTreeUI.toggleExpandState(BasicTreeUI.java:2204)
>
> javax.swing.plaf.basic.BasicTreeUI.selectPathForEvent(BasicTreeUI.java:2313)
>
> javax.swing.plaf.basic.BasicTreeUI$Handler.handleSelection(BasicTreeUI.java:3520)
>
> javax.swing.plaf.basic.BasicTreeUI$Handler.mousePressed(BasicTreeUI.java:3459)
>
> java.awt.AWTEventMulticaster.mousePressed(AWTEventMulticaster.java:262)
>
> java.awt.AWTEventMulticaster.mousePressed(AWTEventMulticaster.java:262)
>
> java.awt.AWTEventMulticaster.mousePressed(AWTEventMulticaster.java:262)
>
> java.awt.AWTEventMulticaster.mousePressed(AWTEventMulticaster.java:262)
>
> java.awt.AWTEventMulticaster.mousePressed(AWTEventMulticaster.java:262)
>
> java.awt.AWTEventMulticaster.mousePressed(AWTEventMulticaster.java:262)
> java.awt.Component.processMouseEvent(Component.java:6260)
> javax.swing.JComponent.processMouseEvent(JComponent.java:3255)
> java.awt.Component.processEvent(Component.java:6028)
> java.awt.Container.processEvent(Container.java:2041)
> java.awt.Component.dispatchEventImpl(Component.java:4630)
> java.awt.Container.dispatchEventImpl(Container.java:2099)
> java.awt.Component.dispatchEvent(Component.java:4460)
> java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4574)
> java.awt.LightweightDispatcher.processMouseEvent(Container.java:4235)
> java.awt.LightweightDispatcher.dispatchEvent(Container.java:4168)
> java.awt.Container.dispatchEventImpl(Container.java:2085)
> java.awt.Window.dispatchEventImpl(Window.java:2475)
> java.awt.Component.dispatchEvent(Component.java:4460)
> java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
>
> java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
>
> java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
>
> java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
> java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
> ---------------------------------------------------------------------------------------------------
>
>
>
> 2010/4/17 Timothy Redmond <tredmond at stanford.edu
> <mailto:tredmond at stanford.edu>>
>
>
>>
>> but my test ontology
>> http://earth.jscc.ru/ontologies/Ontology_sanscrit.owl (I am
>> sorry for "c")
>> throws exception on this way:
> Funny - I didn't have this problem. I looks like it is showing
> sanscrit. (I don't know any sanscrit but it looks convincing.)
>
> -Timothy
>
>
>
>
> On 04/17/2010 12:12 AM, Alex Shkotin wrote:
>> I am not sure if Manjula has the same,
>>
>> but my test ontology
>> http://earth.jscc.ru/ontologies/Ontology_sanscrit.owl (I am
>> sorry for "c")
>> throws exception on this way:
>>
>> in Protege 4
>> 1. Open "OWL ontology from URI"
>> http://earth.jscc.ru/ontologies/Ontology_sanscrit.owl. = OK.
>> 2. go to "Classes" tab and double click "Thing". = I got
>> exception and interface broken.
>>
>> to see Sanskrit letters in this ontology use
>> http://pellet.owldl.com/owlsight/
>>
>> Is there something wrong with Sanskrit? As with Russian it is OK.
>>
>> Alex
>>
>> 2010/4/17 manjula wijewickrema <manjula53 at gmail.com
>> <mailto:manjula53 at gmail.com>>
>>
>> Hi Timothy,
>> Thanks for your reply. I will try to follow your guidence.
>> Manjula
>>
>> On Fri, Apr 16, 2010 at 7:01 PM, Timothy Redmond
>> <tredmond at stanford.edu <mailto:tredmond at stanford.edu>> wrote:
>>
>> On 04/16/2010 02:06 AM, manjula wijewickrema wrote:
>>> Dear Timothy,
>>> Thanks a lot for your reply. It courages me to study
>>> furthermore. The last issue, I have asked is, if Protege
>>> supports to any other languages (say Sinhala) then what
>>> is the procedure we can follow to use Sinhala in order
>>> to build ontologies in Protege (just instead of default
>>> English language)?
>>
>> Actually there is something else to say and I should have
>> mentioned this in my earlier post. It is very likely
>> that you want all your concepts to have both english and
>> sinhala names (and perhaps some other languages also).
>> In addition depending on who is viewing the ontology, you
>> may want it to be seen in whatever language they use.
>>
>> There is a standard accepted way to do this. Instead of
>> expecting the concepts in the ontology to be viewed by
>> their resource name, you give each concept an rdfs:label
>> annotation value. Users are then expected to use the
>> rdfs:label field to view the name of each concept in the
>> ontology. Each rdfs:label annotation can include a
>> language specification. So for Sinhala you would use
>> "sin" to indicate the language. For english you would
>> use en. Thus different people with different default
>> languages can see the same ontology in their language.
>>
>> This way of writing an ontology is fully supported in
>> Protege 3 and 4 and will be understood by owl tools in
>> general.
>>
>> -Timothy
>>
>>
>>
>>
>>> Are there any references (i.e. Wiki pages or something
>>> else) which have described these kinds of scenarios?
>>> Thanx in advance
>>> Manjula
>>>
>>> On Fri, Apr 16, 2010 at 11:02 AM, Timothy Redmond
>>> <tredmond at stanford.edu <mailto:tredmond at stanford.edu>>
>>> wrote:
>>>
>>>
>>> A question very similar to this was answered very
>>> recently. Sinhala is included in the unicode
>>> standard (chart attached). Unicode is fully
>>> supported by Protege.
>>> There are a couple of system specific issues that
>>> come up though. There is the issue of telling the
>>> operating system to support sinhala keyboard input.
>>> I am able to do this on my linux machine here but I
>>> can't speak for your system. I have done similar
>>> things on os x and windows machines.
>>>
>>> Finally there is the question of whether your java
>>> installation includes all the needed fonts. This
>>> isn't working so well on my linux machine but I
>>> would bet that windows and os x machines will do
>>> fine. This last issue is something that I don't
>>> understand so well at the moment. I would like to
>>> know how to fix this.
>>>
>>> -Timothy
>>>
>>> manjula wijewickrema wrote:
>>>
>>> Hello,
>>> I am a new one leyman for Protege. Is there any
>>> possibility of useing Sinhala language (Sinhala
>>> comes with Unicode) to make ontologies with
>>> Protege. If so how can I change the language to
>>> Sinhala? Is there any material to refer?
>>> Thanks,
>>> Manjula.
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> protege-discussion mailing list
>>> protege-discussion at lists.stanford.edu
>>> <mailto:protege-discussion at lists.stanford.edu>
>>> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>>>
>>> Instructions for unsubscribing:
>>> http://protege.stanford.edu/doc/faq.html#01a.03
>>>
>>>
>>>
>>> _______________________________________________
>>> protege-discussion mailing list
>>> protege-discussion at lists.stanford.edu
>>> <mailto:protege-discussion at lists.stanford.edu>
>>> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>>>
>>> Instructions for unsubscribing:
>>> http://protege.stanford.edu/doc/faq.html#01a.03
>>>
>>>
>>>
>>> _______________________________________________
>>> protege-discussion mailing list
>>> protege-discussion at lists.stanford.edu <mailto:protege-discussion at lists.stanford.edu>
>>> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>>>
>>> Instructions for unsubscribing:http://protege.stanford.edu/doc/faq.html#01a.03
>>>
>>
>>
>> _______________________________________________
>> protege-discussion mailing list
>> protege-discussion at lists.stanford.edu
>> <mailto:protege-discussion at lists.stanford.edu>
>> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>>
>> Instructions for unsubscribing:
>> http://protege.stanford.edu/doc/faq.html#01a.03
>>
>>
>>
>> _______________________________________________
>> protege-discussion mailing list
>> protege-discussion at lists.stanford.edu
>> <mailto:protege-discussion at lists.stanford.edu>
>> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>>
>> Instructions for unsubscribing:
>> http://protege.stanford.edu/doc/faq.html#01a.03
>>
>>
>>
>> _______________________________________________
>> protege-discussion mailing list
>> protege-discussion at lists.stanford.edu <mailto:protege-discussion at lists.stanford.edu>
>> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>>
>> Instructions for unsubscribing:http://protege.stanford.edu/doc/faq.html#01a.03
>>
>
>
> _______________________________________________
> protege-discussion mailing list
> protege-discussion at lists.stanford.edu
> <mailto:protege-discussion at lists.stanford.edu>
> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>
> Instructions for unsubscribing:
> http://protege.stanford.edu/doc/faq.html#01a.03
>
>
>
> _______________________________________________
> protege-discussion mailing list
> protege-discussion at lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.stanford.edu/pipermail/protege-discussion/attachments/20100417/1a4fa255/attachment.html>
More information about the protege-discussion
mailing list