Opened 20 years ago

Closed 17 years ago

Last modified 15 years ago

#1627 closed defect (fixed)

Wrong reference to portuguese dictionary

Reported by: nne@… Owned by: nobody@…
Priority: high Milestone:
Component: spell Version: 1.3.4
Severity: minor Keywords:
Cc: jamatos@…, j.spitzmueller@…, ehmsen@…, iamsergio@…

Description

This is a typo, present since early versions of Lyx, please replace references to:
/usr/lib/aspell/portuges
with
/usr/lib/aspell/portugues
That is the correct location of the portuguese dictionary.

Best regards,
Nelson

Change History (12)

comment:1 by Juergen Spitzmueller, 19 years ago

Cc: j.spitzmueller@… jamatos@… added

AFAICS the problem is that the babel option for portuguese is called
"portuges" (8-char name), and LyX uses this for the spellchecker also.
You have to enter "portugues" into the "alternative language" files of
Preferences->Language->Spellchecker or create a symbolic link
from /usr/lib/aspell/portuges to /usr/lib/aspell/portugues

José, is this correct?

comment:2 by José Matos, 19 years ago

You are right Jürgen.
In a sense this is a bug in lyx by not taking into account this eccentricity of
the Portuguese spellchecker name. BTW, the name doesn't make sense even in
Portuguese, it would need to be "português", or without the accent the same as
the dictionary name.

comment:3 by Juergen Spitzmueller, 19 years ago

There used to be a similar problem with German (babel: "german", aspell:
"deutsch"). Probably LyX should have a list for the alternative dictionary
names?

comment:4 by José Matos, 19 years ago

Subject: Wrong reference to portuguese dictionary

I agree.

comment:5 by Georg Baum, 19 years ago

Looking at src/language.h and lib/languages there are two language names: lang
and babel. I don't know where lang is used for, but maybe it should be used for
the spellchecker instead of babel? Of course the portuges entry in
lib/languages would need to be updated.
Or maybe this is done already, and only the entry in lib/languages is wrong?

comment:6 by levon, 19 years ago

Owner: changed from levon to nobody@…

comment:7 by ehmsen@…, 18 years ago

Cc: ehmsen@… added

Any news on fixing this?

comment:8 by José Matos, 18 years ago

I am busy right now, I will only look into this after July.

I guess the fix should be easy, but I don't have the right now to guarantee a
correct patch.

Sorry. :-(

comment:9 by iamsergio@…, 18 years ago

Did you take that look?

comment:10 by iamsergio@…, 18 years ago

Cc: iamsergio@… added

comment:11 by José Matos, 17 years ago

Keywords: fixedintrunk added
Resolution: fixed
Status: newclosed

This problem is fixed in 1.5.0, it can not be fixed earlier as it involves a
file format change.

Now, as far as I understand the different issues, this only happens when the
chosen spellchecker is ispell. Since aspell has an ispell compatibility layer
sometimes we see the error coming from aspell.

In this case the wise choice is to change the preferences to aspell or, if
possible, aspell (library).

comment:12 by ps@…, 15 years ago

Keywords: fixedintrunk removed
Note: See TracTickets for help on using tickets.