I have been running qt-lyx remotely over the network from two
diferent machines. One of these machines is an Alpha running Tru64
unix. The other is a PC running RH8.
Needless to say, these two machines have entirely different fonts
installed. Does anyone have any idea how I might tweak things
On Wed, Jul 16, 2003 at 02:21:51PM +0100, Angus Leeming wrote:
I also find that the RH8 box (uses fontconfig) can display mathed
fonts happily but I get the ubiquitous red string descriptions on the
Tru64 unix machine. Am I right in saying that there is no work around
for this over the
Andre Poenitz wrote:
On Wed, Jul 16, 2003 at 02:21:51PM +0100, Angus Leeming wrote:
I also find that the RH8 box (uses fontconfig) can display mathed
fonts happily but I get the ubiquitous red string descriptions on
the Tru64 unix machine. Am I right in saying that there is no work
around
On Wed, Jul 16, 2003 at 02:54:04PM +0100, Angus Leeming wrote:
I have installed the free replacement for the Bakoma fonts on the
machine running LyX and on the remote RH8 box. I have the non-free
originals on the Tru64 box. If I run LyX locally on the Tru64 machine
then all is Ok. If I log
Andre Poenitz wrote:
Actually, I suspect that this is not the cause of the problem. The
real cause is that the directory trees have a different structure.
On the Tru64 machine the equivalent of /home/aleem is
/usr/users/aleem, so the necessary xfonts dir is not found:
$ Adding
On Wed, Jul 16, 2003 at 02:54:04PM +0100, Angus Leeming wrote:
I have installed the free replacement for the Bakoma fonts on the
machine running LyX and on the remote RH8 box. I have the non-free
originals on the Tru64 box. If I run LyX locally on the Tru64 machine
then all is Ok. If I
On Wed, Jul 16, 2003 at 03:19:30PM +0100, Angus Leeming wrote:
Andre Poenitz wrote:
Actually, I suspect that this is not the cause of the problem. The
real cause is that the directory trees have a different structure.
On the Tru64 machine the equivalent of /home/aleem is
/usr/users/aleem,
Dekel Tsur wrote:
On Wed, Jul 16, 2003 at 02:54:04PM +0100, Angus Leeming wrote:
I have installed the free replacement for the Bakoma fonts on the
machine running LyX and on the remote RH8 box. I have the non-free
originals on the Tru64 box. If I run LyX locally on the Tru64
machine then
On Wed, Jul 16, 2003 at 02:54:04PM +0100, Angus Leeming wrote:
so the necessary xfonts dir is not found:
$ Adding /home/aleem/.lyx-1.3.3cvs/xfonts/ to the font path.
This dir has nothing to do with the fontconfig-based loading of the
latex-xft-fonts
regards
john
John Levon wrote:
On Wed, Jul 16, 2003 at 02:54:04PM +0100, Angus Leeming wrote:
so the necessary xfonts dir is not found:
$ Adding /home/aleem/.lyx-1.3.3cvs/xfonts/ to the font path.
This dir has nothing to do with the fontconfig-based loading of the
latex-xft-fonts
I think we've
I have been running qt-lyx remotely over the network from two
diferent machines. One of these machines is an Alpha running Tru64
unix. The other is a PC running RH8.
Needless to say, these two machines have entirely different fonts
installed. Does anyone have any idea how I might tweak things
On Wed, Jul 16, 2003 at 02:21:51PM +0100, Angus Leeming wrote:
> I also find that the RH8 box (uses fontconfig) can display mathed
> fonts happily but I get the ubiquitous red string descriptions on the
> Tru64 unix machine. Am I right in saying that there is no work around
> for this over the
Andre Poenitz wrote:
> On Wed, Jul 16, 2003 at 02:21:51PM +0100, Angus Leeming wrote:
>> I also find that the RH8 box (uses fontconfig) can display mathed
>> fonts happily but I get the ubiquitous red string descriptions on
>> the Tru64 unix machine. Am I right in saying that there is no work
>>
On Wed, Jul 16, 2003 at 02:54:04PM +0100, Angus Leeming wrote:
> I have installed the free replacement for the Bakoma fonts on the
> machine running LyX and on the remote RH8 box. I have the non-free
> originals on the Tru64 box. If I run LyX locally on the Tru64 machine
> then all is Ok. If I
Andre Poenitz wrote:
>> Actually, I suspect that this is not the cause of the problem. The
>> real cause is that the directory trees have a different structure.
>> On the Tru64 machine the equivalent of /home/aleem is
>> /usr/users/aleem, so the necessary xfonts dir is not found:
>> $ Adding
On Wed, Jul 16, 2003 at 02:54:04PM +0100, Angus Leeming wrote:
>
> I have installed the free replacement for the Bakoma fonts on the
> machine running LyX and on the remote RH8 box. I have the non-free
> originals on the Tru64 box. If I run LyX locally on the Tru64 machine
> then all is Ok. If
On Wed, Jul 16, 2003 at 03:19:30PM +0100, Angus Leeming wrote:
> Andre Poenitz wrote:
> >> Actually, I suspect that this is not the cause of the problem. The
> >> real cause is that the directory trees have a different structure.
> >> On the Tru64 machine the equivalent of /home/aleem is
> >>
Dekel Tsur wrote:
> On Wed, Jul 16, 2003 at 02:54:04PM +0100, Angus Leeming wrote:
>>
>> I have installed the free replacement for the Bakoma fonts on the
>> machine running LyX and on the remote RH8 box. I have the non-free
>> originals on the Tru64 box. If I run LyX locally on the Tru64
>>
On Wed, Jul 16, 2003 at 02:54:04PM +0100, Angus Leeming wrote:
> so the necessary xfonts dir is not found:
> $ Adding /home/aleem/.lyx-1.3.3cvs/xfonts/ to the font path.
This dir has nothing to do with the fontconfig-based loading of the
latex-xft-fonts
regards
john
John Levon wrote:
> On Wed, Jul 16, 2003 at 02:54:04PM +0100, Angus Leeming wrote:
>
>> so the necessary xfonts dir is not found:
>> $ Adding /home/aleem/.lyx-1.3.3cvs/xfonts/ to the font path.
>
> This dir has nothing to do with the fontconfig-based loading of the
> latex-xft-fonts
I think
20 matches
Mail list logo
