Hello, Hans and Taco (once you're back), http://pub.mojca.org/tex/csv/ has the new version of the documentation for the database module, but it's still a bit buggy. Please forget about "feature requests" at the end of the document, they're there just for the guidelines about what could also be useful. There are still some bugs appearing (problems with UTF were introduced recently); a funny thing is also that if I redefine the font encoding to be EC instead of texnansi (I don't understand why texnansi is used by deafault, but I don't really mind), the resulting characters in "Taco's mode" are different (wrong in both cases anyway). "Hans's mode" doesn't compile if utf-8 characters are present. The following definition has to be fixed: \def\setupseparatedlist {\dodoubleempty\dosetupseparatedlist} \def\dosetupseparatedlist[#1][#2]% {\getparameters[\??ls#1][#2]} And if you manage to figure out what's going wrong with \showsetups{startseparatedlistname} \showsetups{processseparatedfile} and with the very last example with TSV, I would be very grateful as well. These are probably my mistakes somewhere, but I don't know where I did a (probably stupid little) mistake. What's the default behaviour with \inmargin inside \placefloat? I guess that that is or should be forbidden, but how can I place something "marginal" next to the float? (I have some other "\marginal" questions, but that's a topic for another mail.) Mojca
Hi Mojca, Mojca Miklavec wrote:
Hello, Hans and Taco (once you're back),
back!
http://pub.mojca.org/tex/csv/ has the new version of the documentation for the database module, but it's still a bit buggy. Please forget about "feature requests" at the end of the document, they're there just for the guidelines about what could also be useful.
First ,a note on the xml loading. these four lines: \usemodule % interface defined in XML [mod-00] \complexloadsetups % syntax definition [m-database.xml] do not work for me (\complexloadsetups is and undefined command). For the bib module docs I have used a hack that goes like this: \usemodule[int-load] % preload \loadsetups command \def\loadsetups{} % disable loading cont-en.xml \usemodule[mod-01] \startXMLmapping[zero] \processXMLfilegrouped{t-bib.xml} \stopXMLmapping It seems this part of the core needs a minor extension to make it easier to document modules (but it may be that you have that already :))
There are still some bugs appearing (problems with UTF were introduced recently); a funny thing is also that if I redefine the font encoding to be EC instead of texnansi (I don't understand why texnansi is used by deafault, but I don't really mind), the resulting characters in "Taco's mode" are different (wrong in both cases anyway). "Hans's mode" doesn't compile if utf-8 characters are present.
In "my mode", this is because of the \convertargument. Hans, is there an easy way that I can detokenize only the characters < 128 ?
The following definition has to be fixed:
\def\dosetupseparatedlist[#1][#2]% {\getparameters[\??ls#1][#2]}
I've fixed my local version as well
And if you manage to figure out what's going wrong with \showsetups{startseparatedlistname}
This one should be defined as:
\showsetups{processseparatedfile}
Use the singular: \showsetup
and with the very last example with TSV, I would be very grateful as
You have a missing comma after the 'last=' entry. Cheers, Taco
\usemodule % interface defined in XML [mod-00] \complexloadsetups % syntax definition [m-database.xml]
do not work for me (\complexloadsetups is and undefined command).
Which version of ConTeXt? from x-set-11.tex: \def\complexloadsetups[#1]% {\startXMLmapping[zero] \processXMLfilegrouped{#1} \stopXMLmapping} or from Hans's email (I just wanted to tell you that you might probably want to use the same command for documenting your module): \def\loadsetups{\complexorsimple\loadsetups} \def\simpleloadsetups {\complexloadsetups[cont-en.xml]} \def\complexloadsetups[#1]% {\startXMLmapping[zero] \processXMLfilegrouped{#1} \stopXMLmapping} and you can use \loadsetups[m-database.xml]
For the bib module docs I have used a hack that goes like this:
\usemodule[int-load] % preload \loadsetups command \def\loadsetups{} % disable loading cont-en.xml
Thanks for this one! (I just wanted to ask how to prevent lenghty loading of cont-en.) I don't understand why I have to do two other things tow prevent something, but since it's a new functionality anyway: would it by any chance be possible that it would't load the cont-eni.xml by default when using [complex]loadsetups?
\usemodule[mod-01] \startXMLmapping[zero] \processXMLfilegrouped{t-bib.xml} \stopXMLmapping
Apart from loading the first module that should be the same.
It seems this part of the core needs a minor extension to make it easier to document modules (but it may be that you have that already :))
It should be in ConTeXt already.
There are still some bugs appearing (problems with UTF were introduced recently); a funny thing is also that if I redefine the font encoding to be EC instead of texnansi (I don't understand why texnansi is used by deafault, but I don't really mind), the resulting characters in "Taco's mode" are different (wrong in both cases anyway). "Hans's mode" doesn't compile if utf-8 characters are present.
In "my mode", this is because of the \convertargument. Hans, is there an easy way that I can detokenize only the characters < 128 ?
And if you manage to figure out what's going wrong with \showsetups{startseparatedlistname}
This one should be defined as:
Thanks. It might make sense (but also most commands in cont-eni.xml should be fixed then as well - I followed the pattern from there). I still don't get the setups shown, but ...
But somehow \showsetup{separatedlistname} doesn't output anything, so it is not entirely your fault (AFAICS). Maybe typesetting is triggered by the presence of an argument?
\showsetups{processseparatedfile}
Use the singular: \showsetup
Thanks. But no luck either. I'll play a bit more.
and with the very last example with TSV, I would be very grateful as
You have a missing comma after the 'last=' entry.
Thanks. Such a stupid mistake! Mojca
Mojca Miklavec wrote:
\usemodule % interface defined in XML [mod-00] \complexloadsetups % syntax definition [m-database.xml]
do not work for me (\complexloadsetups is and undefined command).
Which version of ConTeXt?
non-beta ;-)
or from Hans's email (I just wanted to tell you that you might probably want to use the same command for documenting your module):
Yes, I will. Much better that way Chees, Taco
On Tue, 11 Jul 2006, Taco Hoekwater wrote:
For the bib module docs I have used a hack that goes like this:
\usemodule[int-load] % preload \loadsetups command \def\loadsetups{} % disable loading cont-en.xml \usemodule[mod-01] \startXMLmapping[zero] \processXMLfilegrouped{t-bib.xml} \stopXMLmapping
It seems this part of the core needs a minor extension to make it easier to document modules (but it may be that you have that already :))
Well, after a suggestion from Mojca, the simplest way seems to the following \usemodule[int-load] %Allow context to parse xml markup \loadsetups[arrows.xml] %Name of the file with xml markup % Get gray backgrounds for setups \setupframedtexts [setuptext] [background=screen, frame=off] Then you can use \setup{command} to show its syntax. \showsetup is just defined as \def\showsetup#1% {{\def\y##1{\writestatus{setups}{warning: remove y! from #1}}% \setup{#1}}} which seems to do some checking for commands that defined twice. For the purpose of documenting modules one can even say \let\showsetup\setup Aditya
Aditya Mahajan wrote:
On Tue, 11 Jul 2006, Taco Hoekwater wrote:
For the bib module docs I have used a hack that goes like this:
\usemodule[int-load] % preload \loadsetups command \def\loadsetups{} % disable loading cont-en.xml \usemodule[mod-01] \startXMLmapping[zero] \processXMLfilegrouped{t-bib.xml} \stopXMLmapping
It seems this part of the core needs a minor extension to make it easier to document modules (but it may be that you have that already :))
Well, after a suggestion from Mojca, the simplest way seems to the following
\usemodule[int-load] %Allow context to parse xml markup \loadsetups[arrows.xml] %Name of the file with xml markup
% Get gray backgrounds for setups \setupframedtexts [setuptext] [background=screen, frame=off]
Then you can use \setup{command} to show its syntax.
\showsetup is just defined as
\def\showsetup#1% {{\def\y##1{\writestatus{setups}{warning: remove y! from #1}}% \setup{#1}}}
which seems to do some checking for commands that defined twice.
For the purpose of documenting modules one can even say
\let\showsetup\setup
i didn;t closely follow this thread ... what exactly is the problem Hans
On Wed, 19 Jul 2006, Hans Hagen wrote:
Aditya Mahajan wrote:
On Tue, 11 Jul 2006, Taco Hoekwater wrote:
For the bib module docs I have used a hack that goes like this:
\usemodule[int-load] % preload \loadsetups command \def\loadsetups{} % disable loading cont-en.xml \usemodule[mod-01] \startXMLmapping[zero] \processXMLfilegrouped{t-bib.xml} \stopXMLmapping
It seems this part of the core needs a minor extension to make it easier to document modules (but it may be that you have that already :))
Well, after a suggestion from Mojca, the simplest way seems to the following
\usemodule[int-load] %Allow context to parse xml markup \loadsetups[arrows.xml] %Name of the file with xml markup
% Get gray backgrounds for setups \setupframedtexts [setuptext] [background=screen, frame=off]
Then you can use \setup{command} to show its syntax.
\showsetup is just defined as
\def\showsetup#1% {{\def\y##1{\writestatus{setups}{warning: remove y! from #1}}% \setup{#1}}}
which seems to do some checking for commands that defined twice.
For the purpose of documenting modules one can even say
\let\showsetup\setup
i didn;t closely follow this thread ... what exactly is the problem
How should one load setup definitions that are not in cont-en.xml? Is this the correct way \usemodule[int-load] \loadsetups[my-defs.xml] \starttext \setup{my-command} \stoptext Aditya
Aditya Mahajan wrote:
On Wed, 19 Jul 2006, Hans Hagen wrote:
Aditya Mahajan wrote:
On Tue, 11 Jul 2006, Taco Hoekwater wrote:
For the bib module docs I have used a hack that goes like this:
\usemodule[int-load] % preload \loadsetups command \def\loadsetups{} % disable loading cont-en.xml \usemodule[mod-01] \startXMLmapping[zero] \processXMLfilegrouped{t-bib.xml} \stopXMLmapping
It seems this part of the core needs a minor extension to make it easier to document modules (but it may be that you have that already :))
Well, after a suggestion from Mojca, the simplest way seems to the following
\usemodule[int-load] %Allow context to parse xml markup \loadsetups[arrows.xml] %Name of the file with xml markup
% Get gray backgrounds for setups \setupframedtexts [setuptext] [background=screen, frame=off]
Then you can use \setup{command} to show its syntax.
\showsetup is just defined as
\def\showsetup#1% {{\def\y##1{\writestatus{setups}{warning: remove y! from #1}}% \setup{#1}}}
which seems to do some checking for commands that defined twice.
For the purpose of documenting modules one can even say
\let\showsetup\setup
i didn;t closely follow this thread ... what exactly is the problem
How should one load setup definitions that are not in cont-en.xml? Is this the correct way
\usemodule[int-load] \loadsetups[my-defs.xml]
\starttext \setup{my-command} \stoptext indeed
-- ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
Hans Hagen wrote:
\usemodule[int-load] %Allow context to parse xml markup \loadsetups[arrows.xml] %Name of the file with xml markup
% Get gray backgrounds for setups \setupframedtexts [setuptext] [background=screen, frame=off]
Then you can use \setup{command} to show its syntax.
\showsetup is just defined as
\def\showsetup#1% {{\def\y##1{\writestatus{setups}{warning: remove y! from #1}}% \setup{#1}}}
which seems to do some checking for commands that defined twice.
For the purpose of documenting modules one can even say
\let\showsetup\setup
i didn;t closely follow this thread ... what exactly is the problem
How should one load setup definitions that are not in cont-en.xml? Is this the correct way
\usemodule[int-load] \loadsetups[my-defs.xml]
\starttext \setup{my-command} \stoptext
indeed
Also, it would be nice if there was a clean way to *not* load cont-en.xml when using mod-00 to document as user module (since loading cont-en is quite slow). The current 'solution' is: \usemodule[int-load] \def\simpleloadsetups{} \usemodule[mod-00] which is certainly not a very nice way. Greetings, Taco
Taco Hoekwater wrote:
Also, it would be nice if there was a clean way to *not* load cont-en.xml when using mod-00 to document as user module (since loading cont-en is quite slow). The current 'solution' is:
\usemodule[int-load] \def\simpleloadsetups{} \usemodule[mod-00]
which is certainly not a very nice way.
maybe something: \def\simpleloadsetups {\doifnotmode{no-setup-main} {\complexloadsetups[cont-en.xml]}} \def\complexloadsetups[#1]% {\doifnotmode{no-setup-all} {\startXMLmapping[zero] \processXMLfilegrouped{#1} \stopXMLmapping}} so that one can run with --mode=no-setup-main ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On 7/19/06, Hans Hagen wrote:
Taco Hoekwater wrote:
Also, it would be nice if there was a clean way to *not* load cont-en.xml when using mod-00 to document as user module (since loading cont-en is quite slow). The current 'solution' is:
\usemodule[int-load] \def\simpleloadsetups{} \usemodule[mod-00]
which is certainly not a very nice way.
maybe something:
\def\simpleloadsetups {\doifnotmode{no-setup-main} {\complexloadsetups[cont-en.xml]}}
\def\complexloadsetups[#1]% {\doifnotmode{no-setup-all} {\startXMLmapping[zero] \processXMLfilegrouped{#1} \stopXMLmapping}}
so that one can run with --mode=no-setup-main
I might be wrong here, but wouldn't it make more sense that one has to load cont-en.xml explicitely rather than having to say explicitely that one doesn't want to load it? Mojca
participants (4)
-
Aditya Mahajan -
Hans Hagen -
Mojca Miklavec -
Taco Hoekwater