dictionnaire mozilla thunderbird

Rakotomandimby (R12y) Mihamina

22/12/2004 à 11:12

( Wed, 22 Dec 2004 10:51:01 +0100 ) laurent courbez :

bonjour à tous,

Bonjour a toi.

dans les fichiers .dic des dictionnaires orthographiques de mozilla
thunderbird,[...] y a t-il quelqu'un qui pourrait m'expliquer à quoi
correspondent ces lettres ou mieux me renvoyer à des liens qui
expliquent en détails leur signification ?

fr.comp.mail ?

--
ASPO Infogérance - http://aspo.rktmb.org/activites/infogerance
Unofficial FAQ fcolc - http://faq.fcolc.eu.org/
Linux User Group sur Orléans et alentours.
Tél: + 33 2 38 76 43 65 (France)

laurent courbez

22/12/2004 à 11:17

( Wed, 22 Dec 2004 10:51:01 +0100 ) laurent courbez :

bonjour à tous,

Bonjour a toi.

dans les fichiers .dic des dictionnaires orthographiques de mozilla
thunderbird,[...] y a t-il quelqu'un qui pourrait m'expliquer à quoi
correspondent ces lettres ou mieux me renvoyer à des liens qui
expliquent en détails leur signification ?

fr.comp.mail ?

pas nécessairement, c'est pas vraiment un pb de mail, mais je vois pas
de groupe adapté au sujet.

dans la mesure où on tourne autour de gnu (donc pas trop loin de linux)
j'ai pensé que ...

LC.

Marie-Claude Collilieux

22/12/2004 à 22:40

bonjour à tous,

dans les fichiers .dic des dictionnaires orthographiques de mozilla
thunderbird, on trouve des lignes du genre

abandonner/snmtlM
abandonnerai/jnmtlx
abandonnique/LMS

Il me semble avoir vu sur le site d'OpenOffice.org un lien vers comment

créer et modifier ce dictionnaire.
Les minuscules indiquent je pense les lettres acceptables avant le mot
s' n' m'abandonner etc. Les MAJ, j'ignore...

--
Marie-Claude Collilieux
Bretagne

no_spam

22/12/2004 à 23:42

On Wed, 22 Dec 2004 10:51:01 +0100, laurent courbez wrote:

bonjour à tous,

dans les fichiers .dic des dictionnaires orthographiques de mozilla
thunderbird, on trouve des lignes du genre
[...]

abandonnique/LMS
^^^^^^^^^

Là, j'ai un sérieux doute sur la fiabilité du dictionnaire, ou alors
c'est que j'ai hiberné trop longtemps et que ça a bcp changé ! ;-)

[...]

si par la même occasion, vous avez de bons liens vers le "comment on
code un dictionnaire orthographique ou un dictionnaire des synonymes",
je suis preneur.

Un dictionnaire orthographique ou de synonymes, ce n'est jamais que de la
recherche dans une base de donnée. Avec un index bien fait, ce n'est pas
très dur. Par contre, si tu veux prendre en compte la grammaire et les
conjuguaisons, alors là, ça devient un vrai défi, notement en français...
Tu peux toujours regarder les sources des dictionnaires open-source
existants dans les divers distribs...

jp-oc

23/12/2004 à 23:56

laurent courbez wrote:

bonjour à tous,

dans les fichiers .dic des dictionnaires orthographiques de mozilla
thunderbird, on trouve des lignes du genre

abandonner/snmtlM
abandonnerai/jnmtlx
abandonnique/LMS

y a t-il quelqu'un qui pourrait m'expliquer à quoi correspondent ces
lettres ou mieux me renvoyer à des liens qui expliquent en détails leur
signification ?

si par la même occasion, vous avez de bons liens vers le "comment on
code un dictionnaire orthographique ou un dictionnaire des synonymes",
je suis preneur.

merci d'avance

LC.

Au verbe "abandonne"r on applique les regles s puis n etc. , des "affix"
prefixes et suffixes decrits dans le fichier des affix
onverting Affix Files: Understanding the Affix File Format
------------------------------------------------------------

