Recent changes to bugs

The debian package (64 bit) fail during the Installation

2013-03-13T07:47:31Z

When we try to install the package
TXM_0.7_Linux64.deb
On Ubuntu 12.10 ( 64 bits )

The automatic installation of rgl fail because GL/gl.h file is missing.

Users can solve temporary the problem by installing the debian package : mesa-common-dev before installing TXM.
( I have installed libglu1-mesa-dev, but i think that mesa-common-dev is sufficient ).

I think that the TXM package should contain a dependance with mesa-common-dev to solve the problem.

TXM does not start in ubuntu 11.10

2012-11-07T14:05:13Z

After an installation that went without any problems, TXM however does not start (I've exchanged userid/computername with dummy)

$ TXM &
[1] 7935
dummy@dummy:/usr/lib/TXM/TXM/configuration$ Prepare redirections in /home/dummy/TXMPostInstallLogs.txt and /home/dummy/TXMPostInstallErrorLogs.txt
Nov 7, 2012 3:02:35 PM org.txm.rcpapplication.Application run
INFO: java.version : 1.6.0_24

Nothing else happens, until one presses enter:

[1]+ Exit 13 TXM

I attach config.ini, please let me know whether you need more info or how to solve the problem.

tokenizer with letter t for euphony-TXM 0.6

2012-06-11T10:32:47Z

The splitting tokens set obtained with the TXM tokenizer is different from the usual tokenizer.pl when we consider expression like "chanta-t-il".
This lead TreeTagger to make erroneous tagging.
Hereafter is a small example :

Résults extracted from TXM (format TT for easier comparison)

147 Chanta VER:simp chanter
148 - PUN -
149 t VER:pper t
150 - PUN -
151 il PRO:PER il
152 pour PRP pour
153 m' PRO:PER me
154 écouter VER:infi écouter
155 sans PRP sans
156 s' PRO:PER se
157 assoupir VER:infi assoupir
158 ? SENT ?

2/ Results with Tokeniser.pl

Chanta
-t-il
pour
m'
écouter
sans
s'
assoupir
?

Résults withTreeTagger case 2/

Chanta VER:simp chanter f VER:simp
-t-il PRO:PER il f PRO:PER
pour PRP pour f KON PRP
m' PRO:PER me f PRO:PER
écouter VER:infi écouter f VER:infi
sans PRP sans f KON PRP
s' PRO:PER se f KON PRO:PER
assoupir VER:infi assoupir f VER:infi
? SENT ? f SENT

By the way, we observe also the XML file and found that
for pronouns (m', s') (n #153 #156) there no "type" attribute and is asked for if it was a bug or not ?

<w id="w_propreounon_147" n="147" type="w"><txm:form>Chanta</txm:form><txm:ana resp="#txm" type="#frutf8pos">VER:simp</txm:ana><txm:ana resp="#txm" type="#frutf8lemma">chanter</txm:ana></w>
<w id="w_propreounon_148" n="148" type="pon"><txm:form>-</txm:form><txm:ana resp="#txm" type="#frutf8pos">PUN</txm:ana><txm:ana resp="#txm" type="#frutf8lemma">-</txm:ana></w>
<w id="w_propreounon_149" n="149" type="w"><txm:form>t</txm:form><txm:ana resp="#txm" type="#frutf8pos">VER:pper</txm:ana><txm:ana resp="#txm" type="#frutf8lemma">t</txm:ana></w>
<w id="w_propreounon_150" n="150" type="pon"><txm:form>-</txm:form><txm:ana resp="#txm" type="#frutf8pos">PUN</txm:ana><txm:ana resp="#txm" type="#frutf8lemma">-</txm:ana></w>
<w id="w_propreounon_151" n="151" type="w"><txm:form>il</txm:form><txm:ana resp="#txm" type="#frutf8pos">PRO:PER</txm:ana><txm:ana resp="#txm" type="#frutf8lemma">il</txm:ana></w>
<w id="w_propreounon_152" n="152" type="w"><txm:form>pour</txm:form><txm:ana resp="#txm" type="#frutf8pos">PRP</txm:ana><txm:ana resp="#txm" type="#frutf8lemma">pour</txm:ana></w>
<w id="w_propreounon_153" n="153"><txm:form>m'</txm:form><txm:ana resp="#txm" type="#frutf8pos">PRO:PER</txm:ana><txm:ana resp="#txm" type="#frutf8lemma">me</txm:ana></w>
<w id="w_propreounon_154" n="154" type="w"><txm:form>écouter</txm:form><txm:ana resp="#txm" type="#frutf8pos">VER:infi</txm:ana><txm:ana resp="#txm" type="#frutf8lemma">écouter</txm:ana></w>
<w id="w_propreounon_155" n="155" type="w"><txm:form>sans</txm:form><txm:ana resp="#txm" type="#frutf8pos">PRP</txm:ana><txm:ana resp="#txm" type="#frutf8lemma">sans</txm:ana></w>
<w id="w_propreounon_156" n="156"><txm:form>s'</txm:form><txm:ana resp="#txm" type="#frutf8pos">PRO:PER</txm:ana><txm:ana resp="#txm" type="#frutf8lemma">se</txm:ana></w>
<w id="w_propreounon_157" n="157" type="w"><txm:form>assoupir</txm:form><txm:ana resp="#txm" type="#frutf8pos">VER:infi</txm:ana><txm:ana resp="#txm" type="#frutf8lemma">assoupir</txm:ana></w>
<w id="w_propreounon_158" n="158" type="pon"><txm:form>?</txm:form><txm:ana resp="#txm" type="#frutf8pos">SENT</txm:ana><txm:ana resp="#txm" type="#frutf8lemma">?</txm:ana></w></s>
</p></text></TEI>
hereafter is the example :

import XML-TEI TXM version 0.6 beta2

2012-05-02T16:33:37Z

(XP 32 bits)
We have got the following :
[lemma="__UNDEF__"] and the key is </tei> in
"process the full lexicon with optionproperty set to lemma
This is an anomal add to the reading the file.
(Adding a lf at the end doesn't make any change).
Doesn't seems make any other trouble.

CLM

[TXM 0.6b1] export de cooccurrence vers Concordances

2011-12-08T10:47:51Z

Bonjour,

j'ai un problème avec l'export d'un cooccurrent vers la concordance (TXM 06.b1 RCP, Ubuntu 11.10).

Exemple :

avec le corpus DISCOURS, je fais une requête de cooccurrences sur le mot "Parlement". La liste des cooccurrents s'affiche.

Je fais un clic droit sur l'une des lignes, par exemple, la première, qui contient le mot "législatif" ; j'envoie vers Concordances.

Voici la requête qui est transmise à Concordances :
("Parlement" []* [word="[3815]"] ) | ([word="[3815]"] []* "Parlement") within 51
J'obtiens 6 résultats, qui contiennent le "mot" 3, 8, 1 ou 5, mais pas "législatif".

Pour information : la requête corrigée (ci-dessous) est censée donner 8 résultats :
("Parlement" []* [word="législatif"] ) | ([word="législatif"] []* "Parlement") within 51

text+csv import - tags not set

2011-12-06T20:46:12Z

According to the 7.9 of the txm documentation, we have generated the following metadata.csv file (where file1 and file2 are two text files) :
id,field1,field2,fields3
"file1","data11","data12","data13"
"file2","data21","data22","data23"

we got a metadata.csv.xml file that looks good.

Despite the simplicity of the datas, they are not fully inserted in the both resulting xml files under corpora/txm.
So selecting one of fields above with a previous data for building a sub corpus is not possible.

bug on import csv+txt seems not fixed (XP)

2011-11-30T16:21:10Z

add the parameters to the function as describe for fixing the bug. I've got the following messages :
Erreur lors de l'exécution du script groovygroovy.lang.MissingMethodException: No signature of method: org.txm.metadatas.Metadatas.injectMetadatasInXmlTXM() is applicable for argument types: (java.io.File, java.io.File, java.lang.String, null) values: [C:\Documents and Settings\Charles\TXM\corpora\geneonly\txm\le_monde_1995.xml, C:\Documents and Settings\Charles\TXM\corpora\geneonly\txm\le_monde_1995.xml, text, null]
Possible solutions: injectMetadatasInXmlTXM(java.io.File, java.io.File), injectMetadatasInXml(java.io.File, java.io.File, java.lang.String), injectMetadatasInXml(java.io.File, java.io.File, java.lang.String, java.lang.String)
groovy.lang.MissingMethodException: No signature of method: org.txm.metadatas.Metadatas.injectMetadatasInXmlTXM() is applicable for argument types: (java.io.File, java.io.File, java.lang.String, null) values: [C:\Documents and Settings\Charles\TXM\corpora\geneonly\txm\le_monde_1995.xml, C:\Documents and Settings\Charles\TXM\corpora\geneonly\txm\le_monde_1995.xml, text, null]
Possible solutions: injectMetadatasInXmlTXM(java.io.File, java.io.File), injectMetadatasInXml(java.io.File, java.io.File, java.lang.String), injectMetadatasInXml(java.io.File, java.io.File, java.lang.String, java.lang.String)
at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:54)
at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:51)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:40)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:117)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:137)
at org.txm.importer.quick.quickLoader.run(quickLoader.groovy:84)
at groovy.util.GroovyScriptEngine.run(GroovyScriptEngine.java:464)
at org.txm.rcpapplication.commands.ExecuteScriptImport$1.run(ExecuteScriptImport.java:159)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

cooccurence with only one word/lemme

2011-09-14T19:11:33Z

get the following message :

java.lang.ArrayIndexOutOfBoundsException: 0
at org.txm.functions.cooccurrences.Cooccurrence.<init>(Cooccurrence.java:455)
at org.txm.rcpapplication.editors.cooccurrences.CooccurrencesEditor$11.run(CooccurrencesEditor.java:627)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Perhaps this is related to the number of files of he corpus ( 258 ) ?

Impossible d'exporter Table lexicale

2011-06-15T09:24:30Z

Sous Mac OX 10.6 et TXM 0.5, il est impossible d'exporter une table lexicale quel que soit le corpus testé. La commande provoque une lévée d'exception dans la console (cf. fichiers attachés)

Corpus importé ne s'affiche pas

2011-06-07T14:10:26Z

Un corpus créé par l'intermédiaire du module TXT+CSV à partir d'un répertoire dont le nom comporte une cédille ("Français") ne s'affiche pas dans l'arbre des objets, bien que l'importation semble correctement effectuée (les données apparaissent dans le répertoire corporata).