On Thu, 2007-07-05 at 11:03 +0200, Thomas Lange - Sun Germany - ham02 - Hamburg wrote: > Hi again, > > I forgot to mention that the tagged file format uses also UTF-8 > encoding. Thus you'll need a UTF-8 capable text editor to properly > view > and edit those files. > > Also just in case: > The string following the language tag refers to ISO locale of the > language the dictionary is to be uded with. > E.g. en-US would be English (USA) and de-CH would be German > (Swiss)... > And the line > lang: <none> > will be used for dictionaries that are to be used for all languages. > > Please be aware that in this file format spaces do matter! > Have the wrong number of spaces, use tabs, or add additional spaces at > the end and it may not work. > > > Thomas > >
Dear Lange The problem for me, as it stands now, is solved. Russel Butler became and angel and created the file. But, the thing is, never in the line I understood what was happening. Let me report you the whole thing. 1. It was a zipped text file from Project Gutenberg that contained quite a lot of accents, diacritical marks. When I wanted to open it with OOo, it wanted to know what encoding to use. The default was UTF-8, but this encoding was ruining the file: everything getting mangled and mixed up. 2. Though, according to PGDP standard, it was Latin 1 encoding, when I tried to open it with the Windows Latin 1 encoding, it again got a mixed up thing. 3. Finally the encoding that worked was West Europe (ISO-8859-1). With this it opened nicely. And I did my work on it, editing and all. 4. Now, when I wanted to get the word-list thus generated within the custom dictionary dd.dic into a text file, I was not being able to do that. Russell Butler suggested one macro-loaded ODT (earlier in this thread). I tried that. But that did not work. The list it was generating was the mixed up thing. 5. But, all this time when I open the word-list contained within the custom dictionary from the Tools-Options-Language-Writing-Aid-Edit, it was showing them all quite well. And if I copied and pasted that from the file into gedit or Evolution, that was correct too. But If I open the dd.dic with OOo and give it the encoding WE ISO-8859-1, it was getting mixed up. No other encoding worked too. Including UTF-8. 6. I then sent the file, the original text file, its ODT counter part, and the dd.dic to Butler. He created this thing for me in a .txt file and this again worked fine. And now, I see, when I open the ODT the Tools-Option-Language way, the custom dictionary shows mixed up characters. Though, when I paste them into 'gedit' or 'Evolution' they show correct. 7. All this is quite a mystery to me. Shall I send the files to you. The text file in the first place may be the culprit. Someone else in PGDP who opened it with her Mac, got the problem, like 'château' getting displayed as 'ch,teau', exactly the way I was getting it in the mixed up file. --- das --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
