From: Mica Semrick <mica@silentumbrella.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: TEI to context XML mappings?
Date: Fri, 26 Feb 2016 07:39:42 -0800 [thread overview]
Message-ID: <2683EF97-C8B8-4465-8ACF-CE2BD5BF524D@silentumbrella.com> (raw)
In-Reply-To: <56D01413.80205@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 2859 bytes --]
> You want to autogenerate that? That could become quite huge (And
> probably most would be discarded later anyway of you want all
> permutations of elements and attributes)
Just elements would work for me.
Best,
M
On February 26, 2016 1:00:03 AM PST, Hans Hagen <pragma@wxs.nl> wrote:
>On 2/26/2016 8:52 AM, Pablo Rodriguez wrote:
>> On 02/25/2016 10:48 AM, Hans Hagen wrote:
>>> [...]
>>> i'm still puzzled what you want
>>
>> Hans,
>>
>> I’m only guessing (after testing the XML analyzing ability that you
>> discovered us with a single XML file).
>>
>> The analysis is important, but after that I have to write the actual
>> environment.
>>
>> I think that the basic structure that I sent in
>> https://mailman.ntg.nl/pipermail/ntg-context/2016/084582.html is
>useful
>> to avoid writing myself the environment.
>
>You want to autogenerate that? That could become quite huge (And
>probably most would be discarded later anyway of you want all
>permutations of elements and attributes)
>
>> I mean, of course I have to add the relevant commands to handle in
>> ConTeXt each element. But with the basic scheme, I know which
>elements
>> (in the broadest sense) I have to setup.
>>
>> I want to avoid writing the whole element list in the environment by
>> hand. But I may be doing wrong (this is totally new to me).
>>
>> Or do you write (type) each environment from scratch after using the
>> report generated by ConTeXt?
>
>We just start with the trivial things and then look at the specific
>structures. We get either relative simple html like xml or we get quite
>
>complex educational markup, with quite demanding rendering and multiple
>
>products. The good news is that the number of elements is always
>limited
>(analyzing would not really work well because it can be that thousands
>of files need to be loaded and merged which itself is not a problem,
>but
>one then always need to interpret what needs to get loaded).
>
>Hans
>
>-----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl
>-----------------------------------------------------------------
>___________________________________________________________________________________
>If your question is of interest to others as well, please add an entry
>to the Wiki!
>
>maillist : ntg-context@ntg.nl /
>http://www.ntg.nl/mailman/listinfo/ntg-context
>webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
>archive : http://foundry.supelec.fr/projects/contextrev/
>wiki : http://contextgarden.net
>___________________________________________________________________________________
[-- Attachment #1.2: Type: text/html, Size: 3772 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-02-26 15:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 21:26 Mica Semrick
2016-02-24 8:20 ` Hans Hagen
2016-02-24 9:10 ` Pablo Rodriguez
2016-02-24 9:52 ` Hans Hagen
2016-02-24 10:11 ` Thomas A. Schmitz
2016-02-24 10:26 ` Hans Hagen
2016-02-24 12:05 ` Thomas A. Schmitz
2016-02-24 14:15 ` Hans Hagen
2016-02-24 14:32 ` Thomas A. Schmitz
2016-02-24 14:51 ` Hans Hagen
2016-02-24 15:57 ` Thomas A. Schmitz
2016-02-24 17:32 ` Mica Semrick
2016-02-24 15:34 ` Mica Semrick
2016-02-24 10:32 ` Pablo Rodriguez
2016-02-25 5:04 ` mica
2016-02-25 9:48 ` Hans Hagen
2016-02-26 7:52 ` Pablo Rodriguez
2016-02-26 9:00 ` Hans Hagen
2016-02-26 15:39 ` Mica Semrick [this message]
2016-06-22 5:12 ` Mica Semrick
2016-08-14 5:03 ` Mica Semrick
2016-08-14 13:38 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2683EF97-C8B8-4465-8ACF-CE2BD5BF524D@silentumbrella.com \
--to=mica@silentumbrella.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).