Bug#340373: spellcheck should allow use of fallback language
On Wed, 2005-11-23 at 02:31 +0100, Rene Engelhard wrote:
> Hi,
>
> Drew Parsons wrote:
> > I've defined the default document language in Options: Language
> > Settings->Languages to English (Australian). Likewise, I've selected the
> > dictionary in Language Settings->Writing Aids->Myspell Spellchecker (Edit)
> > to English (UK). But this spellcheck dictionary setting is being ignored.
> >
> > It's not just English (Australian). What if I want to write a multicultural
> > document, with French and German sections, say. How am I supposed to
> > spellcheck them as well when the language used for spellchecking is so
> > tightly bound to the document default language?
>
> It's not. It's bound to the language of the text. You can e.g. have
> german as document default language and format english parts as English
> (UK) at Format->Character. Then that part is considered English (UK) and
> will be checked with the en_UK dictionary.
>
> Is that what you want? Or do I misunderstand this report?
>
OK, Format->Character was something I had missed, thanks for pointing it
out. I can use it to set the text to en(UK), in which case the
spellcheck does check it. That deals with my French/German
multicultural example.
As far as using it to check Australian text with a UK dictionary,
however, it feels like a bit of a nuisance which ought not to be
necessary. In my opinion it should possible to define a default for
each language. That is defining en_GB, for example, as the default
dictionary for any en_XX variant, if it doesn't have its own specific
dictionary.
The same would work for others, e.g. fr_CA falls back to fr, which is
set to an fr_FR dictionary, if there is no specific French Canadian
dictionary installed. Likewise de_AT would fall back to de, which might
be set to the de_DE dictionary.
I apologise if this kind of mechanism goes out of scope from what you
are able to do with OpenOffice.org. It should be something myspell
itself is able to do. Thanks for pointing out the Format->Character
workaround.
Happily for my specific situation, it can been resolved once bug #227655
is closed.
Drew
Reply to: