Jean-Marc Lasgouttes wrote:
What about using AddFontResourceEx with flag FR_PRIVATE instead?
http://msdn2.microsoft.com/en-us/library/ms533937.aspx
Good idea! That should solve the problem.
Joost
> "Joost" == Joost Verburg <[EMAIL PROTECTED]> writes:
Joost> Uwe Stöhr wrote:
>> But I thought that the problem is the doubled file name. How are
>> you sure that the problem is the font name?
Joost> The filename does not have to be changed. Font loading is based
Joost> on font names, not on
Uwe Stöhr wrote:
But I thought that the problem is the doubled file name. How are you
sure that the problem is the font name?
The filename does not have to be changed. Font loading is based on font
names, not on file names. The problem is that the LyX fonts have the
same font name as Scientif
> I don't understand what you are doing. All I can see in the patch is that some filenames have
been > changed. The filename is unrelated to the font name.
But I thought that the problem is the doubled file name. How are you sure that the problem is the
font name?
> What should be done is:
>
Uwe Stöhr wrote:
I think the fix is simple: Rename the fonts to LyX-cmex10 etc. and
modify LyX to use these fonts on Windows.
I opened bug 3962 for this issue and set it to critical as this should
be done before LyX 1.5.0 comes out. Attached the patch that does this.
As far as I tested it wor
Joost Verburg schrieb:
Good. Now the question is: can we do something about that from the LyX
side? Joost? Uwe?
> The official installer does not install the BaKoMa in the Windows fonts
directory. The fonts are
> located in Resources\fonts.
The same as for LyXWinInstaller.
It looks like Sci