Spell checker: Difference between revisions
Jump to navigation
Jump to search
m moved Man 2 ch07s03 to Spell checker |
mNo edit summary |
||
| (6 intermediate revisions by 3 users not shown) | |||
| Line 4: | Line 4: | ||
|lang=en | |lang=en | ||
|rev=2.0.0 | |rev=2.0.0 | ||
|st= | |st=u | ||
|Title= | |Title=Spell checker | ||
|prev= | |prev=Hidden features | ||
|Subtitle= | |Subtitle=More than a Text Editor | ||
|next= | |next=Programming and Markup Languages Function Reference | ||
}} | }} | ||
BlueFish 1 and 2 spell checker doesn't take into account the language written in the file header nor the "lang" attribute of tags. | |||
For the spell checker to work properly, | |||
*<tt>Document > Spell check</tt> must be set. | |||
*you have to select the page language manually. To do so, '''right-click''' in the text you want to check . If your page is in several languages, repeat the operation for each language. | |||
[[File:Man2_spell_checker.png|none|frame|Bluefish Spell Checker]] | [[File:Man2_spell_checker.png|none|frame|Bluefish Spell Checker]] | ||
The language code used in the list is a simplified version of the [http://en.wikipedia.org/wiki/IETF_language_tag IETF language tag], mostly defined in the technical document [http://tools.ietf.org/html/rfc5646#section-2.1 RFC 5 646], except that, in BlueFish spell checker, the hyphen has been replaced by an underscore. The first 2 or 3 small letters stand for the language, while the capital letters after the underscore stand for the region. For instance "en_GB" means "British English". The list of codes is known as the "[http://www.iana.org/assignments/language-subtag-registry language subtag registry]". | |||
Bluefish uses enchant, so most spell dictionaries should be supported. I | Bluefish uses enchant as spell checking backend, so most spell dictionaries should be supported. I think aspell dictionaries are preferred for enchant. Use your package manager to install the dictionaries. | ||
think aspell dictionaries are preferred for enchant. Use your package | |||
manager to install the dictionaries. | |||
The 'string' textstyle is automatically checked. You can disable that in | The 'string' textstyle is automatically checked. You can disable that in the preferences. | ||
the preferences. | |||
Spell checking | <small>Spell checking before 2.0.1 missed the "Ignore spelling" and "Add to dictionnary" functions.</small> | ||
</ | |||
{{Man2bottom | {{Man2bottom | ||
|prev= | |prev=Hidden features | ||
|up= | |up=Indenting | ||
|next= | |next=Programming and Markup Languages Function Reference | ||
|prevname= | |prevname=Hidden features | ||
|nextname= | |nextname=Programming and Markup Languages Function Reference | ||
}} | }} | ||
Latest revision as of 08:33, 8 July 2011
BlueFish 1 and 2 spell checker doesn't take into account the language written in the file header nor the "lang" attribute of tags. For the spell checker to work properly,
- Document > Spell check must be set.
- you have to select the page language manually. To do so, right-click in the text you want to check . If your page is in several languages, repeat the operation for each language.
The language code used in the list is a simplified version of the IETF language tag, mostly defined in the technical document RFC 5 646, except that, in BlueFish spell checker, the hyphen has been replaced by an underscore. The first 2 or 3 small letters stand for the language, while the capital letters after the underscore stand for the region. For instance "en_GB" means "British English". The list of codes is known as the "language subtag registry".
Bluefish uses enchant as spell checking backend, so most spell dictionaries should be supported. I think aspell dictionaries are preferred for enchant. Use your package manager to install the dictionaries.
The 'string' textstyle is automatically checked. You can disable that in the preferences.
Spell checking before 2.0.1 missed the "Ignore spelling" and "Add to dictionnary" functions.