vim-latex-devel — Mailing list for developers/maintainers of the vim-latex project

[Vim-latex-devel] BibT question

[John S H. <jsh...@ee...>]

the credits section of the manual mentions the BibT() function from the
file bibtex.vim, but I don't see any further reference to this function
whatsoever, and I encountered problems using it 'out of the box'.  Is
this function currently _used_ by vim-latex, and if so, how/is there any
documentation on how to take advantage of it?  Is there any other
support for creating bibtex files in vim-latex?

Thanks!

-John Hawkins

Re: [Vim-latex-devel] Times package

[Mikolaj M. <mi...@wp...>]

On Tue, Feb 25, 2003 at 10:17:34AM -0600, th...@bi... wrote:
> I really love latex-suite -- it makes writing LaTeX even easier!
> Anyway, I noticed that there was no package file for the "times" package
> (maybe because it's trivial?).  Anyway, I made one, so here it is.

Thanks but this was deliberate decision not to create package files for
packages which only changes behaviour existing commands not providing
owns. But maybe change its time to change this policy?

Mikolaj

Re: [Vim-latex-devel] sourcing package files under windows

[Benji F. <be...@me...>]

Mikolaj Machowski wrote:
> I have got report about not sourcing package files
> under windows. I found place and this is not working
> also for me (under windows, under Linux everything is OK).
> 
> lines from 216-226 packages.vim:
> 
>             exec "normal! /\[\<CR>lv/\]\<CR>h\"ay"
>             let options = @a
>         else
>             let options = ''
>         endif
> 
>         " The following statement puts the stuff between the { }'s of a
>         " \usepackage{stuff,foo} into @a. Do not use matchstr() and the like
>         " because we can have things split across lines and such.
>         exec "normal! /{\<CR>lv/}\<CR>h\"ay"
> 
> Solution is to remove h.
> But I would like to know if this is working on other machines before
> commiting.

How about

	exec "normal! /{\<CR>\"ayi}"

instead?  Besides being shorter, it works {
even here
}
I think.

					--Benji

[Vim-latex-devel] sourcing package files under windows

[Mikolaj M. <mi...@wp...>]

I have got report about not sourcing package files
under windows. I found place and this is not working
also for me (under windows, under Linux everything is OK).

lines from 216-226 packages.vim:

            exec "normal! /\[\<CR>lv/\]\<CR>h\"ay"
            let options = @a
        else
            let options = ''
        endif

        " The following statement puts the stuff between the { }'s of a
        " \usepackage{stuff,foo} into @a. Do not use matchstr() and the like
        " because we can have things split across lines and such.
        exec "normal! /{\<CR>lv/}\<CR>h\"ay"

Solution is to remove h.
But I would like to know if this is working on other machines before
commiting.

Mikolaj

[Vim-latex-devel] Times package

[<th...@bi...>]

I really love latex-suite -- it makes writing LaTeX even easier!

Anyway, I noticed that there was no package file for the "times" package
(maybe because it's trivial?).  Anyway, I made one, so here it is.

-- mikeh



-- 
Mike Hostetler          
th...@bi... 
http://www.binary.net/thehaas 
GnuPG key: http://www.binary.net/thehaas/mikeh.gpg 

"What good is having someone who can walk on water if you don't follow
in his footsteps?"

[Vim-latex-devel] Re: Re: about vim suite for latex

[Asokan K <as...@re...>]

On Mon, 17 Feb 2003 Srinath Avadhanula wrote :
>
>Hello Asokan,
>
>I am forwarding to the vim-latex-devel group hoping someone finds 
>time
>to solve this...
>
>On Sun, 16 Feb 2003, Asokan  K wrote:
> >
> > I found a minor bug, though. while using vimsuite I am not 
>able to use
> > yank(y) and paste(p) commands between *different files* in the 
>buffer.
> > They work fine through the menu commands, but I rarely use 
>menus in my
> > vim session. Also the y and p commands work well within the 
>same file.
> > This was no problem in earlier versions of latex suite.
> >
>To me this looks like a sure sign that the unnamed buffer is 
>being
>tampered with... Don't know from where though.


Thank you Srinath.  Hope some one will come with a solution.

thanks
Asokan
>
>Srinath
>

[Vim-latex-devel] Re: about vim suite for latex

[Srinath A. <sr...@fa...>]

Hello Asokan,

I am forwarding to the vim-latex-devel group hoping someone finds time
to solve this...

On Sun, 16 Feb 2003, Asokan  K wrote:

> Thank you srinath for the excellent set of tools you provide
> through latex-sute. I am one of those who use both vim and latex
> extensively and I find the toolset extremely usefull.
>
> I found a minor bug, though. while using vimsuite I am not able to use
> yank(y) and paste(p) commands between *different files* in the buffer.
> They work fine through the menu commands, but I rarely use menus in my
> vim session. Also the y and p commands work well within the same file.
> This was no problem in earlier versions of latex suite.
>
To me this looks like a sure sign that the unnamed buffer is being
tampered with... Don't know from where though.

Srinath

Re: [Vim-latex-devel] latex --src does not work

[Srinath A. <sr...@fa...>]

On Tue, 11 Feb 2003, Bernhard Walle wrote:

> > 1. What does
> >         :echo g:Tex_CompileRule_dvi
> >    say?
>
> latex --src \nonstopmode \input{$*}
>
> >    This should show you the actual command line which vim passes to the
> >    shell. Does that look okay? Does the shell give an error?
>
> latexps schriften.tex schriften 2>&1| tee /tmp/v4108/9
>
> There's no such command `latexps' in my texrc and all target formats are
> dvi!
>

Hmm... Apparently, something else is setting 'makeprg'... (which is
pretty bizzare). What does
    :set makeprg?
say? If it doesn't give
    latex --src \nonstopmode \input{$*}
then, something else is getting in the way of latex-suite. Try
    :verbose set makeprg?
that should hopefully tell you where its getting set... That should give
you a file name. Is that part of latex-suite?

Srinath

Re: [Vim-latex-devel] latex --src does not work

[Bernhard W. <ber...@bw...>]

Hello,

On Tue, 11 Feb 2003 at 12:48 (-0800), Srinath Avadhanula wrote:
> 
> Please tell us what the following does:
> 
> 1. What does
>         :echo g:Tex_CompileRule_dvi
>    say?

latex --src \nonstopmode \input{$*}

>    If this doesn't show you what you expect something has gone wrong in
>    the settings.
> 2. What happens when you do
>         :call RunLaTeX()
>    ?

LaTeX runs.

>    This should show you the actual command line which vim passes to the
>    shell. Does that look okay? Does the shell give an error?

latexps schriften.tex schriften 2>&1| tee /tmp/v4108/9

There's no such command `latexps' in my texrc and all target formats are
dvi!


>    Once someone said that they needed to set 'noguipty'. This seems to
>    be a unix specific thing, so I will not be much help except to point
>    you to
>     :help gui-pty

No effect.


Regards,
Bernhard

> On Tue, 11 Feb 2003, Bernhard Walle wrote:
> 
> > Hello,
> >
> > because I want to use 'source specials' with the --src switch I made
> > following change in my configuration file:
> >
> > if has('win32')
> > 	let s:CompileFlags = '--src-specials'
> > 	TexLet g:Tex_EscapeChars = ''
> > else
> > 	let s:CompileFlags = '--src'
> > 	TexLet g:Tex_EscapeChars = '{}\'
> > endif
> >
> > But it doesn't work. Calling latex --src in a xterm works. I updated to
> > the newest version of latex-suite. I also tried to change the latex
> > command to something that doesn't exist but latex was called despite of
> > that. All other changes in my configuration file are recognized. What
> > goes wrong?
> >
> > Regards,
> > Bernhard
> >
> 
> -- 
> Srinath Avadhanula
> Feb 11 12:36pm
> Dimensions will always be expressed in the least usable term.
> Velocity, for example, will be expressed in furlongs per fortnight.
> On Tue, 11 Feb 2003, Bernhard Walle wrote:
> 

Re: [Vim-latex-devel] latex --src does not work

[Srinath A. <sr...@fa...>]

Hello,

Please tell us what the following does:

1. What does
        :echo g:Tex_CompileRule_dvi
   say?
   If this doesn't show you what you expect something has gone wrong in
   the settings.
2. What happens when you do
        :call RunLaTeX()
   ?
   This should show you the actual command line which vim passes to the
   shell. Does that look okay? Does the shell give an error?
   Once someone said that they needed to set 'noguipty'. This seems to
   be a unix specific thing, so I will not be much help except to point
   you to
    :help gui-pty

Srinath

PS: I am changing the subject because I keep repeating these
instructions. Henceforth, this might serve as a template for this
question.

On Tue, 11 Feb 2003, Bernhard Walle wrote:

> Hello,
>
> because I want to use 'source specials' with the --src switch I made
> following change in my configuration file:
>
> if has('win32')
> 	let s:CompileFlags = '--src-specials'
> 	TexLet g:Tex_EscapeChars = ''
> else
> 	let s:CompileFlags = '--src'
> 	TexLet g:Tex_EscapeChars = '{}\'
> endif
>
> But it doesn't work. Calling latex --src in a xterm works. I updated to
> the newest version of latex-suite. I also tried to change the latex
> command to something that doesn't exist but latex was called despite of
> that. All other changes in my configuration file are recognized. What
> goes wrong?
>
> Regards,
> Bernhard
>

-- 
Srinath Avadhanula
Feb 11 12:36pm
Dimensions will always be expressed in the least usable term.
Velocity, for example, will be expressed in furlongs per fortnight.
On Tue, 11 Feb 2003, Bernhard Walle wrote:

[Vim-latex-devel] latex --src does not work

[Bernhard W. <ber...@bw...>]

Hello,

because I want to use 'source specials' with the --src switch I made
following change in my configuration file:

if has('win32')
	let s:CompileFlags = '--src-specials'
	TexLet g:Tex_EscapeChars = ''
else
	let s:CompileFlags = '--src'
	TexLet g:Tex_EscapeChars = '{}\'
endif

But it doesn't work. Calling latex --src in a xterm works. I updated to
the newest version of latex-suite. I also tried to change the latex
command to something that doesn't exist but latex was called despite of
that. All other changes in my configuration file are recognized. What
goes wrong?

Regards,
Bernhard

Re: [Vim-latex-devel] Re: tex-refs project and xml to vim-help conversion

[Benji F. <be...@me...>]

      I have a few questions today.

1. I have been thinking about how to translate DocBook tags into *tags* 
(hyperlinks) for vim help files.  Let's look at an example:

===from tex-refs.xml===
	  <section id="bslash-addtocounter">
	    <title id="bslash-addtocounter-title">\addtocounter</title>
	    <indexterm><primary>\addtocounter</primary></indexterm>

	    <para><literal>\addtocounter{counter}{value}</literal>
	    </para>
	    <para>The <literal>\addtocounter</literal> command increments
	      the <literal>counter</literal> by the
	      amount specified by the <literal>value</literal> argument.
	      The <literal>value</literal> argument can be negative.
	    </para>

	  </section>
========================

===from tex-refs.html===
<div class="section" lang="en">
<div class="titlepage">
<div>
<div>
<h6 class="title"><a name="bslash-addtocounter"></a>1.3.2.1.1
\addtocounter</h6></div></div></div>
<a class="indexterm" name="d0e264"></a>
<p><tt class="literal">\addtocounter{counter}{value}</tt></p>
<p>The <tt class="literal">\addtocounter</tt> command increments
the <tt class="literal">counter</tt> by the amount specified by the
<tt class="literal">value</tt> argument. The <tt class=
"literal">value</tt> argument can be negative.</p></div>
=========================

===from latexhelp.txt===
\addtocounter{counter}{value}			*\addtocounter*
		Increments the {counter} by the amount specified by the
		{value} argument. The {value} argument can be negative.

========================

      It looks to me as if the HTML <a name="bslash-addtocounter"></a> 
is generated from the XML <section id="bslash-addtocounter">.  Is this 
right?  If so, I think we should plan to generate the *\addtocounter* 
from the same element.

2. I think the main reason to prefer Python over XSL is that we need 
plain text with the correct indentation and line breaks.  Am I missing 
something?  Perhaps it would be easier to use a two-step process: 
first, an XSL style sheet that does most of the processing, prducing 
something like this:

===from latexhelp.xml===
\addtocounter{counter}{value}			*\addtocounter*
<block indent=2 tw=80>
Increments the {counter} by the amount specified by the {value} 
argument. The {value} argument can be negative.
</block>

========================

Then a simple Python or vim script could do the rest of the work.  Does 
this sound feasible?

3. If we want a customized format for vim documentation, we could make 
up our own simple DTD and then use XSL to convert this to DocBook.  Is 
this as easy as I make it sound?  Or would it be simpler to use 
attributes in standard DocBook tags?  Srinath proposed

===from options.xml===
<option>
     <optionName>statusline</optionName>
     <optionNameAlias>stl</optionNameAlias>
     <optionType>string</optionType>
     <optionDefault>empty</optionDefault>
     <optionScope>global</optionScope>
     <notInVi/>
     <notInVi>not available when compiled with the <tag>+statusline</tag>
         feature</notInVi>
     <optionDescription>
         When nonempty, this option determines the content of the status 
line.
         Also see <featureTag>status-line</featureTag>
     </optionDescription>
</option>
======================

A variant would be to use attributes:

===from options.xml===
<option name="statusline" alias="stl" type="string" default="empty" 
scope="global">
     <compatibility>not in vi
     </compatibility>
     <compatibility>not available when compiled without the
	<tag>+statusline</tag> feature
     </compatibility>
     <optionDescription>
         When nonempty, this option determines the content of the status
	line.  Also see <featureTag>status-line</featureTag>
     </optionDescription>
</option>
=======================

Is there enough flexibility in DocBook (with attributes and PI's) to so 
something equivalent, or does the custom format, converted to DocBook, 
sound like a good idea?

4. I spent some time trying to set up my system (Red Hat, not Debian) to 
handle the tex-refs conversions.  I adjusted the paths in Makefile.cfg 
and downloaded Saxon from sourceforge.  I think my problem is that I do 
not know what to do to install Saxon.  I copied saxon.jar to 
/usr/share/java but I get this error message:

[benji@localhost tex-refs-0.2.2]$ make tex-refs.html
java -classpath /usr/share/java/saxon.jar com.icl.saxon.StyleSheet 
tex-refs.xml
tex-refs.xsl > tex-refs-saxon.html
Exception in thread "main" java.lang.VerifyError: verification failed at 
PC 65 in com.icl.saxon.style.XSLTemplate:preprocess(()V): incompatible 
type on stack
    at 0x4028115f: java.lang.Throwable.Throwable(java.lang.String) 
(/usr/lib/libgcj.so.3)

Can someone tell me what else I should do?

					--Benji

Re: [Vim-latex-devel] Re: tex-refs project and xml to vim-help conversion

[Srinath A. <sr...@fa...>]

Well, the more I look at DocBook, the more I get the feeling that we
will not be able to use it without some kind of modifications. The
modifications are minor enough that its trivial to modify the xsl
stylesheets as well, but they are kind of essential. I know that Michael
Wiedman objects to such modifications, but unless someone suggests a
constructive way to get around it, I do not see any option but to do
some modifications.

On Fri, 7 Feb 2003, Benji Fisher wrote:
> > Benji, are you interested in taking a look at it? If you are interested
> > in going the python way, its definitely worth a look...
>
>       Yes, please send me what you have.
>

I have been using the vim-latex cvs tree to maintain what I've done...
Check out the following module:

TODO/srinath-files/python

just as you would check out anything else.

Make sure your python has the xml.dom and xml.dom.minidom pacakges
installed. Just for good measure install the PyXML package... (I assume
you know you to do these installs. Python makes it really easy).

After doing that run

$ python option.py

from the command line. That should produce some formatted text on
stdout. It processes latex-suite.xml file to produce the output. As of
now, latex-suite.xml is fully legal docbook, but that as I have said,
might need to change soon. For one, we will definitely need to use a
<tag> markup tag to specify vim-help tags (repitition intended). You
could redirect to /tmp/a.txt and ':set ft=help' to get a better idea...
Obviously, this is a work very much in progress... I only work for very
little time each day...

If you have saxon or some other tool, you can
use the standard docbook xsl stylesheet to produce html too from
latex-suite.xml.

I have not even begun thinking of anything other than docbook.

> * One, which Peter Karp pointed us to, is tBook:
> http://tbookdtd.sourceforge.net/
> This is yet another source format; it can be translated into LaTeX or
> DocBook.  Even if we ultimately decide to use this as our primary source
> format, I think the vim help may as well be generated from DocBook,
> since that will be useful to more people.  Advantages:  they claim fewer
> (but enough) elements than DocBook, lower tag/text ratio, and tag names
> that are similar to LaTeX commands.

This looks interesting. I'll take a look at it next time I get some
time.

Srinath

[Vim-latex-devel] Re: tex-refs project and xml to vim-help conversion

[Benji F. <be...@me...>]

Srinath Avadhanula wrote:
> I will also reply to Benji's mail here...
> 
> He asked whether it will be a good idea to process DocBook XML directly
> from within python. If you remember, I had spent some time mocking up a
> tiny little python script to do this. My experience was that its very
> easy to get started and get some results if you use python. The xml.dom
> and xml.dom.minidom packages are extremeley nice and let you get
> something done without having to know much XML. The problem is that
> after a while, it will become a bit of grunt work supporting each tag.
> Actually, over the last couple of weeks, I have been very slowly hacking
> away at that primitive python code. It has gotten to a pretty
> respectable size now (unfortunately)... It is able to do some good stuff
> now...
> 
> Benji, are you interested in taking a look at it? If you are interested
> in going the python way, its definitely worth a look...

      Yes, please send me what you have.

> I am very surprized to find that there is no docbook-latex converter
> already!!! But it will be a big gain even if we can have just vim-help
> and html...

      There are two approaches I have seen.  I have not actually tried 
either one.

* One, which Peter Karp pointed us to, is tBook: 
http://tbookdtd.sourceforge.net/
This is yet another source format; it can be translated into LaTeX or 
DocBook.  Even if we ultimately decide to use this as our primary source 
format, I think the vim help may as well be generated from DocBook, 
since that will be useful to more people.  Advantages:  they claim fewer 
(but enough) elements than DocBook, lower tag/text ratio, and tag names 
that are similar to LaTeX commands.

* The other approach is to use PassiveTeX: 
http://www.tei-c.org.uk/Software/passivetex/
The idea is to start with DocBook, and then use standard tools to create 
an FO (Format Object) file.  This seems to be another flacor (or DTD) of 
XML.  FO is the opposite of DocBook:  it describes physical markup 
instead of logical markup.  Then PassiveTeX is a set of TeX macros that 
read in the FO file.  I am not really interested in this path, since I 
would rather have something that actually produces a LaTeX file.

					--Benji

[Vim-latex-devel] Plese test this patch: vimfiles/plugin imaps.vim,1.28,1.29

[Srinath A. <sr...@fa...>]

Hello,

Could some of you please test the latest patch on imaps.vim? It attempts
to solve the problem described in the log message below.The patch is a
little kludgy and might break stuff temporarily...

I will wait for feedback on this patch before making a release.
Please update to the latest version using either anonymous cvs, or from:

http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vim-latex/vimfiles/plugin/imaps.vim

Thanks!

Srinath

----------------------------%<----------------------------
On Wed, 5 Feb 2003 sri...@us... wrote:

Update of /cvsroot/vim-latex/vimfiles/plugin
In directory sc8-pr-cvs1:/tmp/cvs-serv9901

Modified Files:
	imaps.vim
Log Message:
Bug: iabs break when latex-suite is triggered.
     (Preben Randhol, Sanip P Deshmukh)
Cause: If a mapping ends in a letter (say '\'), then abbreviations are not
    triggered by that letter. For example, if we have
        imap \ <C-r>='\'<CR>
        iab 12 twelve
    Then typing 12\ doesn't expand to twelve\.
    (Strangely enough "imap \ ?" doesn't have this problem and we get
    twelve?. Vim bug?)
    This problem is aggravated by the fact that latex-suite "protects"
    most letters to avoid expansions such as ``2 -> `\sqrt{}
Solution: After checking for mappings ending in a letter, if that letter is
    not in 'iskeyword', then also check whether the previous word has
    an abbreviation. Since vim does not have the equivalent of
    mapcheck() for abbreviations, this is complicated (maybe even hacky).


Index: imaps.vim
===================================================================
RCS file: /cvsroot/vim-latex/vimfiles/plugin/imaps.vim,v
retrieving revision 1.28
retrieving revision 1.29
diff -C2 -d -r1.28 -r1.29
*** imaps.vim	5 Feb 2003 04:12:28 -0000	1.28
--- imaps.vim	5 Feb 2003 23:29:04 -0000	1.29
***************
*** 227,236 ****
  		let ft = ""
  	else
! 		return a:char
  	endif
  	" Find the longest left-hand side that matches the line so far.
  	" matchstr() returns the match that starts first. This automatically
  	" ensures that the longest LHS is used for the mapping.
! 	let lhs = matchstr(text, '\V\(' . s:LHS_{ft}_{charHash} . '\)\$')
  	if strlen(lhs) == 0
  		return a:char
--- 227,268 ----
  		let ft = ""
  	else
! 		" If this is a character which could have been used to trigger an
! 		" abbreviation, check if an abbreviation exists.
! 		if a:char !~ '\k'
! 			let lastword = matchstr(getline('.'), '\k\+$', '')
! 			if lastword != ''
! 				" An extremeley wierd way to get around the fact that vim
! 				" doesn't have the equivalent of the :mapcheck() function for
! 				" abbreviations.
! 				exec "redir @a | silent! iab ".lastword." | redir END"
! 				if @a =~ "No abbreviation found"
! 					return a:char
! 				endif
! 				let abbreviationRHS = matchstr(@a, "\n".'i\s\+\k\+\s\+@\?\zs.*')
! 				let abbreviationRHS = escape(abbreviationRHS, '<')
! 				exec 'let abbreviationRHS = "'.abbreviationRHS.'"'
!
! 				let lhs = lastword.a:char
! 				let rhs = abbreviationRHS.a:char
! 				let phs = IMAP_GetPlaceHolderStart()
! 				let phe = IMAP_GetPlaceHolderEnd()
! 			else
! 				return a:char
! 			endif
! 		else
! 			return a:char
! 		endif
  	endif
  	" Find the longest left-hand side that matches the line so far.
  	" matchstr() returns the match that starts first. This automatically
  	" ensures that the longest LHS is used for the mapping.
! 	if !exists('lhs') || !exists('rhs')
! 		let lhs = matchstr(text, '\V\(' . s:LHS_{ft}_{charHash} . '\)\$')
! 		let hash = s:Hash(lhs)
! 		let rhs = s:Map_{ft}_{hash}
! 		let phs = s:phs_{ft}_{hash}
! 		let phe = s:phe_{ft}_{hash}
! 	endif
!
  	if strlen(lhs) == 0
  		return a:char
***************
*** 239,245 ****
  	" character typed:
  	let bs = substitute(strpart(lhs, 1), ".", "\<bs>", "g")
! 	let hash = s:Hash(lhs)
! 	return bs . IMAP_PutTextWithMovement(s:Map_{ft}_{hash},
! 				\ s:phs_{ft}_{hash}, s:phe_{ft}_{hash})
  endfunction

--- 271,275 ----
  	" character typed:
  	let bs = substitute(strpart(lhs, 1), ".", "\<bs>", "g")
! 	return bs . IMAP_PutTextWithMovement(rhs, phs, phe)
  endfunction

***************
*** 682,686 ****
  	endif
  endfunction " }}}
! " IMAP_DebugClear: interface to Tex_DebugClear if avaialable, otherwise emulate it {{{
  " Description:
  function! IMAP_DebugPrint(pattern)
--- 712,716 ----
  	endif
  endfunction " }}}
! " IMAP_DebugPrint: interface to Tex_DebugPrint if avaialable, otherwise emulate it {{{
  " Description:
  function! IMAP_DebugPrint(pattern)

[Vim-latex-devel] Re: tex-refs project and xml to vim-help conversion

[Michael W. <mw...@mi...>]

* Srinath Avadhanula <sr...@fa...> [030201 12:29]:
...
> But if I do lynx test.html and from within lynx do
> print -> save to local file -> test.txt
> then I correctly get:
> 
>    =====================================================================
>    Section name                                            *section-tag*

OK, so I will try to get some helpot to customize the XSL stylesheets
to generate your mentioned HTML output. This may take a while....

...
> It looks like customizing docbook xsl stylesheets is a complicated
> affair from what you said about customizing the output of the section
> tag. So another question: how hard is it to add tags of our own... For
> example, in a vim help file, we typically describe vim options in a
> consistent manner which lends itself nicely to markup.
> (For example try :help 'statusline'). We could do the same thing with a
> series of <table>'s but then we'll have to take care of the indexing
> and stuff ourselves which kind of defeats the purpose of docbook.

If you want a 'valid DocBook XML' document, you are _not_ allowed to
add tags of your own. The reason is obvious: usually you want to process
your XML document using several tools to process different kinds of output
formats. And each tool must know whioch tags are valid, so that it can
handle the source file.

One possibility might be the use of so-called 'processing instrucions'
like e.g.:

<?vimhelp some information for the vim help file backend?>

Processing instructions contain information  required by a specific 
application expected to process the XML data. But then your 'application'
must be capable of handling such processing instructions.

Let me know if this might be a way to ease the development of a special
'tex-refs to vim-help filter application'. I could add such PIs to
the XML source file.

Michael
-- 
mw...@mi...                              http://www.miwie.org
mw...@mi...

[Vim-latex-devel] Fold comments?

[Fabio S. <sp...@li...>]

I got a suggestion for a feature, pehraps easy to implement. 
What about automatic folding of several commented lines, maybe with a
standard "message" in the folding line, like "COMMENT" 

I.E. these four lines 

% bla bla bla 
% commented line 
% another 
% bla blah 

becomes folded into: 

+-- 4 lines: COMMENTS 


Do you think it can be fine? 

Bye! 
-- 
  Fabio Spelta
  
   email:  sp...@li...
   jabber: fe...@ja...
   ecdl project: http://ecdllibre.sf.net

[Vim-latex-devel] Re: tex-refs project and xml to vim-help conversion

[Srinath A. <sr...@fa...>]

On Sat, 1 Feb 2003, Michael Wiedmann wrote:

> > <table>
> > <tr><td colspan=2>=====================================================================</td></tr>
> > <tr><td>Section name</td><td align=right>*section-tag*</td></tr>
> > </table>
>
> This might need some complicate customization, but I can ask for some
> help in the DocBook-Apps ML. Could you please test before, whether
> this output would produce the wanted TXT output if dumped with lynx/w3m?

Lynx behaves somewhat strangely... Doing lynx -dump test.html > test.txt
produces something like:

   =====================================================================
   Section name *section-tag*

But if I do lynx test.html and from within lynx do
print -> save to local file -> test.txt
then I correctly get:

   =====================================================================
   Section name                                            *section-tag*

I still do not quite see why it produces extra leading spaces, but that
is easy to take care of...

> <para> foo foo foo foo <emphasis>bar bar</emphasis> foo foo foo</para>
>
> If you completely ignore the contents of the <emphasis> tag, then you'll
> loose the information inside the tag. Just copy the text content of
> any unknown tag to the output file and don't do any sepcial treatment
> for this tag.

Okay... Its trivial enough to just process all text within unkwown
tags in python...

It looks like customizing docbook xsl stylesheets is a complicated
affair from what you said about customizing the output of the section
tag. So another question: how hard is it to add tags of our own... For
example, in a vim help file, we typically describe vim options in a
consistent manner which lends itself nicely to markup.
(For example try :help 'statusline'). We could do the same thing with a
series of <table>'s but then we'll have to take care of the indexing
and stuff ourselves which kind of defeats the purpose of docbook.

Srinath

[Vim-latex-devel] Re: tex-refs project and xml to vim-help conversion

[Michael W. <mw...@mi...>]

* Srinath Avadhanula <sr...@fa...> [030131 18:58]:

> Thats what it looked like :) A question: How hard is it to tweak the xsl
> stylesheets for html non-chunked so that instead of generating sections
> like:
> 
> <h1 class=section><a name="#section-tag">Overview</h1>
> 
> it will do something like:
> 
> <table>
> <tr><td colspan=2>=====================================================================</td></tr>
> <tr><td>Section name</td><td align=right>*section-tag*</td></tr>
> </table>

This might need some complicate customization, but I can ask for some
help in the DocBook-Apps ML. Could you please test before, whether
this output would produce the wanted TXT output if dumped with lynx/w3m?

...
> Its just that supporting each tag becomes more and more work... Well, we
> could always just get the text data from all unsupported tags... Dunno
> how good an idea that is though.... Might even be better just completely
> ignoring unsupported tags.

You cannto just ignore unknown tags, otherwise you'll loose content!
Imagine a peace of source like:

<para> foo foo foo foo <emphasis>bar bar</emphasis> foo foo foo</para>

If you completely ignore the contents of the <emphasis> tag, then you'll
loose the information inside the tag. Just copy the text content of
any unknown tag to the output file and don't do any sepcial treatment
for this tag.

Michael
-- 
mw...@mi...                              http://www.miwie.org
mw...@mi...

[Vim-latex-devel] Re: tex-refs project and xml to vim-help conversion

[Michael W. <mw...@mi...>]

* Benji Fisher <be...@me...> [030131 16:12]:

>      That's too bad.  I was under the impression that LaTeX output was 
> already standard.  Especially for the tex-refs and vim-latex projects, 
> it would be nice to have some form of TeX output!

There is at least one project which tries to convert DocBook XML to
LaTeX (DB2LaTeX: http://www.sourceforge.net/projects/db2latex) but 
it's not yet usable. The author promised to start work at it again,
but AFAIK nothing happened during the last months.

The DocBook XSL Stylesheets to generate XSL-FO work quite good,
but the backends to transform FO to PDF are not completley 
satisfying - at least if you have a 'real life' document using
tables, etc.
But for less complicated documents using FOP from the Apache project
should give already good results.

...
>      We in the vim-latex project know very little about XML and 
> DocBook.  What we really want at this point is a reading list to get 
> started.  What is the structure of a DocBook document?  What is the idea 
> behind it?  What needs to be done to generate a specific output format? 
>  Just point me to some good "getting started" guides, and I think I can 
> go from there ... or at least, it will keep me busy for a while. ;)

The following links might be a bit out of date but should give you 
a start:

Writing Documentation Using DocBook
David Rugge; Mark Galassi; Eric Bischoff
http://www.caldera.de/~eric/crash-course/HTML/index.html

Introduction in DocBook from Marc Galassi
http://nis-www.lanl.gov/~rosalia/mydocs/docbook-intro.html

The Debian SGML/XML HOWTO
http://people.debian.org/~bortz/SGML-HOWTO/potato/howto.html

The Using DocBook HOWTO of the Linux Documentation Project
http://metalab.unc.edu/godoy/using-docbook/using-docbook.html

DocBook FAQ
Dave Pawson
http://www.dpawson.co.uk/docbook/

DocBook Wiki
http://docbook.org/wiki/moin.cgi/

Michael
-- 
mw...@mi...                              http://www.miwie.org
mw...@mi...

[Vim-latex-devel] Re: tex-refs project and xml to vim-help conversion

[Srinath A. <sr...@fa...>]

Hey Michael,

Thanks for the information!

On Fri, 31 Jan 2003, Michael Wiedmann wrote:

> For TXT output we use the HTML non-chunked output and use 'lynx -dump'
> to create TXT output. Note: there are no XSL stylesheets to generate
> directly TXT output!
>

Thats what it looked like :) A question: How hard is it to tweak the xsl
stylesheets for html non-chunked so that instead of generating sections
like:

<h1 class=section><a name="#section-tag">Overview</h1>

it will do something like:

<table>
<tr><td colspan=2>=====================================================================</td></tr>
<tr><td>Section name</td><td align=right>*section-tag*</td></tr>
</table>

I hope you see what I'm trying to say... This way, hopefully lynx -dump
will produce the sections in the familiar way:

=====================================================================
OVERVIEW                                                *section-tag*

So... although a xsl stylesheet for creating plain text does not exist,
how hard is it to tweak the html-nonchunked stylesheet so that lynx
-dump will look reasonable?

Is this a better option? Lesser work maybe?

> > > For a simple vim help file itself, we need not more than a couple of
> > > elements:
> > >
> > > 1. table
> > > 2. option
> > > 3. tag
> > > 4. para
> > >
> > > and maybe a few more.
>
> IMHO it's _not_ a good idea to restrict the use to a subset of all available
> DocBook tags! If a backend cannot handle specific tags it should simply
> copy the contents (all between start and end tag) of the unknown tags
> unchanged to the output file.
>
Its just that supporting each tag becomes more and more work... Well, we
could always just get the text data from all unsupported tags... Dunno
how good an idea that is though.... Might even be better just completely
ignoring unsupported tags.

> Maybe you should consider to split the source XML file into separate
> files. It can be easier to handle only a part (e.g. Chapter 1, TeX)
> of the complete XML file at the beginning. I could provide a XSL
> stylesheets which auomatically extracts a specific section of the
> complete source file into a separate file.
>
I do not really know how splitting XML sources into seperate files will
be much help. A typical vim help file is a single text file with
sections... And unlike the tex-refs project, a vim help file is well
within maybe 10-20 kb.

I will also reply to Benji's mail here...

He asked whether it will be a good idea to process DocBook XML directly
from within python. If you remember, I had spent some time mocking up a
tiny little python script to do this. My experience was that its very
easy to get started and get some results if you use python. The xml.dom
and xml.dom.minidom packages are extremeley nice and let you get
something done without having to know much XML. The problem is that
after a while, it will become a bit of grunt work supporting each tag.
Actually, over the last couple of weeks, I have been very slowly hacking
away at that primitive python code. It has gotten to a pretty
respectable size now (unfortunately)... It is able to do some good stuff
now...

Benji, are you interested in taking a look at it? If you are interested
in going the python way, its definitely worth a look...

I am very surprized to find that there is no docbook-latex converter
already!!! But it will be a big gain even if we can have just vim-help
and html...

Srinath

PS: I am subscribed to the tex-refs mailing list too...

-- 
Srinath Avadhanula
Jan 31 1:04pm
"Not only is this incomprehensible, but the ink is ugly and the paper
is from the wrong kind of tree."
		-- Professor W.

[Vim-latex-devel] Re: xml - latex - vim

[Benji F. <be...@me...>]

Peter Karp wrote:
> Hi Benji,
> 
> thanks for your mail to the list. I guess/hope that Michael will be
> uplifted by your offer to join in our efforts for a great
> documentation for latex and will find time to answer soon. :-)

      Yes, he already has.

> Thanks for subscribing to the list. This (only) time I'll respond to
> your private address, because it's not interesting for the list in
> general.

      It *is* of interest to the vim-latex list, so I am cc'ing them.

>>We are thinking of writing the documentation for LaTeX Suite in XML
>>format, so that we can get LaTeX, HTML, and Vim-help output.  If it works
>>out, we can post a link on http://vimdoc.sourceforge.net/ in case others
>>find it useful.
> 
> I see. Do you already have a nice editor to write the XML files or do
> you use Vim (with plugins) for that job? Vim isn't able to display XML
> files in a tree structured format (with folding), is it?

      I plan to use vim.  It does have some folding abilities.

> I don't know if you already know a way to get from XML to LaTeX. I
> know of one -- tbook:
> 
>     http://tbookdtd.sourceforge.net/
> 
> I have not used it. I wrote my diploma thesis with standard latex
> (using the koma-script which is a _very_ versatile nice package in
> general with some sugar for german users).

      It is worth looking at.  Thanks for the pointer.

					--Benji

[Vim-latex-devel] Re: tex-refs project and xml to vim-help conversion

[Benji F. <be...@me...>]

Michael Wiedmann wrote:
> * Peter Karp <pma...@ka...> [030131 14:34]:
> 
>>>I downloaded 0.2.1 of the tex-refs xml source. It looks like you are
>>>using the DocBook DTD.
> 
> We are using DocBook XML V4.2, currently the most actual version.
> 
> The HTML (chunked and non-chunked) transformation process uses the 
> most actual version of the DocBook XSL Stylesheets (V1.60.1 at the
> time of this writing), using Saxon as XSLT processor (I'd prefer to
> use xsltproc from libxml2 because it would be much faster, but it
> is still buggy).
> 
> For TXT output we use the HTML non-chunked output and use 'lynx -dump'
> to create TXT output. Note: there are no XSL stylesheets to generate
> directly TXT output!
> 
> RTF is generated using openjade and the DSSSL stylesheets (there are
> no XSL stylesheets for RTF output available).
> 
> PDF is still experimental, the XSL-FO output is quite good, but the
> backends to transform this into high quality PDF are not yet ready.
> Currently there is some work undergoing in the ConTeXt community,
> which might lead to good PDF in the near future.

      That's too bad.  I was under the impression that LaTeX output was 
already standard.  Especially for the tex-refs and vim-latex projects, 
it would be nice to have some form of TeX output!

> IMHO it's _not_ a good idea to restrict the use to a subset of all available
> DocBook tags! If a backend cannot handle specific tags it should simply 
> copy the contents (all between start and end tag) of the unknown tags 
> unchanged to the output file.
> 
> Maybe you should consider to split the source XML file into separate
> files. It can be easier to handle only a part (e.g. Chapter 1, TeX) 
> of the complete XML file at the beginning. I could provide a XSL
> stylesheets which auomatically extracts a specific section of the
> complete source file into a separate file.
> 
> Please let me know if you need any further information or help
> (as Peter already mentioned I'm quite busy at the moment but will
> do my best to assist you in your work).
> 
> Michael

      Thanks for the information.  It is beginning to sound as if XSLT 
is not the right tool for us to use, after all.  I am inclined to write 
a custom filter from DocBook directly to vim help, rather than use some 
intermediate format.  We might use Python, which already has support for 
processing XML.

      We in the vim-latex project know very little about XML and 
DocBook.  What we really want at this point is a reading list to get 
started.  What is the structure of a DocBook document?  What is the idea 
behind it?  What needs to be done to generate a specific output format? 
  Just point me to some good "getting started" guides, and I think I can 
go from there ... or at least, it will keep me busy for a while. ;)

					--Benji

[Vim-latex-devel] Re: tex-refs project and xml to vim-help conversion

[Michael W. <mw...@mi...>]

* Peter Karp <pma...@ka...> [030131 14:34]:

> > I downloaded 0.2.1 of the tex-refs xml source. It looks like you are
> > using the DocBook DTD.

We are using DocBook XML V4.2, currently the most actual version.

> > But I am quite unclear about how exactly they process the xml source to
> > generate the various formats. It looks like they would use the docbook
> > xsl stylesheets available at
> > 
> > http://docbook.sourceforge.net/projects/xsl/

The HTML (chunked and non-chunked) transformation process uses the 
most actual version of the DocBook XSL Stylesheets (V1.60.1 at the
time of this writing), using Saxon as XSLT processor (I'd prefer to
use xsltproc from libxml2 because it would be much faster, but it
is still buggy).

For TXT output we use the HTML non-chunked output and use 'lynx -dump'
to create TXT output. Note: there are no XSL stylesheets to generate
directly TXT output!

RTF is generated using openjade and the DSSSL stylesheets (there are
no XSL stylesheets for RTF output available).

PDF is still experimental, the XSL-FO output is quite good, but the
backends to transform this into high quality PDF are not yet ready.
Currently there is some work undergoing in the ConTeXt community,
which might lead to good PDF in the near future.

> > stylesheets for it, because we will have to do all the rendering
> > ourselves. 
> 
> I hope that it won't be that hard, because the stylesheet for the plain
> ascii text output could be used as a starting point.

See the note above: there are _no_ XSL stylesheets to genertate directly
TXT output.

> > Therefore, it is of importance to know how many elements of
> > the docbook DTD definition the tex-refs project uses. Each new element
> > used will be more work.
...
> > For a simple vim help file itself, we need not more than a couple of
> > elements:
> > 
> > 1. table
> > 2. option
> > 3. tag
> > 4. para
> > 
> > and maybe a few more.

IMHO it's _not_ a good idea to restrict the use to a subset of all available
DocBook tags! If a backend cannot handle specific tags it should simply 
copy the contents (all between start and end tag) of the unknown tags 
unchanged to the output file.

> I guess Michael is right and it's easier to create an XSLT transformation
> instead of writing a Vim macro (awk or whatever script) to do all the
> formatting, but maybe I'm wrong -- especially considering that you both
> have experience to write vim macros, but not with XSLT.
> 
> The next best bet would be to use the text output format and reformat that
> to the Vim help format. That's not as nice as doing a direct translation,
> but might be a much easier solution -- more a (I hope so) quick hack to
> have the information at least inside vim so that the help tags file can be
> generated.

Maybe you should consider to split the source XML file into separate
files. It can be easier to handle only a part (e.g. Chapter 1, TeX) 
of the complete XML file at the beginning. I could provide a XSL
stylesheets which auomatically extracts a specific section of the
complete source file into a separate file.

Please let me know if you need any further information or help
(as Peter already mentioned I'm quite busy at the moment but will
do my best to assist you in your work).

Michael
-- 
mw...@mi...                              http://www.miwie.org
mw...@mi...

Re: [Vim-latex-devel] vim latex on mandrake 8.0 (vim 6.0av beta)

[Benji F. <be...@me...>]

Jason Stein wrote:
> Thanks for producing a tool that fits my needs!
> 
> The only problem I had was when attempting to use an insert
> mode map (eg. ECE) I would get an error about an undefined 
> function 'cursor'. I traced it back to line ~698 of 
> imap.vim. After commenting out the line, insert mode maps 
> seem to work fine.
> 
> Am I breaking vim latex or is there a more elegant fix?

      I think this is likely to cause problems.  It looks as though the 
cursor() function was added in vim 6.1.  Since our goal is to support 
vim 6.0, we should try to find another way to do this.  If you can 
upgrade to 6.1, it should work for you.

      OTOH, we have no intention to support beta versions of vim 6.0.  I 
think it was a big mistake on Red Hat's part (and of course Mandrake 
copied it) to include a beta version of vim, especially since they used 
it as the system vi.

HTH					--Benji Fisher