[ooo-build] How to set location of dictionary files

[espinosa_cz]

Caolán McNamara wrote:
>>> Was there any discussion with
>>> freedesktop.org/LSB/myspell/hunspell/Mozilla teams
>>> about the naming and structure? I know, symbolic links can help a lot
>>> here, but it sound you are laying down a new linux filesytem standard here.
>>>       
>> I am afraid that it wasn't. As I said, it was implemented by the Sun 
>> developers. I think that you could ask in the bug if you report it.
>>     
>
> I'm pretty sure I implemented a chunk of the current OOo-side of the use
> "external dictionary" stuff, mostly because I had a problem I wanted to
> solve, so I solved it. 
As a developer myself it is very difficult for me to imagine a solution 
based on hard coding once variable configuration option like directory 
path. Perhaps may be as a very temporary work around.
Can we rejoice in expectation of this being fixed in 3.x lifeline?
I am positive that making go-oo build cross distribution is a priority 
for go-oo team and this issue breaks it.
Now even non-external dictionaries fail to work for me for some reason :(

> I did not get into a ludicrous gathering of the
> twelve tribes of free software to discuss the location of the dir, just
> picked the first directory that the standalone hunspell searches as the
> default for hunspell dicts (of course previously it used myspell as its
> first dir to search which is why Fedora and some other stick them there
> instead, ah well) and made up some reasonably similar ones for the
> thesaurus and hyphenators.
>   
Well you don't have to gather tribes, just a humble announcement and 
opening a discussion parallel to implementation would be enough, at 
least for start.

I always supposed that freedesktop.org was established (also) for this 
purposes.
> Personally, I wouldn't waste any upstream developers time on any bugs
> wrt. complaints about the default dirs or configurable search paths
> without a provided implementation.
>   
Well, I have just reported it to upstream as I have already written 
(#104133).
If for for developers rushing to fix it then at least for statistical 
and documentation purposes ;-)

Thank you for all you great work
Jan