From: mf via ntg-context <ntg-context@ntg.nl>
To: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
Cc: mf <massifr@fastwebnet.it>
Subject: Re: ignore not closed tags in XML input
Date: Mon, 16 May 2022 17:22:44 +0200 [thread overview]
Message-ID: <2da65c71-c8ca-f7e5-6598-610c73560683@fastwebnet.it> (raw)
In-Reply-To: <b1f1c56c-4abf-df1a-fde6-312512ec4181@gmx.es>
See HTML-tidy,
https://www.html-tidy.org/
it could help you pre-processing your HTML files.
Massi
Il 16/05/22 17:08, Pablo Rodriguez via ntg-context ha scritto:
> Dear list,
>
> I would like to feed
> https://seumasjeltzz.github.io/LinguaeGraecaePerSeIllustrata/001.html as
> XML input for ConTeXt.
>
> The problem is that (as many other XML files that I haven’t generated
> myself) some <meta> and <link> tags aren’t closed, such as in:
>
> <meta charset="utf-8">
> <link href="https://fonts/css?greek" rel="stylesheet">
> <link href="style.css" rel="stylesheet">
>
> So, all that I get is the following message:
>
> invalid xml file - parsed text
>
> Unsuccessfully I have tried the following:
>
> \xmlsetsetup{#1}{html/head/(meta|link)}{-}
>
> Is there no way to make ConTeXt more tolerant, so that it is able to
> ignore those tags?
>
> 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
___________________________________________________________________________________
next prev parent reply other threads:[~2022-05-16 15:22 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 [this message]
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
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=2da65c71-c8ca-f7e5-6598-610c73560683@fastwebnet.it \
--to=ntg-context@ntg.nl \
--cc=massifr@fastwebnet.it \
/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).