An affix is either a prefix or a suffix attached to root words to make
other words. For example supply -> supplied by dropping the "y" and
adding an "ied" (the suffix).

Here is an example of how to define one specific suffix borrowed
from the en_US.aff file used by the OpenOffice org spellchecker

SFX D Y 4
SFX D 0 d e
SFX D y ied [^aeiou]y
SFX D 0 ed [^ey]
SFX D 0 ed [aeiou]y

This file is space delimited and case sensitive.
So this information can be interpreted as follows:

The first line has 4 fields:

Field
-----
1 SFX - indicates this is a suffix
2 D - is the name of the character which represents this suffix
3 Y - indicates it can be combined with prefixes (cross product)
4 4 - indicates that sequence of 4 affix entries are needed to
properly store the affix information

The remaining lines describe the unique information for the 4 affix
entries that make up this affix. Each line can be interpreted
as follows: (note fields 1 and 2 are used as a check against line 1 info)

Field
-----
1 SFX - indicates this is a suffix
2 D - is the name of the character which represents this affix
3 y - the string of chars to strip off before adding affix
(a 0 here indicates the NULL string)
4 ied - the string of affix characters to add
(a 0 here indicates the NULL string)
5 [^aeiou]y - the conditions which must be met before the affix
can be applied

Field 5 is interesting. Since this is a suffix, field 5 tells us that
there are 2 conditions that must be met. The first condition is that
the next to the last character in the word must *NOT* be any of the
following "a", "e", "i", "o" or "u". The second condition is that
the last character of the word must end in "y".

Now for comparison purposes, here is the same information from the
Ispell english.aff compression file which was used as the basis
for the OOo one.

flag *D:
E > D # As in create > created
[^AEIOU]Y > -Y,IED # As in imply > implied
[^EY] > ED # As in cross > crossed
[AEIOU]Y > ED # As in convey > conveyed

The Ispell information has exactly the same information but in a
slightly different (case-insensitive) format:

Here are the ways to see the mapping from Ispell .aff format to our
OOo format.

1. The ispell english.aff has flag D under the "suffix" section so
you know it is a suffix.

2. The D is the character assigned to this suffix

3. * indicates that it can be combined with prefixes

4. Each line following the : describes the affix entries needed
to define this suffix

- The first field is the conditions that must be met.

- The second field is after the > if a "-" occurs is the
string to strip off (can be blank).

- The third field is the string to add (the affix)

In addition all chars in ispell aff files are in UPPERCASE.

So the easiest way to create an OOo .aff file is to start with
an Ispell .aff file (make sure you get the wordlist author's
permission first). Then literally one by one, use a text editor
to convert the information for each prefix and suffix into the
OOo format (or write a perl script if need be).

Note: MySpell does *NOT* support multi-byte characters. It needs both
the affix file and the wordlist to use just one 8-bit character set which
is then specified in the affix file.

If the Ispell affix file and wordlist uses multiple bytes to
indicate one character, a script or editor must be used to convert
them to the proper single byte character encoding. For example,
the Ispell german affix file uses the byte sequence u" to actually
indicate the a u-umlaut character. All occurences of these
multi-byte characters must be converted to their single byte encoding
using the ISO-8859-1 character set in the affix file and the
wordlist.

FYI, the changes made to the format of the .aff file are necessary
to support on-the-fly parsing of both the affix .aff file and the
munched wordlists so that all dictionaries are literally stored
as ISO text files with associated .aff files and not endian
dependent binary hash tables dumped in some compile specific
format. The code is then smart enough to build a hashtable on
the fly just from the munched wordlist and the .aff file as long
as the text files end in either rn or simply n.

There are two other things you need to add to the MySpell affix file.

The first line specifies the character set used for both the
wordlist and the affix file (should be all uppercase).

For example:

SET ISO8859-1

And the second line specifies the characters to be used in building
suggestions for misspelled words. The should be listed in order or
character frequency (highest to lowest). A good way to develop this
string is to sort a simple character count of the wordlist.

