ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: Thangalin via ntg-context <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: Re: ignore not closed tags in XML input
Date: Wed, 18 May 2022 18:00:20 +0200	[thread overview]
Message-ID: <aeeeb2d4-ab34-1396-7ecb-438d4d54f866@gmx.es> (raw)
In-Reply-To: <CAANrE7pW=F_vEia1xSZrj4oCU_k8ai66cct2Q08ZLFjhaTQWXw@mail.gmail.com>

On 5/18/22 03:23, Thangalin via ntg-context wrote:
> […]
>   I wanted to write an introduction on how to typeset XML sources with
>   ConTeXt (at least, in Spanish).
>
> See:
> https://dave.autonoma.ca/blog/2020/04/11/project-gutenberg-projects/
>
> It's English, but describes a fair amount of what you're probably
> looking to accomplish, and there are all sorts of free translation
> services now.

Hi Dave,

many thanks for your reply.

Your introduction clearly states
(https://dave.autonoma.ca/blog/2020/04/11/project-gutenberg-projects/#xhtml-to-markdown):

  Even though ConTeXt can typeset XML documents, we’ll use XSLT—the
  verbose language only gurus grok without gripes—to convert XHTML into
  a Markdown document that pandoc can read to produce a native ConTeXt
  file.

I’m afraid I’m interested in typesetting XML documents with ConTeXt.

Actually, I have been typesetting XHML documents (generated by pandoc
from Markdown sources) for years now.

Sorry for having explained myself like crap. I wanted to write an
introduction on how to typeset XML sources in ConTeXt. I cannot see how
free translation services may be of help here.

>   One of the main issues I face is to find examples.
>
> See:
>
> https://wiki.contextgarden.net/XML
> https://wiki.contextgarden.net/Getting_Started_with_XML_and_ConTeXt_using_TEXML
>
> And themes for my text editor, KeenWrite, in particular:
>
> https://github.com/DaveJarvis/keenwrite-themes/tree/main/xhtml
> https://github.com/DaveJarvis/keenwrite-themes/tree/main/tarmes
> https://github.com/DaveJarvis/keenwrite-themes/tree/main/boschet

Sorry for explaining myself so poorly.

One of the not irrelevant tasks for me is finding examples of XML code.

>   Maybe all XML handling is way more complex than I originally thought.
>
> It takes some elbow grease. Conceptually, it's essentially mapping XML
> elements to xmlsetups, which are used to apply typesetting instructions.

I agree, this is basically the idea.

But my worries came from having to sanitize HTML sources (which aren’t
strict XML-compliant).

Many thanks for your help,

Pablo
___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2022-05-18 16:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16 15:08 Pablo Rodriguez via ntg-context
2022-05-16 15:22 ` mf via ntg-context
2022-05-16 16:37   ` Pablo Rodriguez via ntg-context
2022-05-16 15:30 ` Hans van der Meer via ntg-context
2022-05-16 16:50   ` Pablo Rodriguez via ntg-context
2022-05-16 18:13     ` Taco Hoekwater via ntg-context
2022-05-17 16:36       ` Pablo Rodriguez via ntg-context
2022-05-18  1:23         ` Thangalin via ntg-context
2022-05-18 16:00           ` Pablo Rodriguez via ntg-context [this message]
2022-05-18 17:14             ` Thangalin via ntg-context
2022-05-21 17:01               ` Pablo Rodriguez via ntg-context
2022-05-18 22:09             ` Bruce Horrocks via ntg-context
2022-05-21 17:28               ` Pablo Rodriguez via ntg-context
2022-05-19 15:33             ` juh via ntg-context
2022-05-21 18:23               ` Pablo Rodriguez via ntg-context

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=aeeeb2d4-ab34-1396-7ecb-438d4d54f866@gmx.es \
    --to=ntg-context@ntg.nl \
    --cc=oinos@gmx.es \
    /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).