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





------- Additional comments from [EMAIL PROTECTED] Mon Jul  7 08:12:50 +0000 
2008 -------
It can be done. See attachment sampleDics.zip in issue 60698.

For example the content may look like this:
OOoUserDict1
lang: en-US
type: positive
---
wrong
correct

The encoding will be UTF-8.
But that format does not have much of a parser it very much depends on using the
correct amount of spaces for the keywords (in line 2 and 3). And you better not
have leading or trailing spaces as well.

However that encoding was only added on request while the current default
encoding was already in existence and being used.
Thus you can use it. But it is not the default.

Thus it works like this:
You can't create dictionaries with that encoding from within the OOo UI.
But if you already have one with it it will work and that encoding will be kept
even if you modify the content via UI.

Thus what you need to do is:

- either create an empty dictionary (similar to the one in the sampleDics
archive) and copy that to the location where all the other ones are saved as
file. Then you can write a little macro to copy the contents from your previous
ones one-by-one to the new one. Following that you can modify that new file in
any UTF-8 editor. (Beware of the spaces!)

- You could create a complete new dictionary from scratch in an editor.
Of course that way you would have to enter all entries manually...

For the time being that is all there is.
In the long run it would be nice if the user dictionaries were to use a
hunspell/myspell compatible format. But right now user dictionaries are not an
issue handled by hunspell directly.


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