Am Samstag, 20. Mai 2006 19:26 schrieb Jean-Marc Lasgouttes:
> No, I think it was for images in paths with space. The extra "quote"
> qre left in the dvi, and the dvi tools do not like it. The cleqn_dvi
> script removes them. I do not like it, but it seems there is no better
> solution.
You are
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> Am Samstag, 20. Mai 2006 16:43 schrieb Joost Verburg:
>> Right. Then I don't understand the reason why we have clean_dvi, it
>> always seems to work without it.
Georg> IIRC (Angus please correct me if I am wrong) the clean_dvi
Georg>
> "Edwin" == Edwin Leuven <[EMAIL PROTECTED]> writes:
Edwin> Jean-Marc Lasgouttes wrote:
>>> "Joost" == Joost Verburg <[EMAIL PROTECTED]>
>>> writes:
>>
Joost> The parenthesis on the last line here are wrong. With the last
Joost> one removed, it compiles.
>> Thanks. The patch is in no
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>> We should banish the windows port, then.
Abdelrazak> This was friday man...
Wasn't it still friday when I ansewered?
Abdelrazak> Beside, Windows does not require #ifdef, programming style
Abdelrazak> does. I would prefer l
Am Samstag, 20. Mai 2006 17:10 schrieb Joost Verburg:
> Georg Baum wrote:
> > IIRC (Angus please correct me if I am wrong) the clean_dvi script was
> > invented for images that are included by preamble commands or ERT.
>
> So these are images that will not be stored in the temporary directory?
Georg Baum wrote:
IIRC (Angus please correct me if I am wrong) the clean_dvi script was
invented for images that are included by preamble commands or ERT.
So these are images that will not be stored in the temporary directory?
Do you have an example for me to test?
Joost
Am Samstag, 20. Mai 2006 16:43 schrieb Joost Verburg:
> Right. Then I don't understand the reason why we have clean_dvi, it
> always seems to work without it.
IIRC (Angus please correct me if I am wrong) the clean_dvi script was
invented for images that are included by preamble commands or ERT.
Georg Baum wrote:
What do you mean by new copies of graphics files? If you mean that
the .eps files from the temp dir with mangled names are copied to the
document directory: This is intended behaviour and no bug. The .eps files
are required for the dvi, and we use the mangled ones since it was
Am Samstag, 20. Mai 2006 10:32 schrieb Joost Verburg:
> configure.py should be updated to add the entires for clean_dvi on
> Windows. It however looks like new copies of graphics files are created
> when I use File>Export>DVI, is that a bug?
What do you mean by new copies of graphics files? If y
Jean-Marc Lasgouttes wrote:
"Joost" == Joost Verburg <[EMAIL PROTECTED]> writes:
Joost> The parenthesis on the last line here are wrong. With the last
Joost> one removed, it compiles.
Thanks. The patch is in now. What else did you need?
JMarc
missing include or library while linking?
qt4 o
Lars Gullik Bjønnes a écrit :
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Jean-Marc Lasgouttes a écrit :
| >> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| >>
| >
| > Abdelrazak> Tested 1.4 Does not compile on qt4 (and I guess also on
| > Abdelrazak> qt3), remove th
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Jean-Marc Lasgouttes a écrit :
| >> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| >>
| >
| > Abdelrazak> Tested 1.4 Does not compile on qt4 (and I guess also on
| > Abdelrazak> qt3), remove the last bracket:
| >
| > Doh! Tha
Jean-Marc Lasgouttes a écrit :
"Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> Tested 1.4 Does not compile on qt4 (and I guess also on
Abdelrazak> qt3), remove the last bracket:
Doh! Thanks.
Abdelrazak> This is why I hate #ifdef, they should be banished
Jean-Marc Lasgouttes wrote:
I do not know about this stuff, sorry.
However, I do not think this should prevent you from showing us your
brand new installer :)
I'll have to wait for Angus then.
How can I show the new installer? It makes no sense to put the whole
source code in a message. May
> "Joost" == Joost Verburg <[EMAIL PROTECTED]> writes:
Joost> Jean-Marc Lasgouttes wrote:
>> Thanks. The patch is in now. What else did you need?
Joost> configure.py should be updated to add the entires for clean_dvi
Joost> on Windows. It however looks like new copies of graphics files
Joost>
Jean-Marc Lasgouttes wrote:
Thanks. The patch is in now. What else did you need?
configure.py should be updated to add the entires for clean_dvi on
Windows. It however looks like new copies of graphics files are created
when I use File>Export>DVI, is that a bug?
Joost
> "Joost" == Joost Verburg <[EMAIL PROTECTED]> writes:
Joost> The parenthesis on the last line here are wrong. With the last
Joost> one removed, it compiles.
Thanks. The patch is in now. What else did you need?
JMarc
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> Tested 1.4 Does not compile on qt4 (and I guess also on
Abdelrazak> qt3), remove the last bracket:
Doh! Thanks.
Abdelrazak> This is why I hate #ifdef, they should be banished from
Abdelrazak> normal code.
We should
+FontLoader::~FontLoader() {
+#ifdef Q_WS_WIN
+ // Windows only: Remove BaKoMa TrueType font resources
+ string const fonts_dir = AddPath(package().system_support(), "fonts");
+
+ for(int i = 0 ; i < num_fonts_truetype ; ++i) {
+ string const font_current =
+ AddName(f
Jean-Marc Lasgouttes a écrit :
"Joost" == Joost Verburg <[EMAIL PROTECTED]> writes:
Joost> Let's not make things too complicated and go for
Joost> AddFontResource and RemoveFontResource. The attached patch now
Joost> also includes the second part. I tested it, the fonts are
Joost> loaded correc
> "Joost" == Joost Verburg <[EMAIL PROTECTED]> writes:
Joost> Let's not make things too complicated and go for
Joost> AddFontResource and RemoveFontResource. The attached patch now
Joost> also includes the second part. I tested it, the fonts are
Joost> loaded correctly and the files are not lo
Jean-Marc Lasgouttes wrote:
If we can support Win9x, we should. Isn't there some kind way to fall
back to AddFontResource when it is the only one available?
Anyway Joost, I'll let you decide.
Let's not make things too complicated and go for AddFontResource and
RemoveFontResource. The attached
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>> Win98/Me are currently not supported, so maybe we should indeed
>> use AddFontResourceEx. Or is LyX 1.5 with Qt4 going to support
>> 98/Me?
Abdelrazak> At least it seems to work fine right now on Windows Me. So
Abdelrazak> if
Joost Verburg a écrit :
Jean-Marc Lasgouttes wrote:
You could do it in FontLoader destructor, I guess. Of course, it is
not very symmetrical, but I do not think initFontPath could be
called in FontLoader constructor (the lyxdir is not known at this
point).
Of course, if we used AddFontResourceE
Jean-Marc Lasgouttes wrote:
You could do it in FontLoader destructor, I guess. Of course, it is
not very symmetrical, but I do not think initFontPath could be
called in FontLoader constructor (the lyxdir is not known at this
point).
Of course, if we used AddFontResourceEx... ;)
Win98/Me are cu
> "Joost" == Joost Verburg <[EMAIL PROTECTED]> writes:
Joost> Joost Verburg wrote:
>> Attached the new patch for 1.4 with the code moved to the qt2
>> frontend. Is this OK?
Joost> It would be better to also remove the font resources when
Joost> closing LyX. How should I add an unload function
Joost Verburg wrote:
Attached the new patch for 1.4 with the code moved to the qt2 frontend.
Is this OK?
It would be better to also remove the font resources when closing LyX.
How should I add an unload function for this FontLoader?
Joost
Jean-Marc Lasgouttes wrote:
I'd appreciate if you could update the patch according to the remarks
above, or find someone who can do so.
Attached the new patch for 1.4 with the code moved to the qt2 frontend.
Is this OK?
Joost
Index: src/frontends/qt2/qfont_loader.C
==
Georg Baum wrote:
No, I think what you mean is NewApis.h, but I don't know if it includes
AddFontResourceEx.
No, it's Windows NT stuff, it will never work on Win9x/Me.
Joost
Jean-Marc Lasgouttes wrote:
> I thought there was a provision in the header files or something
> to replace automatically the function with a stub. I must have been
> dreaming :)
No, I think what you mean is NewApis.h, but I don't know if it includes
AddFontResourceEx.
Georg
> "Joost" == Joost Verburg <[EMAIL PROTECTED]> writes:
Joost> If you link against an API function that does not exist, like
Joost> AddFontResourceEx on Win9x/ME, the application won't start.
Joost> There are however compiler options to delay the load of a
Joost> function.
I thought there was
Jean-Marc Lasgouttes wrote:
Joost> Do you mean that you want it to use AddFontResourceEx on
Joost> Win2K/XP? That would require some hacks, if you link to this
Joost> API it won't work on Win9x anymore.
I thought the windows way of handling this was to return an error
value when the function is
> "Joost" == Joost Verburg <[EMAIL PROTECTED]> writes:
Joost> Jean-Marc Lasgouttes wrote:
>> This is indeed a good idea. We already do that for Lyx/Mac. This is
>> done currently in qt2/qfont_loader::initFontPath. Could you move
>> the code there?
Joost> I'll make a new patch.
Thanks.
>> I
Jean-Marc Lasgouttes wrote:
This is indeed a good idea. We already do that for Lyx/Mac. This is
done currently in qt2/qfont_loader::initFontPath. Could you move the
code there?
I'll make a new patch.
I would also prefer to use private fonts in Win2k/xp also.
Do you mean that you want it to
> "Joost" == Joost Verburg <[EMAIL PROTECTED]> writes:
Joost> Currently, LyX relies on the BaKoMa fonts to be installed as a
Joost> system font in order to be able to display math. This is not a
Joost> good thing, it of course requires administrator privileges to
Joost> install a system font a
35 matches
Mail list logo