The standard dictionary file (standard.dic) and other user generated files contain a first line which refers to OOo. Steps to reproduce: 1. Go to standard.dic in User folder (under Windows that is C:\Dokumente und Einstellungen\~user\Anwendungsdaten\LibreOffice\3\user\wordbook 2. Open standard.dic with text editor 3. In first text line it reads "OOoUserDict1" 4. Reproduce with any other user generated user dictionary and the first line reads "OOoUserDict1" again Current behavior: - shows wrong first indication line in standard .dic file - shows wrong first indication line in user genrated .dic file and should continue numbering like "OOoUserDict2" Expected behavior: - first text line it reads "OOoUserDict1" insead of "LibUserDict1" - further user generated .dic files should number up "LibUserDict2", "LibUserDict3" etc. Platform (if different from the browser): - XP with LibO 3.4.3 (Browser: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20100101 Firefox/7.0.1) - same happens under Ubuntu 10.10 with LibO 3.4.3
'OOoUserDict1' is the file format (encoding, 'magic string') for user-readable and user-editable custom dictionaries [introduced with OOo]. See, e.g.: https://issues.apache.org/ooo/show_bug.cgi?id=60698#c15 https://issues.apache.org/ooo/show_bug.cgi?id=91392 IMHO: RESOLVED INVALID. Feel free to reopen that bug, if you did not agree with this decision.
(In reply to comment #1) > 'OOoUserDict1' is the file format (encoding, 'magic string') for user-readable > and user-editable custom dictionaries [introduced with OOo]. > > See, e.g.: > https://issues.apache.org/ooo/show_bug.cgi?id=60698#c15 > https://issues.apache.org/ooo/show_bug.cgi?id=91392 > > IMHO: RESOLVED INVALID. > > Feel free to reopen that bug, if you did not agree with this decision. I would like to reopen this bug, because I think that the decision was right for OOo, but now that LibO exists I think the dictionaries instead of 'OOoUserDict1' should contain a LobO related string like 'LibOUserDict1' I would like to hear more voices on this issue as it could have long lasting relevance.
(In reply to comment #2) > [...] > I would like to hear more voices on this issue as it could have long lasting > relevance. Agreed. I've modified 'Version' to 'unspecified' (= valid for all versions of LibO).
Why should we BREAK COMPATIBILITY for vanity? Maybe you won't believe that, but some people are actually trying to WORK in LibreOffice...