On Wed, Feb 12, 2003 at 11:02:52AM +, Angus Leeming wrote:
> Thank you. All is clearer now. Would verbatimItem return '4.5 \columnwidth'
> too?
Yes. It looks for something within balanced braces. Not entirely correct,
but not too far off.
> One more thing: LyX can read all of minipage's opti
On Wednesday 12 February 2003 10:55 am, Andre Poenitz wrote:
> On Wed, Feb 12, 2003 at 10:50:30AM +, Angus Leeming wrote:
> > >> Sure. One question. Would ' - 4,5 cM ' count as one token or two?
> > >
> > > Six. - 4 5 , c M.
> > >
> > > The conversion has to be done on output.
> >
> > ??? Ok.
On Wed, Feb 12, 2003 at 10:50:30AM +, Angus Leeming wrote:
> >> Sure. One question. Would ' - 4,5 cM ' count as one token or two?
> >
> > Six. - 4 5 , c M.
> >
> > The conversion has to be done on output.
>
> ??? Ok. You tokenise and then parse. Fair enough.
But wrong. Tokenization should
Andre Poenitz wrote:
> On Wed, Feb 12, 2003 at 10:06:56AM +, Angus Leeming wrote:
>> > Currently I like the idea of tex2lyx being small and independent very
>> > much.
>>
>> Sure. One question. Would ' - 4,5 cM ' count as one token or two?
>
> Six. - 4 5 , c M.
>
> The conversion has to be
On Wed, Feb 12, 2003 at 10:06:56AM +, Angus Leeming wrote:
> > Currently I like the idea of tex2lyx being small and independent very much.
>
> Sure. One question. Would ' - 4,5 cM ' count as one token or two?
Six. - 4 5 , c M.
The conversion has to be done on output.
Andre'
--
Those who
-BEGIN PGP SIGNED MESSAGE-
On Mittwoch, 12. Februar 2003 10:21, Angus Leeming wrote:
...
>
> $ ./trial ' - 3.5 cM' ' + 4,5 Cm ' ' + 4.5 \columnWidth '
> ' - 3.5 cM' becomes '-3.5cm'
> ' + 4,5 Cm ' becomes '+4.5cm'
> ' + 4.5 \columnWidth ' becomes '+4.5\columnWidth'
You may miss '.3 cm'
>
On Wednesday 12 February 2003 9:40 am, Andre Poenitz wrote:
> On Wed, Feb 12, 2003 at 09:38:06AM +, Angus Leeming wrote:
> > Should I write the equivalent of this as a function for tex2lyx using the
> > boost regex library?
>
> Overkill.
>
> Better use a simple loop over the string than adding
On Wed, Feb 12, 2003 at 11:00:33AM +0100, Jean-Marc Lasgouttes wrote:
> While I agree about being independent from boost, you will have to
> have some dependency on the lyx sources: the parsing of things like
> \section depends on the .layout files, and I do not think it would be
> wise to do a re-
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
Andre> Currently I like the idea of tex2lyx being small and
Andre> independent very much.
While I agree about being independent from boost, you will have to
have some dependency on the lyx sources: the parsing of things like
\section dep
On Wed, Feb 12, 2003 at 09:38:06AM +, Angus Leeming wrote:
> Should I write the equivalent of this as a function for tex2lyx using the
> boost regex library?
Overkill.
Better use a simple loop over the string than adding a dependance on boost
stuff.
Currently I like the idea of tex2lyx bein
On Wednesday 12 February 2003 9:31 am, Andre Poenitz wrote:
> On Wed, Feb 12, 2003 at 09:21:12AM +, Angus Leeming wrote:
> > > And I believe '4.5 Cm' and '4.5 cM' are valid as well...
> >
> > Geeez.
>
> Someone should check it first
That's why I gave you a little program to run, you noodle
On Wed, Feb 12, 2003 at 09:21:12AM +, Angus Leeming wrote:
> > And I believe '4.5 Cm' and '4.5 cM' are valid as well...
>
> Geeez.
Someone should check it first
> Would this suffice do you think?
> $LatexLength =~ s/^\s*([+-]?)\s*(\d+)[.,]?(\d*)\s*/$1$2.$3/;
> # Now ensu
Andre Poenitz wrote:
> On Tue, Feb 11, 2003 at 09:47:13PM +0100, Georg Baum wrote:
>> Am Dienstag, 11. Februar 2003 12:00 schrieb Angus Leeming:
>> > I have a trivial patch to the reLyX minibuffer output:
>> >
>> > * reLyX/BasicLyX.pm: Wrap minipage width and height output in
>> >
On Tue, Feb 11, 2003 at 09:47:13PM +0100, Georg Baum wrote:
> Am Dienstag, 11. Februar 2003 12:00 schrieb Angus Leeming:
> > I have a trivial patch to the reLyX minibuffer output:
> >
> > * reLyX/BasicLyX.pm: Wrap minipage width and height output in
> > inverted commas to keep the L
Am Dienstag, 11. Februar 2003 12:00 schrieb Angus Leeming:
> I have a trivial patch to the reLyX minibuffer output:
>
> * reLyX/BasicLyX.pm: Wrap minipage width and height output in
> inverted commas to keep the LyX parser happy with "4.5 cm".
> (Note the space.)
While you
On Tue, Feb 11, 2003 at 03:02:52PM +0100, Jean-Marc Lasgouttes wrote:
> Andre> Of course, if at one point of time the format has evolved too
> Andre> far, tex2lyx might get an update.
>
> Like reLyX that produces a strange file format with a mix of old
> constructs and new ones...
Not necessarily
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
Andre> But it has certain benefits:
Andre> - No dependence on LyX proper. - Small. - No need to access
Andre> fragile LyX internals.
Indeed. But at least, when the internals change, you know about it
because it does not compile anymore
On Tue, Feb 11, 2003 at 02:46:48PM +0100, Jean-Marc Lasgouttes wrote:
> Andre> The tokenizer should be ok unless someone starts changing
> Andre> catcodes ore redefines macros. The "backend" (i.e. writing the
> Andre> proper .lyx constructs) is far from working, let alone
> Andre> complete...
>
>
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
Andre> The tokenizer should be ok unless someone starts changing
Andre> catcodes ore redefines macros. The "backend" (i.e. writing the
Andre> proper .lyx constructs) is far from working, let alone
Andre> complete...
Are you sure that prod
On Tuesday 11 February 2003 1:21 pm, Lars Gullik Bjønnes wrote:
> Andre Poenitz <[EMAIL PROTECTED]> writes:
> | > $ mkdir src/tex2lyx/.deps
> | > $ touch src/tex2lyx/.deps/tex2lyx.Po
> | >
> | > solves the problem. Should it be generated automatically or cvs added?
>
> No!
>
> That was something wr
Andre Poenitz <[EMAIL PROTECTED]> writes:
| > $ mkdir src/tex2lyx/.deps
| > $ touch src/tex2lyx/.deps/tex2lyx.Po
| >
| > solves the problem. Should it be generated automatically or cvs added?
No!
That was something wrong on your end.
a autogen, re-configure, make distclean etc would have fixed
On Tue, Feb 11, 2003 at 01:12:33PM +, Angus Leeming wrote:
> As JMarc noted yesterday, this approach:
> else if (t.cs() == "usepackage") {
> string const options = getArg('[', ']');
> string const name = getArg('{', '}');
>
On Tue, Feb 11, 2003 at 12:51:24PM +, Angus Leeming wrote:
> I wonder too. However, my motivation has been:
> 1. learn enough perl to feel comfortable when confronted with it.
> 2. LyX 1.3 will be around for at least 6 months.
Currently there is no dependency on LyX in tex2lyx (quite contrary
Andre Poenitz wrote:
> On Tue, Feb 11, 2003 at 11:00:37AM +, Angus Leeming wrote:
>> I have a trivial patch to the reLyX minibuffer output:
>>
>> * reLyX/BasicLyX.pm: Wrap minipage width and height output in
>> inverted commas to keep the LyX parser happy with "4.5 cm".
>>
On Tuesday 11 February 2003 12:39 pm, Andre Poenitz wrote:
> On Tue, Feb 11, 2003 at 11:00:37AM +, Angus Leeming wrote:
> > I have a trivial patch to the reLyX minibuffer output:
> >
> > * reLyX/BasicLyX.pm: Wrap minipage width and height output in
> > inverted commas to keep th
On Tue, Feb 11, 2003 at 11:00:37AM +, Angus Leeming wrote:
> I have a trivial patch to the reLyX minibuffer output:
>
> * reLyX/BasicLyX.pm: Wrap minipage width and height output in
> inverted commas to keep the LyX parser happy with "4.5 cm".
> (Note the space.)
>
> H
I have a trivial patch to the reLyX minibuffer output:
* reLyX/BasicLyX.pm: Wrap minipage width and height output in
inverted commas to keep the LyX parser happy with "4.5 cm".
(Note the space.)
However, I wonder whether I should do this or whether I should strip out the
27 matches
Mail list logo
