From: Bruce Horrocks via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Bruce Horrocks <ntg@scorecrow.com>, Pablo Rodriguez <oinos@gmx.es>
Subject: Re: ignore not closed tags in XML input
Date: Wed, 18 May 2022 23:09:07 +0100 [thread overview]
Message-ID: <22BF61AB-4073-49B5-BA26-E7D7BF9F8925@scorecrow.com> (raw)
In-Reply-To: <aeeeb2d4-ab34-1396-7ecb-438d4d54f866@gmx.es>
> On 18 May 2022, at 17:00, Pablo Rodriguez via ntg-context <ntg-context@ntg.nl> wrote:
>
>
> Sorry for explaining myself so poorly.
>
> One of the not irrelevant tasks for me is finding examples of XML code.
Perhaps you could start by typesetting a technical source rather than prose?
I suggest trying to typeset the UK Meteorological Office's Shipping Forecast :-)
- web page version
<https://www.metoffice.gov.uk/weather/specialist-forecasts/coast-and-sea/shipping-forecast>
- XML source data
<https://www.metoffice.gov.uk/public/data/CoreProductCache/ShippingForecast/Latest>
- as broadcast on the Radio
<https://www.radio-uk.co.uk/podcasts/random-shipping-forecast>
It's a good (in my opinion) source because it is amenable to being printed in several different ways: one might be to simply copy the webpage's layout, while another could be to use columns to fit more onto a single page of text.
Alternatively, a much more demanding exercise would be to typeset the user manual for the XML editing software "Oxygen".
<https://www.oxygenxml.com>
The XML source for the manual is here:
<https://github.com/oxygenxml/userguide/blob/master/DITA/UserManual.ditamap>
—
Bruce Horrocks
Hampshire, UK
___________________________________________________________________________________
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-18 22:09 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
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 [this message]
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=22BF61AB-4073-49B5-BA26-E7D7BF9F8925@scorecrow.com \
--to=ntg-context@ntg.nl \
--cc=ntg@scorecrow.com \
--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).