Issue 13849 - de-select option to install US language module and its installed anyway
Summary: de-select option to install US language module and its installed anyway
Status: CONFIRMED
Alias: None
Product: lingucomponent
Classification: Code
Component: other (show other issues)
Version: current
Hardware: PC Windows 2000
: P3 Trivial (vote)
Target Milestone: not determined
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-26 16:19 UTC by thegoldenear
Modified: 2013-02-07 22:32 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description thegoldenear 2003-04-26 16:19:01 UTC
in OOo 1.0.3.1 and 1.1beta, if you de-select the option to install US language
module upon program installation (atleast in network/multi-user install mode)
the US language module is still copied to the
OOo-program-directory\share\dict\ooo directory

(as is hyphenation for da, de, en and ru)
Comment 1 Olaf Felka 2003-05-15 16:13:13 UTC
Hi Kevin,
deselecting the US language module at setup removes only
liblthxxxxx.so, th_en_US.idx and th_en_US.dat. I think that the user
want to see en_US.dic and en_US.aff removed also. Is this possible?
Comment 2 khendricks 2003-05-15 18:36:30 UTC
Hi,  
  
I am not sure how to deal with this.   In fact, I am not even sure there should be a  
way to disable the en US module at least not for a standard en_US build.  
  
The reason I say this is because:  
  
1. without the spell component no spellchecking in any language would work  
2. without the thesaurus component no other thesauri would work  
 (there is now a German and a Czech thesauri I believe)  
3. without the hyphenator component no hyphenation in any language would work  
  
So if we always register those components to enable Writing Aids for any language,  
but we don't install en_US.* then we would then need to somehow have to update the 
dictionary.lst file to show that nothing (no language ductionaries) should be 
registered (and I am not sure if they would even work right now without the spell 
component segfaulting trying to find at least one dictionary and affix file. 
  
So it is an either keep it all or remove it all kind of thing.  If I remove it all, then no  
writing aids will work in any language.  If I keep the components,  they expect to see  
a correctly specified dictionary.lst and a correct set of dictionaries, thesauri,  
hyphenation dicts, etc.  
  
The only way around this would be to actually deliver 2 dictionary.lst files to the  
solver with one blank and one with the en_US pieces listed. Then try to find a way for 
the spell component to properly ignore the fact it registered a service but can supply 
no dictionaries for the service to make use of.  I am not sure but I do not think 
the Spellchecking and hyphenation will work properly without at least one dictionary  
of some kind installed.  
  
So the best way to handle this right now is to literally remove the option of not  
installing the US language modules until other dictionaries and writing aids have the  
right license to be incorporated into the tree in such a way to make those modules  
usable with a different set of dictionaries for a different language.  
  
Sorry but this is probably something for OOo 1.X with X >= 2 when the license  
difficulties have been worked out properly and we can actually have multiple  
dictionaries in the tree.  
  
Kevin  
  
Comment 3 khendricks 2003-06-08 14:46:42 UTC
Hi, 
 
An update.  This should soon be closed.  I am removing the option completely 
since it makes no sense to disable en_US separately in a standard en_US build. 
 
So now, the builder will decide wkich spellcheck modules to include and which not. 
This is done with a configure line during build  
 
--with-dict= 
 
and a list of writing aids to include. 
 
So a localized build will be able to completely disable the 
en_US components resulting in a build that will not install 
them by default and or replace them with en_GB or it_IT 
or some combination as the builder desires. 
 
User's can use DictInstall to remove and add dictionaries 
including the  full range of GPL dictionaries available. 
 
So the module options will simply go away. 
 
Kevin 
 
Comment 4 khendricks 2003-11-02 14:16:17 UTC
Hi,

Moving this to lingucomponent for proper tracking and target setting.

Kevin