Task #2371
RCP: 0.7.9, update instructions on naming TreeTagger language models in TXM manual
| Status: | New | Start date: | 04/25/2018 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | Import | Spent time: | - | |
| Target version: | TXM X.X |
Description
Current TXM Manual, section 2.2.1 (http://txm.sourceforge.net/doc/manual/0.7.9/fr/manual8.xhtml#toc46) says:
5. Renommer chaque fichier de modèle en utilisant les codes de langues ISO 639-1 à deux lettres.
Actually, users can use other file names and manually type them in the import form.
It may be more useful to use the available language models in current installation in the dropdown list than all ISO 639-1 language codes.
[SLH,MD] the "dropdown list" content is also used to define the corpus LOCALE (language), used to sort alphabetically objets produced from the corpus (index, concordance...). So there must also be a correspondance list to define and maintain between file names and LOCALE names.
History
#1 Updated by Serge Heiden over 5 years ago
- Subject changed from DOC: 0.7.9, update instructions on naming TreeTagger language models in TXM manual to RCP: 0.7.9, update instructions on naming TreeTagger language models in TXM manual
- Description updated (diff)
- Category set to Import
- Target version set to TXM 0.8.0a (split/restructuration)
#2 Updated by Alexey Lavrentev over 5 years ago
Corpus locale and annotation model should probably be different parameters. However, corpus locale may be used by default to select the language model.
For the current state of TXM, I think the documentation should explain why it is useful to select the ISO language code for the corpus. (Even if the corpus is not annotated by Treetagger?)
#3 Updated by Sebastien Jacquot over 5 years ago
- Target version changed from TXM 0.8.0a (split/restructuration) to TXM 0.8.0
#4 Updated by Matthieu Decorde over 4 years ago
- Target version changed from TXM 0.8.0 to TXM X.X