For example:

TRY esianrtolcdugmphbyfvkw

Converting an Ispell "munched" Wordlists
----------------------------------------

To convert an Ispell "munched" wordlist to the format needed
by MySpell simply count the number of "root" words in the file and
add that count to the first line of the file (this speeds loading
the file since two passes are not needed).

laurent courbez wrote:

bonjour à tous,

dans les fichiers .dic des dictionnaires orthographiques de mozilla
thunderbird, on trouve des lignes du genre

abandonner/snmtlM
abandonnerai/jnmtlx
abandonnique/LMS

y a t-il quelqu'un qui pourrait m'expliquer à quoi correspondent ces
lettres ou mieux me renvoyer à des liens qui expliquent en détails leur
signification ?

si par la même occasion, vous avez de bons liens vers le "comment on
code un dictionnaire orthographique ou un dictionnaire des synonymes",
je suis preneur.

merci d'avance

LC.

Au verbe "abandonne"r on applique les regles s puis n etc. , des "affix"
prefixes et suffixes decrits dans le fichier des affix
onverting Affix Files: Understanding the Affix File Format
------------------------------------------------------------

An affix is either a prefix or a suffix attached to root words to make
other words. For example supply -> supplied by dropping the "y" and
adding an "ied" (the suffix).

Here is an example of how to define one specific suffix borrowed
from the en_US.aff file used by the OpenOffice org spellchecker

SFX D Y 4
SFX D 0 d e
SFX D y ied [^aeiou]y
SFX D 0 ed [^ey]
SFX D 0 ed [aeiou]y

This file is space delimited and case sensitive.
So this information can be interpreted as follows:

The first line has 4 fields:

Field
-----
1 SFX - indicates this is a suffix
2 D - is the name of the character which represents this suffix
3 Y - indicates it can be combined with prefixes (cross product)
4 4 - indicates that sequence of 4 affix entries are needed to
properly store the affix information

The remaining lines describe the unique information for the 4 affix
entries that make up this affix. Each line can be interpreted
as follows: (note fields 1 and 2 are used as a check against line 1 info)

Field
-----
1 SFX - indicates this is a suffix
2 D - is the name of the character which represents this affix
3 y - the string of chars to strip off before adding affix
(a 0 here indicates the NULL string)
4 ied - the string of affix characters to add
(a 0 here indicates the NULL string)
5 [^aeiou]y - the conditions which must be met before the affix
can be applied

Field 5 is interesting. Since this is a suffix, field 5 tells us that
there are 2 conditions that must be met. The first condition is that
the next to the last character in the word must *NOT* be any of the
following "a", "e", "i", "o" or "u". The second condition is that
the last character of the word must end in "y".

Now for comparison purposes, here is the same information from the
Ispell english.aff compression file which was used as the basis
for the OOo one.

flag *D:
E > D # As in create > created
[^AEIOU]Y > -Y,IED # As in imply > implied
[^EY] > ED # As in cross > crossed
[AEIOU]Y > ED # As in convey > conveyed

The Ispell information has exactly the same information but in a
slightly different (case-insensitive) format:

Here are the ways to see the mapping from Ispell .aff format to our
OOo format.

1. The ispell english.aff has flag D under the "suffix" section so
you know it is a suffix.

2. The D is the character assigned to this suffix

3. * indicates that it can be combined with prefixes

4. Each line following the : describes the affix entries needed
to define this suffix

- The first field is the conditions that must be met.

- The second field is after the > if a "-" occurs is the
string to strip off (can be blank).

- The third field is the string to add (the affix)

In addition all chars in ispell aff files are in UPPERCASE.

So the easiest way to create an OOo .aff file is to start with
an Ispell .aff file (make sure you get the wordlist author's
permission first). Then literally one by one, use a text editor
to convert the information for each prefix and suffix into the
OOo format (or write a perl script if need be).

Note: MySpell does *NOT* support multi-byte characters. It needs both
the affix file and the wordlist to use just one 8-bit character set which
is then specified in the affix file.

