From: Aditya Mahajan <adityam@umich.edu>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Exporting verbatim text
Date: Sat, 15 Oct 2011 11:54:33 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.02.1110151141030.14104@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <4E99484E.3070305@wxs.nl>
On Sat, 15 Oct 2011, Hans Hagen wrote:
> On 15-10-2011 05:29, Aditya Mahajan wrote:
>> Hi,
>>
>> In the vim module, I use vim to generate TeX code that looks roughly as
>>
>> ~~~
>> \SYN[Type]{public} \SYN[Type]{static} \SYN[Type]{void}
>> main\SYN[javaParen]{(}String args\SYN[javaParen]{)} \{
>> System.out.println\SYN[javaParen]{(}\SYN[Constant]{"Hello
>> World"}\SYN[javaParen]{)} ;
>> \}
>> ~~~
>>
>> When generating pdf output, I simply set appropriate catcodes so that
>> the line breaks and leading white spaces are significant. However, when
>> exporting to xml, leading white space is ignored while line break is
>> translated to <break/>. How can I export in such a way that leading
>> white spaces are preserved (and ideally no <break/> is generated, but I
>> can deal with that using CSS).
>
> brrr .. catcodes ... can't you wrap lines in a macro and tag spaces too?
I can, but I went out of the way to ensure that I do not have to do that.
I dislike formatters that add macros for newlines and spaces:
http://randomdeterminism.wordpress.com/2011/06/06/clean-tex-output/
> in principle you should be able to use some of of the regular typing
> wrapping code for that but anything other than catcoded characters will
> do (also, keep in mind that people might want to pass the generated code
> around as arguments in which case catcodes can create a mess
Agreed. But this is for syntax highlighting, so I have to mess with
catcodes anyways. My code wail fail if it is passed as an argument to some
other macro, but so does \starttyping ... \stoptyping. (Maybe I will
provice a \process<...>buffer to take care of that).
> \setupbackend[export=yes]
>
> \starttext
>
> \startlines
> \zwnj \char32\char32\char32 test \char32 test test
> \zwnj \char32\char32 test \char32 test test
> \zwnj \char32 test \char32 test test
> test \char32 test test
> \stoplines
>
> \stoptext
I really do not want to produce such output. I'll see if I can abuse the
visualizer code and create a null grammer that just adds new line and
space tags.
Aditya
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2011-10-15 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-15 3:29 Aditya Mahajan
2011-10-15 8:46 ` Hans Hagen
2011-10-15 15:54 ` Aditya Mahajan [this message]
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=alpine.LNX.2.02.1110151141030.14104@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).