* Re: typeseting XML [not found] <Pine.BSF.3.96.1010515225104.2197B-100000@vertigo.fme.vutbr .cz> @ 2001-05-18 14:10 ` Hans Hagen 2001-05-18 16:15 ` Petr Ferdus [not found] ` <Pine.BSF.3.96.1010518180453.16005F-100000@vertigo.fme.vutb r.cz> 0 siblings, 2 replies; 20+ messages in thread From: Hans Hagen @ 2001-05-18 14:10 UTC (permalink / raw) Cc: ntg-context At 01:54 AM 5/17/01 +0200, Petr Ferdus wrote: >Hi, >how could be typeset backslash character parsed from XML stream? <...>bla \bla bla<...> should work ok >I tryed: > >\defineXMLsingular [backslash] {$\backslash$} > >having in XML doc an empty element <backslash/>, with no success (no >error either, it was just silently discarded). \defineXMLsingular [backslash] {\tex{}} i still need to add named chars for backslash and so. >Also, would it be possible to have # char in the name of XML entity? Like: > >\defineXMLentity [#937] {$\Omega$} %instead of >\defineXMLentity [937] {$\Omega$} > >because it seems to be rather conforming to naming convention of entities >based on unicode position of its glyph (Ω in this case). that's being worked on [for that taco and i need to have the math unicode part finished] Hans ------------------------------------------------------------------------- Hans Hagen | PRAGMA ADE | pragma@wxs.nl Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com ------------------------------------------------------------------------- ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: typeseting XML 2001-05-18 14:10 ` typeseting XML Hans Hagen @ 2001-05-18 16:15 ` Petr Ferdus [not found] ` <Pine.BSF.3.96.1010518180453.16005F-100000@vertigo.fme.vutb r.cz> 1 sibling, 0 replies; 20+ messages in thread From: Petr Ferdus @ 2001-05-18 16:15 UTC (permalink / raw) Cc: ntg-context On Fri, 18 May 2001, Hans Hagen wrote: > <...>bla \bla bla<...> should work ok It did not worked (and for some reason still doesn't) in my setup (source documents encoded in win1250), so I decided to contvert those characters which didn't show to singular elements. This way I get them in output. Peter ^ permalink raw reply [flat|nested] 20+ messages in thread
[parent not found: <Pine.BSF.3.96.1010518180453.16005F-100000@vertigo.fme.vutb r.cz>]
* Re: typeseting XML [not found] ` <Pine.BSF.3.96.1010518180453.16005F-100000@vertigo.fme.vutb r.cz> @ 2001-05-18 16:53 ` Hans Hagen 0 siblings, 0 replies; 20+ messages in thread From: Hans Hagen @ 2001-05-18 16:53 UTC (permalink / raw) Cc: ntg-context At 06:15 PM 5/18/01 +0200, you wrote: >On Fri, 18 May 2001, Hans Hagen wrote: > >> <...>bla \bla bla<...> should work ok > >It did not worked (and for some reason still doesn't) in my setup (source >documents encoded in win1250), so I decided to contvert those characters >which didn't show to singular elements. This way I get them in output. i'm working on a simple perl xml-cleanup thing Hans ------------------------------------------------------------------------- Hans Hagen | PRAGMA ADE | pragma@wxs.nl Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com ------------------------------------------------------------------------- ^ permalink raw reply [flat|nested] 20+ messages in thread
[parent not found: <3.0.6.32.20010525212835.0127d390@server-1>]
[parent not found: <Pine.BSF.3.96.1010529101027.14223A-100000@vertigo.fme.vutb r.cz>]
* Re: typeseting XML [not found] ` <Pine.BSF.3.96.1010529101027.14223A-100000@vertigo.fme.vutb r.cz> @ 2001-05-29 9:45 ` Hans Hagen 2001-05-29 14:05 ` Petr Ferdus ` (3 more replies) 0 siblings, 4 replies; 20+ messages in thread From: Hans Hagen @ 2001-05-29 9:45 UTC (permalink / raw) Cc: ntg-context At 10:27 AM 5/29/01 +0200, Petr Ferdus wrote: >How to make \XMLerase to work? In construction like: >\defineXMLenvironment[pprikazy] > {\bgroup > \defineXMLpush[pprikazy] > \XMLerase {pprikazy}}%first part end > > {%\defXMLstring \GCislo {pprikazy} > \egroup}%second part end > >one could (at least I did) expect to get rid of whatever stays between ><pprikazy></pprikazy> tags. Not the case. It gets happily typeset to >ouput. Would be nice no know the way, how to prevent printing same >elements and still have it somehow available (that what I thought would >\defXMLstring accomplish) (\XMLignore works, but the element is gone) Can you give an small example; do you use pprikazy nested? If so, then you need the grouped approach. or play with \xdef\GCislo{\XMLpop{pprikazy} and alike Hans ------------------------------------------------------------------------- Hans Hagen | PRAGMA ADE | pragma@wxs.nl Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com ------------------------------------------------------------------------- ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: typeseting XML 2001-05-29 9:45 ` Hans Hagen @ 2001-05-29 14:05 ` Petr Ferdus 2001-05-30 15:01 ` Petr Ferdus ` (2 subsequent siblings) 3 siblings, 0 replies; 20+ messages in thread From: Petr Ferdus @ 2001-05-29 14:05 UTC (permalink / raw) Cc: ntg-context [-- Attachment #1: Type: TEXT/PLAIN, Size: 364 bytes --] On Tue, 29 May 2001, Hans Hagen wrote: > Can you give an small example; do you use pprikazy nested? If so, then you > need the grouped approach. > > or play with \xdef\GCislo{\XMLpop{pprikazy} and alike This element is not nested. But knowing how to solve nested case wouldn't hurt. Attached is a small example, with tiny XML source and resulting pdf. Peter [-- Attachment #2: Type: APPLICATION/ZIP, Size: 13166 bytes --] ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: typeseting XML 2001-05-29 9:45 ` Hans Hagen 2001-05-29 14:05 ` Petr Ferdus @ 2001-05-30 15:01 ` Petr Ferdus [not found] ` <Pine.BSF.3.96.1010529153914.15436A-101000@vertigo.fme.vutb r.cz> [not found] ` <Pine.BSF.3.96.1010530154343.20742A-101000@vertigo.fme.vutb r.cz> 3 siblings, 0 replies; 20+ messages in thread From: Petr Ferdus @ 2001-05-30 15:01 UTC (permalink / raw) Cc: ntg-context [-- Attachment #1: Type: TEXT/PLAIN, Size: 743 bytes --] Hi, In this example are processed data comming from XML source file. It typesets it mostly(1) in correct manner except processing lists (predefined or user defined). In that case "raw" XML stream is used, which inflicts with further processing of lists. (1)also if there is an entity at the beginning of element passed by argument (example in XML data). It is possible to persuade context to process lists in way, it processes text, so the expanded text would show up correctly, and all entities and singular elements would not bother processing and the links get resolved correctly? What should be done for it? Many thanks in advance. Peter Attached: gtest.tex - test file gtest__.xml - XML data source gtest.pdf - resulting pdf file [-- Attachment #2: Type: APPLICATION/ZIP, Size: 16777 bytes --] ^ permalink raw reply [flat|nested] 20+ messages in thread
[parent not found: <Pine.BSF.3.96.1010529153914.15436A-101000@vertigo.fme.vutb r.cz>]
* Re: typeseting XML [not found] ` <Pine.BSF.3.96.1010529153914.15436A-101000@vertigo.fme.vutb r.cz> @ 2001-05-30 15:09 ` Hans Hagen 2001-05-30 20:12 ` Petr Ferdus ` (2 more replies) 0 siblings, 3 replies; 20+ messages in thread From: Hans Hagen @ 2001-05-30 15:09 UTC (permalink / raw) Cc: ntg-context At 04:05 PM 5/29/01 +0200, Petr Ferdus wrote: >On Tue, 29 May 2001, Hans Hagen wrote: >> Can you give an small example; do you use pprikazy nested? If so, then you >> need the grouped approach. >> >> or play with \xdef\GCislo{\XMLpop{pprikazy} and alike > >This element is not nested. But knowing how to solve nested case wouldn't >hurt. i come back to that later. \defineXMLenvironment [table] \bTABLE \eTABLE \defineXMLnested [tr] \bTR \eTR \defineXMLnested [td] \bTD \eTD does the nesting, pretty dirty code btw Hans ------------------------------------------------------------------------- Hans Hagen | PRAGMA ADE | pragma@wxs.nl Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com ------------------------------------------------------------------------- ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: typeseting XML 2001-05-30 15:09 ` Hans Hagen @ 2001-05-30 20:12 ` Petr Ferdus 2001-06-14 23:07 ` Petr Ferdus [not found] ` <Pine.BSF.3.96.1010615004606.12697C-100000@vertigo.fme.vutb r.cz> 2 siblings, 0 replies; 20+ messages in thread From: Petr Ferdus @ 2001-05-30 20:12 UTC (permalink / raw) Cc: ntg-context On Wed, 30 May 2001, Hans Hagen wrote: > > \defineXMLenvironment [table] \bTABLE \eTABLE > \defineXMLnested [tr] \bTR \eTR > \defineXMLnested [td] \bTD \eTD > > does the nesting, pretty dirty code btw Thanks, it is as an example in "example" manual. It solves tables quite nicely. % Would be great to be able get some parameters as well. % What makes next code fragment misbehave? (it doesn't place % border aroud table, remapping \mapXMLvalue seems not to work) %--interface=en --output=pdf --translate-file=cp1250cs %% to run: texexec gtest2.tex %tables \defineXMLenvironment [table] { %\bgroup \mapXMLvalue{table}{border}{0}{off} \mapXMLvalue{table}{border}{1}{on} XMLpar:\XMLpar{table}{border}{aaa}:\par XMLvar:\XMLvar{table}{border}{bbb}:\par XMLval:\XMLval{table}{border}{ccc}:\par %\bTABLE[frame=on] \bTABLE[frame={\XMLvar{table}{border}{ddd}}] %\egroup } {\eTABLE }% \defineXMLnested [tr] \bTR \eTR \defineXMLnested [td] \bTD \eTD \starttext some text \enableXML <table border='1' cellspacing='0' cellpadding='0'> <tr> <td valign='top'> <pMsoNormal>19.30 </pMsoNormal> </td> <td valign='top'> <pMsoNormal>dinner</pMsoNormal> </td> </tr> <tr> <td valign='top'> <pMsoNormal>20.00 </pMsoNormal> </td> <td valign='top'> <pMsoNormal>sight-seeing</pMsoNormal> </td> </tr> </table> <?context-command \stoptext ?> Peter ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: typeseting XML 2001-05-30 15:09 ` Hans Hagen 2001-05-30 20:12 ` Petr Ferdus @ 2001-06-14 23:07 ` Petr Ferdus [not found] ` <Pine.BSF.3.96.1010615004606.12697C-100000@vertigo.fme.vutb r.cz> 2 siblings, 0 replies; 20+ messages in thread From: Petr Ferdus @ 2001-06-14 23:07 UTC (permalink / raw) Cc: ntg-context Is it already possible to break natural tables on page boundaries? After some tries (being appetized by natural table manual), I have found remark in core-ntb which says that break over page is on TODO list. Is there any progress in this area or what would be the options with XML processing? Would be very appreciated. Thank you. Peter ^ permalink raw reply [flat|nested] 20+ messages in thread
[parent not found: <Pine.BSF.3.96.1010615004606.12697C-100000@vertigo.fme.vutb r.cz>]
* Re: typeseting XML [not found] ` <Pine.BSF.3.96.1010615004606.12697C-100000@vertigo.fme.vutb r.cz> @ 2001-06-15 8:09 ` Hans Hagen 0 siblings, 0 replies; 20+ messages in thread From: Hans Hagen @ 2001-06-15 8:09 UTC (permalink / raw) Cc: ntg-context At 01:07 AM 6/15/01 +0200, Petr Ferdus wrote: >Is it already possible to break natural tables on page boundaries? After >some tries (being appetized by natural table manual), I have found remark >in core-ntb which says that break over page is on TODO list. >Is there any progress in this area or what would be the options with XML >processing? still on the todo list Hans ------------------------------------------------------------------------- Hans Hagen | PRAGMA ADE | pragma@wxs.nl Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com ------------------------------------------------------------------------- ^ permalink raw reply [flat|nested] 20+ messages in thread
[parent not found: <Pine.BSF.3.96.1010530154343.20742A-101000@vertigo.fme.vutb r.cz>]
* Re: typeseting XML [not found] ` <Pine.BSF.3.96.1010530154343.20742A-101000@vertigo.fme.vutb r.cz> @ 2001-05-31 9:12 ` Hans Hagen 2001-06-01 8:03 ` Petr Ferdus [not found] ` <Pine.BSF.3.96.1010601083337.29526A-100000@vertigo.fme.vutb r.cz> 0 siblings, 2 replies; 20+ messages in thread From: Hans Hagen @ 2001-05-31 9:12 UTC (permalink / raw) Cc: ntg-context At 05:01 PM 5/30/01 +0200, Petr Ferdus wrote: >Hi, >In this example are processed data comming from XML source >file. It typesets it mostly(1) in correct manner except processing >lists (predefined or user defined). In that case "raw" XML >stream is used, which inflicts with further processing of lists. That will be handled automatically later, when i've added status info to the tui/tuo files. \appendtoks \enableXMLelements \to \everyreadfile % test hack will work for now, given that you use a recent version. >(1)also if there is an entity at the beginning of element passed >by argument (example in XML data). dontknow/dontsee, anyway i'll send you the latest xtag files [there is also a new \defineXMLenv..push one you may want to use] > It is possible to persuade context to process lists in way, it >processes text, so the expanded text would show up correctly, and >all entities and singular elements would not bother processing >and the links get resolved correctly? What should be done for it? try: \setuplist[whatever][expansion=yes] ------------------------------------------------------------------------- Hans Hagen | PRAGMA ADE | pragma@wxs.nl Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com ------------------------------------------------------------------------- ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: typeseting XML 2001-05-31 9:12 ` Hans Hagen @ 2001-06-01 8:03 ` Petr Ferdus [not found] ` <Pine.BSF.3.96.1010601083337.29526A-100000@vertigo.fme.vutb r.cz> 1 sibling, 0 replies; 20+ messages in thread From: Petr Ferdus @ 2001-06-01 8:03 UTC (permalink / raw) Cc: ntg-context On Thu, 31 May 2001, Hans Hagen wrote: > >(1)also if there is an entity at the beginning of element passed > >by argument (example in XML data). > > dontknow/dontsee, anyway i'll send you the latest xtag files [there is also > a new \defineXMLenv..push one you may want to use] Right placement of \appendtoks ... sequence with expansion of list makes them nicely expand. Thank you very much. Unafected remains only case (1) than means, if one line of XML data in gtest example would look like: <h2>&Title H2 with any entity an the very beginning of it</h2> which is processed by some macro e.g.: \long\def\MySection#1{\section{#1}}% which could do more, would it had % chance and declared as: \defineXMLargument [h2] {\MySection} it produces "! Incomplete \ifnum; error. ..." (data from elements, which have no macros hooked to their processing, do process correctly) Thanks Peter ^ permalink raw reply [flat|nested] 20+ messages in thread
[parent not found: <Pine.BSF.3.96.1010601083337.29526A-100000@vertigo.fme.vutb r.cz>]
* Re: typeseting XML [not found] ` <Pine.BSF.3.96.1010601083337.29526A-100000@vertigo.fme.vutb r.cz> @ 2001-06-04 9:55 ` Hans Hagen 2001-06-06 4:47 ` Petr Ferdus 0 siblings, 1 reply; 20+ messages in thread From: Hans Hagen @ 2001-06-04 9:55 UTC (permalink / raw) Cc: ntg-context At 10:03 AM 6/1/01 +0200, Petr Ferdus wrote: >On Thu, 31 May 2001, Hans Hagen wrote: > >> >(1)also if there is an entity at the beginning of element passed >> >by argument (example in XML data). >> >> dontknow/dontsee, anyway i'll send you the latest xtag files [there is also >> a new \defineXMLenv..push one you may want to use] > >Right placement of \appendtoks ... sequence with expansion of >list makes them nicely expand. Thank you very much. > >Unafected remains only case (1) than means, if one line of XML data in >gtest example would look like: ><h2>&Title H2 with any entity an the very beginning of it</h2> > >which is processed by some macro e.g.: >\long\def\MySection#1{\section{#1}}% which could do more, would it had > % chance >and declared as: >\defineXMLargument [h2] {\MySection} > >it produces "! Incomplete \ifnum; error. ..." > >(data from elements, which have no macros hooked to their processing, do >process correctly) well, define own macros as \unexpanded\def\blabla{ some \rubish\ commands } also, use \definehead[MySection][section] and try \setuphead[MySection][expansion=yes|command|no] Hans ------------------------------------------------------------------------- Hans Hagen | PRAGMA ADE | pragma@wxs.nl Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com ------------------------------------------------------------------------- ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: typeseting XML 2001-06-04 9:55 ` Hans Hagen @ 2001-06-06 4:47 ` Petr Ferdus 0 siblings, 0 replies; 20+ messages in thread From: Petr Ferdus @ 2001-06-06 4:47 UTC (permalink / raw) Cc: ntg-context On Mon, 4 Jun 2001, Hans Hagen wrote: > well, define own macros as > > \unexpanded\def\blabla{ some \rubish\ commands } > > also, use > > \definehead[MySection][section] > > and try > > \setuphead[MySection][expansion=yes|command|no] Haven't had much success with this. For now I am changing source data (just three occurences in text), hoping to tackle it later. Peter ^ permalink raw reply [flat|nested] 20+ messages in thread
* typeseting XML @ 2001-05-16 23:54 Petr Ferdus 2002-02-03 19:51 ` Johannes Hüsing 0 siblings, 1 reply; 20+ messages in thread From: Petr Ferdus @ 2001-05-16 23:54 UTC (permalink / raw) Hi, how could be typeset backslash character parsed from XML stream? I tryed: \defineXMLsingular [backslash] {$\backslash$} having in XML doc an empty element <backslash/>, with no success (no error either, it was just silently discarded). Also, would it be possible to have # char in the name of XML entity? Like: \defineXMLentity [#937] {$\Omega$} %instead of \defineXMLentity [937] {$\Omega$} because it seems to be rather conforming to naming convention of entities based on unicode position of its glyph (Ω in this case). Thanks very much. Petr Ferdus ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: typeseting XML 2001-05-16 23:54 Petr Ferdus @ 2002-02-03 19:51 ` Johannes Hüsing 2002-02-05 8:26 ` Hans Hagen 0 siblings, 1 reply; 20+ messages in thread From: Johannes Hüsing @ 2002-02-03 19:51 UTC (permalink / raw) Hi all, coming across a problem with encoding I searched my private mailing list archive and found this question: On Thu, May 17, 2001 at 01:54:54AM +0200, Petr Ferdus wrote: [...] > Also, would it be possible to have # char in the name of XML entity? Like: > > \defineXMLentity [#937] {$\Omega$} %instead of > \defineXMLentity [937] {$\Omega$} > > because it seems to be rather conforming to naming convention of entities > based on unicode position of its glyph (Ω in this case). > That would be a feature I would value very much. Has this been accomplished already? I see ConTeXt in a quite confused state about the hash sign when I try the above. Greetings Johannes -- Johannes Hüsing There is something fascinating about science. One gets hannes@ruhrau.de such wholesale returns of conjecture from such a trifling investment of fact. Mark Twain ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: typeseting XML 2002-02-03 19:51 ` Johannes Hüsing @ 2002-02-05 8:26 ` Hans Hagen 2002-02-05 13:20 ` Taco Hoekwater 0 siblings, 1 reply; 20+ messages in thread From: Hans Hagen @ 2002-02-05 8:26 UTC (permalink / raw) Cc: ntg-context At 08:51 PM 2/3/2002 +0100, Johannes Hüsing wrote: >Hi all, > >coming across a problem with encoding I searched my private >mailing list archive and found this question: > >On Thu, May 17, 2001 at 01:54:54AM +0200, Petr Ferdus wrote: >[...] > > Also, would it be possible to have # char in the name of XML entity? Like: > > > > \defineXMLentity [#937] {$\Omega$} %instead of > > \defineXMLentity [937] {$\Omega$} > > > > because it seems to be rather conforming to naming convention of entities > > based on unicode position of its glyph (Ω in this case). > > > >That would be a feature I would value very much. Has this been accomplished >already? I see ConTeXt in a quite confused state about the hash sign when >I try the above. hashes are very special to tex, and once they end up in macro bodies they spontaniously replicate etc etc i even think (but taco should confirm that) that once the # is in the line buffer, there is no way to get rid of the # message Hans ------------------------------------------------------------------------- Hans Hagen | PRAGMA ADE | pragma@wxs.nl Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com ------------------------------------------------------------------------- fall-back web server: www.pragma-pod.nl ------------------------------------------------------------------------- ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: typeseting XML 2002-02-05 8:26 ` Hans Hagen @ 2002-02-05 13:20 ` Taco Hoekwater 2002-02-05 13:57 ` Hans Hagen 2002-02-05 21:40 ` Johannes Hüsing 0 siblings, 2 replies; 20+ messages in thread From: Taco Hoekwater @ 2002-02-05 13:20 UTC (permalink / raw) Cc: johannes.huesing, ntg-context Hi Hans, Hashes are very weird things, true. But the problem shouldn't occur. ConTeXt should insert a hashmark behind the scenes as soon as it discovers that the entity starts with a '9', or balk with an error message about an invalid entity. Entities that do not start with # are named entities, as opposed to character references. And names are not allowed to start with a number. Therefore, "&937;" is not valid XM. "Ω" is the correct way. Allowed alternative notations are "Ω" and "Ω". All may have any number of leading zeroes, and the XML spec also states that the character referenced itself should be a valid XML character (so � is also illegal) It would be much cleaner if there was a new command \defineXMLchar, that takes a number as argument instead of a csname string. Then the Context XML parser could have support for all of the possible inputs. Greetings, Taco On Tue, 05 Feb 2002 09:26:13 +0100 "Hans Hagen" <pragma@wxs.nl> wrote: > hashes are very special to tex, and once they end up in macro bodies they > spontaniously replicate etc etc -- groeten, Taco ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: typeseting XML 2002-02-05 13:20 ` Taco Hoekwater @ 2002-02-05 13:57 ` Hans Hagen 2002-02-05 21:40 ` Johannes Hüsing 1 sibling, 0 replies; 20+ messages in thread From: Hans Hagen @ 2002-02-05 13:57 UTC (permalink / raw) Cc: johannes.huesing, ntg-context At 02:20 PM 2/5/2002 +0100, Taco Hoekwater wrote: >Hashes are very weird things, true. But the problem shouldn't occur. indeed, so Taco (and other tex-hackers), how about this: \unprotected \def\bla{\bgroup\catcode`\#=\@@ignore\dobla} \def\dobla[#1]{\egroup\dorecurse{#1}{hello }} \bla[#123] \unprotected \def\bla{\bgroup\catcode`\#=\@@space\dobla} \def\dobla[#1]{\egroup\dorecurse{#1}{hello }} \bla[#123] > ..... ok, i will look into that later (error messages/recovery and such, since i have to look into chars anyway). Hans ------------------------------------------------------------------------- Hans Hagen | PRAGMA ADE | pragma@wxs.nl Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com ------------------------------------------------------------------------- fall-back web server: www.pragma-pod.nl ------------------------------------------------------------------------- ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: typeseting XML 2002-02-05 13:20 ` Taco Hoekwater 2002-02-05 13:57 ` Hans Hagen @ 2002-02-05 21:40 ` Johannes Hüsing 1 sibling, 0 replies; 20+ messages in thread From: Johannes Hüsing @ 2002-02-05 21:40 UTC (permalink / raw) On Tue, Feb 05, 2002 at 02:20:28PM +0100, Taco Hoekwater wrote: > Therefore, "&937;" is not valid XM. "Ω" is the correct way. ok, so for the moment I could just filter out all hash signs of my XML source and I'll be fine. > > Allowed alternative notations are "Ω" and "Ω". Yes, and I used hex codes and wrote a small emacs function that replaced it by single chars, but after Perl's XML::DOM parsed it they were turned into decimals :-( Thanks very much Johannes -- Johannes Hüsing There is something fascinating about science. One gets hannes@ruhrau.de such wholesale returns of conjecture from such a trifling investment of fact. Mark Twain ^ permalink raw reply [flat|nested] 20+ messages in thread
end of thread, other threads:[~2002-02-05 21:40 UTC | newest] Thread overview: 20+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [not found] <Pine.BSF.3.96.1010515225104.2197B-100000@vertigo.fme.vutbr .cz> 2001-05-18 14:10 ` typeseting XML Hans Hagen 2001-05-18 16:15 ` Petr Ferdus [not found] ` <Pine.BSF.3.96.1010518180453.16005F-100000@vertigo.fme.vutb r.cz> 2001-05-18 16:53 ` Hans Hagen [not found] <3.0.6.32.20010525212835.0127d390@server-1> [not found] ` <Pine.BSF.3.96.1010529101027.14223A-100000@vertigo.fme.vutb r.cz> 2001-05-29 9:45 ` Hans Hagen 2001-05-29 14:05 ` Petr Ferdus 2001-05-30 15:01 ` Petr Ferdus [not found] ` <Pine.BSF.3.96.1010529153914.15436A-101000@vertigo.fme.vutb r.cz> 2001-05-30 15:09 ` Hans Hagen 2001-05-30 20:12 ` Petr Ferdus 2001-06-14 23:07 ` Petr Ferdus [not found] ` <Pine.BSF.3.96.1010615004606.12697C-100000@vertigo.fme.vutb r.cz> 2001-06-15 8:09 ` Hans Hagen [not found] ` <Pine.BSF.3.96.1010530154343.20742A-101000@vertigo.fme.vutb r.cz> 2001-05-31 9:12 ` Hans Hagen 2001-06-01 8:03 ` Petr Ferdus [not found] ` <Pine.BSF.3.96.1010601083337.29526A-100000@vertigo.fme.vutb r.cz> 2001-06-04 9:55 ` Hans Hagen 2001-06-06 4:47 ` Petr Ferdus 2001-05-16 23:54 Petr Ferdus 2002-02-03 19:51 ` Johannes Hüsing 2002-02-05 8:26 ` Hans Hagen 2002-02-05 13:20 ` Taco Hoekwater 2002-02-05 13:57 ` Hans Hagen 2002-02-05 21:40 ` Johannes Hüsing
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).