Re: System Font issues: XeTeX and LuaTeX

2010-12-16 Thread The Wilsons
Thanks for the note.  The situation is workable, but  fix before too
long would be welcome.

Daron

On Thu, Dec 16, 2010 at 01:27, Nikos Chantziaras  wrote:
> On 12/15/2010 05:25 PM, Daron Wilson wrote:
>>
>> Greetings all,
>>
>> I am using LyX 2 beta 2, and I have been trying out the use of system
>> fonts with XeTeX and LuaTeX.  Whenever I chose the fonts I want, I click
>> apply, and then ok.  If I exit the document and then reopen, the sans serif
>> font and the typewriter font are reset to default, and the font scale is set
>> to 10%.  Both engines are happy with this, and all sans serif portions of
>> the document are nicely typeset at 10% scale.   As long as the documents
>> remain open, the fonts and font scale I choose will stay selected, and the
>> output is as expected.  There seem to be no issues when I deselect
>> XeTeX/LuaTeX in the font area of document settings--pdflatex has no scaling
>> issues. I have experienced this problem both with documents that worked fine
>> under older versions, and with documents newly created.
>
> This has been fixed, but unfortunately only after beta 2 was released. Let's
> hope for a quick beta 3 or RC1 which will contain the fix.
>
>


Re: System Font issues: XeTeX and LuaTeX

2010-12-15 Thread Nikos Chantziaras

On 12/15/2010 05:25 PM, Daron Wilson wrote:

Greetings all,

I am using LyX 2 beta 2, and I have been trying out the use of system fonts 
with XeTeX and LuaTeX.  Whenever I chose the fonts I want, I click apply, and 
then ok.  If I exit the document and then reopen, the sans serif font and the 
typewriter font are reset to default, and the font scale is set to 10%.  Both 
engines are happy with this, and all sans serif portions of the document are 
nicely typeset at 10% scale.   As long as the documents remain open, the fonts 
and font scale I choose will stay selected, and the output is as expected.  
There seem to be no issues when I deselect XeTeX/LuaTeX in the font area of 
document settings--pdflatex has no scaling issues. I have experienced this 
problem both with documents that worked fine under older versions, and with 
documents newly created.


This has been fixed, but unfortunately only after beta 2 was released. 
Let's hope for a quick beta 3 or RC1 which will contain the fix.




Re: System Font issues: XeTeX and LuaTeX

2010-12-15 Thread Fareed Qureshi
On 12/15/2010 10:25 AM, Daron Wilson wrote:
> Greetings all,
> 
> I am using LyX 2 beta 2, and I have been trying out the use of system
> fonts with XeTeX and LuaTeX.  Whenever I chose the fonts I want, I
> click apply, and then ok.  If I exit the document and then reopen,
> the sans serif font and the typewriter font are reset to default, and
> the font scale is set to 10%.  Both engines are happy with this, and
> all sans serif portions of the document are nicely typeset at 10%
> scale.   As long as the documents remain open, the fonts and font
> scale I choose will stay selected, and the output is as expected.
> There seem to be no issues when I deselect XeTeX/LuaTeX in the font
> area of document settings--pdflatex has no scaling issues. I have
> experienced this problem both with documents that worked fine under
> older versions, and with documents newly created.
> 
> Has anyone else experienced this problem, or could I get some 
> suggestions for debugging?

I have also experienced this in one document, newly created in LyX
2.0beta2, using TeX Live 2010 on Ubuntu 10.10.

In my case, I create the document, change to XeTeX in the font settings,
then select some fonts for serif, sans-serif, and typewriter families,
all at 100% scale. Proceed to write as normal, save, preview PDF
(XeTeX), all looks well. Then close document. When I reopen the
document, the font settings now look as Daron describes — XeTeX is still
selected, the serif family is still correct, but sans-serif and
typewriter are now set to default and 10% scale. However, if I preview
my document the text set in typewriter is exported normally.
Subsequently, editing the text of the document (whether that text was
set in serif or typewriter) does not change the correct scaling in the
PDF preview.

Running LyX from the command line only gives this output, when I preview
the PDF:

This is XeTeX, Version 3.1415926-2.2-0.9997.4 (TeX Live 2010)
 restricted \write18 enabled.
entering extended mode
(./test_document.tex
LaTeX2e <2009/09/24>
Babel  and hyphenation patterns for english, dumylang,
nohyphenation, ge
rman-x-2009-06-19, ngerman-x-2009-06-19, afrikaans, ancientgreek,
ibycus, arabi
c, armenian, basque, bulgarian, catalan, pinyin, coptic, croatian,
czech, danis
h, dutch, ukenglish, usenglishmax, esperanto, estonian, farsi, finnish,
french,
 galician, german, ngerman, swissgerman, monogreek, greek, hungarian,
icelandic
, assamese, bengali, gujarati, hindi, kannada, malayalam, marathi,
oriya, panja
bi, tamil, telugu, indonesian, interlingua, irish, italian, kurmanji,
lao, lati
n, latvian, lithuanian, mongolian, mongolianlmc, bokmal, nynorsk,
polish, portu
guese, romanian, russian, sanskrit, serbian, slovak, slovenian, spanish,
swedis
h, turkish, turkmen, ukrainian, uppersorbian, welsh, loaded.


System Font issues: XeTeX and LuaTeX

2010-12-15 Thread Daron Wilson
Greetings all,

I am using LyX 2 beta 2, and I have been trying out the use of system fonts 
with XeTeX and LuaTeX.  Whenever I chose the fonts I want, I click apply, and 
then ok.  If I exit the document and then reopen, the sans serif font and the 
typewriter font are reset to default, and the font scale is set to 10%.  Both 
engines are happy with this, and all sans serif portions of the document are 
nicely typeset at 10% scale.   As long as the documents remain open, the fonts 
and font scale I choose will stay selected, and the output is as expected.  
There seem to be no issues when I deselect XeTeX/LuaTeX in the font area of 
document settings--pdflatex has no scaling issues. I have experienced this 
problem both with documents that worked fine under older versions, and with 
documents newly created.  

Has anyone else experienced this problem, or could I get some suggestions for 
debugging?

Regards,

Daron