If the Ispell affix file and wordlist uses multiple bytes to
indicate one character, a script or editor must be used to convert
them to the proper single byte character encoding. For example,
the Ispell german affix file uses the byte sequence u" to actually
indicate the a u-umlaut character. All occurences of these
multi-byte characters must be converted to their single byte encoding
using the ISO-8859-1 character set in the affix file and the
wordlist.

FYI, the changes made to the format of the .aff file are necessary
to support on-the-fly parsing of both the affix .aff file and the
munched wordlists so that all dictionaries are literally stored
as ISO text files with associated .aff files and not endian
dependent binary hash tables dumped in some compile specific
format. The code is then smart enough to build a hashtable on
the fly just from the munched wordlist and the .aff file as long
as the text files end in either rn or simply n.

There are two other things you need to add to the MySpell affix file.

The first line specifies the character set used for both the
wordlist and the affix file (should be all uppercase).

For example:

SET ISO8859-1

And the second line specifies the characters to be used in building
suggestions for misspelled words. The should be listed in order or
character frequency (highest to lowest). A good way to develop this
string is to sort a simple character count of the wordlist.

For example:

TRY esianrtolcdugmphbyfvkw

Converting an Ispell "munched" Wordlists
----------------------------------------

To convert an Ispell "munched" wordlist to the format needed
by MySpell simply count the number of "root" words in the file and
add that count to the first line of the file (this speeds loading
the file since two passes are not needed).

Vous avez filtré cet utilisateur ! Consultez son message

laurent courbez wrote:

bonjour à tous,

dans les fichiers .dic des dictionnaires orthographiques de mozilla
thunderbird, on trouve des lignes du genre

abandonner/snmtlM
abandonnerai/jnmtlx
abandonnique/LMS

y a t-il quelqu'un qui pourrait m'expliquer à quoi correspondent ces
lettres ou mieux me renvoyer à des liens qui expliquent en détails leur
signification ?

si par la même occasion, vous avez de bons liens vers le "comment on
code un dictionnaire orthographique ou un dictionnaire des synonymes",
je suis preneur.

merci d'avance

LC.

Au verbe "abandonne"r on applique les regles s puis n etc. , des "affix"
prefixes et suffixes decrits dans le fichier des affix
onverting Affix Files: Understanding the Affix File Format
------------------------------------------------------------

An affix is either a prefix or a suffix attached to root words to make
other words. For example supply -> supplied by dropping the "y" and
adding an "ied" (the suffix).

Here is an example of how to define one specific suffix borrowed
from the en_US.aff file used by the OpenOffice org spellchecker

SFX D Y 4
SFX D 0 d e
SFX D y ied [^aeiou]y
SFX D 0 ed [^ey]
SFX D 0 ed [aeiou]y

This file is space delimited and case sensitive.
So this information can be interpreted as follows:

The first line has 4 fields:

Field
-----
1 SFX - indicates this is a suffix
2 D - is the name of the character which represents this suffix
3 Y - indicates it can be combined with prefixes (cross product)
4 4 - indicates that sequence of 4 affix entries are needed to
properly store the affix information

The remaining lines describe the unique information for the 4 affix
entries that make up this affix. Each line can be interpreted
as follows: (note fields 1 and 2 are used as a check against line 1 info)

Field
-----
1 SFX - indicates this is a suffix
2 D - is the name of the character which represents this affix
3 y - the string of chars to strip off before adding affix
(a 0 here indicates the NULL string)
4 ied - the string of affix characters to add
(a 0 here indicates the NULL string)
5 [^aeiou]y - the conditions which must be met before the affix
can be applied

Field 5 is interesting. Since this is a suffix, field 5 tells us that
there are 2 conditions that must be met. The first condition is that
the next to the last character in the word must *NOT* be any of the
following "a", "e", "i", "o" or "u". The second condition is that
the last character of the word must end in "y".

Now for comparison purposes, here is the same information from the
Ispell english.aff compression file which was used as the basis
for the OOo one.

