Hi !
I have a proposal about making new chunks in interchunk. At the moment
if we want to make a new chunk we have to put in <lit> tags with '{' and
'}' -- this is superugly. Here is an example:
<chunk>
<lit v="prep"/>
<lit-tag v="PREP"/>
<lit v="{^na"/>
<lit-tag v="pr"/>
<lit v="$}"/>
</chunk>
output: ^prep<PREP>{^na<pr>$}$
It would be supernicer if it were like this:
<chunk>
<lit v="prep"/>
<lit-tag v="PREP"/>
<chcontent>
<lu>
<lit v="на"/>
<lit-tag v="pr"/>
</lu>
</chcontent>
</chunk>
output: ^prep<PREP>{^na<pr>$}$
What do people think ? It would mean changing the DTD and the transfer
code... But quite a simple change I think, and backwards compatible.
<chcontent> outputs {
</chcontent> outputs }
<lu> (in chunker) outputs ^
</lu> (in chunker) outputs $
Fran
PS. People are really using the <lit v="{"/> hack at the moment:
$ cat trunk/apertium-[a-z][a-z]-[a-z][a-z]/*.t2x | grep '{' |wc -l
586
It appears in the following files:
/home/fran/source/apertium//trunk/apertium-br-fr/apertium-br-fr.br-fr.t2x
/home/fran/source/apertium//trunk/apertium-cy-en/apertium-cy-en.cy-en.t2x
/home/fran/source/apertium//trunk/apertium-en-ca/apertium-en-ca.ca-en.t2x
/home/fran/source/apertium//trunk/apertium-en-ca/apertium-en-ca.en-ca.t2x
/home/fran/source/apertium//trunk/apertium-en-es/apertium-en-es.en-es.t2x
/home/fran/source/apertium//trunk/apertium-en-es/apertium-en-es.es-en.t2x
/home/fran/source/apertium//trunk/apertium-en-gl/apertium-en-gl.en-gl.t2x
/home/fran/source/apertium//trunk/apertium-en-gl/apertium-en-gl.gl-en.t2x
/home/fran/source/apertium//trunk/apertium-eo-ca/apertium-eo-ca.ca-eo.t2x
/home/fran/source/apertium//trunk/apertium-eo-en/apertium-eo-en.en-eo.t2x
/home/fran/source/apertium//trunk/apertium-eo-en/apertium-eo-en.eo-en.t2x
/home/fran/source/apertium//trunk/apertium-eo-es/apertium-eo-es.es-eo.t2x
/home/fran/source/apertium//trunk/apertium-eo-fr/apertium-eo-fr.fr-eo.t2x
/home/fran/source/apertium//trunk/apertium-eu-es/apertium-eu-es.eu-es.t2x
/home/fran/source/apertium//trunk/apertium-fr-ca/apertium-fr-ca.fr-ca.t2x
/home/fran/source/apertium//trunk/apertium-fr-es/apertium-fr-es.es-fr.t2x
/home/fran/source/apertium//trunk/apertium-fr-es/apertium-fr-es.fr-es.t2x
/home/fran/source/apertium//trunk/apertium-is-en/apertium-is-en.is-en.t2x
/home/fran/source/apertium//trunk/apertium-nn-nb/apertium-nn-nb.nb-nn.t2x
/home/fran/source/apertium//trunk/apertium-oc-ca/apertium-oc-ca.ca-oc.t2x
/home/fran/source/apertium//trunk/apertium-oc-ca/apertium-oc-ca.oc-ca.t2x
/home/fran/source/apertium//trunk/apertium-oc-ca/[email protected]
/home/fran/source/apertium//trunk/apertium-oc-ca/ca-oc.t2x
/home/fran/source/apertium//trunk/apertium-oc-es/apertium-oc-es.es-oc.t2x
/home/fran/source/apertium//trunk/apertium-oc-es/[email protected]
/home/fran/source/apertium//trunk/apertium-oc-es/es-oc.t2x
So we should really have a way of expressing it properly.
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Apertium-stuff mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/apertium-stuff
