This makes sense to me. The source files I am working from are
electronic dictionaries (not print dictionaries), so the
approach is appropriate. It makes a lot of sense to handle different
dictionaries differently. I will focus on the English-Vietnamese
dictionary first, and as the filters tak
Daniel Owens wrote:
> Like I said, for what it's worth... Perhaps Lexique will give you some
> food for thought. It's a nice program for producing a nicely typeset
> dictionary quickly and with minimal expertise. I might create Perl
> scripts to go between TEI and their format if I ever have the
Like I said, for what it's worth... Perhaps Lexique will give you some
food for thought. It's a nice program for producing a nicely typeset
dictionary quickly and with minimal expertise. I might create Perl
scripts to go between TEI and their format if I ever have the need.
I should have start
On May 19, 2008, at 12:41 AM, Daniel Owens wrote:
The HTML didn't come through very well. Here is a screenshot of the
Lexique-formatted entry:
Daniel
Daniel Owens wrote:
I have been working on some TEI dictionaries, and (this is obvious,
I know)
vanilla TEI produces very boring entries
The HTML didn't come through very well. Here is a screenshot of the
Lexique-formatted entry:
Daniel
Daniel Owens wrote:
I have been working on some TEI dictionaries, and (this is obvious, I know)
vanilla TEI produces very boring entries in the front-ends. I point this out as
a preface t
I have been working on some TEI dictionaries, and (this is obvious, I
know) vanilla TEI produces very boring entries in the front-ends. I
point this out as a preface to offering a suggestion for front-end
developers preparing to introduce TEI support. Here is a typical TEI
entry:
an toạ(phonet
