From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Marco Pessotto <melmothx@gmail.com>
Subject: Re: \unknown lost on xml export
Date: Sun, 06 Nov 2011 13:03:00 +0100 [thread overview]
Message-ID: <4EB67774.7090903@wxs.nl> (raw)
In-Reply-To: <87hb2ioc3n.fsf@universe.krase.net>
On 5-11-2011 15:52, Marco Pessotto wrote:
>
> Hello there.
>
> While exporting the ellipses are completely lost. Is there a workaround
> for cases like that (I have the feeling this is the top of the iceberg)?
Not using \unknown but \textellipsis
I'm not sure why you're seeing an iceberg. The \unknown\ commands uses
leaders deep down and those don't get exported. I'll change the
definition to the less efficient variant
\def\doperiods[#1]%
{\dontleavehmode
\hbox\bgroup
\setbox\scratchbox\hbox to \periodswidth{\hss.\hss}%
\dorecurse{\iffirstargument#1\else\periodsdefault\fi}{\copy\scratchbox}%
\egroup}
which does export periods (but spaced, as expected).
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | 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
___________________________________________________________________________________
next prev parent reply other threads:[~2011-11-06 12:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-05 14:52 Marco Pessotto
2011-11-06 12:03 ` Hans Hagen [this message]
2011-11-06 13:12 ` Marco
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=4EB67774.7090903@wxs.nl \
--to=pragma@wxs.nl \
--cc=melmothx@gmail.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).