To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=94420





------- Additional comments from [EMAIL PROTECTED] Mon Sep 29 11:00:25 +0000 
2008 -------
TL: I have not yet debugged into it but just by looking at it the use of both of
them is already troublesome, because the do make use of the same node names for
the dictionaries. And after all node names should be unique!
It shouldn't cause a crash but having the same node names is already potentially
inviting trouble.

I'll quote a posting from MBA in the lingucomponent dev board about this
(25.09.2008 19:40):
======================================
If people outside the core developer cycle want to provide an
extensions, I recommend to use the reversed domain schema notation. If
e.g. you are employed by company "linguprovider" in Russia that has the
domain linguprovider.ru you could name your node

"ru.linguprovider.grabinski.dict_ru"

This should help to avoid name clashes. If your company was too big to
make you feel comfortable with being the only "Grabinski", you could add
more "namespaces", e.g.

"ru.linguprovider.division1.grabinski.dict_ru"

Just break it down to a level where you think you can arrange everything
easily.

If you are doing your dictionary just as a private person you can use
your own domain or your e-mail address etc. This should help to keep the
probability of name clashes low.
======================================

Thus it would be interesting to know if everything is fine if the node name
problem is solved. 

TL->Milek: Do you have the time to repack one of the extensions to see what
happens then?


---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to