Jürgen Spitzmüller writes:
> Jean-Marc Lasgouttes wrote:
>
>> So as a preamble, is there a reason why getOUtputFormat, instead of
>> looking
>> at various hardcoded variables, could not be written like the following?
>>
>> string Buffer::getDefaultOutputFormat() const
>> {
>> string format = lyx
Guenter Milde writes:
>> My goal is to implement the new tag OutputFormat in layout files, that
>> would complement OutputType. However I'd like to do it right.
>
> Another useful case is the setting in a module. Instead of n >= 3
> "*-literate" layouts we could have a "literate" or "noweb" module
Jean-Marc Lasgouttes wrote:
>> Without re-viewing the code: yes, sure.
>
> You mean that there is a reason?
No, I mean that refactoring would probably make sense. I'm sorry I do not
have time to look at the code now.
Jürgen
Jürgen Spitzmüller writes:
>>> Without re-viewing the code: yes, sure.
>>
>> You mean that there is a reason?
>
> No, I mean that refactoring would probably make sense. I'm sorry I do not
> have time to look at the code now.
My problem is that, last time I 'simplified' this code (doExport, I
be
>i slowly start to remember our last dispute about
>this... :) iirc i mostly dislike the fact that it
>would be inconsistent with the way reload/commit
>works otherwise (ie question for saving)...
I slowly start to remember that I didn't understand this reasoning ;-).
>pavel
Vincent
Jean-Marc Lasgouttes wrote:
> My problem is that, last time I 'simplified' this code (doExport, I
> believe), I broke it :) And this although I thought at the time that my
> changes were straightforward. Since defaultOutputFormat is a (recent)
> creation of yours, I'd rather have your thoughts on
Uwe Stöhr writes:
> Jean-Marc Lasgouttes schrieb:
>
>> Do you have problems with importing the following file (an accent in
>> a comment)
>
> Yes, absolutely: tex2lyx vanishes the character and everything behind it, see
> the attached result.
I do not have the file I sent anymore. Was there som
Jean-Marc Lasgouttes writes:
> Uwe Stöhr writes:
>
>> Jean-Marc Lasgouttes schrieb:
>>
>>> Do you have problems with importing the following file (an accent in
>>> a comment)
>>
>> Yes, absolutely: tex2lyx vanishes the character and everything behind it,
>> see the attached result.
>
> I do not
Hi Andre,
I stumbled over an error when compiling LyX-1.6.X (Rev 29386) on SLES9.
Maybe the GCC 3.3.3 is the problem... but the README and INSTALL doesn't say so.
The error is:
/usr/local/QT4/include/QtCore/qglobal.h: In instantiation of
`QTypeInfo::MenuDefinition>':
/usr/local/QT4/include/QtCo
On 2009-04-23, Jean-Marc Lasgouttes wrote:
> Guenter Milde writes:
>>> My goal is to implement the new tag OutputFormat in layout files, that
>>> would complement OutputType. However I'd like to do it right.
...
> What I have in mind is to allow any string in OutputFormat. If the
> correspondin
Guenter Milde writes:
> Sorry, I choose the first (and wrong) auto-completion.
>
> (What is an OutputTye, by the way?)
It used to tell what output routine we should invoke for export (mainly
latex or docbook). Now it can take 3 different values:
/// The different output types
enum OutputType {
Jean-Marc Lasgouttes schrieb:
I do not have the file I sent anymore. Was there something after the
accented character?
Yes, some characters like "aabb" behind the comment.
regards Uwe
When I have a branch inset taller than the main window, scrolling
becomes problematic.
Scrolling with the scrollbar is fine. Scrolling with arrow-up/down cause
surprising jumps. It is sometimes hard to use arrows to reach the middle
of such a inset.
Helge Hafting
Stephan Witt writes:
> Hi Andre,
>
> I stumbled over an error when compiling LyX-1.6.X (Rev 29386) on
> SLES9. Maybe the GCC 3.3.3 is the problem... but the README and
> INSTALL doesn't say so.
Looks like this is at qt level...
JMarc
Jean-Marc Lasgouttes schrieb:
While we are at it, here is my next try. You can revert all other
patches I made you apply, BTW.
Still the same problem :-(
regards Uwe
Le 23 avr. 09 à 23:23, Uwe Stöhr a écrit :
Jean-Marc Lasgouttes schrieb:
While we are at it, here is my next try. You can revert all other
patches I made you apply, BTW.
Still the same problem :-(
OK, something different now. The issue seems to be that iconv returns
an error
qnd then the
Jean-Marc Lasgouttes schrieb:
OK, something different now. The issue seems to be that iconv returns an
error
qnd then the stream is set to fail() forever. This patch sets avoid setting
an error condition when iconv signal an error with errno==0.
You found the fix! Formulas are correctly parse
Uwe Stöhr schrieb:
Where does your iconv come from BTW? Is there some documentation
attached to it?
It is version 1.11 of iconv provided as dll
I now found iconv version 1.9.2 for Windows.
But also with this version I get the same problem without you patch.
Btw. what is more recent iconv 1.
On 2009-04-23, Jean-Marc Lasgouttes wrote:
> Guenter Milde writes:
>> Sorry, I choose the first (and wrong) auto-completion.
>> (What is an OutputTye, by the way?)
> It used to tell what output routine we should invoke for export (mainly
> latex or docbook). Now it can take 3 different values:
19 matches
Mail list logo
