Gaurav Agrawal <[email protected]>
writes:
> Hello Kevil,
>
> Thanks for answering my queries, I have some further doubts.
>
> Thanks and Regards,
> Gaurav Agrawal
> M.Tech CSE
> IIIT, Hyderabad
>
> IRC #ergaurav2
>
> On Tue, Mar 11, 2014 at 1:36 PM, Kevin Brubeck Unhammer
> <[email protected]> wrote:
>
>
> Gaurav Agrawal <[email protected]>
> writes:
>
>
> > Hello all,
> >
> > I have few queries related to non-standard dictionary format:
> >
> > 1. The one non-standard that I am aware of is metadix. Is there
> any
> > other non standard dictionary format ?
>
>
> Any language pair developer is essentially free to make up new
> XSLT's
> and use those (e.g. in nn-nb, we have a script to create a version
> of
> the dix without compounding tags).
>
>
> If we are using the xslts to have some transformation on the one
> form of .dix file to the other .dix file, then both the format is
> still a kind of the standard dictionary format (.dix). I think
> both will be validated by the dix.dtd ?
In the nn-nb case, yes.
> Is there any other higher level format like .metadix in which we
> are storing the dictionary ?
I'm not aware of any other such dix-like formats that would not validate
using dix.dtd – anyone know?
[...]
> > 2. How can we identify a language pair uses which format ?
>
>
> The makefile rule for compiling generators/analysers will not just
> say
> "lt-comp $< $@", but have some transformation, typically using
> xsltproc,
> first.
>
>
>
>
>
>
>
>
>
> But it is also possible we are doing some pre processing on the
> standard dictionary also.
>
> Yes if it's the case of the metadix, I will definitely find the
> buscaPar.xsl in the Makefile, but what about xslt transformation
> in standard dictionary also ?
I'm not sure I understand. But here's a list of xsl files I found in
SVN, sorted according to how many times I found them in Makefile.am's:
135 alt.xsl
43 buscaPar.xsl
30 translate-to-default-equivalent.xsl
22 tmp2gen.xsl
15 lexchoicebil.xsl
15 filter.xsl
14 tmp1gen.xsl
14 $$gen.xsl
4 rem-compounds.xsl
4 filterbil.xsl
2 .deps/$(LANG1).gen.xsl
alt.xsl and rem-compounds.xsl are not metadix. I don't know about the
rest.
> > 3. What is the use of the alt.xsl file ?
>
>
> In some dictionaries, there's an alt-attribute on some entries,
> this is
> typically used for marking language variants. E.g. in an English
> dix,
> you might have alt="en_GB" on the entry for "colour", and
> alt="en_US" on
> the entry for "color". Then the alt.xsl script called with en_GB
> as the
> option would include only those entries that have alt="en_GB" or
> that
> have no alt-attribute.
>
>
> Is alt.xsl will not contribute to the non standard format to any
> way ? like I mean, I will compiling the only the dictionary file
> (.dix) for the entries with the alt="en_GB" or for the alt="en_US"
> or any and will get only the .dix format ?
Well, the output after alt.xsl validates with dix.dtd.
Actually … it seems alt.xsl is deprecated now, since dix.dtd and lt-comp
(used to compile .dix files) now accepts an "--alt" option. I think you
can disregard alt.xsl.
best regards,
Kevin's evil twin K-evil
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Apertium-stuff mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/apertium-stuff
