Making layouts more flexible
One of my frustrations using LyX (and there are very few!) is finding an elegant way to easily mix layouts. I may simply be ignorant of how to do it correctly. Here's an example. As a long time (La)TeX user I've developed my own set of handy environments that I use in addition to the standard ones. I simply \input{macros}, and I'm off. I'd like that same functionality in LyX, but with the ability to use those environments without resorting to ERT. The way I've been doing this so far, and it's really a kludge, is to create a local layout (in ~/.lyx/layouts) called stdlists.inc. I create a symbolic link to the real stdlists.inc ones and call it dist-stdlists.inc. My stdlists.inc contains my environments, and Includes dist-stdlists.inc. That way my environments are available in all layouts (assuming I use layouts which include stdlists.inc), and the symbolic link ensures that I'm never out of sync with the real stdlists.inc. This makes my life easier, but makes it almost impossible to work collaboratively on a document, as all of my the collaborators would have to perform this behind the scenes configuration. This is just not practical. I could create a layout specifically for each document that I need to share, but that's nuts! I couldn't recommend this approach to my colleagues who are just starting out with LyX either. It really really steepens the learning curve. I think that a practical solution would be to allow the user to interactively select multiple layouts. LyX would essentially build a wrapper layout file which would include them. That way one could create a library of sub-layouts which could be used interchangeably with very little effort. Thanks, Diab
Making layouts more flexible
One of my frustrations using LyX (and there are very few!) is finding an elegant way to easily mix layouts. I may simply be ignorant of how to do it correctly. Here's an example. As a long time (La)TeX user I've developed my own set of handy environments that I use in addition to the standard ones. I simply \input{macros}, and I'm off. I'd like that same functionality in LyX, but with the ability to use those environments without resorting to ERT. The way I've been doing this so far, and it's really a kludge, is to create a local layout (in ~/.lyx/layouts) called stdlists.inc. I create a symbolic link to the real stdlists.inc ones and call it dist-stdlists.inc. My stdlists.inc contains my environments, and Includes dist-stdlists.inc. That way my environments are available in all layouts (assuming I use layouts which include stdlists.inc), and the symbolic link ensures that I'm never out of sync with the real stdlists.inc. This makes my life easier, but makes it almost impossible to work collaboratively on a document, as all of my the collaborators would have to perform this behind the scenes configuration. This is just not practical. I could create a layout specifically for each document that I need to share, but that's nuts! I couldn't recommend this approach to my colleagues who are just starting out with LyX either. It really really steepens the learning curve. I think that a practical solution would be to allow the user to interactively select multiple layouts. LyX would essentially build a wrapper layout file which would include them. That way one could create a library of sub-layouts which could be used interchangeably with very little effort. Thanks, Diab
Making layouts more flexible
One of my frustrations using LyX (and there are very few!) is finding an elegant way to easily mix layouts. I may simply be ignorant of how to do it correctly. Here's an example. As a long time (La)TeX user I've developed my own set of handy environments that I use in addition to the standard ones. I simply \input{macros}, and I'm off. I'd like that same functionality in LyX, but with the ability to use those environments without resorting to ERT. The way I've been doing this so far, and it's really a kludge, is to create a local layout (in ~/.lyx/layouts) called "stdlists.inc". I create a symbolic link to the real stdlists.inc ones and call it "dist-stdlists.inc". My stdlists.inc contains my environments, and Includes dist-stdlists.inc. That way my environments are available in all layouts (assuming I use layouts which include stdlists.inc), and the symbolic link ensures that I'm never out of sync with the real stdlists.inc. This makes my life easier, but makes it almost impossible to work collaboratively on a document, as all of my the collaborators would have to perform this "behind the scenes" configuration. This is just not practical. I could create a layout specifically for each document that I need to share, but that's nuts! I couldn't recommend this approach to my colleagues who are just starting out with LyX either. It really really steepens the learning curve. I think that a practical solution would be to allow the user to interactively select multiple layouts. LyX would essentially build a wrapper layout file which would include them. That way one could create a library of "sub"-layouts which could be used interchangeably with very little effort. Thanks, Diab
How to turn off babel?
I'm using the SPIE class file (v 2.8) of 16 July 2003. It's redefining the reference citation macros in such a way that they collide with babel, causing failed runs. The error messages vary, depending upon the age of the TeX distribution. On Debian testing/unstable, I get: ! Missing \endcsname inserted. to be read again \mathsurround l.13 ...s presented in \cite{2000SPIE.4012...17J}. This is not a LyX bug. In the short run however, (i.e. paper was due two months ago, must have it in by next Tuesday) I need to turn babel off in the LyX output. Is there any way of doing this? There's no language=none option that I could find. I'm using 1.3.2, xforms. Thanks! Diab -- Diab Jerius Harvard-Smithsonian Center for Astrophysics 60 Garden St, MS 70, Cambridge MA 02138 USA [EMAIL PROTECTED] vox: 617 496 7575 fax: 617 495 7356
Re: How to turn off babel?
On 23 Aug, Christian Ridderström wrote: On Sat, 23 Aug 2003, Diab Jerius wrote: Is there any way of doing this? There's no language=none option that I could find. Hopefully there's a way to do this from LyX, but... if you get desperate, you can try this as a last resort: * export as LaTeX * manually remove the babel-code from the .tex-file * compile manually Oh, I am that desperate; that's actually how I tracked this down, as other LaTeX only papers were working. The problem is that since LaTeX dies with an error, I can't preview the paper. I've just discovered that I can temporarily insert natbib; that seems to override things enough so it'll work. I don't get the approved look to the in-text references, but as you point out, manual intevention before the final output will do the trick. Thanks, Diab -- Diab Jerius Harvard-Smithsonian Center for Astrophysics 60 Garden St, MS 70, Cambridge MA 02138 USA [EMAIL PROTECTED] vox: 617 496 7575 fax: 617 495 7356
How to turn off babel?
I'm using the SPIE class file (v 2.8) of 16 July 2003. It's redefining the reference citation macros in such a way that they collide with babel, causing failed runs. The error messages vary, depending upon the age of the TeX distribution. On Debian testing/unstable, I get: ! Missing \endcsname inserted. to be read again \mathsurround l.13 ...s presented in \cite{2000SPIE.4012...17J}. This is not a LyX bug. In the short run however, (i.e. paper was due two months ago, must have it in by next Tuesday) I need to turn babel off in the LyX output. Is there any way of doing this? There's no language=none option that I could find. I'm using 1.3.2, xforms. Thanks! Diab -- Diab Jerius Harvard-Smithsonian Center for Astrophysics 60 Garden St, MS 70, Cambridge MA 02138 USA [EMAIL PROTECTED] vox: 617 496 7575 fax: 617 495 7356
Re: How to turn off babel?
On 23 Aug, Christian Ridderström wrote: On Sat, 23 Aug 2003, Diab Jerius wrote: Is there any way of doing this? There's no language=none option that I could find. Hopefully there's a way to do this from LyX, but... if you get desperate, you can try this as a last resort: * export as LaTeX * manually remove the babel-code from the .tex-file * compile manually Oh, I am that desperate; that's actually how I tracked this down, as other LaTeX only papers were working. The problem is that since LaTeX dies with an error, I can't preview the paper. I've just discovered that I can temporarily insert natbib; that seems to override things enough so it'll work. I don't get the approved look to the in-text references, but as you point out, manual intevention before the final output will do the trick. Thanks, Diab -- Diab Jerius Harvard-Smithsonian Center for Astrophysics 60 Garden St, MS 70, Cambridge MA 02138 USA [EMAIL PROTECTED] vox: 617 496 7575 fax: 617 495 7356
How to turn off babel?
I'm using the SPIE class file (v 2.8) of 16 July 2003. It's redefining the reference citation macros in such a way that they collide with babel, causing failed runs. The error messages vary, depending upon the age of the TeX distribution. On Debian testing/unstable, I get: ! Missing \endcsname inserted. \mathsurround l.13 ...s presented in \cite{2000SPIE.4012...17J}. This is not a LyX bug. In the short run however, (i.e. paper was due two months ago, must have it in by next Tuesday) I need to turn babel off in the LyX output. Is there any way of doing this? There's no language=none option that I could find. I'm using 1.3.2, xforms. Thanks! Diab -- Diab Jerius Harvard-Smithsonian Center for Astrophysics 60 Garden St, MS 70, Cambridge MA 02138 USA [EMAIL PROTECTED] vox: 617 496 7575 fax: 617 495 7356
Re: How to turn off babel?
On 23 Aug, Christian Ridderström wrote: > On Sat, 23 Aug 2003, Diab Jerius wrote: > >> Is there any way of doing this? There's no language=none option that >> I could find. > > Hopefully there's a way to do this from LyX, but... > > if you get desperate, you can try this as a last resort: > * export as LaTeX > * manually remove the babel-code from the .tex-file > * compile manually Oh, I am that desperate; that's actually how I tracked this down, as other LaTeX only papers were working. The problem is that since LaTeX dies with an error, I can't preview the paper. I've just discovered that I can temporarily insert natbib; that seems to override things enough so it'll work. I don't get the approved look to the in-text references, but as you point out, manual intevention before the final output will do the trick. Thanks, Diab -- Diab Jerius Harvard-Smithsonian Center for Astrophysics 60 Garden St, MS 70, Cambridge MA 02138 USA [EMAIL PROTECTED] vox: 617 496 7575 fax: 617 495 7356
setting graphics height to % of text height?
I'm using lyx-1.3.2, xforms. I'm generating a page of thumbnail images and need to specify the graphics height as a percentage of the text height. The width should scale with the height, as it is not the constraining dimension. What I'd like to get is the equivalent of \includegraphics[height=0.2\textheight]{foo.ps} I can't figure out how to do this. In order to make the Height input box active, I select anything but Scale% for the Width. I then select text% for Height, but it translates that to textwidth, not textheight, in the output LaTeX. Is there some way to do this? Thanks, Diab -- Diab Jerius Harvard-Smithsonian Center for Astrophysics 60 Garden St, MS 70, Cambridge MA 02138 USA [EMAIL PROTECTED] vox: 617 496 7575 fax: 617 495 7356
Re: setting graphics height to % of text height?
On 22 Aug, Christian Ridderström wrote: On Fri, 22 Aug 2003, Diab Jerius wrote: I'm using lyx-1.3.2, xforms. I'm generating a page of thumbnail images and need to specify the graphics height as a percentage of the text height. The width should scale with the height, as it is not the constraining dimension. What I'd like to get is the equivalent of \includegraphics[height=0.2\textheight]{foo.ps} I can't figure out how to do this. In order to make the Height input box active, I select anything but Scale% for the Width. I then select text% for Height, but it translates that to textwidth, not textheight, in the output LaTeX. IIRC, just set the horizontal value to 0cm or something. Lyx uses the largest value, if you have clicked keep proportions. /Christian Hmm. no go. LyX still translates that to a textwidth \includegraphics[% bb=36bp 236bp 577bp 529bp, clip, height=0.2\textwidth, keepaspectratio]{graphics/02+hrma_00.00:01.00.ps}
Re: setting graphics height to % of text height?
On 22 Aug, Juergen Spitzmueller wrote: Diab Jerius wrote: What I'd like to get is the equivalent of \includegraphics[height=0.2\textheight]{foo.ps} I can't figure out how to do this. Select width: 0 %theight height: 20 %theight Are you using lyx-qt? %theight isn't one of the choices I get in the xforms version. Diab
Re: setting graphics height to % of text height?
Thanks for the confirmation; the bug report is filed. On 22 Aug, Christian Ridderström wrote: On Fri, 22 Aug 2003, Diab Jerius wrote: Select width: 0 %theight height: 20 %theight Are you using lyx-qt? %theight isn't one of the choices I get in the xforms version. You're right.. there is no %theight in lyx 1.3.2-xforms... You should file a bug about this in bugzilla. Diab
setting graphics height to % of text height?
I'm using lyx-1.3.2, xforms. I'm generating a page of thumbnail images and need to specify the graphics height as a percentage of the text height. The width should scale with the height, as it is not the constraining dimension. What I'd like to get is the equivalent of \includegraphics[height=0.2\textheight]{foo.ps} I can't figure out how to do this. In order to make the Height input box active, I select anything but Scale% for the Width. I then select text% for Height, but it translates that to textwidth, not textheight, in the output LaTeX. Is there some way to do this? Thanks, Diab -- Diab Jerius Harvard-Smithsonian Center for Astrophysics 60 Garden St, MS 70, Cambridge MA 02138 USA [EMAIL PROTECTED] vox: 617 496 7575 fax: 617 495 7356
Re: setting graphics height to % of text height?
On 22 Aug, Christian Ridderström wrote: On Fri, 22 Aug 2003, Diab Jerius wrote: I'm using lyx-1.3.2, xforms. I'm generating a page of thumbnail images and need to specify the graphics height as a percentage of the text height. The width should scale with the height, as it is not the constraining dimension. What I'd like to get is the equivalent of \includegraphics[height=0.2\textheight]{foo.ps} I can't figure out how to do this. In order to make the Height input box active, I select anything but Scale% for the Width. I then select text% for Height, but it translates that to textwidth, not textheight, in the output LaTeX. IIRC, just set the horizontal value to 0cm or something. Lyx uses the largest value, if you have clicked keep proportions. /Christian Hmm. no go. LyX still translates that to a textwidth \includegraphics[% bb=36bp 236bp 577bp 529bp, clip, height=0.2\textwidth, keepaspectratio]{graphics/02+hrma_00.00:01.00.ps}
Re: setting graphics height to % of text height?
On 22 Aug, Juergen Spitzmueller wrote: Diab Jerius wrote: What I'd like to get is the equivalent of \includegraphics[height=0.2\textheight]{foo.ps} I can't figure out how to do this. Select width: 0 %theight height: 20 %theight Are you using lyx-qt? %theight isn't one of the choices I get in the xforms version. Diab
Re: setting graphics height to % of text height?
Thanks for the confirmation; the bug report is filed. On 22 Aug, Christian Ridderström wrote: On Fri, 22 Aug 2003, Diab Jerius wrote: Select width: 0 %theight height: 20 %theight Are you using lyx-qt? %theight isn't one of the choices I get in the xforms version. You're right.. there is no %theight in lyx 1.3.2-xforms... You should file a bug about this in bugzilla. Diab
setting graphics height to % of text height?
I'm using lyx-1.3.2, xforms. I'm generating a page of "thumbnail" images and need to specify the graphics height as a percentage of the text height. The width should scale with the height, as it is not the constraining dimension. What I'd like to get is the equivalent of \includegraphics[height=0.2\textheight]{foo.ps} I can't figure out how to do this. In order to make the Height input box active, I select anything but Scale% for the Width. I then select text% for Height, but it translates that to textwidth, not textheight, in the output LaTeX. Is there some way to do this? Thanks, Diab -- Diab Jerius Harvard-Smithsonian Center for Astrophysics 60 Garden St, MS 70, Cambridge MA 02138 USA [EMAIL PROTECTED] vox: 617 496 7575 fax: 617 495 7356
Re: setting graphics height to % of text height?
On 22 Aug, Christian Ridderström wrote: > On Fri, 22 Aug 2003, Diab Jerius wrote: > >> I'm using lyx-1.3.2, xforms. >> >> I'm generating a page of "thumbnail" images and need to specify the >> graphics height as a percentage of the text height. The width should >> scale with the height, as it is not the constraining dimension. >> >> What I'd like to get is the equivalent of >> >> \includegraphics[height=0.2\textheight]{foo.ps} >> >> I can't figure out how to do this. >> >> In order to make the Height input box active, I select anything but >> Scale% for the Width. I then select text% for Height, but it translates >> that to textwidth, not textheight, in the output LaTeX. >> > > IIRC, just set the horizontal value to 0cm or something. Lyx uses the > largest value, if you have clicked keep proportions. > > /Christian > Hmm. no go. LyX still translates that to a textwidth \includegraphics[% bb=36bp 236bp 577bp 529bp, clip, height=0.2\textwidth, keepaspectratio]{graphics/02+hrma_00.00:01.00.ps}&
Re: setting graphics height to % of text height?
On 22 Aug, Juergen Spitzmueller wrote: > Diab Jerius wrote: >> What I'd like to get is the equivalent of >> >> \includegraphics[height=0.2\textheight]{foo.ps} >> >> I can't figure out how to do this. > > Select > width: 0 %theight > height: 20 %theight > Are you using lyx-qt? %theight isn't one of the choices I get in the xforms version. Diab
Re: setting graphics height to % of text height?
Thanks for the confirmation; the bug report is filed. On 22 Aug, Christian Ridderström wrote: > On Fri, 22 Aug 2003, Diab Jerius wrote: > >> >> > Select >> > width: 0 %theight >> > height: 20 %theight >> > >> >> Are you using lyx-qt? %theight isn't one of the choices I get in >> the xforms version. >> > You're right.. there is no %theight in lyx 1.3.2-xforms... You should file > a bug about this in bugzilla. > Diab
More info on Math font problems w/ 1.3.2 Solaris
I've run into the same problems with Solaris 1.3 mentioned on the list a couple of times before. The problem is that characters are rendered incorrectly in the mathed display (the math panel is fine). For example, \sum shows as P. This problem does not occur under 1.2.2. I've created a simple LyX file (attached) with just \sum. I've run both 1.2.2 and 1.3.2 on the file with the -dbg font flag. I've attached the resultant output. Note that 1.2.2 maps the character onto the adobe symbol font, while 1.3.2 maps it onto the cmsy font. More info: I notice that 1.3.2 loads the cm* PostScript fonts into the server: pelf% xlsfonts | grep cmsy pelf% lyx-1.3 test.lyx Adding /soft/tex/pkgs/lyx-1.3.2/share/lyx-1.3/xfonts/ to the font path. [...] pelf% xlsfonts | grep cmsy -unknown-cmsy10-medium-r-normal--0-0-0-0-p-0-adobe-fontspecific So, they're still there after 1.3.2 exits. Now, if I run directly after 1.2.2, *it* displays the character incorrectly! (I attach the -dbg font output) If I run xset fp default purging the fonts, and then run 1.2.2, it displays the character correctly. Manually adding *either* the lyx-1.2.2 or lyx-1.3.2 xfonts directory to the font path results in incorrect rendering by lyx-1.2.2. Interestingly, if I run xfd on the cmsy font while it is loaded into the server, I don't see any indication of a \sum symbol; just lots of latin characters. I note that the cmsy font is linked to my system's TeX font correctly: /soft/tex/share/texmf/fonts/type1/bluesky/cm/cmsy10.pfb So, does this mean that the bluesky font encoding is somehow different from what the Solaris X server requires? Diab #LyX 1.2 created this file. For more info see http://www.lyx.org/ \lyxformat 220 \textclass article \language american \inputencoding auto \fontscheme default \graphics default \paperfontsize default \papersize Default \paperpackage a4 \use_geometry 0 \use_amsmath 0 \use_natbib 0 \use_numerical_citations 0 \paperorientation portrait \secnumdepth 3 \tocdepth 3 \paragraph_separation indent \defskip medskip \quotes_language english \quotes_times 2 \papercolumns 1 \papersides 1 \paperpagestyle default \layout Standard \begin_inset Formula $\sum $ \end_inset \the_end Setting debug level to font Debugging `font' (Font handling) directory /soft/tex/bin/sparc-sun-solaris/ is a link directory sparc-sun-solaris2.6 is a link Math font 19 not available. Math font 18 not available. Math font 20 not available. Math font 22 not available. Math font 23 not available. Math font 21 not available. match #0 -adobe-symbol-medium-r-normal--12-120-72-72-p-0-adobe-fontspecific match #1 -adobe-symbol-medium-r-normal--0-0-0-0-p-0-adobe-fontspecific match #2 -adobe-symbol-medium-r-normal--10-100-75-75-p-61-adobe-fontspecific match #3 -adobe-symbol-medium-r-normal--12-120-75-75-p-74-adobe-fontspecific match #4 -adobe-symbol-medium-r-normal--14-140-75-75-p-85-adobe-fontspecific match #5 -adobe-symbol-medium-r-normal--18-180-75-75-p-107-adobe-fontspecific match #6 -adobe-symbol-medium-r-normal--24-240-75-75-p-142-adobe-fontspecific match #7 -adobe-symbol-medium-r-normal--8-80-75-75-p-51-adobe-fontspecific match #8 -adobe-symbol-medium-r-normal--12-120-72-72-p-0-adobe-fontspecific match #9 -adobe-symbol-medium-r-normal--0-0-75-75-p-0-adobe-fontspecific match #10 -adobe-symbol-medium-r-normal--11-80-100-100-p-61-adobe-fontspecific match #11 -adobe-symbol-medium-r-normal--14-100-100-100-p-85-adobe-fontspecific match #12 -adobe-symbol-medium-r-normal--17-120-100-100-p-95-adobe-fontspecific match #13 -adobe-symbol-medium-r-normal--20-140-100-100-p-107-adobe-fontspecific match #14 -adobe-symbol-medium-r-normal--25-180-100-100-p-142-adobe-fontspecific match #15 -adobe-symbol-medium-r-normal--34-240-100-100-p-191-adobe-fontspecific match #16 -adobe-symbol-medium-r-normal--12-120-72-72-p-0-adobe-fontspecific match #17 -adobe-symbol-medium-r-normal--0-0-100-100-p-0-adobe-fontspecific Using scalable font to get -adobe-symbol-medium-r-normal--4-0-0-0-p-0-adobe-fontspecific Exact font match with -adobe-symbol-medium-r-normal--17-120-100-100-p-95-adobe-fontspecific Font 'Symbol, Medium, Italic, Normal, Language: English' matched by -adobe-symbol-medium-r-normal--17-120-100-100-p-95-adobe-fontspecific match #0 -linotype-times-medium-r-normal--12-120-72-72-p-0-iso8859-1 match #1 -linotype-times-medium-r-normal--0-0-0-0-p-0-iso8859-1 match #2 -linotype-times-medium-r-normal--10-100-72-72-p-51-iso8859-1 match #3 -linotype-times-medium-r-normal--12-120-72-72-p-62-iso8859-1 match #4 -linotype-times-medium-r-normal--14-140-72-72-p-73-iso8859-1 match #5 -linotype-times-medium-r-normal--6-60-72-72-p-31-iso8859-1 match #6 -linotype-times-medium-r-normal--8-80-72-72-p-42-iso8859-1 match #7 -linotype-times-medium-r-normal--12-120-72-72-p-0-iso8859-1 match #8 -linotype-times-medium-r-normal--0-0-72-72-p-0-iso8859-1 match #9 -adobe-times-medium-r-normal--12-120-72-72-p-0-iso8859-1 match #10
More info on Math font problems w/ 1.3.2 Solaris
I've run into the same problems with Solaris 1.3 mentioned on the list a couple of times before. The problem is that characters are rendered incorrectly in the mathed display (the math panel is fine). For example, \sum shows as P. This problem does not occur under 1.2.2. I've created a simple LyX file (attached) with just \sum. I've run both 1.2.2 and 1.3.2 on the file with the -dbg font flag. I've attached the resultant output. Note that 1.2.2 maps the character onto the adobe symbol font, while 1.3.2 maps it onto the cmsy font. More info: I notice that 1.3.2 loads the cm* PostScript fonts into the server: pelf% xlsfonts | grep cmsy pelf% lyx-1.3 test.lyx Adding /soft/tex/pkgs/lyx-1.3.2/share/lyx-1.3/xfonts/ to the font path. [...] pelf% xlsfonts | grep cmsy -unknown-cmsy10-medium-r-normal--0-0-0-0-p-0-adobe-fontspecific So, they're still there after 1.3.2 exits. Now, if I run directly after 1.2.2, *it* displays the character incorrectly! (I attach the -dbg font output) If I run xset fp default purging the fonts, and then run 1.2.2, it displays the character correctly. Manually adding *either* the lyx-1.2.2 or lyx-1.3.2 xfonts directory to the font path results in incorrect rendering by lyx-1.2.2. Interestingly, if I run xfd on the cmsy font while it is loaded into the server, I don't see any indication of a \sum symbol; just lots of latin characters. I note that the cmsy font is linked to my system's TeX font correctly: /soft/tex/share/texmf/fonts/type1/bluesky/cm/cmsy10.pfb So, does this mean that the bluesky font encoding is somehow different from what the Solaris X server requires? Diab #LyX 1.2 created this file. For more info see http://www.lyx.org/ \lyxformat 220 \textclass article \language american \inputencoding auto \fontscheme default \graphics default \paperfontsize default \papersize Default \paperpackage a4 \use_geometry 0 \use_amsmath 0 \use_natbib 0 \use_numerical_citations 0 \paperorientation portrait \secnumdepth 3 \tocdepth 3 \paragraph_separation indent \defskip medskip \quotes_language english \quotes_times 2 \papercolumns 1 \papersides 1 \paperpagestyle default \layout Standard \begin_inset Formula $\sum $ \end_inset \the_end Setting debug level to font Debugging `font' (Font handling) directory /soft/tex/bin/sparc-sun-solaris/ is a link directory sparc-sun-solaris2.6 is a link Math font 19 not available. Math font 18 not available. Math font 20 not available. Math font 22 not available. Math font 23 not available. Math font 21 not available. match #0 -adobe-symbol-medium-r-normal--12-120-72-72-p-0-adobe-fontspecific match #1 -adobe-symbol-medium-r-normal--0-0-0-0-p-0-adobe-fontspecific match #2 -adobe-symbol-medium-r-normal--10-100-75-75-p-61-adobe-fontspecific match #3 -adobe-symbol-medium-r-normal--12-120-75-75-p-74-adobe-fontspecific match #4 -adobe-symbol-medium-r-normal--14-140-75-75-p-85-adobe-fontspecific match #5 -adobe-symbol-medium-r-normal--18-180-75-75-p-107-adobe-fontspecific match #6 -adobe-symbol-medium-r-normal--24-240-75-75-p-142-adobe-fontspecific match #7 -adobe-symbol-medium-r-normal--8-80-75-75-p-51-adobe-fontspecific match #8 -adobe-symbol-medium-r-normal--12-120-72-72-p-0-adobe-fontspecific match #9 -adobe-symbol-medium-r-normal--0-0-75-75-p-0-adobe-fontspecific match #10 -adobe-symbol-medium-r-normal--11-80-100-100-p-61-adobe-fontspecific match #11 -adobe-symbol-medium-r-normal--14-100-100-100-p-85-adobe-fontspecific match #12 -adobe-symbol-medium-r-normal--17-120-100-100-p-95-adobe-fontspecific match #13 -adobe-symbol-medium-r-normal--20-140-100-100-p-107-adobe-fontspecific match #14 -adobe-symbol-medium-r-normal--25-180-100-100-p-142-adobe-fontspecific match #15 -adobe-symbol-medium-r-normal--34-240-100-100-p-191-adobe-fontspecific match #16 -adobe-symbol-medium-r-normal--12-120-72-72-p-0-adobe-fontspecific match #17 -adobe-symbol-medium-r-normal--0-0-100-100-p-0-adobe-fontspecific Using scalable font to get -adobe-symbol-medium-r-normal--4-0-0-0-p-0-adobe-fontspecific Exact font match with -adobe-symbol-medium-r-normal--17-120-100-100-p-95-adobe-fontspecific Font 'Symbol, Medium, Italic, Normal, Language: English' matched by -adobe-symbol-medium-r-normal--17-120-100-100-p-95-adobe-fontspecific match #0 -linotype-times-medium-r-normal--12-120-72-72-p-0-iso8859-1 match #1 -linotype-times-medium-r-normal--0-0-0-0-p-0-iso8859-1 match #2 -linotype-times-medium-r-normal--10-100-72-72-p-51-iso8859-1 match #3 -linotype-times-medium-r-normal--12-120-72-72-p-62-iso8859-1 match #4 -linotype-times-medium-r-normal--14-140-72-72-p-73-iso8859-1 match #5 -linotype-times-medium-r-normal--6-60-72-72-p-31-iso8859-1 match #6 -linotype-times-medium-r-normal--8-80-72-72-p-42-iso8859-1 match #7 -linotype-times-medium-r-normal--12-120-72-72-p-0-iso8859-1 match #8 -linotype-times-medium-r-normal--0-0-72-72-p-0-iso8859-1 match #9 -adobe-times-medium-r-normal--12-120-72-72-p-0-iso8859-1 match #10
More info on Math font problems w/ 1.3.2 & Solaris
I've run into the same problems with Solaris & 1.3 mentioned on the list a couple of times before. The problem is that characters are rendered incorrectly in the mathed display (the math panel is fine). For example, \sum shows as P. This problem does not occur under 1.2.2. I've created a simple LyX file (attached) with just \sum. I've run both 1.2.2 and 1.3.2 on the file with the "-dbg font" flag. I've attached the resultant output. Note that 1.2.2 maps the character onto the adobe symbol font, while 1.3.2 maps it onto the cmsy font. More info: I notice that 1.3.2 loads the cm* PostScript fonts into the server: pelf% xlsfonts | grep cmsy pelf% lyx-1.3 test.lyx Adding /soft/tex/pkgs/lyx-1.3.2/share/lyx-1.3/xfonts/ to the font path. [...] pelf% xlsfonts | grep cmsy -unknown-cmsy10-medium-r-normal--0-0-0-0-p-0-adobe-fontspecific So, they're still there after 1.3.2 exits. Now, if I run directly after 1.2.2, *it* displays the character incorrectly! (I attach the -dbg font output) If I run xset fp default purging the fonts, and then run 1.2.2, it displays the character correctly. Manually adding *either* the lyx-1.2.2 or lyx-1.3.2 xfonts directory to the font path results in incorrect rendering by lyx-1.2.2. Interestingly, if I run xfd on the cmsy font while it is loaded into the server, I don't see any indication of a \sum symbol; just lots of latin characters. I note that the cmsy font is linked to my system's TeX font correctly: /soft/tex/share/texmf/fonts/type1/bluesky/cm/cmsy10.pfb So, does this mean that the bluesky font encoding is somehow different from what the Solaris X server requires? Diab #LyX 1.2 created this file. For more info see http://www.lyx.org/ \lyxformat 220 \textclass article \language american \inputencoding auto \fontscheme default \graphics default \paperfontsize default \papersize Default \paperpackage a4 \use_geometry 0 \use_amsmath 0 \use_natbib 0 \use_numerical_citations 0 \paperorientation portrait \secnumdepth 3 \tocdepth 3 \paragraph_separation indent \defskip medskip \quotes_language english \quotes_times 2 \papercolumns 1 \papersides 1 \paperpagestyle default \layout Standard \begin_inset Formula $\sum $ \end_inset \the_end Setting debug level to font Debugging `font' (Font handling) directory /soft/tex/bin/sparc-sun-solaris/ is a link directory sparc-sun-solaris2.6 is a link Math font 19 not available. Math font 18 not available. Math font 20 not available. Math font 22 not available. Math font 23 not available. Math font 21 not available. match #0 -adobe-symbol-medium-r-normal--12-120-72-72-p-0-adobe-fontspecific match #1 -adobe-symbol-medium-r-normal--0-0-0-0-p-0-adobe-fontspecific match #2 -adobe-symbol-medium-r-normal--10-100-75-75-p-61-adobe-fontspecific match #3 -adobe-symbol-medium-r-normal--12-120-75-75-p-74-adobe-fontspecific match #4 -adobe-symbol-medium-r-normal--14-140-75-75-p-85-adobe-fontspecific match #5 -adobe-symbol-medium-r-normal--18-180-75-75-p-107-adobe-fontspecific match #6 -adobe-symbol-medium-r-normal--24-240-75-75-p-142-adobe-fontspecific match #7 -adobe-symbol-medium-r-normal--8-80-75-75-p-51-adobe-fontspecific match #8 -adobe-symbol-medium-r-normal--12-120-72-72-p-0-adobe-fontspecific match #9 -adobe-symbol-medium-r-normal--0-0-75-75-p-0-adobe-fontspecific match #10 -adobe-symbol-medium-r-normal--11-80-100-100-p-61-adobe-fontspecific match #11 -adobe-symbol-medium-r-normal--14-100-100-100-p-85-adobe-fontspecific match #12 -adobe-symbol-medium-r-normal--17-120-100-100-p-95-adobe-fontspecific match #13 -adobe-symbol-medium-r-normal--20-140-100-100-p-107-adobe-fontspecific match #14 -adobe-symbol-medium-r-normal--25-180-100-100-p-142-adobe-fontspecific match #15 -adobe-symbol-medium-r-normal--34-240-100-100-p-191-adobe-fontspecific match #16 -adobe-symbol-medium-r-normal--12-120-72-72-p-0-adobe-fontspecific match #17 -adobe-symbol-medium-r-normal--0-0-100-100-p-0-adobe-fontspecific Using scalable font to get -adobe-symbol-medium-r-normal--4-0-0-0-p-0-adobe-fontspecific Exact font match with -adobe-symbol-medium-r-normal--17-120-100-100-p-95-adobe-fontspecific Font 'Symbol, Medium, Italic, Normal, Language: English' matched by -adobe-symbol-medium-r-normal--17-120-100-100-p-95-adobe-fontspecific match #0 -linotype-times-medium-r-normal--12-120-72-72-p-0-iso8859-1 match #1 -linotype-times-medium-r-normal--0-0-0-0-p-0-iso8859-1 match #2 -linotype-times-medium-r-normal--10-100-72-72-p-51-iso8859-1 match #3 -linotype-times-medium-r-normal--12-120-72-72-p-62-iso8859-1 match #4 -linotype-times-medium-r-normal--14-140-72-72-p-73-iso8859-1 match #5 -linotype-times-medium-r-normal--6-60-72-72-p-31-iso8859-1 match #6 -linotype-times-medium-r-normal--8-80-72-72-p-42-iso8859-1 match #7 -linotype-times-medium-r-normal--12-120-72-72-p-0-iso8859-1 match #8 -linotype-times-medium-r-normal--0-0-72-72-p-0-iso8859-1 match #9 -adobe-times-medium-r-normal--12-120-72-72-p-0-iso8859-1 match #10
Re: Compiling xforms-1.0
On my Solaris box w/ Sun cc, I did this after xmkmf -a perl -i.bak -pe 's/PICFLAGS\s*=.*/PICFLAGS = -KPIC/' `find . -name Makefile` (some sub Makefiles hardwired -fPIC for cc, which doesn't work, and this catches that as well) you'll need to do a make clean make On 17 Dec, Jean-Pierre.Chretien wrote: Hello, It's a bit off topic, but I get this: ld: fatal: too many symbols require `small' PIC references: have 2424, maximum 2048 -- recompile some modules -K PIC. Thanks for a hint.
Re: Compiling xforms-1.0
On my Solaris box w/ Sun cc, I did this after xmkmf -a perl -i.bak -pe 's/PICFLAGS\s*=.*/PICFLAGS = -KPIC/' `find . -name Makefile` (some sub Makefiles hardwired -fPIC for cc, which doesn't work, and this catches that as well) you'll need to do a make clean make On 17 Dec, Jean-Pierre.Chretien wrote: Hello, It's a bit off topic, but I get this: ld: fatal: too many symbols require `small' PIC references: have 2424, maximum 2048 -- recompile some modules -K PIC. Thanks for a hint.
Re: Compiling xforms-1.0
On my Solaris box w/ Sun cc, I did this after xmkmf -a perl -i.bak -pe 's/PICFLAGS\s*=.*/PICFLAGS = -KPIC/' `find . -name Makefile` (some sub Makefiles hardwired -fPIC for cc, which doesn't work, and this catches that as well) you'll need to do a make clean make On 17 Dec, Jean-Pierre.Chretien wrote: > > Hello, > > It's a bit off topic, but I get this: > > ld: fatal: too many symbols require `small' PIC references: > have 2424, maximum 2048 -- recompile some modules -K PIC. > > Thanks for a hint. >
embedding LaTeX commands in layouts
Hi, I'm trying to create a layout for a memo style which requires the following Format: %-- \begin{document} \From{From} \To{To} \Subject{Subject} \ShortSubj{Subject for page headers} \RE{In Regards to} \Cc{Carbon Copy list} \File{File name} \Version{Version} \memo{} memo text goes here \end{document} %-- The problem is that \memo{} MUST appear after the field specifications, but before the memo text. That's the macro which outputs the memo header. I've created layouts for all of the fields, but am unable to come up with a good way of getting the empty \memo{} to appear. I'd rather not have to use ERT, as I'm creating the layout for unsophisticated users. My first attempt for a layout is Style Memo LatexType Command LatexName memo KeepEmpty 1 End Unfortunately, if the user doesn't notice the layout is Memo and not Standard, the resultant text gets passed to \memo{}, which must not happen. (It takes an argument, but in this case it must be passed an empty one). Additionally, is there a way of ensuring that the \memo{} always is present, other than putting a label in the layout which says do not delete? Thanks, Diab
embedding LaTeX commands in layouts
Hi, I'm trying to create a layout for a memo style which requires the following Format: %-- \begin{document} \From{From} \To{To} \Subject{Subject} \ShortSubj{Subject for page headers} \RE{In Regards to} \Cc{Carbon Copy list} \File{File name} \Version{Version} \memo{} memo text goes here \end{document} %-- The problem is that \memo{} MUST appear after the field specifications, but before the memo text. That's the macro which outputs the memo header. I've created layouts for all of the fields, but am unable to come up with a good way of getting the empty \memo{} to appear. I'd rather not have to use ERT, as I'm creating the layout for unsophisticated users. My first attempt for a layout is Style Memo LatexType Command LatexName memo KeepEmpty 1 End Unfortunately, if the user doesn't notice the layout is Memo and not Standard, the resultant text gets passed to \memo{}, which must not happen. (It takes an argument, but in this case it must be passed an empty one). Additionally, is there a way of ensuring that the \memo{} always is present, other than putting a label in the layout which says do not delete? Thanks, Diab
embedding LaTeX commands in layouts
Hi, I'm trying to create a layout for a memo style which requires the following Format: %-- \begin{document} \From{} \To{} \Subject{} \ShortSubj{} \RE{} \Cc{} \File{} \Version{} \memo{} \end{document} %-- The problem is that \memo{} MUST appear after the field specifications, but before the memo text. That's the macro which outputs the memo header. I've created layouts for all of the fields, but am unable to come up with a good way of getting the empty \memo{} to appear. I'd rather not have to use ERT, as I'm creating the layout for unsophisticated users. My first attempt for a layout is Style Memo LatexType Command LatexName memo KeepEmpty 1 End Unfortunately, if the user doesn't notice the layout is Memo and not Standard, the resultant text gets passed to \memo{}, which must not happen. (It takes an argument, but in this case it must be passed an empty one). Additionally, is there a way of ensuring that the \memo{} always is present, other than putting a label in the layout which says "do not delete"? Thanks, Diab
Re: pdf won't open on other platform
On 5 Dec, Paul Tremblay wrote: On Thu, Dec 05, 2002 at 05:36:17PM -0500, Diab Jerius wrote: I just had this experience last night, as a matter of fact. I exported a document to PDF, sent it off to a Windows user, who complained that it wasn't recognized (I couldn't get a more technical description than that). I was able to view it with acroread under Linux. I re-exported the PDF using the pslatex fonts and the document was succesfully viewed on Windows. Do you mean that you used the package pslatex ( \usepackage{pslatex})? I thought this package was deprecated? (Which I guess doesn't matter for now, if it works!) I am just curios so I can try this myself. In the Layout-Document popup, under the Document tab, choose Fonts: pslatex. (in 1.1.6fix2)
Re: pdf won't open on other platform
On 5 Dec, John Coppens wrote: On Thu, 5 Dec 2002 17:36:17 -0500 (EST) Diab Jerius [EMAIL PROTECTED] wrote: On 5 Dec, Paul Tremblay wrote: I have just done a search on the web and found that no one else has had this problem, or at least that I could find. I just had this experience last night, as a matter of fact. I exported a document to PDF, sent it off to a Windows user, who complained that it wasn't recognized (I couldn't get a more technical description than that). I was able to view it with acroread under Linux. Ok... 'It wasn't recognized'... Does this mean that the plug-in didn't get called in the browser? Or was it Reader that complained? In the first case, did you send the file with the correct extension? As Windows hides extension this can be difficult to establish. Well, as I said, that was as techinical a description as I was given. As I noted (see quoted message below), exporting using the pslatex fonts did work correctly. Nothing to do with extensions, etc. I'd suggest to ask the Windows users to _download_ the file (right click save as...) then try to open it explicitly with Acrobat. John I re-exported the PDF using the pslatex fonts and the document was succesfully viewed on Windows. Diab -- Diab Jerius Harvard-Smithsonian Center for Astrophysics 60 Garden St, MS 70, Cambridge MA 02138 USA [EMAIL PROTECTED] vox: 617 496 7575 fax: 617 495 7356
Re: pdf won't open on other platform
On 5 Dec, Paul Tremblay wrote: On Thu, Dec 05, 2002 at 05:36:17PM -0500, Diab Jerius wrote: I just had this experience last night, as a matter of fact. I exported a document to PDF, sent it off to a Windows user, who complained that it wasn't recognized (I couldn't get a more technical description than that). I was able to view it with acroread under Linux. I re-exported the PDF using the pslatex fonts and the document was succesfully viewed on Windows. Do you mean that you used the package pslatex ( \usepackage{pslatex})? I thought this package was deprecated? (Which I guess doesn't matter for now, if it works!) I am just curios so I can try this myself. In the Layout-Document popup, under the Document tab, choose Fonts: pslatex. (in 1.1.6fix2)
Re: pdf won't open on other platform
On 5 Dec, John Coppens wrote: On Thu, 5 Dec 2002 17:36:17 -0500 (EST) Diab Jerius [EMAIL PROTECTED] wrote: On 5 Dec, Paul Tremblay wrote: I have just done a search on the web and found that no one else has had this problem, or at least that I could find. I just had this experience last night, as a matter of fact. I exported a document to PDF, sent it off to a Windows user, who complained that it wasn't recognized (I couldn't get a more technical description than that). I was able to view it with acroread under Linux. Ok... 'It wasn't recognized'... Does this mean that the plug-in didn't get called in the browser? Or was it Reader that complained? In the first case, did you send the file with the correct extension? As Windows hides extension this can be difficult to establish. Well, as I said, that was as techinical a description as I was given. As I noted (see quoted message below), exporting using the pslatex fonts did work correctly. Nothing to do with extensions, etc. I'd suggest to ask the Windows users to _download_ the file (right click save as...) then try to open it explicitly with Acrobat. John I re-exported the PDF using the pslatex fonts and the document was succesfully viewed on Windows. Diab -- Diab Jerius Harvard-Smithsonian Center for Astrophysics 60 Garden St, MS 70, Cambridge MA 02138 USA [EMAIL PROTECTED] vox: 617 496 7575 fax: 617 495 7356
Re: pdf won't open on other platform
On 5 Dec, Paul Tremblay wrote: > On Thu, Dec 05, 2002 at 05:36:17PM -0500, Diab Jerius wrote: >> I just had this experience last night, as a matter of fact. I exported >> a document to PDF, sent it off to a Windows user, who complained that it >> wasn't recognized (I couldn't get a more technical description than >> that). I was able to view it with acroread under Linux. >> >> I re-exported the PDF using the pslatex fonts and the document was >> succesfully viewed on Windows. >> > > Do you mean that you used the package pslatex ( \usepackage{pslatex})? > I thought this package was deprecated? (Which I guess doesn't matter for > now, if it works!) I am just curios so I can try this myself. > In the Layout->Document popup, under the Document tab, choose Fonts: pslatex. (in 1.1.6fix2)
Re: pdf won't open on other platform
On 5 Dec, John Coppens wrote: > On Thu, 5 Dec 2002 17:36:17 -0500 (EST) > Diab Jerius <[EMAIL PROTECTED]> wrote: > >> On 5 Dec, Paul Tremblay wrote: >> > I have just done a search on the web and found that no one else has had >> > this problem, or at least that I could find. >> >> I just had this experience last night, as a matter of fact. I exported >> a document to PDF, sent it off to a Windows user, who complained that it >> wasn't recognized (I couldn't get a more technical description than >> that). I was able to view it with acroread under Linux. > > Ok... 'It wasn't recognized'... Does this mean that the plug-in didn't > get called in the browser? Or was it Reader that complained? > In the first case, did you send the file with the correct extension? > As Windows hides extension this can be difficult to establish. Well, as I said, that was as techinical a description as I was given. As I noted (see quoted message below), exporting using the pslatex fonts did work correctly. Nothing to do with extensions, etc. > > I'd suggest to ask the Windows users to _download_ the file (right > click & save as...) then try to open it explicitly with Acrobat. > > John > >> >> I re-exported the PDF using the pslatex fonts and the document was >> succesfully viewed on Windows. >> >> Diab >> -- Diab Jerius Harvard-Smithsonian Center for Astrophysics 60 Garden St, MS 70, Cambridge MA 02138 USA [EMAIL PROTECTED] vox: 617 496 7575 fax: 617 495 7356
Re: pdf won't open on other platform
On 5 Dec, Paul Tremblay wrote: I have just done a search on the web and found that no one else has had this problem, or at least that I could find. I just had this experience last night, as a matter of fact. I exported a document to PDF, sent it off to a Windows user, who complained that it wasn't recognized (I couldn't get a more technical description than that). I was able to view it with acroread under Linux. I re-exported the PDF using the pslatex fonts and the document was succesfully viewed on Windows. Diab
Re: pdf won't open on other platform
On 5 Dec, Paul Tremblay wrote: I have just done a search on the web and found that no one else has had this problem, or at least that I could find. I just had this experience last night, as a matter of fact. I exported a document to PDF, sent it off to a Windows user, who complained that it wasn't recognized (I couldn't get a more technical description than that). I was able to view it with acroread under Linux. I re-exported the PDF using the pslatex fonts and the document was succesfully viewed on Windows. Diab
Re: pdf won't open on other platform
On 5 Dec, Paul Tremblay wrote: > I have just done a search on the web and found that no one else has had > this problem, or at least that I could find. I just had this experience last night, as a matter of fact. I exported a document to PDF, sent it off to a Windows user, who complained that it wasn't recognized (I couldn't get a more technical description than that). I was able to view it with acroread under Linux. I re-exported the PDF using the pslatex fonts and the document was succesfully viewed on Windows. Diab