ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Renaud Aubin <aubin@nibua-r.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Verbatim Text (esp. XML/XSL + opportunity of a brand new support for the RelaxNG Compact syntax)
Date: Mon, 20 Oct 2008 19:37:27 +0200	[thread overview]
Message-ID: <48FCC1D7.2030204@nibua-r.org> (raw)
In-Reply-To: <48FC3BE3.5000607@elvenkind.com>

Taco, Aditya,

Thanks, t-vim will do the job for the end of october... Even if I will 
surely give a try to MarkIV on this particular point.

Regards,

Renaud

Taco Hoekwater a écrit :
> Hi Renaud,
>
> Renaud Aubin wrote:
>> Hi Folks !
>>
>> I'm currently writting a technical report in which I need to type some 
>> XML an non-XML text.
>>
>> Sample file (xml_test.tex):
>> I have some custom XML text (trivial) + a not-so-complicated xsl 
>> transformation (a part is included within the test file). I know there 
>> is verb-xml but... I need to improve it to support xpath expr. More 
>> over, I want to preserve the initial indentation. The point is now, how 
>> to improve verb-xml to support xpath expressions ? I'm working with Mark 
>> II... Should I switch to Mark IV if I want to write a new XML verbatim 
>> support (with lua)?
>>
>> + the bonus question: I want to add some support for the RelaxNG Compact 
>> syntax, should I follow the procedure described on the wiki or switch to 
>> Mark IV ?
>>
>> The deadline for this technical report: end of october...
>
> Mark IV's framework for syntax highlighting is definately easier to
> use if you are somewhat familiar with 'normal' scripting languages
> (as opposed to TeX). But 'end of october' is pretty close, so I would
> suggest using t-vim, maybe with some postprocessing.
>
>    http://modules.contextgarden.net/vim
>
> Best wishes,
> Taco
> ___________________________________________________________________________________
> 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  : https://foundry.supelec.fr/projects/contextrev/
> wiki     : http://contextgarden.net
> ___________________________________________________________________________________
>
>
>   

___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


      reply	other threads:[~2008-10-20 17:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-17 18:21 Renaud Aubin
2008-10-17 18:40 ` Aditya Mahajan
2008-10-17 18:57 ` Renaud Aubin
2008-10-20  8:05 ` Taco Hoekwater
2008-10-20 17:37   ` Renaud Aubin [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=48FCC1D7.2030204@nibua-r.org \
    --to=aubin@nibua-r.org \
    --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).