flag *D:
E > D # As in create > created
[^AEIOU]Y > -Y,IED # As in imply > implied
[^EY] > ED # As in cross > crossed
[AEIOU]Y > ED # As in convey > conveyed

The Ispell information has exactly the same information but in a
slightly different (case-insensitive) format:

Here are the ways to see the mapping from Ispell .aff format to our
OOo format.

1. The ispell english.aff has flag D under the "suffix" section so
you know it is a suffix.

2. The D is the character assigned to this suffix

3. * indicates that it can be combined with prefixes

4. Each line following the : describes the affix entries needed
to define this suffix

- The first field is the conditions that must be met.

- The second field is after the > if a "-" occurs is the
string to strip off (can be blank).

- The third field is the string to add (the affix)

In addition all chars in ispell aff files are in UPPERCASE.

So the easiest way to create an OOo .aff file is to start with
an Ispell .aff file (make sure you get the wordlist author's
permission first). Then literally one by one, use a text editor
to convert the information for each prefix and suffix into the
OOo format (or write a perl script if need be).

Note: MySpell does *NOT* support multi-byte characters. It needs both
the affix file and the wordlist to use just one 8-bit character set which
is then specified in the affix file.

If the Ispell affix file and wordlist uses multiple bytes to
indicate one character, a script or editor must be used to convert
them to the proper single byte character encoding. For example,
the Ispell german affix file uses the byte sequence u" to actually
indicate the a u-umlaut character. All occurences of these
multi-byte characters must be converted to their single byte encoding
using the ISO-8859-1 character set in the affix file and the
wordlist.

FYI, the changes made to the format of the .aff file are necessary
to support on-the-fly parsing of both the affix .aff file and the
munched wordlists so that all dictionaries are literally stored
as ISO text files with associated .aff files and not endian
dependent binary hash tables dumped in some compile specific
format. The code is then smart enough to build a hashtable on
the fly just from the munched wordlist and the .aff file as long
as the text files end in either rn or simply n.

There are two other things you need to add to the MySpell affix file.

The first line specifies the character set used for both the
wordlist and the affix file (should be all uppercase).

For example:

SET ISO8859-1

And the second line specifies the characters to be used in building
suggestions for misspelled words. The should be listed in order or
character frequency (highest to lowest). A good way to develop this
string is to sort a simple character count of the wordlist.

For example:

TRY esianrtolcdugmphbyfvkw

Converting an Ispell "munched" Wordlists
----------------------------------------

To convert an Ispell "munched" wordlist to the format needed
by MySpell simply count the number of "root" words in the file and
add that count to the first line of the file (this speeds loading
the file since two passes are not needed).

Rakotomandimby (R12y) Mihamina

25/12/2004 à 10:44

( Wed, 22 Dec 2004 11:17:50 +0100 ) laurent courbez :

dans la mesure où on tourne autour de gnu

Autour de GNU, il ya fr.comp.applications.libres (modéré).
C'est peut-etre aussi un bon point de depart...
--
ASPO Infogérance - http://aspo.rktmb.org/activites/infogerance
Unofficial FAQ fcolc - http://faq.fcolc.eu.org/
Linux User Group sur Orléans et alentours.
Tél: + 33 2 38 76 43 65 (France)

jp-oc

25/12/2004 à 19:04

jp-oc wrote:
pour compléter

pour les langues
il faut un dictionnaire des mots , verbes, noms propre
exemple fr-FR.dic
avec tous les mots à la suite les uns des autres
à priori cela suffirait mais il faudrait mettre les féminins, les
pluriels ,tous les verbes conjugués,les articles l', etc...
pour simplifier on décrit dans un fichier des affixes : les préfixes,
suffixes et conjugaisons
par exemple le fichier fr-FR.aff

dans mon fichier .dic
j'inscris le verbe avaler par exemple

dans le fichier .aff je vais décrire la conjugaison des verbes réguliers du
premier groupe type chanter
j'appelle la règle R par exemple qui sera une règle de suffixe
ou il faudra remplacer la fin du verbe "er" par "a" pour la conjugaison a la
première personne du présent et ainsi de suite

