Next Meeting: July 2: Social Gathering Next Installfest: Saturday, January 26th Latest News: Mar. 22: Slides from "Making Predictions Using Linux and R" talk Page last updated: 2001 Dec 30 17:08
Re: [vox-tech] Another TeX question

# Re: [vox-tech] Another TeX question

bill, some commands have "moving arguments", meaning that the arguments get
changed around in various parts of the file.  i think tables are included in
this list.  you need to protect "fragile" commands from getting
discombobulated.

try putting \protect in front of your call to barcode.  see if that helps.

let me know if it works, because i'm curious myself.

peter

begin: William Kendrick <nbs@sonic.net> quote
> I was working on a chunk of Latex to be parsed by Template-Toolkit
> to build code39 barcodes.  Someone at my work pointed out a TeX macro
> which does the job (more easily, and I'm assuming it's been tested and
> is accurate :) )
>
> It works like so:
>
>   \begincodethirtynine{TEXT TO TURN TO BARCODE}\endcodethirtynine
>
>
> Is there any reason anyone can think of why having the above inside a
> tabular table would cause the "TEXT TO..." to actually appear as plaintext
> versus being encoded into barcodes?
>
> In other words, when I throw the above somewhere in the Latex code that
> isn't in the table, it comes out fine:
>
>
>  || || | || | ||| ||| |||  ||| ||  || ||
>
>
> But when it's in the table, it looks like this:
>
>
>  || | TEXT TO TURN TO BARCODE || |
>
> (The barcodes on the left/right are the required starting/stopping codes,
> which the TeX macro is somehow getting to appear just fine)
>
>
> Here's a snippet:
>
>   \begin{tabular*}{3.25in}[t]{|llll|r@{:}}%
>   ...
>   \multicolumn{4}{|l|}{\begincodethirtynine{ TEST }\endcodethirtynine}&\\%
>   ...
>   \end{tabular*}%
>
>
>
> Thx for any tips!
>
> -bill!

--