headers
Lars Gullik Bjønnes | 1 Mar 2004 09:07

Re: fixes for lyx-1.3.4 on OpenBSD

larsbj <at> gullik.net (Lars Gullik Bjønnes) writes:

| Angus Leeming <leeming <at> lyx.org> writes:
>
| | Zvezdan Petkovic wrote:
>>
>>> Hello everybody,
>>> 
>>> I've built a port of lyx-1.3.4 for OpenBSD.
>>> Here are the fixes I had to apply.
>>
>>> 3. I had to patch boost platform specific file.  It makes a wrong
>>>    assumption that all BSDs have macro based <ctype.h>.  Patch is
>>>    attached below.
>>
| | Lars, can I leave this one to you?
>
| Yes.

In my folly I reported this to the boost list... but that macro is not
used anymore, so this is a 1.3.4 fix only.

Jean-Marc, I guess you should put it in for 1.3.5.

--

-- 
	Lgb
Permalink | Reply | 0 comments |
headers
Lars Gullik Bjønnes | 1 Mar 2004 09:13

Re: [patch] encapsulate a font optimization

Alfredo Braunstein <abraunst <at> lyx.org> writes:

| Lars Gullik Bjønnes wrote:
>
>> It looks like this is supposed to be a forward_iterator?
>
| Attached a second version... It aditionally fixes now a (it seems
| long-standing) rebreaking bug that shows f.ex. in multiline paragraphs in
| the Description layout (see for instance UG, section 3.1.2 with current
| cvs, Amsart or Amsbook items).
>
| [About std::iterator... I've read a bit and it seems we are pretty much
| stuck with output iterators for now? forward_iterator's operator* must give
| a (non-const) reference]

You should still inherit from std::iterator so that more stl/std
algorighmts can be used with this iterator.

And IMHO operator-> should be implemented.

--

-- 
	Lgb
Permalink | Reply | 5 comments |
headers
Guru - | 1 Mar 2004 09:43
Picon
Favicon

script to copy each description section from a lyx document and output in order

Hi everyone,

Please note that I'm not subscribed to the list so please CC me replies if 
there are any.

The purpose of this script would be to create a summary of the GNU/Linux 
tools summary, ie. an alphabetical list with the name and then 1line (or 
2line) descriptions of each command, a user could then go to the relevant 
section about that command....
The document is obviously setup so this can happen

Does anyone know of a simple way to copy/move the description style with the 
LyX file?

I've being working on a script that will go through the LyX file, take out 
each area which is of type Description and store it somewhere. (Its a little 
more complicated then this, see below).

It will then sort all the descriptions and output a file with them in 
alphabetical order.

Does anyone know an easy way to do this? I've currently being creating a 
script in Python to do this but its quite buggy and I've still got a lot of 
work to do on it....

The rough description is:
Find each of type description in the LyX file, copy the information from 
that point until we reach a point where their is:
a) increase of depth (embedded).
b) another thing of type description.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Alfredo Braunstein | 1 Mar 2004 10:03
Favicon

Re: [patch] encapsulate a font optimization

Lars Gullik Bjønnes wrote:

> Alfredo Braunstein <abraunst <at> lyx.org> writes:
> 
> | Lars Gullik Bjønnes wrote:
>>
>>> It looks like this is supposed to be a forward_iterator?
>>
> | Attached a second version... It aditionally fixes now a (it seems
> | long-standing) rebreaking bug that shows f.ex. in multiline paragraphs
> | in the Description layout (see for instance UG, section 3.1.2 with
> | current cvs, Amsart or Amsbook items).
>>
> | [About std::iterator... I've read a bit and it seems we are pretty much
> | stuck with output iterators for now? forward_iterator's operator* must
> | give a (non-const) reference]
> 
> You should still inherit from std::iterator so that more stl/std
> algorighmts can be used with this iterator.

Done.

> And IMHO operator-> should be implemented.