je vais faire aussi une règle des préfixes
par exemple la règle l et la règle n qui rajouteront l' et n'

Pour revenir à mon verbe avaler de l'exemple
dans le fichier dico fr-FR.dic je vais l'écrire comme suit
avaler/lnR

ce qui veut dire que j'applique à avaler les regles d'affixes l puis n puis
R
cela évite d'inscrire dans ce .dic
l'avaler
n'avaler
avala
n'avala
etc.. au moins 50 lignes de déclinaisons possibles

si je rajoute chanter dans mon dico
chanter/R
là je n'applique que la règle R et pas l ou n car l'chanta ou d'chantai
n'existent pas

Bien sûr pour les verbes irreguliers on est obligé d'inscrire in extension
toutes les formes dans le .dic

il y aussi d'autres fonctions dévolues au fichier .aff

PS : Je suis entrain de faire le Dico Occitan

Rakotomandimby (R12y) Mihamina

25/12/2004 à 20:06

lamb or a good beef roast if the haunch
it is in any way diseased. But sometimes surgeons make mistakes,
and if a healthy young limb is at hand, then don?t hesitate to cook
it to perfection!

1 high quality limb, rack, or roast
Potatoes, carrot
Oil
celery
onions
green onions
parsley
garlic
salt, pepper, etc
2 cups beef stock

Marinate meat (optional, not necessary with better cuts).
Season liberally and lace with garlic cloves by making incisions,
and placing whole cloves deep into the meat.
Grease a baking pan, and fill with a thick bed of onions,
celery, green onions, and parsley.
Place roast on top with fat side up.
Place uncovered in 500° oven for 20 minutes, reduce oven to 325°.
Bake till medium rare (150°) and let roast rest.
Pour stock over onions and drippings, carve the meat and
place the slices in the au jus.

Bisque à l?Enfant

Honor the memory of Grandma with this dish by utilizing her good
silver soup tureen and her great grandchildren (crawfish, crab or
lobster will work just as well, however this dish is classically
made with crawfish).

Stuffed infant heads, stuffed crawfish heads, stuffed crab or lobster shells;
make patties if shell or head is not available
(such as with packaged crawfish, crab, or headless baby).
Flour
oil
onions
bell peppers
garlic salt, pepper, etc.
3 cups chicken stock
2 sticks butter
3 tablespoons oil

First stuff the heads, or make the patties (see index)
then fry or bake.
Set aside to drain on paper towels.
Make a roux wit

jp-oc

25/12/2004 à 22:11

with whole roasted children replete with apples in mouths -
and babies? heads stuffed with wild rice. Or keep it simple with a
hearty main course such as stew, lasagna, or meat loaf.

Some suggestions

Pre-mie pot pies, beef stew, leg of lamb, stuffed chicken, roast pork spiral ham,
Cranberry pineapple salad, sweet potatoes in butter, vegetable platter, tossed salad with tomato and avocado, parsley new potatoes, spinich cucumber salad, fruit salad
Bran muffins, dinner rolls, soft breadsticks, rice pilaf, croissants
Apple cake with rum sauce, frosted banana nut bread sherbet, home made brownies
Iced tea, water, beer, bloody marys, lemonade, coffee

The guests select food, beverages, silverware... everything from the buffet table.
They move to wherever they are comfortable, and sit with whoever they choose.
Provide trays so your guests will not spill everything all over your house from
carrying too much, nor will they have to make 10 trips back and fourth from the
service stations.

Roast Leg of Amputee

By all means, substitute lamb or a good beef roast if the haunch
it is in any way diseased. But sometimes surgeons make mistakes,
and if a healthy young limb is at hand, then don?t hesitate to cook
it to perfection!

1 high quality limb, rack, or roast
Potatoes, carrot
Oil
celery
onions
green onions
parsley
garlic
salt, pepper, etc
2 cups beef stock

Marinate meat (optional, not necessary with better cuts).

dictionnaire mozilla thunderbird

9 réponses

Veuillez sélectionner un problème