Re: [NTG-context] math symbol \doteq cause error in mk||
No, after adding the \relax, same problem here.
Regards,
Andy
On Tue, Apr 21, 2009 at 8:40 AM, Wolfgang Schuster <
schuster.wolfg...@googlemail.com> wrote:
>
> Am 21.04.2009 um 15:35 schrieb Andy Wong:
>
> Hello,
>> I use the context minimal with updating to lastest beta. when using
>> $\doteq$ in my equation, texexec catch an error:
>>
>> ! Illegal unit of measure (pt inserted).
>>
>> =
>> \buildrel ...mathrel {\mathop {\kern \zerocount #2
>> }\limits ^{#1}}
>> l.3 Test $\doteq
>>$
>> ?
>>
>> I check the definition in math-pln.mkii, the \doteq is defined as:
>>
>> \def\buildrel#1\over#2%
>> {\mathrel{\mathop{\kern\zerocount#2}\limits^{#1}}}
>>
>
> {\mathrel{\mathop{\kern\zerocount\relax#2}\limits^{#1}}}
>
> Did a \relax help?
>
> Wolfgang
>
>
> ___
> 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
___
[NTG-context] math symbol \doteq cause error in mk||
Hello,
I use the context minimal with updating to lastest beta. when using $\doteq$
in my equation, texexec catch an error:
! Illegal unit of measure (pt inserted).
=
\buildrel ...mathrel {\mathop {\kern \zerocount #2
}\limits ^{#1}}
l.3 Test $\doteq
$
?
I check the definition in math-pln.mkii, the \doteq is defined as:
\def\buildrel#1\over#2%
{\mathrel{\mathop{\kern\zerocount#2}\limits^{#1}}}
\def\doteq
{\buildrel\textstyle.\over=}
The problem seems caused by \zerocount. After comparing with the definition
in math-pln.mkiv, I changed it to \zeropoint and texexec run successfully.
Regards,
Andy
___
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
___
Re: [NTG-context] mtxrun --noquotes on windows
It may be windows has problem to handle the space in quoted parameters? write those commands to a batch file then call by mtxrun works right. May be it is a solution. :) Andy On Fri, Apr 10, 2009 at 3:32 PM, Aditya Mahajan wrote: > On Fri, 10 Apr 2009, Andy Wong wrote: > > Yes, if leave a space between the last two quotes, mtx output seems ok. >> >> MTXrun | >> MTXrun | executing: vim -u NONE -c "set tabstop=8" "test.tex" >> MTXrun | >> But it still cause vim open two file named "tabstop=8" and "test.tex" to >> edit. So it seems vim treat tabstop=8 as a file? that still a quotes >> problem, right? I also test if there no space in quoted arguments, such as >> > > I am beginning to suspect that it is a shell problem rather than a mtxrun > problem. Mtxrun passes the correct commands and quotes to the shell, but the > shell for some reason ignores that. > > > 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 : 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 ___
Re: [NTG-context] t-vim failed under windows
Thanks. Andy On Fri, Apr 10, 2009 at 3:28 PM, Aditya Mahajan wrote: > On Fri, 10 Apr 2009, Andy Wong wrote: > > It did not work, either. Same problem. >> > > Then, for the moment use your workaround of having a batch file. I will try > to get access to a windows environment in a few days and then check what is > going wrong on windows. > > > 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 : 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 ___
Re: [NTG-context] t-vim failed under windows
It did not work, either. Same problem.
Andy
On Fri, Apr 10, 2009 at 3:13 PM, Aditya Mahajan wrote:
> On Thu, 9 Apr 2009, Andy Wong wrote:
>
> Hello,
>>
>> I have tried the example using the vim mode to typeset some c codes. When
>> I
>> run the sample file, context stop with errors. the sample file and log
>> file
>> as
>> list below. I use the windowsXP with the minimal context from ConTeXt
>> garden
>> and \write18 is enabled. From the log file, it seems the vim command is
>> not
>> properly quoted as follows:
>>
>
> Another attempt. Does the following test file work for you?
>
> %
> %%% Start file
> %
>
> \unprotect
> \def\shellescapedquote{\letterdoublequote}
>
> \def\runvimsyntax#1
> {\executesystemcommand
> {mtxrun --verbose bin:vim
> -u NONE % No need to read unnessary configurations
> -e % run in ex mode
> -C % Set compatibile
> -n % No swap
> -c \shellescapedquote set tabstop=\@@vstab\shellescapedquote\space
> -c \shellescapedquote syntax on\shellescapedquote\space
> -c \shellescapedquote set syntax=\@@vssyntax\shellescapedquote\space
> -c \shellescapedquote let
> contextstartline=\@@vsstart\shellescapedquote\space
> -c \shellescapedquote let contextstopline=\@@vsstop\shellescapedquote
> \space
> -c \shellescapedquote source
> kpse:2context.vim\shellescapedquote\space
> -c \shellescapedquote wqa\shellescapedquote\space
>\shellescapedquote#1\shellescapedquote}}
> \protect
>
> \setupcolors[state=start]
> \usemodule[vim]
> \definevimtyping [C] [syntax=c]
> \starttext
> \startC
> #include
> #include
> void main()
> {
> printf("Hello World\n") ;
> return;
> }
> \stopC
> \stoptext
>
> %
> %%% End file
> %
>
>
> 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 : 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
___
Re: [NTG-context] mtxrun --noquotes on windows
Yes, if leave a space between the last two quotes, mtx output seems ok. MTXrun | MTXrun | executing: vim -u NONE -c "set tabstop=8" "test.tex" MTXrun | But it still cause vim open two file named "tabstop=8" and "test.tex" to edit. So it seems vim treat tabstop=8 as a file? that still a quotes problem, right? I also test if there no space in quoted arguments, such as mtxrun --noquotes bin:vim "-u NONE -c \"help\" \"test.tex\" " This time vim will open the "test.tex" and help window as expected. If any command with space in -c parameter, vim can not correct executed. manually execute the vim command: vim -u NONE -c "set tabstop=8" "test.tex" vim open the "test.tex" only to edit as expected. Andy On Fri, Apr 10, 2009 at 2:49 PM, Aditya Mahajan wrote: > On Fri, 10 Apr 2009, Andy Wong wrote: > > I think I may not write it clear in my previous email. I run the command as >> >> mtxrun --noquotes bin:vim "-u NONE -c \"set tabstop=8\" \"test.tex\"" >> > > If you quote the filename, then it should be > mtxrun --noquotes bin:vim "-u NONE -c \"set tabstop=8\" \"test.tex\" " > > Notice the space before the last quote. This will open two files test.tex > and "", but that it is ok. The last file is ignored by t-vim. > > which got the mtxrun output has spurious " before test.tex. if omit the \" >> around the test.tex, like this, >> >> mtxrun --noquotes bin:vim "-u NONE -c \"set tabstop=8\" test.tex" >> >> there are no spurious " in mtxrun output. >> > > So it is not mtxrun's fault. > > However, both will make vim open a >> new file named "tabset=8" >> > > You mean tabstop=8? > > and the test.tex to be edited. That is the >> problem. I guess under linux this command should open vim to edit the >> test.tex only instead. >> > > If vim is passed the correct command, I do not see why it should not > execute it in the same way in windows. Try one more thing. Run > > mtxrun --noquotes bin:vim "-u NONE -c \"set tabstop=8\" \"test.tex\" " > > mtxrun should report that it is executing > > vim -u NONE -c "set tabstop=8" "test.tex" > > Execute the above command manually on the terminal. Do you get the same > result in both cases? > > Aditya > > > > > On Fri, Apr 10, 2009 at 1:40 PM, Aditya Mahajan wrote: >> >> Hi, >>> >>> It seems that mtxrun --noquotes behaves differently on windows and linux. >>> Can someone on windows (who has vim) check the following. Run >>> >>> mtxrun --noquotes bin:vim "-u NONE -c \"set tabstop=8\" test.tex" >>> >>> You will enter in vim. Press :qa! to exit vim. What does the output on >>> the >>> terminal say? On my linux machine, I get >>> >>> MTXrun | executing: vim -u NONE -c "set tabstop=8" test.tex >>> >>> Andy Wong tested it on windows and he gets >>> >>> MTXrun | executing: vim -u NONE -c "set tabstop=8" "test.tex >>> >>> Notice the spurious " before test.tex. This causes t-vim to fail on >>> windows. Do others on windows get the same behavour? I do not see a >>> reason >>> why mtxrun should behave differently on linux and windows. >>> >>> Thanks, >>> 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 : 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 > > ___ > ___ 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 ___
Re: [NTG-context] mtxrun --noquotes on windows
I think I may not write it clear in my previous email. I run the command as mtxrun --noquotes bin:vim "-u NONE -c \"set tabstop=8\" \"test.tex\"" which got the mtxrun output has spurious " before test.tex. if omit the \" around the test.tex, like this, mtxrun --noquotes bin:vim "-u NONE -c \"set tabstop=8\" test.tex" there are no spurious " in mtxrun output. However, both will make vim open a new file named "tabset=8" and the test.tex to be edited. That is the problem. I guess under linux this command should open vim to edit the test.tex only instead. Andy On Fri, Apr 10, 2009 at 1:40 PM, Aditya Mahajan wrote: > Hi, > > It seems that mtxrun --noquotes behaves differently on windows and linux. > Can someone on windows (who has vim) check the following. Run > > mtxrun --noquotes bin:vim "-u NONE -c \"set tabstop=8\" test.tex" > > You will enter in vim. Press :qa! to exit vim. What does the output on the > terminal say? On my linux machine, I get > > MTXrun | executing: vim -u NONE -c "set tabstop=8" test.tex > > Andy Wong tested it on windows and he gets > > MTXrun | executing: vim -u NONE -c "set tabstop=8" "test.tex > > Notice the spurious " before test.tex. This causes t-vim to fail on > windows. Do others on windows get the same behavour? I do not see a reason > why mtxrun should behave differently on linux and windows. > > Thanks, > 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 : 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 ___
Re: [NTG-context] t-vim failed under windows
> It should be -u NONE (all capitals) -u NONE is the same result. > It is mtxrun related. It works in linux, so it could be windows related. I do not have a windows machine > to test (and not enough diskspace to install windows on a VM). mtxrun seems not execute the vim command line correctly. > As a last resort, what does the log file say for this (all in one line) >mtxrun --verbose --noquotes bin:vim "-u NONE -e -C -n -V10log -c \"set tabstop=8\" -c \"syntax on\" -c \"set syntax=c\" -c \"let contextstartline=1\" -c \"let contextstopline=0\" -c \"source c:/context/tex/texmf-context/tex/context/third/vim/2context.vim\" -c \"wqa\" \"vimdemo-vimsyntax.tmp\" " The log file list as follows: - "tabstop=8" [New File] line 0: set --- Options --- helplang=En ttyfast verbose=20 noloadplugins updatecount=0 verbosefile=log iskeyword=@,48-57,_,192-255 line 0: syntax No Syntax items defined for this buffer line 0: set --- Options --- helplang=En ttyfast verbose=20 noloadplugins updatecount=0 verbosefile=log iskeyword=@,48-57,_,192-255 line 0: let b:changedtick #3 v:version #702 v:beval_winnr #0 v:lnum#0 v:scrollstart command line line 0 v:dying #0 v:lang C v:count #0 v:progname vim.exe v:cmdbang #0 v:foldlevel #0 v:ctypeC v:prevcount #0 v:mouse_win #0 v:count1 #0 v:foldstart #0 v:foldend #0 v:profiling #0 v:beval_col #0 v:beval_lnum #0 v:mouse_lnum #0 v:beval_bufnr #0 v:shell_error #0 v:servername VIM v:lc_time English_United States.1252 v:searchforward #1 v:mouse_col #0 v:statusmsgline 0: let line 0: let b:changedtick #3 v:version #702 v:beval_winnr #0 v:lnum#0 v:scrollstart command line line 0 v:dying #0 v:lang C v:count #0 v:progname vim.exe v:cmdbang #0 v:foldlevel #0 v:ctypeC v:prevcount #0 v:mouse_win #0 v:count1 #0 v:foldstart #0 v:foldend #0 v:profiling #0 v:beval_col #0 v:beval_lnum #0 v:mouse_lnum #0 v:beval_bufnr #0 v:shell_error #0 v:servername VIM v:lc_time English_United States.1252 v:searchforward #1 v:mouse_col #0 v:statusmsgline 0: let line 0: source Error detected while processing command line: E471: Argument required line 0: wqa > If this does not work, does replacing bin:vim with bin:gvim work? No. Andy ___ 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 ___
Re: [NTG-context] t-vim failed under windows
The same problem. It seems the \shellescapedquote generated to the wrong position. So vim complains the -c parameters is wrong. Andy. On Thu, Apr 9, 2009 at 4:22 PM, Aditya Mahajan wrote: > On Thu, 9 Apr 2009, Andy Wong wrote: > > Hello, >> >> I have tried the example using the vim mode to typeset some c codes. When >> I >> run the sample file, context stop with errors. the sample file and log >> file >> as >> list below. I use the windowsXP with the minimal context from ConTeXt >> garden >> and \write18 is enabled. From the log file, it seems the vim command is >> not >> properly quoted as follows: >> >> MTXrun | executing: vim "-u NONE -e -C -n -V10log -c set" "tabstop=8 -c >> syntax" >> "on -c set" "syntax=c -c let" "contextstartline=1 -c let" >> "contextstopline=0 >> -c >> source" "c:/context/tex/texmf-context/tex/context/third/vim/2context.vim >> -c >> wqa >> vimdemo-vimsyntax.tmp " >> I check the t-vim.tex, the definition of the vim command is correct. I >> don't >> know why the \shellescapedquote is not properly resolved. >> Any help? thanks. >> > > Does changing "noquote" to "noquotes" in line 797 of t-vim help? > > 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 : 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 ___
[NTG-context] t-vim failed under windows
Hello,
I have tried the example using the vim mode to typeset some c codes. When I
run the sample file, context stop with errors. the sample file and log file
as
list below. I use the windowsXP with the minimal context from ConTeXt garden
and \write18 is enabled. From the log file, it seems the vim command is not
properly quoted as follows:
MTXrun | executing: vim "-u NONE -e -C -n -V10log -c set" "tabstop=8 -c
syntax"
"on -c set" "syntax=c -c let" "contextstartline=1 -c let" "contextstopline=0
-c
source" "c:/context/tex/texmf-context/tex/context/third/vim/2context.vim -c
wqa
vimdemo-vimsyntax.tmp "
I check the t-vim.tex, the definition of the vim command is correct. I don't
know why the \shellescapedquote is not properly resolved.
Any help? thanks.
Andy
---
Sample file:_
\setupcolors[state=start]
\usetypescript[modern-base][texnansi]
\setupbodyfont[modern,10pt]
\usemodule[vim]
\starttext
\title{Matlab Code Listing -- Color}
\definevimtyping [C] [syntax=c]
\startC
#include
#include
void main()
{
printf("Hello World\n") ;
return;
}
\stopC
\stoptext
--
The Log file
C:\Documents\TeX>context --verbose vimdemo.tex
MTXrun | variable SELFAUTOLOC set to c:/context/tex/texmf-mswin/bin
MTXrun | variable SELFAUTODIR set to c:/context/tex/texmf-mswin
MTXrun | variable SELFAUTOPARENT set to c:/context/tex
MTXrun | variable TEXMFCNF set to
c:\context\tex\texmf{-local,-context,}/web2c
MTXrun | loading configuration for c:/context/tex/texmf/web2c from
c:/context/te
x/texmf-cache/luatex-cache/context/2fea56f92e5267d7cc9662e4d5f52e1e/trees/53ad5f
8b88994bdd02baa17501789699
MTXrun | locating list of c:/context/tex/texmf-project
MTXrun | locating list of c:/context/tex/texmf-fonts
MTXrun | locating list of c:/context/tex/texmf-local
MTXrun | locating list of c:/context/tex/texmf-mswin
MTXrun | locating list of c:/context/tex/texmf-context
MTXrun | locating list of c:/context/tex/texmf-extra
MTXrun | locating list of c:/context/tex/texmf
MTXrun | loading files for c:/context/tex/texmf-mswin from
c:/context/tex/texmf-
cache/luatex-cache/context/2fea56f92e5267d7cc9662e4d5f52e1e/trees/ad82a2edc94cf3
e384a3b09c57286765
MTXrun | loading files for c:/context/tex/texmf-context from
c:/context/tex/texm
f-cache/luatex-cache/context/2fea56f92e5267d7cc9662e4d5f52e1e/trees/3063f1ad75eb
7de075a8e56a9b4e93ce
MTXrun | loading files for c:/context/tex/texmf from
c:/context/tex/texmf-cache/
luatex-cache/context/2fea56f92e5267d7cc9662e4d5f52e1e/trees/e4a2bdb91bf5cb68211e
9b73648a473b
MTXrun | using script:
c:/context/tex/texmf-context/scripts/context/lua/mtx-cont
ext.lua
MTXrun | run 1: luatex
--fmt="c:/context/tex/texmf-cache/luatex-cache/context/2f
ea56f92e5267d7cc9662e4d5f52e1e/formats/cont-en"
--lua="c:/context/tex/texmf-cach
e/luatex-cache/context/2fea56f92e5267d7cc9662e4d5f52e1e/formats/cont-en.luc"
"./
vimdemo.tex"
This is LuaTeX, Version snapshot-0.37.0-2009040118 (Web2C 7.5.7)
\write18 enabled.
(vimdemo.tex
ConTeXt ver: 2009.04.06 18:43 MKIV fmt: 2009.4.6 int: english/english
system : cont-new loaded
(c:/context/tex/texmf-context/tex/context/base/cont-new.tex
systems : beware: some patches loaded from cont-new.tex
(c:/context/tex/texmf-context/tex/context/base/cont-new.mkiv)
(c:/context/tex/te
xmf-context/tex/context/base/cont-mtx.tex))
system : cont-fil loaded
(c:/context/tex/texmf-context/tex/context/base/cont-fil.tex
loading : ConTeXt File Synonyms
)
system : cont-sys loaded
(c:/context/tex/texmf-context/tex/context/user/cont-sys.tex
(c:/context/tex/texm
f-context/tex/context/base/type-tmf.tex)
(c:/context/tex/texmf-context/tex/conte
xt/base/type-siz.tex
(c:/context/tex/texmf-context/tex/context/base/type-siz.mki
v)) (c:/context/tex/texmf-context/tex/context/base/type-otf.tex
(c:/context/tex/
texmf-context/tex/context/base/type-otf.mkiv))
system : module plus loaded
(c:/context/tex/texmf-context/tex/context/base/m-plus.tex))
system : vimdemo.top loaded
(vimdemo.top)
specials : pdftex loaded
language : language en is active
color : mpcmyk color space is supported
color : mpspot color space is supported
color : system rgb is global activated
system : module vim loaded
(c:/context/tex/texmf-context/tex/context/third/vim/t-vim.tex
loading : Context Module for ViM Sytax Highlighting
color : system hex is loaded
(c:/context/tex/texmf-context/tex/context/base/colo-hex.tex))
systems : begin file vimdemo at line 5
title : - Matlab Code Listing -- Color
MTXrun | variable SELFAUTOLOC set to c:/context/tex/texmf-mswin/bin
MTXrun | variable SELFAUTODIR set to c:/context/tex/texmf-mswin
MTXrun | variable SELFAUTOPARENT set to c:/context/tex
MTXrun | variable TEXMFCNF set to
c:\context\tex\texmf{-local,-context,}/web2c
MTXrun | loading c
Re: [NTG-context] xhtml form to pdf form?
Thanks. The document is helpful. Now the textfield, radio button, etc. can be translate to fields. But I am not very clear how to collect those fields into a form and assign the form action. I saw the \setupforms command but didn't find any examples to show how to use it. Any hints? Andy. On Thu, Mar 26, 2009 at 7:45 PM, Wolfgang Schuster < schuster.wolfg...@googlemail.com> wrote: > > Am 26.03.2009 um 18:14 schrieb Andy: > > Hello, >> >> I want to know if ConTeXt can convert xhtml form to pdf form? I learned >> some examples in Garden wiki about typesetting html files using ConTeXt. But >> they just translate the form tag to empty. Is there any ConTeXt way to >> handle forms just like the \form commands in latex package hyperref? >> Thanks. >> > > http://articles.contextgarden.net/article/111 > > Wolfgang > > > ___ > 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 ___