Done (are you sure it's a requirement?).

Result attached. Ok to go in?

Alfredo
(Continue reading)

Permalink | Reply | 4 comments |
headers
Jose' Matos | 1 Mar 2004 10:26
Picon
Favicon

Re: script to copy each description section from a lyx document and output in order

On Monday 01 March 2004 08:43, Guru - wrote:
> Hi everyone,
>
> Please note that I'm not subscribed to the list so please CC me replies
> if there are any.
>
> The purpose of this script would be to create a summary of the GNU/Linux
> tools summary, ie. an alphabetical list with the name and then 1line (or
> 2line) descriptions of each command, a user could then go to the relevant
> section about that command....
> The document is obviously setup so this can happen

  [...]

> Currently the scripts get some of it right, I'm just double checking that
> no one has done this before....

  Not sure if that is what you want but since you are using a python script 
you can use the parser tools that comes with the lyx2lyx component of lyx.

  That will help with some of your requests.

--

-- 
José Abílio

LyX and docbook, a perfect match. :-)
Permalink | Reply | 0 comments |
headers
Lars Gullik Bjønnes | 1 Mar 2004 10:56

Re: [patch] encapsulate a font optimization

Alfredo Braunstein <abraunst <at> lyx.org> writes:

>> And IMHO operator-> should be implemented.
>
| Done (are you sure it's a requirement?).

Perhaps not... but then you can use fit->method instead of
(*fit).method

--

-- 
	Lgb
Permalink | Reply | 0 comments |
headers
Lars Gullik Bjønnes | 1 Mar 2004 10:57

Re: [patch] encapsulate a font optimization

Alfredo Braunstein <abraunst <at> lyx.org> writes:

| Result attached. Ok to go in?

I have no problem with it.

(
>
| Alfredo
>
| Btw: Do you know a better place to put it than lyxtext.h/text.C ?
>
| ? PosIterator.C-save
| ? PosIterator.h-save
| ? all.diff
| ? bfs.cpp
| ? files
| ? save
| ? frontends/screen.C-save

--

-- 
	Lgb
Permalink | Reply | 0 comments |
headers
Angus Leeming | 1 Mar 2004 11:19
Favicon

Re: [patch] encapsulate a font optimization

Alfredo Braunstein wrote:
> Btw: Do you know a better place to put it than lyxtext.h/text.C ?

Why not font_iterator.[Ch]? You could even add some explanatory text 
describing briefly what the iterator does and what problem it 
solves...

Angus
Permalink | Reply | 1 comment |
headers
Jean-Marc Lasgouttes | 1 Mar 2004 11:45
Picon
Picon
Favicon

Re: [patch] Fix bugs 605, 1231, and 1244

>>>>> "Georg" == Georg Baum <Georg.Baum <at> post.rwth-aachen.de> writes:

Georg> This is the promised fix for bugs 605, 1231, and 1244. It is
Georg> work in progress, the html export is not fixed yet.

That's a large patch, indeed... It is difficult to understand all of
it, but I trust that you know what you are doing. People who try to
understand it may want to read my patch in bug #605, which is included
in there and solves part of the problems.

BTW, Georg, I want to include my patch in #605 in 1.3.5, provided that
I extend it to insetexternal. Could you describe what you had to do
there? 

Georg> - copy included .tex files into the temp dir rather than
Georg> referencing them through input <at> path. This is a preparation for
Georg> html export.

Do you mangle the names?

Georg> Open questions:

Georg> - The ExportData struct is rather a hack because it circumvents
Georg> the const'ness of runparams. How to do this properly? 

Can you collect the file names at validate() time? I'd think that this
pass is the right one for what you try to do.

Georg> - Does the \lyxdot trick work on other platforms than unix?
(Continue reading)

Permalink | Reply | 57 comments |
headers
Alfredo Braunstein | 1 Mar 2004 11:50
Favicon

Re: [patch] encapsulate a font optimization

Angus Leeming wrote:

> Why not font_iterator.[Ch]? You could even add some explanatory text
> describing briefly what the iterator does and what problem it
> solves...

Done.

Alfredo
Permalink | Reply | 0 comments |

Gmane