Hans Hagen wrote:
> there is no need for verbatim mode when you convert anyway!
Technically true, but if a simple \processinlineverbatim solves the
same problem as yet-to-write code in almost any language, I's go for the
former, since it does already exist. Other than that, I'd use ConTeXt's
xm
Nikolai Weibull wrote:
That’s just horrendous. The ‘n’ attribute on ‘line’ is useless (and why
are empty lines unnumbered?). You can just as easily use XSLT’s
to get that effect:
if i remember right it has to to with the fact that while editing
inserted lines were treated different (sub n
Hans Hagen wrote:
> Nikolai Weibull wrote:
> > Is there (going to be) any support for this export format in ConTeXt
> > so that I can just generate this kind of XML instead so that we only
> > do things once? I found this in mscite-p.pdf: “The exporter will be
> > descibed as soon as there are s
Nikolai Weibull wrote:
> We were planning on using Vim for preprocessing things like this instead
> of hacking TeX to do the lexing. I think Mojca (?) had some ideas for
> this and perhaps even a simple implementation, and given that there is
> now structured support for preprocessing in texexec I
Christopher Creutzig wrote:
Nikolai Weibull wrote:
this than I have is welcome to finish it. The \highlight command should
be defined something like this (pseudo-tex-code):
\pdef\highlight[#1]{#2}%
{\bgroup
\setupcolorforgroup[#1]%
\type{#2}%
\egroup}
#1 is a group name, such as S
Hans Hagen wrote:
[good tips on how to implement the TeX side of things]
Great, thanks!
> [it's what i did with the scite exporter -- i output highligting in a
> compact XML where even spaces are tagged]
Is there (going to be) any support for this export format in ConTeXt so
that I can just ge
Nikolai Weibull wrote:
Nikolai Weibull wrote:
It would require very little programming. syntax/2html.vim, which
converts the buffer to a HTML document with syntax highlighting, is 526
lines in the current CVS incarnation. A syntax/2context.vim would be
even shorter, perhaps 150 to 200 lin
Christopher Creutzig wrote:
> Nikolai Weibull wrote:
>
> > this than I have is welcome to finish it. The \highlight command
> > should be defined something like this (pseudo-tex-code):
> >
> > \pdef\highlight[#1]{#2}%
> > {\bgroup
> >\setupcolorforgroup[#1]%
> >\type{#2}%
> >\egro
Nikolai Weibull wrote:
> this than I have is welcome to finish it. The \highlight command should
> be defined something like this (pseudo-tex-code):
>
> \pdef\highlight[#1]{#2}%
> {\bgroup
>\setupcolorforgroup[#1]%
>\type{#2}%
>\egroup}
>
> #1 is a group name, such as Statement, O
Nikolai Weibull wrote:
> It would require very little programming. syntax/2html.vim, which
> converts the buffer to a HTML document with syntax highlighting, is 526
> lines in the current CVS incarnation. A syntax/2context.vim would be
> even shorter, perhaps 150 to 200 lines. If I find the tim
Friday, December 2, 2005 Taco Hoekwater wrote:
> Nikolai Weibull wrote:
>> We were planning on using Vim for preprocessing things like this instead
>> of hacking TeX to do the lexing. I think Mojca (?) had some ideas for
>> this and perhaps even a simple implementation, and given that there is
Zeljko Vrba wrote:
> On Fri, Dec 02, 2005 at 05:56:36PM +0100, Nikolai Weibull wrote:
> > We were planning on using Vim for preprocessing things like this
> > instead
> Vim for preprocessing? Isn't it a bit too painful compared to using a
> "real" programming language?
You misunderstand. Vim c
On Fri, Dec 02, 2005 at 05:56:36PM +0100, Nikolai Weibull wrote:
>
> We were planning on using Vim for preprocessing things like this instead
>
Vim for preprocessing? Isn't it a bit too painful compared to using a "real"
programming language?
>
> of hacking TeX to do the lexing. I think Mojca (?
On Fri, Dec 02, 2005 at 03:14:30PM +0100, Hans Hagen wrote:
>
> what do you mean with source code formatting?
>
Something akin to lgrind. Pretty-printing C++ source code. I tried to
adapt some existing Context code to C and C++ keywords, but failed
somewhere.. AFAIR, I may have even once asked on
Nikolai Weibull wrote:
We were planning on using Vim for preprocessing things like this instead
of hacking TeX to do the lexing. I think Mojca (?) had some ideas for
this and perhaps even a simple implementation, and given that there is
now structured support for preprocessing in texexec I thi
Zeljko Vrba wrote:
> A motivation and idea that came to mind while writing a post to
> comp.text.tex:
>
> ==
> Then again, most (all?) of publishers require Latex source, if my
> document ever makes it that far.. And Latex has nicer source code
> formatting than Context. so I'm really split betwe
Zeljko Vrba wrote:
A motivation and idea that came to mind while writing a post to comp.text.tex:
==
Then again, most (all?) of publishers require Latex source, if my document
ever makes it that far.. And Latex has nicer source code formatting than
Context. so I'm really split between Latex and
A motivation and idea that came to mind while writing a post to comp.text.tex:
==
Then again, most (all?) of publishers require Latex source, if my document
ever makes it that far.. And Latex has nicer source code formatting than
Context. so I'm really split between Latex and Context..
None of t
18 matches
Mail list logo
