Re: source view empty
On 31.03.09, Vincent van Ravesteijn - TNW wrote: When I tried today to look at the LaTeX source with ViewSource, the field stays empty and the tick-boxes (complete source and automatic update) are greyed out. Did anyone else experience this problem? Is there a known remedy? I have the same with 1.6.2.. I've no clue what happened.. Are you on Windows ? If so, deleting the following key from the registry solves the problem: HKEY_USERS\S-1-5-21-2082945442-480271342-340043625-47002\Software\LyX\LyX-1.6.2\views\0\view-source No, I am on Unix (Debian Gnu/Linux). But I found that removing the file ~/.config/LyX/LyX-1.6.2.conf did the trick (with the unwanted side-effect of restoring window size and toolbar visibility to the defaults). Changing 0\view-source\autoupdate=false to 0\view-source\autoupdate=true helped without side effects. Furthermore, I found the reason: You can reproduce the bug if you untick both, complete source and autoupdate in the source view window. Günter
Re: source view empty
On 31.03.09, Vincent van Ravesteijn - TNW wrote: When I tried today to look at the LaTeX source with ViewSource, the field stays empty and the tick-boxes (complete source and automatic update) are greyed out. Did anyone else experience this problem? Is there a known remedy? I have the same with 1.6.2.. I've no clue what happened.. Are you on Windows ? If so, deleting the following key from the registry solves the problem: HKEY_USERS\S-1-5-21-2082945442-480271342-340043625-47002\Software\LyX\LyX-1.6.2\views\0\view-source No, I am on Unix (Debian Gnu/Linux). But I found that removing the file ~/.config/LyX/LyX-1.6.2.conf did the trick (with the unwanted side-effect of restoring window size and toolbar visibility to the defaults). Changing 0\view-source\autoupdate=false to 0\view-source\autoupdate=true helped without side effects. Furthermore, I found the reason: You can reproduce the bug if you untick both, complete source and autoupdate in the source view window. Günter
Re: source view empty
On 31.03.09, Vincent van Ravesteijn - TNW wrote: > >>When I tried today to look at the LaTeX source with View>Source, the > >>field stays empty and the tick-boxes (complete source and automatic > >>update) are greyed out. > >>Did anyone else experience this problem? Is there a known remedy? > > > >I have the same with 1.6.2.. I've no clue what happened.. > Are you on Windows ? > If so, deleting the following key from the registry solves the problem: > HKEY_USERS\S-1-5-21-2082945442-480271342-340043625-47002\Software\LyX\LyX-1.6.2\views\0\view-source No, I am on Unix (Debian Gnu/Linux). But I found that removing the file ~/.config/LyX/LyX-1.6.2.conf did the trick (with the unwanted side-effect of restoring window size and toolbar visibility to the defaults). Changing 0\view-source\autoupdate=false to 0\view-source\autoupdate=true helped without side effects. Furthermore, I found the reason: You can reproduce the bug if you untick both, "complete source" and "autoupdate" in the source view window. Günter
Re: Disable Alt-f and similar?
On 27.11.08, Jean-Marc Lasgouttes wrote: Guenter Milde [EMAIL PROTECTED] writes: Is there a way to disable Alt+something for the cases where there is no explicite definition? This is a supposedly 'helpful' functionality that should be removed IMO. This happens when there is no function bound to the binding that you try. I filed a bug, http://bugzilla.lyx.org/show_bug.cgi?id=5575 Thanks, Günter
Re: Disable Alt-f and similar?
On 27.11.08, Jean-Marc Lasgouttes wrote: Guenter Milde [EMAIL PROTECTED] writes: Is there a way to disable Alt+something for the cases where there is no explicite definition? This is a supposedly 'helpful' functionality that should be removed IMO. This happens when there is no function bound to the binding that you try. I filed a bug, http://bugzilla.lyx.org/show_bug.cgi?id=5575 Thanks, Günter
Re: Disable Alt-f and similar?
On 27.11.08, Jean-Marc Lasgouttes wrote: > Guenter Milde <[EMAIL PROTECTED]> writes: > > > > Is there a way to disable Alt+ for the cases where there > > is no explicite definition? > This is a supposedly 'helpful' functionality that should be removed IMO. > This happens when there is no function bound to the binding that you > try. I filed a bug, http://bugzilla.lyx.org/show_bug.cgi?id=5575 Thanks, Günter
Re: Loading Babel with parameter
Máté Salát [EMAIL PROTECTED] schrieb:
From: Marcelo Acu=F1a=20
You know that LyX adds \usepackage{babel} to the end of
the preamble of the tex file by default. How can it changed
to \usepackage[magyar]{babel} to load the Hungarian one?
put magyar in options of documents
Or set the language with the DocumentSettingsLanguage Dialogue.
If I set the language in the document options then it appears only among =
the options of \documentclass. The \begin{document} remains without =
option. Look at it here: http://screencast.com/t/ZQuXO1sXqQ.
Options in \documentclass are passed to all packages loaded with
\usepackage, to this should work.
You can, however untick the [x] Global box in
ToolsPreferencesLanguage settingsLanguage.
Downside: other packages (like index generators) will not pick up the
language setting.
Günter
Re: Loading Babel with parameter
Máté Salát [EMAIL PROTECTED] schrieb:
From: Marcelo Acu=F1a=20
You know that LyX adds \usepackage{babel} to the end of
the preamble of the tex file by default. How can it changed
to \usepackage[magyar]{babel} to load the Hungarian one?
put magyar in options of documents
Or set the language with the DocumentSettingsLanguage Dialogue.
If I set the language in the document options then it appears only among =
the options of \documentclass. The \begin{document} remains without =
option. Look at it here: http://screencast.com/t/ZQuXO1sXqQ.
Options in \documentclass are passed to all packages loaded with
\usepackage, to this should work.
You can, however untick the [x] Global box in
ToolsPreferencesLanguage settingsLanguage.
Downside: other packages (like index generators) will not pick up the
language setting.
Günter
Re: Loading Babel with parameter
Máté Salát <[EMAIL PROTECTED]> schrieb:
> From: Marcelo Acu=F1a=20
> > You know that LyX adds \usepackage{babel} to the end of
> > the preamble of the tex file by default. How can it changed
> > to \usepackage[magyar]{babel} to load the Hungarian one?
>put magyar in options of documents
Or set the language with the Document>Settings>Language Dialogue.
> If I set the language in the document options then it appears only among =
> the options of \documentclass. The \begin{document} remains without =
> option. Look at it here: http://screencast.com/t/ZQuXO1sXqQ.
Options in \documentclass are passed to all packages loaded with
\usepackage, to this should work.
You can, however untick the "[x] Global" box in
Tools>Preferences>Language settings>Language.
Downside: other packages (like index generators) will not pick up the
language setting.
Günter
Re: RC2 and graphics, follow up
Hellmut Weber [EMAIL PROTECTED] schrieb: Viewing with kpdf is quite slow too, somebody sugested that may be a problem of graphic format conversion. Which format does lyx use? I could easily convert all my pictures to that format using convert. Then no additional time would be needed. The converted images are chached, so this would not really matter. You might have a look at the chache configuration in ToolsSettings, though. OTOH, kpdf is quite slow -- especially if you are not using KDE. Setting this to xpdf, say, in the ToolsSettingsFormatsPDF* variants might speed things up. In some cases two pictures which should be on a line are put on different lines and the need a whole page, i.e. the first picture is at the beginning of the upper half of a page, the second one in the lower half of the page, right justified. Looks like your pictures are too wide (or you have a space inbetween: 50% + 50% + space 100% ;-). As automatic line-breaking is not shown in LyX, you see this only in the output. I could overcome this problem putting the picturers in one big minipage, then the two pictures which should stay beside each other in two single minipages which again are put in a minipage for the line. In the minipage, if the pictures do not fit on the line, they have no chance to sort otherwise, so the line will become too long (have a look at the overfull line warnings in the DocumentLaTeX_log). Günter
Re: New LyX user, problem with uncodable characters
Nikos Alexandris [EMAIL PROTECTED] schrieb: 2. While trying to export the document to pdf I get twice the LyX: Uncodable characters in listings inset \ The following characters in one of the program listings are not representable in the current encoding and have been omitted: -. #It's kind of a long dash! Well, the '-' you posted here is the ASCII dash (002D HYPHEN-MINUS) that should not pose problems. Did you copy and past it from the log? After pressing OK the pdf is produced and viewed properly. Since I have lots of Program Listing insets it's hard to tell where or what this character is (?). If you could copy the actual character from the log, you could examine with e.g. gucharmap or the `unicode` command. Or just search and replace it in the *.lyx source file in a text editor. 4. How do I create a custom summary environment (e.g. chapter summary) an add it in the book document class? On 1.6 it would be most easy to read about the layout modules in HelpCustomization. Günter
Re: RC2 and graphics, follow up
Hellmut Weber [EMAIL PROTECTED] schrieb: Viewing with kpdf is quite slow too, somebody sugested that may be a problem of graphic format conversion. Which format does lyx use? I could easily convert all my pictures to that format using convert. Then no additional time would be needed. The converted images are chached, so this would not really matter. You might have a look at the chache configuration in ToolsSettings, though. OTOH, kpdf is quite slow -- especially if you are not using KDE. Setting this to xpdf, say, in the ToolsSettingsFormatsPDF* variants might speed things up. In some cases two pictures which should be on a line are put on different lines and the need a whole page, i.e. the first picture is at the beginning of the upper half of a page, the second one in the lower half of the page, right justified. Looks like your pictures are too wide (or you have a space inbetween: 50% + 50% + space 100% ;-). As automatic line-breaking is not shown in LyX, you see this only in the output. I could overcome this problem putting the picturers in one big minipage, then the two pictures which should stay beside each other in two single minipages which again are put in a minipage for the line. In the minipage, if the pictures do not fit on the line, they have no chance to sort otherwise, so the line will become too long (have a look at the overfull line warnings in the DocumentLaTeX_log). Günter
Re: New LyX user, problem with uncodable characters
Nikos Alexandris [EMAIL PROTECTED] schrieb: 2. While trying to export the document to pdf I get twice the LyX: Uncodable characters in listings inset \ The following characters in one of the program listings are not representable in the current encoding and have been omitted: -. #It's kind of a long dash! Well, the '-' you posted here is the ASCII dash (002D HYPHEN-MINUS) that should not pose problems. Did you copy and past it from the log? After pressing OK the pdf is produced and viewed properly. Since I have lots of Program Listing insets it's hard to tell where or what this character is (?). If you could copy the actual character from the log, you could examine with e.g. gucharmap or the `unicode` command. Or just search and replace it in the *.lyx source file in a text editor. 4. How do I create a custom summary environment (e.g. chapter summary) an add it in the book document class? On 1.6 it would be most easy to read about the layout modules in HelpCustomization. Günter
Re: RC2 and graphics, follow up
Hellmut Weber <[EMAIL PROTECTED]> schrieb: > Viewing with kpdf is quite slow too, somebody sugested that may be a > problem of graphic format conversion. > Which format does lyx use? I could easily convert all my pictures to > that format using convert. Then no additional time would be needed. The converted images are chached, so this would not really matter. You might have a look at the chache configuration in Tools>Settings, though. OTOH, kpdf is quite slow -- especially if you are not using KDE. Setting this to xpdf, say, in the Tools>Settings>Formats>PDF* variants might speed things up. > In some cases two pictures which should be on a line are put on > different lines and the need a whole page, i.e. the first picture is at > the beginning of the upper half of a page, the second one in the lower > half of the page, right justified. Looks like your pictures are too wide (or you have a space inbetween: 50% + 50% + space > 100% ;-). As automatic line-breaking is not shown in LyX, you see this only in the output. > I could overcome this problem putting the picturers in one big minipage, > then the two pictures which should stay beside each other in two single > minipages which again are put in a minipage for the "line". In the minipage, if the pictures do not fit on the line, they have no chance to sort otherwise, so the line will become too long (have a look at the "overfull line" warnings in the Document>LaTeX_log). Günter
Re: New LyX user, problem with "uncodable characters"
Nikos Alexandris <[EMAIL PROTECTED]> schrieb: > 2. While trying to export the document to pdf I get twice the "LyX: > Uncodable characters in listings inset \ The following characters in one > of the program listings are not representable in the current encoding > and have been omitted: -." #It's kind of a long dash! Well, the '-' you posted here is the ASCII dash (002D HYPHEN-MINUS) that should not pose problems. Did you copy and past it from the log? > After pressing "OK" the pdf is produced and viewed properly. Since I > have lots of Program Listing insets it's hard to tell where or what this > character is (?). If you could copy the actual character from the log, you could examine with e.g. gucharmap or the `unicode` command. Or just search and replace it in the *.lyx source file in a text editor. > 4. How do I create a custom "summary" environment (e.g. chapter summary) > an add it in the "book" document class? On 1.6 it would be most easy to read about the layout modules in Help>Customization. Günter
Re: I killed Latex, ¡hel p me, please!
On 20.09.08, Marcelo Acuña wrote:
I update several packages that in texlive provided for opensuse 11.0
are very old. When I finished and run texhash lyx (and kile) no run
anymore.
Did you try with a simple example?
I get:
Undefinid control sequence
Missing \begin{document}
Undefinid control sequence
Missing \begin{document}
What does the LaTeX log say?
How I can restore latex work without reverse to obsolete version of
texlive provided for opensuse?
This very much depends on what is really wrong?
Could you append the example file and the LaTeX log so we can check?
Günter
Re: custom layouts - inserting a mandatory parameter
Micha [EMAIL PROTECTED] schrieb:
I'm trying to see if I can write a layout file for the currvita latex class.
The main environment is a list environment that should come out something like
\begin{cvlist}{title}
\item[one] text
\item[two] text
\end{cvlist}
I can get the {title} part by adding
LatexParam{title}
but that doesn't allow me to change this. Is there a way to insert that
mandatory argument, layout file style option, tex code or otherwise?
There are two ways: as optional parameter (short title) or as a separate
Style. My dinbrief.layout uses the latter:
# dinbrief's \phone has 2 args, area and number. We define an empty
# command that can be set by the Area_Code style
Preamble
\newcommand{\areacode}{}
EndPreamble
# dinbrief's \phone has 2 args, area and number,
# define both as distinct styles
Style Area_Code
CopyStyle DinBrief
LabelString Vorwahl:
LatexName renewcommand{\areacode}
End
Style Telephone
CopyStyle DinBrief
LabelString Telefon:
LatexName phone
LatexParam {\areacode}
End
For the short-title way, you would need to define an auxiliary latex
command with optional argument, enable the optional arg with the keyword
OptionalArgs 1
and set it with (the misnamed) InsertShort-Title.
Günter
Re: I killed Latex, ¡hel p me, please!
On 20.09.08, Marcelo Acuña wrote:
I update several packages that in texlive provided for opensuse 11.0
are very old. When I finished and run texhash lyx (and kile) no run
anymore.
Did you try with a simple example?
I get:
Undefinid control sequence
Missing \begin{document}
Undefinid control sequence
Missing \begin{document}
What does the LaTeX log say?
How I can restore latex work without reverse to obsolete version of
texlive provided for opensuse?
This very much depends on what is really wrong?
Could you append the example file and the LaTeX log so we can check?
Günter
Re: custom layouts - inserting a mandatory parameter
Micha [EMAIL PROTECTED] schrieb:
I'm trying to see if I can write a layout file for the currvita latex class.
The main environment is a list environment that should come out something like
\begin{cvlist}{title}
\item[one] text
\item[two] text
\end{cvlist}
I can get the {title} part by adding
LatexParam{title}
but that doesn't allow me to change this. Is there a way to insert that
mandatory argument, layout file style option, tex code or otherwise?
There are two ways: as optional parameter (short title) or as a separate
Style. My dinbrief.layout uses the latter:
# dinbrief's \phone has 2 args, area and number. We define an empty
# command that can be set by the Area_Code style
Preamble
\newcommand{\areacode}{}
EndPreamble
# dinbrief's \phone has 2 args, area and number,
# define both as distinct styles
Style Area_Code
CopyStyle DinBrief
LabelString Vorwahl:
LatexName renewcommand{\areacode}
End
Style Telephone
CopyStyle DinBrief
LabelString Telefon:
LatexName phone
LatexParam {\areacode}
End
For the short-title way, you would need to define an auxiliary latex
command with optional argument, enable the optional arg with the keyword
OptionalArgs 1
and set it with (the misnamed) InsertShort-Title.
Günter
Re: I killed Latex, ¡hel p me, please!
On 20.09.08, Marcelo Acuña wrote:
> I update several packages that in texlive provided for opensuse 11.0
> are very old. When I finished and run texhash lyx (and kile) no run
> anymore.
Did you try with a simple example?
> I get:
> Undefinid control sequence
> Missing \begin{document}
> Undefinid control sequence
> Missing \begin{document}
What does the LaTeX log say?
> How I can restore latex work without reverse to obsolete version of
> texlive provided for opensuse?
This very much depends on what is really wrong?
Could you append the example file and the LaTeX log so we can check?
Günter
Re: custom layouts - inserting a mandatory parameter
Micha <[EMAIL PROTECTED]> schrieb:
> I'm trying to see if I can write a layout file for the currvita latex class.
> The main environment is a list environment that should come out something like
> \begin{cvlist}{title}
> \item[one] text
> \item[two] text
> \end{cvlist}
> I can get the {title} part by adding
> LatexParam{title}
> but that doesn't allow me to change this. Is there a way to insert that
> mandatory argument, layout file style option, tex code or otherwise?
There are two ways: as optional parameter (short title) or as a separate
Style. My dinbrief.layout uses the latter:
# dinbrief's \phone has 2 args, area and number. We define an empty
# command that can be set by the Area_Code style
Preamble
\newcommand{\areacode}{}
EndPreamble
# dinbrief's \phone has 2 args, area and number,
# define both as distinct styles
Style Area_Code
CopyStyle DinBrief
LabelString "Vorwahl:"
LatexName "renewcommand{\areacode}"
End
Style Telephone
CopyStyle DinBrief
LabelString "Telefon:"
LatexName phone
LatexParam {\areacode}
End
For the "short-title" way, you would need to define an auxiliary latex
command with optional argument, enable the optional arg with the keyword
OptionalArgs 1
and set it with (the misnamed) Insert>Short-Title.
Günter
Re: Problems with 1.6 RC2
On 15.09.08, rgheck wrote: Steve Litt wrote: It would be kinda cool to have a running instance of LyX, and program it using commands to the pipe file. Yeah, it's very cool. You can do (almost) anything you can do from the GUI remotely. More info on http://wiki.lyx.org/LyX/LyXServer. I used the LyXServer, for instance, to program a `lyx-remote` script, that opens given files in a running LyX session (or starts LyX with the file if there is no LyX running). It is part of my LyX-Python-interface package http://wiki.lyx.org/Tools/PyClient. Günter
Re: Theorems in LyX
On 16.09.08, bigblop wrote: How is it possible to make theorems in LyX thats automatically assigned a number like figures? In the userguide in LyX it says that the description environment should be used but can't see how the above is achieved using this. Which LyX verison are you using? In 1.6 this is easy to do with a layout module (copy and modify the LYXDIR/layouts/theorems-ams-extended.module file). Günter
Re: Problems with 1.6 RC2
On 15.09.08, rgheck wrote: Steve Litt wrote: It would be kinda cool to have a running instance of LyX, and program it using commands to the pipe file. Yeah, it's very cool. You can do (almost) anything you can do from the GUI remotely. More info on http://wiki.lyx.org/LyX/LyXServer. I used the LyXServer, for instance, to program a `lyx-remote` script, that opens given files in a running LyX session (or starts LyX with the file if there is no LyX running). It is part of my LyX-Python-interface package http://wiki.lyx.org/Tools/PyClient. Günter
Re: Theorems in LyX
On 16.09.08, bigblop wrote: How is it possible to make theorems in LyX thats automatically assigned a number like figures? In the userguide in LyX it says that the description environment should be used but can't see how the above is achieved using this. Which LyX verison are you using? In 1.6 this is easy to do with a layout module (copy and modify the LYXDIR/layouts/theorems-ams-extended.module file). Günter
Re: Problems with 1.6 RC2
On 15.09.08, rgheck wrote: > Steve Litt wrote: >> It would be kinda cool to have a running instance of LyX, and program >> it using commands to the pipe file. > Yeah, it's very cool. You can do (almost) anything you can do from the > GUI remotely. More info on http://wiki.lyx.org/LyX/LyXServer. I used the LyXServer, for instance, to program a `lyx-remote` script, that opens given files in a running LyX session (or starts LyX with the file if there is no LyX running). It is part of my LyX-Python-interface package http://wiki.lyx.org/Tools/PyClient. Günter
Re: Theorems in LyX
On 16.09.08, bigblop wrote: > How is it possible to make theorems in LyX thats automatically assigned a > number like figures? In the userguide in LyX it says that the description > environment should be used but can't see how the above is achieved using > this. Which LyX verison are you using? In 1.6 this is easy to do with a "layout module" (copy and modify the /layouts/theorems-ams-extended.module file). Günter
Re: LyX 1.5.6 1.6.0rc2 Theorem redefinition
On 11.09.08, rgheck wrote:
Atlas wrote:
Background: * CLS file == www.stacs-conf.org/for_authors/stacs.cls
(note: stacs.cls
is based on amsart.cls)
...
* Conference-supplied TEX file (note: this file does not import correctly
nor compile in LyX 1.5.6 nor 1.6.0):
http://www.stacs-conf.org/for_authors/stacs-smp.tex
* In stacs-smp.tex, it states:
%% due to the dependence on amsart.cls, \begin{document} has to occur
%% BEFORE the title and author information: \begin{document}
As amsart.cls works with LyX, this should not be a problem.
\title[Using stacs.cls]{How to use stacs.cls} \author[lab1]{A.
Uthor}{Alice Uthor}
%% the abstract has to PRECEDE the command \maketitle: %% be sure not
to issue the \maketitle command twice! \begin{abstract} STUB.
\end{abstract} \maketitle
So you will need the InTitle flag for the Abstract style. This is already
true for the amsart layout.
QUESTION how would I get stacs-smp.tex to import and
compile correctly in LyX?
You need a layout file for stacs.cls. See the Customization manual for
the details. You can start by copying amsart.cls to stacs.cls and
changing the first two lines to:
#% Do not delete the line below; configure depends on this
# \DeclareLaTeXClass{article (stacs)}
I would rather start with a new file and include amsart.layout:
#% Do not delete the line below; configure depends on this
# \DeclareLaTeXClass{article (stacs)}
input amsart.layout
Now you can add, overwrite, and disable layouts to adapt to the stacs class.
I do not know whether this works with 1.6, though.
Is there an analogy to NoStyle to undo UseModule calls (NoModule, say)?
- The problem is that LyX hides most of the details in its preamble
and also apparently inserts a redefinition of the theorem
environment.
LyX adds this:
\theoremstyle{plain}
\newtheorem{thm}{Theorem}
So you need to stop LyX from issuing this code.
Fortunately, all of this is user-controllable.
In 1.5, add to your stacs.layout file
Style Theorem
Preamble
EndPreamble
End
to overwrite the Preamble definition in amsmaths.inc with an empty
preamble.
In 1.6, the theorem layout is in theorems-ams.inc, which is included by
the theorems-ams.module, which is included by default by amsart.layout.
So you'd want to copy theorems-ams.inc to something like
theorems-stacs.inc; make the necessary change there; copy
theorems-ams.module to theorems-stacs.module; make the change there;
and then change stacs.layout so it does this: UseModule
theorems-stacs.module instead of using theorems-ams.module. (Note that
this is a default include: the user can override it in
DocumentSettings.)
In analogy, I'd just copy theorems-ams.module to theorems-stacs.module
and overwrite the offending parts from included files there.
If there are theorem environments other than the ones theorems-ams.inc
defines, then you will need to add those to theorems-stacs.inc, as well.
Otherwise, LyX won't know about them.
The good thing is that you only have to do this once. Then you can post
it on the wiki, or maybe your layout can even be included with LyX
itself.
Günter
Re: Sure-fire LyX layout files
On 11.09.08, rgheck wrote: Rich Shepard wrote: On Thu, 11 Sep 2008, Steve Litt wrote: I think part of what Steve wants, which other people have also wanted, is to be able to keep the layout file with the document ... Yes, I want to have additional styles for personal use but at the same time to keep the option to send my document to a colleague without with just the LyX standard layouts. The layouts module in 1.6 will alleviate this problem somewhat. In most cases, I suspect, the reason people will have lots of layouts is because they have various customizations to some base class that they want to apply in different combinations for different projects. This is precisely what layout modules are for. I am looking forward to this much cleaner way of adding my styles to the standard classes (hopefully a stable 1.6 is out soon). That said, sometimes you just want to add some layout information to one document. or, as stated above, to ship your private extensions with the LyX file. ** WARNING: Read what follows at your own risk! ** LyX 1.6 includes a facility that can also be used for this purpose. I call it local layout. ..., this is just layout information, embedded directly into the document. LyX reads it, if it's there, and uses it. There is, as yet, no UI for this, because it is really quite experimental and may prove dangerous. How about an embed button for selected modules? This way it would be easy to create self-contained lyx documents with private styles. You can create and test a module in ~/.lyx/layouts/ and if you want it in a document for others to use, simply embed it. (It will still show up in *your* modules list but not in everyones.) it'll be a trivial matter to add a simple UI, like the one for preamble. With appropriate warnings. Maybe this is not even needed with an embed button for modules. But still a possible supplement for one-off layouts. Personally, I don't want to see this overused. Part of the point of the way LyX uses layouts (and soon, modules) is to promote reusability. Local layout is not reusable except by cut-and-paste, and that's not really what one means by reusability. But there is also the problem with compatibility. My private reusable modules can (currently) not be used in files that should work everywhere. Maybe there could be an extract-module tool, that can extract embedded modules to ~/.lyx/layouts/ Günter
Re: LyX 1.5.6 1.6.0rc2 Theorem redefinition
On 11.09.08, rgheck wrote:
Atlas wrote:
Background: * CLS file == www.stacs-conf.org/for_authors/stacs.cls
(note: stacs.cls
is based on amsart.cls)
...
* Conference-supplied TEX file (note: this file does not import correctly
nor compile in LyX 1.5.6 nor 1.6.0):
http://www.stacs-conf.org/for_authors/stacs-smp.tex
* In stacs-smp.tex, it states:
%% due to the dependence on amsart.cls, \begin{document} has to occur
%% BEFORE the title and author information: \begin{document}
As amsart.cls works with LyX, this should not be a problem.
\title[Using stacs.cls]{How to use stacs.cls} \author[lab1]{A.
Uthor}{Alice Uthor}
%% the abstract has to PRECEDE the command \maketitle: %% be sure not
to issue the \maketitle command twice! \begin{abstract} STUB.
\end{abstract} \maketitle
So you will need the InTitle flag for the Abstract style. This is already
true for the amsart layout.
QUESTION how would I get stacs-smp.tex to import and
compile correctly in LyX?
You need a layout file for stacs.cls. See the Customization manual for
the details. You can start by copying amsart.cls to stacs.cls and
changing the first two lines to:
#% Do not delete the line below; configure depends on this
# \DeclareLaTeXClass{article (stacs)}
I would rather start with a new file and include amsart.layout:
#% Do not delete the line below; configure depends on this
# \DeclareLaTeXClass{article (stacs)}
input amsart.layout
Now you can add, overwrite, and disable layouts to adapt to the stacs class.
I do not know whether this works with 1.6, though.
Is there an analogy to NoStyle to undo UseModule calls (NoModule, say)?
- The problem is that LyX hides most of the details in its preamble
and also apparently inserts a redefinition of the theorem
environment.
LyX adds this:
\theoremstyle{plain}
\newtheorem{thm}{Theorem}
So you need to stop LyX from issuing this code.
Fortunately, all of this is user-controllable.
In 1.5, add to your stacs.layout file
Style Theorem
Preamble
EndPreamble
End
to overwrite the Preamble definition in amsmaths.inc with an empty
preamble.
In 1.6, the theorem layout is in theorems-ams.inc, which is included by
the theorems-ams.module, which is included by default by amsart.layout.
So you'd want to copy theorems-ams.inc to something like
theorems-stacs.inc; make the necessary change there; copy
theorems-ams.module to theorems-stacs.module; make the change there;
and then change stacs.layout so it does this: UseModule
theorems-stacs.module instead of using theorems-ams.module. (Note that
this is a default include: the user can override it in
DocumentSettings.)
In analogy, I'd just copy theorems-ams.module to theorems-stacs.module
and overwrite the offending parts from included files there.
If there are theorem environments other than the ones theorems-ams.inc
defines, then you will need to add those to theorems-stacs.inc, as well.
Otherwise, LyX won't know about them.
The good thing is that you only have to do this once. Then you can post
it on the wiki, or maybe your layout can even be included with LyX
itself.
Günter
Re: Sure-fire LyX layout files
On 11.09.08, rgheck wrote: Rich Shepard wrote: On Thu, 11 Sep 2008, Steve Litt wrote: I think part of what Steve wants, which other people have also wanted, is to be able to keep the layout file with the document ... Yes, I want to have additional styles for personal use but at the same time to keep the option to send my document to a colleague without with just the LyX standard layouts. The layouts module in 1.6 will alleviate this problem somewhat. In most cases, I suspect, the reason people will have lots of layouts is because they have various customizations to some base class that they want to apply in different combinations for different projects. This is precisely what layout modules are for. I am looking forward to this much cleaner way of adding my styles to the standard classes (hopefully a stable 1.6 is out soon). That said, sometimes you just want to add some layout information to one document. or, as stated above, to ship your private extensions with the LyX file. ** WARNING: Read what follows at your own risk! ** LyX 1.6 includes a facility that can also be used for this purpose. I call it local layout. ..., this is just layout information, embedded directly into the document. LyX reads it, if it's there, and uses it. There is, as yet, no UI for this, because it is really quite experimental and may prove dangerous. How about an embed button for selected modules? This way it would be easy to create self-contained lyx documents with private styles. You can create and test a module in ~/.lyx/layouts/ and if you want it in a document for others to use, simply embed it. (It will still show up in *your* modules list but not in everyones.) it'll be a trivial matter to add a simple UI, like the one for preamble. With appropriate warnings. Maybe this is not even needed with an embed button for modules. But still a possible supplement for one-off layouts. Personally, I don't want to see this overused. Part of the point of the way LyX uses layouts (and soon, modules) is to promote reusability. Local layout is not reusable except by cut-and-paste, and that's not really what one means by reusability. But there is also the problem with compatibility. My private reusable modules can (currently) not be used in files that should work everywhere. Maybe there could be an extract-module tool, that can extract embedded modules to ~/.lyx/layouts/ Günter
Re: LyX 1.5.6 & 1.6.0rc2 Theorem redefinition
On 11.09.08, rgheck wrote:
> Atlas wrote:
>> Background: * CLS file ==> www.stacs-conf.org/for_authors/stacs.cls
>> (note: stacs.cls
>> is based on amsart.cls)
...
>> * Conference-supplied TEX file (note: this file does not import correctly
>> nor compile in LyX 1.5.6 nor 1.6.0):
>> http://www.stacs-conf.org/for_authors/stacs-smp.tex
>> * In stacs-smp.tex, it states:
>> %% due to the dependence on amsart.cls, \begin{document} has to occur
>> %% BEFORE the title and author information: \begin{document}
As amsart.cls works with LyX, this should not be a problem.
>> \title[Using stacs.cls]{How to use stacs.cls} \author[lab1]{A.
>> Uthor}{Alice Uthor}
>> %% the abstract has to PRECEDE the command \maketitle: %% be sure not
>> to issue the \maketitle command twice! \begin{abstract} STUB.
>> \end{abstract} \maketitle
So you will need the InTitle flag for the Abstract style. This is already
true for the amsart layout.
>> QUESTION how would I get stacs-smp.tex to import and
>> compile correctly in LyX?
> You need a layout file for stacs.cls. See the Customization manual for
> the details. You can start by copying amsart.cls to stacs.cls and
> changing the first two lines to:
> #% Do not delete the line below; configure depends on this
> # \DeclareLaTeXClass{article (stacs)}
I would rather start with a new file and include amsart.layout:
#% Do not delete the line below; configure depends on this
# \DeclareLaTeXClass{article (stacs)}
input amsart.layout
Now you can add, overwrite, and disable layouts to adapt to the stacs class.
I do not know whether this works with 1.6, though.
Is there an analogy to NoStyle to undo UseModule calls (NoModule, say)?
>> - The problem is that LyX hides most of the details in its preamble
>> and also apparently inserts a redefinition of the theorem
>> environment.
> LyX adds this:
> \theoremstyle{plain}
> \newtheorem{thm}{Theorem}
> So you need to stop LyX from issuing this code.
> Fortunately, all of this is user-controllable.
In 1.5, add to your stacs.layout file
Style Theorem
Preamble
EndPreamble
End
to overwrite the Preamble definition in amsmaths.inc with an empty
preamble.
> In 1.6, the theorem layout is in theorems-ams.inc, which is included by
> the theorems-ams.module, which is included by default by amsart.layout.
> So you'd want to copy theorems-ams.inc to something like
> theorems-stacs.inc; make the necessary change there; copy
> theorems-ams.module to theorems-stacs.module; make the change there;
> and then change stacs.layout so it does this: UseModule
> theorems-stacs.module instead of using theorems-ams.module. (Note that
> this is a default include: the user can override it in
> Document>Settings.)
In analogy, I'd just copy theorems-ams.module to theorems-stacs.module
and overwrite the offending parts from included files there.
> If there are theorem environments other than the ones theorems-ams.inc
> defines, then you will need to add those to theorems-stacs.inc, as well.
> Otherwise, LyX won't know about them.
> The good thing is that you only have to do this once. Then you can post
> it on the wiki, or maybe your layout can even be included with LyX
> itself.
Günter
Re: Sure-fire LyX layout files
On 11.09.08, rgheck wrote: > Rich Shepard wrote: >> On Thu, 11 Sep 2008, Steve Litt wrote: > I think part of what Steve wants, which other people have also wanted, > is to be able to keep the layout file with the document ... Yes, I want to have additional styles for personal use but at the same time to keep the option to send my document to a colleague without with just the LyX standard layouts. > The layouts module in 1.6 will alleviate this problem somewhat. In most > cases, I suspect, the reason people will have lots of layouts is because > they have various customizations to some base class that they want to > apply in different combinations for different projects. This is > precisely what layout modules are for. I am looking forward to this much cleaner way of adding my styles to the standard classes (hopefully a stable 1.6 is out soon). > That said, sometimes you just want to add some layout information to one > document. or, as stated above, to ship your private extensions with the LyX file. > ** > WARNING: Read what follows at your own risk! > ** > LyX 1.6 includes a facility that can also be used for this purpose. I > call it "local layout". > ..., this is just layout information, embedded directly into > the document. LyX reads it, if it's there, and uses it. > There is, as yet, no UI for this, because it is really quite > experimental and may prove dangerous. How about an "embed" button for selected modules? This way it would be easy to create self-contained lyx documents with private styles. You can create and test a module in ~/.lyx/layouts/ and if you want it in a document for others to use, simply embed it. (It will still show up in *your* modules list but not in everyones.) > it'll be a trivial matter to add a simple UI, like the one for preamble. > With appropriate warnings. Maybe this is not even needed with an "embed" button for modules. But still a possible supplement for one-off layouts. > Personally, I don't want to see this overused. Part of the point of the > way LyX uses layouts (and soon, modules) is to promote reusability. > Local layout is not reusable except by cut-and-paste, and that's not > really what one means by "reusability". But there is also the problem with compatibility. My private reusable modules can (currently) not be used in files that should work everywhere. Maybe there could be an "extract-module" tool, that can extract embedded modules to ~/.lyx/layouts/ Günter
unicode in math
Dear LyX users,
with LyX 1.6, using unicode characters other than the first block is
possible also in math mode. The character in question is either replaced
by a math-equivalent (if defined in the unicodesymbols file) or by
text in math with the text-equivalent.
This is a vast improvement over the silent failure in LyX 1.5, my thanks
go out to the relevant developer(s)!
However, there remain some inconsistencies:
* while A is typeset italic, Ä (and other accented characters) are not.
* while l is typeset italic, λ (and other Greek characters) are not.
So, the question is:
* should Ä be replaced with \A in math?
More generally: should latin-1 supplement characters for which a math
equivalent exists use this instead of a text-version?
* should λ be replaced with \lambda in math?
More generally:
* should Greek characters from the Greek and Coptic
unicode block use the math-equivalent, or
* should only Greek symbols (from Greek and Coptic and/or from
Mathematical Alphanumeric Symbols) be converted to math symbols?
and could these also show as italic in the LyX GUI?
Attached is a patch for Greek in math.
Günter
--- /usr/local/src/lyx-devel/lib/unicodesymbols 2008-07-29 14:34:04.0 +0200
+++ /home/milde/.lyx16/unicodesymbols-greek-math 2008-09-07 21:15:59.0 +0200
@@ -737,30 +737,30 @@
0x038e \\textgreek{\char39U}textgreek # GREEK CAPITAL LETTER UPSILON WITH TONOS
0x038f \\textgreek{\char39W}textgreek # GREEK CAPITAL LETTER OMEGA WITH TONOS
0x0390 \\textgreek{\char242}textgreek # GREEK SMALL LETTER IOTA WITH DIALYTKA
-0x0391 \\textgreek{A} textgreek # GREEK CAPITAL LETTER ALPHA
-0x0392 \\textgreek{B} textgreek # GREEK CAPITAL LETTER BETA
-0x0393 \\textgreek{G} textgreek # GREEK CAPITAL LETTER GAMMA
-0x0394 \\textgreek{D} textgreek # GREEK CAPITAL LETTER DELTA
-0x0395 \\textgreek{E} textgreek # GREEK CAPITAL LETTER EPSILON
-0x0396 \\textgreek{Z} textgreek # GREEK CAPITAL LETTER ZETA
-0x0397 \\textgreek{H} textgreek # GREEK CAPITAL LETTER ETA
-0x0398 \\textgreek{J} textgreek # GREEK CAPITAL LETTER THETA
-0x0399 \\textgreek{I} textgreek # GREEK CAPITAL LETTER IOTA
-0x039a \\textgreek{K} textgreek # GREEK CAPITAL LETTER KAPPA
-0x039b \\textgreek{L} textgreek # GREEK CAPITAL LETTER LAMDA
-0x039c \\textgreek{M} textgreek # GREEK CAPITAL LETTER MU
-0x039d \\textgreek{N} textgreek # GREEK CAPITAL LETTER NU
-0x039e \\textgreek{X} textgreek # GREEK CAPITAL LETTER XI
-0x039f \\textgreek{O} textgreek # GREEK CAPITAL LETTER OMICRON
-0x03a0 \\textgreek{P} textgreek # GREEK CAPITAL LETTER PI
-0x03a1 \\textgreek{R} textgreek # GREEK CAPITAL LETTER RHO
-0x03a3 \\textgreek{S} textgreek # GREEK CAPITAL LETTER SIGMA
-0x03a4 \\textgreek{T} textgreek # GREEK CAPITAL LETTER TAU
-0x03a5 \\textgreek{U} textgreek # GREEK CAPITAL LETTER UPSILON
-0x03a6 \\textgreek{F} textgreek # GREEK CAPITAL LETTER PHI
-0x03a7 \\textgreek{Q} textgreek # GREEK CAPITAL LETTER CHI
-0x03a8 \\textgreek{Y} textgreek # GREEK CAPITAL LETTER PSI
-0x03a9 \\textgreek{W} textgreek # GREEK CAPITAL LETTER OMEGA
+0x0391 \\textgreek{A} textgreek # A # GREEK CAPITAL LETTER ALPHA
+0x0392 \\textgreek{B} textgreek # B # GREEK CAPITAL LETTER BETA
+0x0393 \\textgreek{G} textgreek \Gamma # GREEK CAPITAL LETTER GAMMA
+0x0394 \\textgreek{D} textgreek \Delta # GREEK CAPITAL LETTER DELTA
+0x0395 \\textgreek{E} textgreek # E # GREEK CAPITAL LETTER EPSILON
+0x0396 \\textgreek{Z} textgreek # Z # GREEK CAPITAL LETTER ZETA
+0x0397 \\textgreek{H} textgreek # H # GREEK CAPITAL LETTER ETA
+0x0398 \\textgreek{J} textgreek \Theta # GREEK CAPITAL LETTER THETA
+0x0399 \\textgreek{I} textgreek # I # GREEK CAPITAL LETTER IOTA
+0x039a \\textgreek{K} textgreek # K # GREEK CAPITAL LETTER KAPPA
+0x039b \\textgreek{L} textgreek \Lambda # GREEK CAPITAL LETTER LAMDA
+0x039c \\textgreek{M} textgreek # M # GREEK CAPITAL LETTER MU
+0x039d \\textgreek{N} textgreek # N # GREEK CAPITAL LETTER NU
+0x039e \\textgreek{X} textgreek \Xi # GREEK CAPITAL LETTER XI
+0x039f \\textgreek{O} textgreek # O # GREEK CAPITAL LETTER OMICRON
+0x03a0 \\textgreek{P} textgreek \Pi # GREEK CAPITAL LETTER PI
+0x03a1 \\textgreek{R} textgreek \Rho # GREEK CAPITAL LETTER RHO
+0x03a3 \\textgreek{S} textgreek \Sigma # GREEK CAPITAL LETTER SIGMA
+0x03a4 \\textgreek{T} textgreek # T # GREEK CAPITAL LETTER TAU
+0x03a5 \\textgreek{U} textgreek \Upsilon # GREEK CAPITAL LETTER UPSILON
+0x03a6 \\textgreek{F} textgreek \Phi # GREEK CAPITAL LETTER PHI
+0x03a7 \\textgreek{Q}
Re: Generating PDF/A from LyX/LaTeX
On 9.09.08, Steve Litt wrote:
On Tuesday 09 September 2008 12:54:38 pm Ernesto Posse wrote:
This question is not a LyX-only question, but I thought maybe someone
here could have an idea on this issue.
Has anyone succeeded in producing a PDF/A file (PDF for archival) from
LyX/LaTeX? I've tried tools that claim to generate PDF/A from
PostScript files or PDF files (both for Windows and Linux) but I
haven't been successful in generating a file which is considered PDF/A
compliant by at least two different validators, even with the
following minimal file (in LaTeX) via dvips:
=== file a.tex ===
\documentclass{article}
\begin{document}
Just this line...
\end{document}
=== end of file ===
The PDF/A Wikipedia page makes it look pretty straightforward -- all fonts
embedded, all fonts legal everywhere, no video, audio or javascript, device
independent color.
Maybe it's a font issue (the validator not knowing the CM latex fonts)?
How about trying the standard PS fonts, like
=== file a.tex ===
\documentclass{article}
\usepackage{mathptmx} % or \usepackage{mathpazo}
\begin{document}
Just this line...
\end{document}
=== end of file ===
?
Günter
Re: Ubuntu missing screen fonts for symbols: solution.
On 4.09.08, Pavel Sanda wrote: On 3.09.08, Paul Johnson wrote: In Debian, latex-xft-fonts is suggested. I agree that the more convincing recommended might be the better choice but there is no need to require latex-xft-fonts. i don't know how debian has handled this, but note, that lyx is shipped with bakoma fonts already, so there is no need to even recommend latex-xft-fonts; the only thing is that apt-get install those files correctly. The Debian lyx package does not ship the bakoma fonts. As there are more packages that need the latex math fonts as ttf, packing them separately in Debian is fine. However, as the fonts and LyX are found together ... in all but unusual installations, the dependency should be changed to Recommends. (@Sven: Should I still file a bug report?) Günter
unicode in math
Dear LyX users,
with LyX 1.6, using unicode characters other than the first block is
possible also in math mode. The character in question is either replaced
by a math-equivalent (if defined in the unicodesymbols file) or by
text in math with the text-equivalent.
This is a vast improvement over the silent failure in LyX 1.5, my thanks
go out to the relevant developer(s)!
However, there remain some inconsistencies:
* while A is typeset italic, Ä (and other accented characters) are not.
* while l is typeset italic, λ (and other Greek characters) are not.
So, the question is:
* should Ä be replaced with \A in math?
More generally: should latin-1 supplement characters for which a math
equivalent exists use this instead of a text-version?
* should λ be replaced with \lambda in math?
More generally:
* should Greek characters from the Greek and Coptic
unicode block use the math-equivalent, or
* should only Greek symbols (from Greek and Coptic and/or from
Mathematical Alphanumeric Symbols) be converted to math symbols?
and could these also show as italic in the LyX GUI?
Attached is a patch for Greek in math.
Günter
--- /usr/local/src/lyx-devel/lib/unicodesymbols 2008-07-29 14:34:04.0 +0200
+++ /home/milde/.lyx16/unicodesymbols-greek-math 2008-09-07 21:15:59.0 +0200
@@ -737,30 +737,30 @@
0x038e \\textgreek{\char39U}textgreek # GREEK CAPITAL LETTER UPSILON WITH TONOS
0x038f \\textgreek{\char39W}textgreek # GREEK CAPITAL LETTER OMEGA WITH TONOS
0x0390 \\textgreek{\char242}textgreek # GREEK SMALL LETTER IOTA WITH DIALYTKA
-0x0391 \\textgreek{A} textgreek # GREEK CAPITAL LETTER ALPHA
-0x0392 \\textgreek{B} textgreek # GREEK CAPITAL LETTER BETA
-0x0393 \\textgreek{G} textgreek # GREEK CAPITAL LETTER GAMMA
-0x0394 \\textgreek{D} textgreek # GREEK CAPITAL LETTER DELTA
-0x0395 \\textgreek{E} textgreek # GREEK CAPITAL LETTER EPSILON
-0x0396 \\textgreek{Z} textgreek # GREEK CAPITAL LETTER ZETA
-0x0397 \\textgreek{H} textgreek # GREEK CAPITAL LETTER ETA
-0x0398 \\textgreek{J} textgreek # GREEK CAPITAL LETTER THETA
-0x0399 \\textgreek{I} textgreek # GREEK CAPITAL LETTER IOTA
-0x039a \\textgreek{K} textgreek # GREEK CAPITAL LETTER KAPPA
-0x039b \\textgreek{L} textgreek # GREEK CAPITAL LETTER LAMDA
-0x039c \\textgreek{M} textgreek # GREEK CAPITAL LETTER MU
-0x039d \\textgreek{N} textgreek # GREEK CAPITAL LETTER NU
-0x039e \\textgreek{X} textgreek # GREEK CAPITAL LETTER XI
-0x039f \\textgreek{O} textgreek # GREEK CAPITAL LETTER OMICRON
-0x03a0 \\textgreek{P} textgreek # GREEK CAPITAL LETTER PI
-0x03a1 \\textgreek{R} textgreek # GREEK CAPITAL LETTER RHO
-0x03a3 \\textgreek{S} textgreek # GREEK CAPITAL LETTER SIGMA
-0x03a4 \\textgreek{T} textgreek # GREEK CAPITAL LETTER TAU
-0x03a5 \\textgreek{U} textgreek # GREEK CAPITAL LETTER UPSILON
-0x03a6 \\textgreek{F} textgreek # GREEK CAPITAL LETTER PHI
-0x03a7 \\textgreek{Q} textgreek # GREEK CAPITAL LETTER CHI
-0x03a8 \\textgreek{Y} textgreek # GREEK CAPITAL LETTER PSI
-0x03a9 \\textgreek{W} textgreek # GREEK CAPITAL LETTER OMEGA
+0x0391 \\textgreek{A} textgreek # A # GREEK CAPITAL LETTER ALPHA
+0x0392 \\textgreek{B} textgreek # B # GREEK CAPITAL LETTER BETA
+0x0393 \\textgreek{G} textgreek \Gamma # GREEK CAPITAL LETTER GAMMA
+0x0394 \\textgreek{D} textgreek \Delta # GREEK CAPITAL LETTER DELTA
+0x0395 \\textgreek{E} textgreek # E # GREEK CAPITAL LETTER EPSILON
+0x0396 \\textgreek{Z} textgreek # Z # GREEK CAPITAL LETTER ZETA
+0x0397 \\textgreek{H} textgreek # H # GREEK CAPITAL LETTER ETA
+0x0398 \\textgreek{J} textgreek \Theta # GREEK CAPITAL LETTER THETA
+0x0399 \\textgreek{I} textgreek # I # GREEK CAPITAL LETTER IOTA
+0x039a \\textgreek{K} textgreek # K # GREEK CAPITAL LETTER KAPPA
+0x039b \\textgreek{L} textgreek \Lambda # GREEK CAPITAL LETTER LAMDA
+0x039c \\textgreek{M} textgreek # M # GREEK CAPITAL LETTER MU
+0x039d \\textgreek{N} textgreek # N # GREEK CAPITAL LETTER NU
+0x039e \\textgreek{X} textgreek \Xi # GREEK CAPITAL LETTER XI
+0x039f \\textgreek{O} textgreek # O # GREEK CAPITAL LETTER OMICRON
+0x03a0 \\textgreek{P} textgreek \Pi # GREEK CAPITAL LETTER PI
+0x03a1 \\textgreek{R} textgreek \Rho # GREEK CAPITAL LETTER RHO
+0x03a3 \\textgreek{S} textgreek \Sigma # GREEK CAPITAL LETTER SIGMA
+0x03a4 \\textgreek{T} textgreek # T # GREEK CAPITAL LETTER TAU
+0x03a5 \\textgreek{U} textgreek \Upsilon # GREEK CAPITAL LETTER UPSILON
+0x03a6 \\textgreek{F} textgreek \Phi # GREEK CAPITAL LETTER PHI
+0x03a7 \\textgreek{Q}
Re: Generating PDF/A from LyX/LaTeX
On 9.09.08, Steve Litt wrote:
On Tuesday 09 September 2008 12:54:38 pm Ernesto Posse wrote:
This question is not a LyX-only question, but I thought maybe someone
here could have an idea on this issue.
Has anyone succeeded in producing a PDF/A file (PDF for archival) from
LyX/LaTeX? I've tried tools that claim to generate PDF/A from
PostScript files or PDF files (both for Windows and Linux) but I
haven't been successful in generating a file which is considered PDF/A
compliant by at least two different validators, even with the
following minimal file (in LaTeX) via dvips:
=== file a.tex ===
\documentclass{article}
\begin{document}
Just this line...
\end{document}
=== end of file ===
The PDF/A Wikipedia page makes it look pretty straightforward -- all fonts
embedded, all fonts legal everywhere, no video, audio or javascript, device
independent color.
Maybe it's a font issue (the validator not knowing the CM latex fonts)?
How about trying the standard PS fonts, like
=== file a.tex ===
\documentclass{article}
\usepackage{mathptmx} % or \usepackage{mathpazo}
\begin{document}
Just this line...
\end{document}
=== end of file ===
?
Günter
Re: Ubuntu missing screen fonts for symbols: solution.
On 4.09.08, Pavel Sanda wrote: On 3.09.08, Paul Johnson wrote: In Debian, latex-xft-fonts is suggested. I agree that the more convincing recommended might be the better choice but there is no need to require latex-xft-fonts. i don't know how debian has handled this, but note, that lyx is shipped with bakoma fonts already, so there is no need to even recommend latex-xft-fonts; the only thing is that apt-get install those files correctly. The Debian lyx package does not ship the bakoma fonts. As there are more packages that need the latex math fonts as ttf, packing them separately in Debian is fine. However, as the fonts and LyX are found together ... in all but unusual installations, the dependency should be changed to Recommends. (@Sven: Should I still file a bug report?) Günter
unicode in math
Dear LyX users,
with LyX 1.6, using unicode characters other than the first block is
possible also in math mode. The character in question is either replaced
by a math-equivalent (if defined in the "unicodesymbols" file) or by
"text in math" with the text-equivalent.
This is a vast improvement over the silent failure in LyX 1.5, my thanks
go out to the relevant developer(s)!
However, there remain some inconsistencies:
* while A is typeset italic, Ä (and other accented characters) are not.
* while l is typeset italic, λ (and other Greek characters) are not.
So, the question is:
* should Ä be replaced with \"A in math?
More generally: should "latin-1 supplement" characters for which a math
equivalent exists use this instead of a text-version?
* should λ be replaced with \lambda in math?
More generally:
* should Greek characters from the "Greek and Coptic"
unicode block use the math-equivalent, or
* should only Greek symbols (from Greek and Coptic" and/or from
"Mathematical Alphanumeric Symbols") be converted to math symbols?
and could these also show as italic in the LyX GUI?
Attached is a patch for Greek in math.
Günter
--- /usr/local/src/lyx-devel/lib/unicodesymbols 2008-07-29 14:34:04.0 +0200
+++ /home/milde/.lyx16/unicodesymbols-greek-math 2008-09-07 21:15:59.0 +0200
@@ -737,30 +737,30 @@
0x038e "\\textgreek{\char39U}""textgreek" "" # GREEK CAPITAL LETTER UPSILON WITH TONOS
0x038f "\\textgreek{\char39W}""textgreek" "" # GREEK CAPITAL LETTER OMEGA WITH TONOS
0x0390 "\\textgreek{\char242}""textgreek" "" # GREEK SMALL LETTER IOTA WITH DIALYTKA
-0x0391 "\\textgreek{A}" "textgreek" "" # GREEK CAPITAL LETTER ALPHA
-0x0392 "\\textgreek{B}" "textgreek" "" # GREEK CAPITAL LETTER BETA
-0x0393 "\\textgreek{G}" "textgreek" "" # GREEK CAPITAL LETTER GAMMA
-0x0394 "\\textgreek{D}" "textgreek" "" # GREEK CAPITAL LETTER DELTA
-0x0395 "\\textgreek{E}" "textgreek" "" # GREEK CAPITAL LETTER EPSILON
-0x0396 "\\textgreek{Z}" "textgreek" "" # GREEK CAPITAL LETTER ZETA
-0x0397 "\\textgreek{H}" "textgreek" "" # GREEK CAPITAL LETTER ETA
-0x0398 "\\textgreek{J}" "textgreek" "" # GREEK CAPITAL LETTER THETA
-0x0399 "\\textgreek{I}" "textgreek" "" # GREEK CAPITAL LETTER IOTA
-0x039a "\\textgreek{K}" "textgreek" "" # GREEK CAPITAL LETTER KAPPA
-0x039b "\\textgreek{L}" "textgreek" "" # GREEK CAPITAL LETTER LAMDA
-0x039c "\\textgreek{M}" "textgreek" "" # GREEK CAPITAL LETTER MU
-0x039d "\\textgreek{N}" "textgreek" "" # GREEK CAPITAL LETTER NU
-0x039e "\\textgreek{X}" "textgreek" "" # GREEK CAPITAL LETTER XI
-0x039f "\\textgreek{O}" "textgreek" "" # GREEK CAPITAL LETTER OMICRON
-0x03a0 "\\textgreek{P}" "textgreek" "" # GREEK CAPITAL LETTER PI
-0x03a1 "\\textgreek{R}" "textgreek" "" # GREEK CAPITAL LETTER RHO
-0x03a3 "\\textgreek{S}" "textgreek" "" # GREEK CAPITAL LETTER SIGMA
-0x03a4 "\\textgreek{T}" "textgreek" "" # GREEK CAPITAL LETTER TAU
-0x03a5 "\\textgreek{U}" "textgreek" "" # GREEK CAPITAL LETTER UPSILON
-0x03a6 "\\textgreek{F}" "textgreek" "" # GREEK CAPITAL LETTER PHI
-0x03a7 "\\textgreek{Q}" "textgreek" "" # GREEK CAPITAL LETTER CHI
-0x03a8 "\\textgreek{Y}" "textgreek" "" # GREEK CAPITAL LETTER PSI
-0x03a9 "\\textgreek{W}" "textgreek" "" # GREEK CAPITAL LETTER OMEGA
+0x0391 "\\textgreek{A}" "textgreek" "" # "A" # GREEK CAPITAL LETTER ALPHA
+0x0392 "\\textgreek{B}" "textgreek" "" # "B" # GREEK CAPITAL LETTER BETA
+0x0393 "\\textgreek{G}" "textgreek" "" "\Gamma" # GREEK CAPITAL LETTER GAMMA
+0x0394 "\\textgreek{D}" "textgreek" "" "\Delta" # GREEK CAPITAL LETTER DELTA
+0x0395 "\\textgreek{E}" "textgreek" "" # "E" # GREEK CAPITAL LETTER EPSILON
+0x0396 "\\textgreek{Z}" "textgreek" "" # "Z" # GREEK CAPITAL LETTER ZETA
+0x0397 "\\textgreek{H}" "textgreek" "" # "H" # GREEK CAPITAL LETTER ETA
+0x0398 "\\textgreek{J}" "textgreek" "" "\Theta" # GREEK CAPITAL LETTER THETA
+0x0399 "\\textgreek{I}" "textgreek" "" # "I" # GREEK CAPITAL LETTER IOTA
+0x039a "\\textgreek{K}" "textgreek" "" # "K" # GREEK CAPITAL LETTER KAPPA
+0x039b "\\textgreek{L}" "textgreek" "" "\Lambda" # GREEK CAPITAL LETTER LAMDA
+0x039c "\\textgreek{M}" "textgreek" "" # "M" # GREEK CAPITAL LETTER MU
+0x039d "\\textgreek{N}" "textgreek" "" # "N" # GREEK CAPITAL LETTER NU
+0x039e "\\textgreek{X}" "textgreek" "" "\Xi" # GREEK CAPITAL LETTER XI
+0x039f "\\textgreek{O}" "textgreek" "" # "O" # GREEK CAPITAL LETTER OMICRON
+0x03a0 "\\textgreek{P}" "textgreek" "" "\Pi" # GREEK CAPITAL LETTER PI
+0x03a1 "\\textgreek{R}" "textgreek" "" "\Rho" # GREEK CAPITAL LETTER RHO
+0x03a3 "\\textgreek{S}"
Re: Generating PDF/A from LyX/LaTeX
On 9.09.08, Steve Litt wrote:
> > > On Tuesday 09 September 2008 12:54:38 pm Ernesto Posse wrote:
> > >> This question is not a LyX-only question, but I thought maybe someone
> > >> here could have an idea on this issue.
> > >>
> > >> Has anyone succeeded in producing a PDF/A file (PDF for archival) from
> > >> LyX/LaTeX? I've tried tools that claim to generate PDF/A from
> > >> PostScript files or PDF files (both for Windows and Linux) but I
> > >> haven't been successful in generating a file which is considered PDF/A
> > >> compliant by at least two different validators, even with the
> > >> following minimal file (in LaTeX) via dvips:
> > >>
> > >> === file a.tex ===
> > >> \documentclass{article}
> > >> \begin{document}
> > >> Just this line...
> > >> \end{document}
> > >> === end of file ===
> The PDF/A Wikipedia page makes it look pretty straightforward -- all fonts
> embedded, all fonts legal everywhere, no video, audio or javascript, device
> independent color.
Maybe it's a font issue (the validator not knowing the CM latex fonts)?
How about trying the standard PS fonts, like
=== file a.tex ===
\documentclass{article}
\usepackage{mathptmx} % or \usepackage{mathpazo}
\begin{document}
Just this line...
\end{document}
=== end of file ===
?
Günter
Re: Ubuntu missing screen fonts for symbols: solution.
On 4.09.08, Pavel Sanda wrote: > > On 3.09.08, Paul Johnson wrote: > > > > > In Debian, latex-xft-fonts is "suggested". I agree that the more > > > convincing "recommended" might be the better choice but there is no > > > need to "require" latex-xft-fonts. > i don't know how debian has handled this, but note, that lyx is shipped > with bakoma fonts already, so there is no need to even recommend > latex-xft-fonts; the only thing is that apt-get install those files > correctly. The Debian lyx package does not ship the bakoma fonts. As there are more packages that need the latex math fonts as ttf, packing them separately in Debian is fine. However, as the fonts and LyX are "found together ... in all but unusual installations", the dependency should be changed to "Recommends". (@Sven: Should I still file a bug report?) Günter
Re: OT: post-process postscript or PDF document to add page numbering and footer
On 6.09.08, Jeremy C. Reed wrote: I am looking for a solution to add running page numbering to a postscript or PDF document and maybe add a footer or header (maybe with a horizontal rule). I suppose scribus (www.scribus.net) is able to do this (in a WYSIWYG manner). It is a page layout program producing printer-ready PDF of professional quality and comes with a QT GUI. Günter
Re: Koma-script chapterentry font option
On 6.09.08, Guillaume Larocque wrote: Jean-Marie Pacquet a écrit : Is there any way I can change that font?? chapterentry does not belong to the list of elements whose type style can be changed with these commands. Maybe this is a new feature. Do the versions of the documentation and the used style files match? My scrguide.pdf says: Der Eintrag für die oberste Gliederungsebene unter \part, also \chapter bei scrbook und scrreprt beziehungsweise \section bei scrartcl wird nicht eingerückt. Dafür findet auf ihn die Schriftart für das Element sectioning (siehe Tabelle 3.3, Seite 61) Anwendung. so you could try configuring sectioning instead of chapterentry. Günter
Re: lyx 1.60cr2 issues
On 8.09.08, Matthew wrote:
... the export document command doesn't appear to generate any output,
... In particular I'm trying to convert a lyx 1.6 file back into a
1.5.3 file so that I can run a more 'stable' version.
Besides the bug mentionend in another reply: The default settings will
use the extension .lyx15 for the exported file and the file-open
dialogue in LyX-1.5 will not show it, as it expects a .lyx extension.
My next problem is the bold font toggling in math mode. ctrl-B generates a
default \mathsymbol{} command which is wrong wrong wrong!
No, not generally!
A bold math character should almost always be non-italicized. The one
exception may be Greek characters, but only because Latex has issues
with that anyway. The reason is that a bold letter represents a vector
or matrix, which should never be in italic font.
The `International Union of Pure and Applied Physics` (IUPAP) and other
international bodies recommend typsetting math according to International
Standards ISO 31-0:1992 to ISO 31-13:1992 (see also [NIST]_).
The traditional `LaTeX-style` deviates in some points from this rules:
* The ``\vec`` command produces an array accent, while ISO 31 recommends
an italic-bold typeface for vector symbols.
.. [NIST] Typefaces for Symbols in Scientific Manuscripts:
http://physics.nist.gov/Document/typefaces.pdf
-- http://pylit.berlios.de/examples/isomath.sty.html
Günter
Re: lyx 1.60cr2 issues
On 9.09.08, Konrad Hofbauer wrote: G. Milde wrote: Besides the bug mentionend in another reply: The default settings will use the extension .lyx15 for the exported file and the file-open dialogue in LyX-1.5 will not show it, as it expects a .lyx extension. At least here on the Mac LyX-1.5.6 DOES show the .lyx15-files. Here at Debian Linux; LyX 1.5.6 the file-open dialogue does * NOT show *.lyx15 with the default filter setting LyX files (*.lyx), * show them (of course) with All files (*). But in the second case also all sort of irrelevant files are shown. I solved this (partially) with changing the settings under ToolsPreferencesFile HandlingFile formats Format: Lyx 1.5 Extension from lyx15 to 15.lyx. Günter
Re: OT: post-process postscript or PDF document to add page numbering and footer
On 6.09.08, Jeremy C. Reed wrote: I am looking for a solution to add running page numbering to a postscript or PDF document and maybe add a footer or header (maybe with a horizontal rule). I suppose scribus (www.scribus.net) is able to do this (in a WYSIWYG manner). It is a page layout program producing printer-ready PDF of professional quality and comes with a QT GUI. Günter
Re: Koma-script chapterentry font option
On 6.09.08, Guillaume Larocque wrote: Jean-Marie Pacquet a écrit : Is there any way I can change that font?? chapterentry does not belong to the list of elements whose type style can be changed with these commands. Maybe this is a new feature. Do the versions of the documentation and the used style files match? My scrguide.pdf says: Der Eintrag für die oberste Gliederungsebene unter \part, also \chapter bei scrbook und scrreprt beziehungsweise \section bei scrartcl wird nicht eingerückt. Dafür findet auf ihn die Schriftart für das Element sectioning (siehe Tabelle 3.3, Seite 61) Anwendung. so you could try configuring sectioning instead of chapterentry. Günter
Re: lyx 1.60cr2 issues
On 8.09.08, Matthew wrote:
... the export document command doesn't appear to generate any output,
... In particular I'm trying to convert a lyx 1.6 file back into a
1.5.3 file so that I can run a more 'stable' version.
Besides the bug mentionend in another reply: The default settings will
use the extension .lyx15 for the exported file and the file-open
dialogue in LyX-1.5 will not show it, as it expects a .lyx extension.
My next problem is the bold font toggling in math mode. ctrl-B generates a
default \mathsymbol{} command which is wrong wrong wrong!
No, not generally!
A bold math character should almost always be non-italicized. The one
exception may be Greek characters, but only because Latex has issues
with that anyway. The reason is that a bold letter represents a vector
or matrix, which should never be in italic font.
The `International Union of Pure and Applied Physics` (IUPAP) and other
international bodies recommend typsetting math according to International
Standards ISO 31-0:1992 to ISO 31-13:1992 (see also [NIST]_).
The traditional `LaTeX-style` deviates in some points from this rules:
* The ``\vec`` command produces an array accent, while ISO 31 recommends
an italic-bold typeface for vector symbols.
.. [NIST] Typefaces for Symbols in Scientific Manuscripts:
http://physics.nist.gov/Document/typefaces.pdf
-- http://pylit.berlios.de/examples/isomath.sty.html
Günter
Re: lyx 1.60cr2 issues
On 9.09.08, Konrad Hofbauer wrote: G. Milde wrote: Besides the bug mentionend in another reply: The default settings will use the extension .lyx15 for the exported file and the file-open dialogue in LyX-1.5 will not show it, as it expects a .lyx extension. At least here on the Mac LyX-1.5.6 DOES show the .lyx15-files. Here at Debian Linux; LyX 1.5.6 the file-open dialogue does * NOT show *.lyx15 with the default filter setting LyX files (*.lyx), * show them (of course) with All files (*). But in the second case also all sort of irrelevant files are shown. I solved this (partially) with changing the settings under ToolsPreferencesFile HandlingFile formats Format: Lyx 1.5 Extension from lyx15 to 15.lyx. Günter
Re: OT: post-process postscript or PDF document to add page numbering and footer
On 6.09.08, Jeremy C. Reed wrote: > I am looking for a solution to add running page numbering to a postscript > or PDF document and maybe add a footer or header (maybe with a horizontal > rule). I suppose scribus (www.scribus.net) is able to do this (in a WYSIWYG manner). It is a page layout program producing printer-ready PDF of professional quality and comes with a QT GUI. Günter
Re: Koma-script chapterentry font option
On 6.09.08, Guillaume Larocque wrote: > Jean-Marie Pacquet a écrit : >>> Is there any way I can change that font?? >> "chapterentry" does not belong to the list of elements whose type >> style can be changed with these commands. Maybe this is a new feature. Do the versions of the documentation and the used style files match? My scrguide.pdf says: Der Eintrag für die oberste Gliederungsebene unter \part, also \chapter bei scrbook und scrreprt beziehungsweise \section bei scrartcl wird nicht eingerückt. Dafür findet auf ihn die Schriftart für das Element sectioning (siehe Tabelle 3.3, Seite 61) Anwendung. so you could try configuring "sectioning" instead of "chapterentry". Günter
Re: lyx 1.60cr2 issues
On 8.09.08, Matthew wrote:
> ... the export document command doesn't appear to generate any output,
> ... In particular I'm trying to convert a lyx 1.6 file back into a
> 1.5.3 file so that I can run a more 'stable' version.
Besides the bug mentionend in another reply: The default settings will
use the extension ".lyx15" for the exported file and the file-open
dialogue in LyX-1.5 will not show it, as it expects a ".lyx" extension.
> My next problem is the bold font toggling in math mode. ctrl-B generates a
> default \mathsymbol{} command which is wrong wrong wrong!
No, not generally!
> A bold math character should almost always be non-italicized. The one
> exception may be Greek characters, but only because Latex has issues
> with that anyway. The reason is that a bold letter represents a vector
> or matrix, which should never be in italic font.
The `International Union of Pure and Applied Physics` (IUPAP) and other
international bodies recommend typsetting math according to International
Standards ISO 31-0:1992 to ISO 31-13:1992 (see also [NIST]_).
The traditional `LaTeX-style` deviates in some points from this rules:
* The ``\vec`` command produces an array accent, while ISO 31 recommends
an italic-bold typeface for vector symbols.
.. [NIST] Typefaces for Symbols in Scientific Manuscripts:
http://physics.nist.gov/Document/typefaces.pdf
-- http://pylit.berlios.de/examples/isomath.sty.html
Günter
Re: lyx 1.60cr2 issues
On 9.09.08, Konrad Hofbauer wrote: > G. Milde wrote: >> Besides the bug mentionend in another reply: The default settings will >> use the extension ".lyx15" for the exported file and the file-open >> dialogue in LyX-1.5 will not show it, as it expects a ".lyx" extension. > At least here on the Mac LyX-1.5.6 DOES show the .lyx15-files. Here at Debian Linux; LyX 1.5.6 the file-open dialogue does * NOT show *.lyx15 with the default filter setting "LyX files (*.lyx)", * show them (of course) with "All files (*)". But in the second case also all sort of irrelevant files are shown. I solved this (partially) with changing the settings under Tools>Preferences>File Handling>File formats> Format: Lyx 1.5 > Extension from lyx15 to 15.lyx. Günter
Re: Ubuntu missing screen fonts for symbols: solution.
On 3.09.08, Paul Johnson wrote: I was asking about missing or incorrect symbols yesterday. I found a solution. I can only spead for Debian, but as Ubuntu uses the same package format, things might be similar. In Lyx on Ubuntu 8.04, I noticed that SOME mathematical characters do not show properly on the screen. ... So far, in Ubuntu, I've found 2 solutions. One approach is to install the font package http://movementarian.org/latex-xft-fonts-0.1.tar.gz; under ~/.fonts and run fc-cache -fv. ... the above workaround also works if one uses the supposedly better BaKoMa fonts, but I don't see much difference myself. ... After some googling, I learned that cmsy10.ttf is available as an optional Ubuntu package latex-xft-fonts. The apt-file command (package apt-file) provides a convenient way to find out which Debian (or Ubuntu?) package a given file is in. Generally, if I have the choice between installing from a tar-archive or a package for my system, I prefer the package. Example: before downloading and installing the recommended latex-xft-fonts tarball, I'll check in my install-manager (aptitude) whether a package of same (or similar) name is available. So I suppose that many Ubuntu users have that installed automatically so they never fight the mystery of missing screen fonts. I'll suggest to Ubuntu's lyx packager that latex-xft-fonts should be a required package. In Debian, latex-xft-fonts is suggested. I agree that the more convincing recommended might be the better choice but there is no need to require latex-xft-fonts. (Require means that the requiring package is completely broken without the requirement, while recommended means that without the recommended package the behaviour is impaired in some way.) Günter
Re: LyX 1.6 PDF output
On 4.09.08, Julio Rojas wrote: I just saw thru Adobe Reader that fonts are embedded in the document. Almost all of them are Type 1, but there's one, called F15, which is Type 3. Could it be the culprit? Is there any way I can replace this font? You might search the latex log to see if F15 pops up there. Maybe it comes from the included eps files, though. (Try without included eps and check the embedded fonts again...) GM
Re: Ubuntu missing screen fonts for symbols: solution.
On 3.09.08, Paul Johnson wrote: I was asking about missing or incorrect symbols yesterday. I found a solution. I can only spead for Debian, but as Ubuntu uses the same package format, things might be similar. In Lyx on Ubuntu 8.04, I noticed that SOME mathematical characters do not show properly on the screen. ... So far, in Ubuntu, I've found 2 solutions. One approach is to install the font package http://movementarian.org/latex-xft-fonts-0.1.tar.gz; under ~/.fonts and run fc-cache -fv. ... the above workaround also works if one uses the supposedly better BaKoMa fonts, but I don't see much difference myself. ... After some googling, I learned that cmsy10.ttf is available as an optional Ubuntu package latex-xft-fonts. The apt-file command (package apt-file) provides a convenient way to find out which Debian (or Ubuntu?) package a given file is in. Generally, if I have the choice between installing from a tar-archive or a package for my system, I prefer the package. Example: before downloading and installing the recommended latex-xft-fonts tarball, I'll check in my install-manager (aptitude) whether a package of same (or similar) name is available. So I suppose that many Ubuntu users have that installed automatically so they never fight the mystery of missing screen fonts. I'll suggest to Ubuntu's lyx packager that latex-xft-fonts should be a required package. In Debian, latex-xft-fonts is suggested. I agree that the more convincing recommended might be the better choice but there is no need to require latex-xft-fonts. (Require means that the requiring package is completely broken without the requirement, while recommended means that without the recommended package the behaviour is impaired in some way.) Günter
Re: LyX 1.6 PDF output
On 4.09.08, Julio Rojas wrote: I just saw thru Adobe Reader that fonts are embedded in the document. Almost all of them are Type 1, but there's one, called F15, which is Type 3. Could it be the culprit? Is there any way I can replace this font? You might search the latex log to see if F15 pops up there. Maybe it comes from the included eps files, though. (Try without included eps and check the embedded fonts again...) GM
Re: Ubuntu missing screen fonts for symbols: solution.
On 3.09.08, Paul Johnson wrote:
> I was asking about missing or incorrect symbols yesterday. I found a
> solution.
I can only spead for Debian, but as Ubuntu uses the same package
format, things might be similar.
> In Lyx on Ubuntu 8.04, I noticed that SOME mathematical characters do
> not show properly on the screen.
...
> So far, in Ubuntu, I've found 2 solutions.
> One approach is to install the font package
> "http://movementarian.org/latex-xft-fonts-0.1.tar.gz; under ~/.fonts
> and run "fc-cache -fv".
...
> the above workaround also works if one uses the supposedly better
> BaKoMa fonts, but I don't see much difference myself.
...
> After some googling, I learned that "cmsy10.ttf" is available as an
> optional Ubuntu package "latex-xft-fonts".
The apt-file command (package apt-file) provides a convenient way to
find out which Debian (or Ubuntu?) package a given file is in.
Generally, if I have the choice between installing from a tar-archive
or a package for my system, I prefer the package.
Example: before downloading and installing the recommended
latex-xft-fonts tarball, I'll check in my install-manager (aptitude)
whether a package of same (or similar) name is available.
> So I suppose that many Ubuntu users have that installed automatically
> so they never fight the mystery of missing screen fonts. I'll suggest
> to Ubuntu's lyx packager that latex-xft-fonts should be a required
> package.
In Debian, latex-xft-fonts is "suggested". I agree that the more
convincing "recommended" might be the better choice but there is no need
to "require" latex-xft-fonts.
("Require" means that the requiring package is completely broken without
the requirement, while "recommended" means that without the recommended
package the behaviour is impaired in some way.)
Günter
Re: LyX 1.6 PDF output
On 4.09.08, Julio Rojas wrote: > I just saw thru Adobe Reader that fonts are embedded in the document. > Almost all of them are Type 1, but there's one, called F15, which is > Type 3. Could it be the culprit? Is there any way I can replace this > font? You might search the latex log to see if F15 pops up there. Maybe it comes from the included eps files, though. (Try without included eps and check the embedded fonts again...) GM
Re: view PDF doesn't work with a certain mathematical formula
On 3.09.08, Florin Oprina wrote: On Wed, Sep 3, 2008 at 1:15 PM, Eric Cavalcanti BTW, I notice that in the endocing drop-down list there are utf8 and UTF8 (not to mention utf8-plain and utf8x). Does anyone know what the differences between them are? It is described in the UserGuide in Attachment A.6 The Document Menu and now also in http://wiki.lyx.org/LyX/Unicode. In LyX 1.6 the encodings drop-down list will use user-friendly GUI names (see also http://bugzilla.lyx.org/show_bug.cgi?id=4971). Günter
Re: view PDF doesn't work with a certain mathematical formula
On 3.09.08, Florin Oprina wrote: On Wed, Sep 3, 2008 at 1:15 PM, Eric Cavalcanti BTW, I notice that in the endocing drop-down list there are utf8 and UTF8 (not to mention utf8-plain and utf8x). Does anyone know what the differences between them are? It is described in the UserGuide in Attachment A.6 The Document Menu and now also in http://wiki.lyx.org/LyX/Unicode. In LyX 1.6 the encodings drop-down list will use user-friendly GUI names (see also http://bugzilla.lyx.org/show_bug.cgi?id=4971). Günter
Re: view PDF doesn't work with a certain mathematical formula
On 3.09.08, Florin Oprina wrote: > On Wed, Sep 3, 2008 at 1:15 PM, Eric Cavalcanti > BTW, I notice that in the endocing drop-down list there are utf8 and UTF8 > (not to mention utf8-plain and utf8x). Does anyone know what the differences > between them are? It is described in the UserGuide in Attachment A.6 "The Document Menu" and now also in http://wiki.lyx.org/LyX/Unicode. In LyX 1.6 the encodings drop-down list will use user-friendly "GUI names" (see also http://bugzilla.lyx.org/show_bug.cgi?id=4971). Günter
Re: LyX 1.6
On 2.09.08, Andre Poenitz wrote: On Mon, Sep 01, 2008 at 03:02:33PM -0600, James Sutherland wrote: On Sep 1, 2008, at 1:31 PM, Louis A. Turk wrote: Is LyX 1.6 going to be able to use files made by LyX 1.6? If you mean is 1.6 going to be able to use files made by 1.5 then the answer is YES. Incidentally, the answer to the original question is, 'yes', too ;-) However, if the question was is 1.5 going to be able to use files made by 1.6, the answer is IT DEPENDS: * = 1.5.6 NO * upcoming 1.5.7 YES * files exported with FileExportLyX15 YES GM
Re: references between child documents
On 2.09.08, Joao P Leitao wrote: Hi, I'm using Lyx for a few weeks and have a few child documents. I'd like to reference a Chapter of child document A in child document B. If you open the parent document first and from it the child documents (right-click on the Include button and click on open, or just compile the parent), the InsertReference dialog should sport a combo-box to choose between the child documents. GM
Re: LyX 1.6
On 2.09.08, Andre Poenitz wrote: On Mon, Sep 01, 2008 at 03:02:33PM -0600, James Sutherland wrote: On Sep 1, 2008, at 1:31 PM, Louis A. Turk wrote: Is LyX 1.6 going to be able to use files made by LyX 1.6? If you mean is 1.6 going to be able to use files made by 1.5 then the answer is YES. Incidentally, the answer to the original question is, 'yes', too ;-) However, if the question was is 1.5 going to be able to use files made by 1.6, the answer is IT DEPENDS: * = 1.5.6 NO * upcoming 1.5.7 YES * files exported with FileExportLyX15 YES GM
Re: references between child documents
On 2.09.08, Joao P Leitao wrote: Hi, I'm using Lyx for a few weeks and have a few child documents. I'd like to reference a Chapter of child document A in child document B. If you open the parent document first and from it the child documents (right-click on the Include button and click on open, or just compile the parent), the InsertReference dialog should sport a combo-box to choose between the child documents. GM
Re: LyX 1.6
On 2.09.08, Andre Poenitz wrote: > On Mon, Sep 01, 2008 at 03:02:33PM -0600, James Sutherland wrote: > > On Sep 1, 2008, at 1:31 PM, Louis A. Turk wrote: > > > >> Is LyX 1.6 going to be able to use files made by LyX 1.6? > > > > If you mean "is 1.6 going to be able to use files made by 1.5" then the > > answer is YES. > Incidentally, the answer to the original question is, 'yes', too ;-) However, if the question was "is 1.5 going to be able to use files made by 1.6", the answer is IT DEPENDS: * <= 1.5.6 NO * upcoming 1.5.7 YES * files exported with File>Export>LyX15 YES GM
Re: references between child documents
On 2.09.08, Joao P Leitao wrote: > Hi, > I'm using Lyx for a few weeks and have a few child documents. I'd like > to reference a Chapter of "child document A" in "child document B". If you open the parent document first and from it the child documents (right-click on the Include button and click on open, or just compile the parent), the Insert>Reference dialog should sport a combo-box to choose between the child documents. GM
Re: Times Roman vs Latin Modern Roman Font
On 29.08.08, William Adams wrote: On Aug 29, 2008, at 6:30 AM, G. Milde wrote: There is no Palatino Sans Actually, the new Palatino Nova family introduces Palatino Sans and Palatino Sans Informal. More actually, Palatino Sans is a new typeface, not part of but related to Palatino Nova (but as well and as close to the traditional Palatino families). http://www.linotype.com/3201/palatinosans.html However, it is not free. GM
Re: Using Lyx with Xetex and french accents
On 31.08.08, Nicolas Triart wrote: I am using Lyx 1.5.6. I followed the instructions on the wiki to make it works with Xetex (included in MikTex 2.7). ... The problem is that when I write something in french the accents are missing on the output document. Did you set DocumentSettingsLanguage Encoding to utf8-plain? Could you append a minimal example file? Günter
Re: Times Roman vs Latin Modern Roman Font
On 29.08.08, William Adams wrote: On Aug 29, 2008, at 6:30 AM, G. Milde wrote: There is no Palatino Sans Actually, the new Palatino Nova family introduces Palatino Sans and Palatino Sans Informal. More actually, Palatino Sans is a new typeface, not part of but related to Palatino Nova (but as well and as close to the traditional Palatino families). http://www.linotype.com/3201/palatinosans.html However, it is not free. GM
Re: Using Lyx with Xetex and french accents
On 31.08.08, Nicolas Triart wrote: I am using Lyx 1.5.6. I followed the instructions on the wiki to make it works with Xetex (included in MikTex 2.7). ... The problem is that when I write something in french the accents are missing on the output document. Did you set DocumentSettingsLanguage Encoding to utf8-plain? Could you append a minimal example file? Günter
Re: Times Roman vs Latin Modern Roman Font
On 29.08.08, William Adams wrote: > On Aug 29, 2008, at 6:30 AM, G. Milde wrote: >> There is no Palatino Sans > Actually, the new Palatino Nova family introduces Palatino Sans and > Palatino Sans Informal. More actually, Palatino Sans is a new typeface, not part of but related to Palatino Nova (but as well and as close to the "traditional" Palatino families). http://www.linotype.com/3201/palatinosans.html However, it is not free. GM
Re: Using Lyx with Xetex and french accents
On 31.08.08, Nicolas Triart wrote: > I am using Lyx 1.5.6. I followed the instructions on the wiki to make it > works with Xetex (included in MikTex 2.7). ... > The problem is that when I write > something in french the accents are missing on the output document. Did you set Document>Settings>Language Encoding to utf8-plain? Could you append a minimal example file? Günter
Re: tab through eqnarray environment - bug in 1.6rc1?
On 29.08.08, Abdelrazak Younes wrote: James Sutherland wrote: Shift-Tab cycles in reverse as it has in the past, but Tab does not cycle forward... This is a known problem that we intend to fix before 1.6.0. The problem is that the completion framework monopolize the tab key for requesting completion. Just courious: * even if the completion feature is switched off? * is the Tab binding hard-coded or configurable? We need to find a good key in replacement for tab but we didn't reach a consensus yet. Feel free to suggest something. In my favourite text editor, I use Ctrl-A for completion and Tab for indenting. But IMO, there is need for configurable adaptive keybindings: user configurable: This is already possible (via the *.bind files and since 1.6 also via GUI) adaptive: smart bindings that take into account the context, e.g. the same key should be configurable to different lfuns in math and text mode. There are simply too few keys for too many actions, so we should avoid bindings that result in command disabled. Günter
Re: Times Roman vs Latin Modern Roman Font
On 28.08.08, Paul A. Rubin wrote:
Rich Shepard wrote:
My default typeface is Palatino. It's a combination of
traditional and modern and always evokes a positive response.
The LyX font dialog lists Palatino but not Palatino Sans.
There is no Palatino Sans (there is no Times-Sans either). Actually, only
few font brands inclode both a serif and sans-serif family.
What do you use for sans serif (and for typewriter), default?
Sans-Serif: default, because I do not use sans serifs in the document.
Otherwise, depending on the audience
I'd take one of Iwona, Helvetica, Avant-Garde or a
Vera-Sans variant (Bera or Arev).
There are TeX-Gyre extensions for Helvetica and Avant-Garde
as well (but not via the GUI).
Typewriter: txtt (nice font with bold, slanted and
small-caps, part of the txfonts bundle)
default in the GUI and
\renewcommand{\ttdefault}{txtt}
in the LaTeX preamble.
(see also http://bugzilla.lyx.org/show_bug.cgi?id=4979)
Although I am by far not a font-guru, I spend some amount of time and
effort into the topic and compiled an up-to-date survey about Free math
fonts for LaTeX (in German) with 40 samples of both serif and
sans-serif text-math font combinations. I just wonder, where to publish
it.
Günter
Re: Times Roman vs Latin Modern Roman Font
On 28.08.08, Paul A. Rubin wrote: G. Milde wrote: For on-screen viewing (e.g. of generated PDF) I'd recommend the Vera family (Bera Serif in the DocumentSettings). I tried this in a beamer presentation (originally Latin Modern, default size). Apparently the Bera fonts are bigger, because some text was driven off the slide. Different metrics for different fonts is perfectly normal. (Times is especially narrow, Bookman especially wide, Palatino and CM in the middle. Also, the x-hight varies.) I had to change the document default to 10 pt to get things right. Is this normal? No, in a beamer presentation you should rather put less text on a slide than decrease the script size so that the audience still has a chance to recognise what is written ;-) An example for an especially wide font intended for presentations are the lxfonts http://dante.ctan.org/CTAN/help/Catalogue/entries/lxfonts.html with discussion of the topic in http://dante.ctan.org/CTAN/fonts/lxfonts/doc/fonts/lxfonts/LXfonts-demo.pdf Günter
Re: tab through eqnarray environment - bug in 1.6rc1?
On 29.08.08, Abdelrazak Younes wrote: James Sutherland wrote: Shift-Tab cycles in reverse as it has in the past, but Tab does not cycle forward... This is a known problem that we intend to fix before 1.6.0. The problem is that the completion framework monopolize the tab key for requesting completion. Just courious: * even if the completion feature is switched off? * is the Tab binding hard-coded or configurable? We need to find a good key in replacement for tab but we didn't reach a consensus yet. Feel free to suggest something. In my favourite text editor, I use Ctrl-A for completion and Tab for indenting. But IMO, there is need for configurable adaptive keybindings: user configurable: This is already possible (via the *.bind files and since 1.6 also via GUI) adaptive: smart bindings that take into account the context, e.g. the same key should be configurable to different lfuns in math and text mode. There are simply too few keys for too many actions, so we should avoid bindings that result in command disabled. Günter
Re: Times Roman vs Latin Modern Roman Font
On 28.08.08, Paul A. Rubin wrote:
Rich Shepard wrote:
My default typeface is Palatino. It's a combination of
traditional and modern and always evokes a positive response.
The LyX font dialog lists Palatino but not Palatino Sans.
There is no Palatino Sans (there is no Times-Sans either). Actually, only
few font brands inclode both a serif and sans-serif family.
What do you use for sans serif (and for typewriter), default?
Sans-Serif: default, because I do not use sans serifs in the document.
Otherwise, depending on the audience
I'd take one of Iwona, Helvetica, Avant-Garde or a
Vera-Sans variant (Bera or Arev).
There are TeX-Gyre extensions for Helvetica and Avant-Garde
as well (but not via the GUI).
Typewriter: txtt (nice font with bold, slanted and
small-caps, part of the txfonts bundle)
default in the GUI and
\renewcommand{\ttdefault}{txtt}
in the LaTeX preamble.
(see also http://bugzilla.lyx.org/show_bug.cgi?id=4979)
Although I am by far not a font-guru, I spend some amount of time and
effort into the topic and compiled an up-to-date survey about Free math
fonts for LaTeX (in German) with 40 samples of both serif and
sans-serif text-math font combinations. I just wonder, where to publish
it.
Günter
Re: Times Roman vs Latin Modern Roman Font
On 28.08.08, Paul A. Rubin wrote: G. Milde wrote: For on-screen viewing (e.g. of generated PDF) I'd recommend the Vera family (Bera Serif in the DocumentSettings). I tried this in a beamer presentation (originally Latin Modern, default size). Apparently the Bera fonts are bigger, because some text was driven off the slide. Different metrics for different fonts is perfectly normal. (Times is especially narrow, Bookman especially wide, Palatino and CM in the middle. Also, the x-hight varies.) I had to change the document default to 10 pt to get things right. Is this normal? No, in a beamer presentation you should rather put less text on a slide than decrease the script size so that the audience still has a chance to recognise what is written ;-) An example for an especially wide font intended for presentations are the lxfonts http://dante.ctan.org/CTAN/help/Catalogue/entries/lxfonts.html with discussion of the topic in http://dante.ctan.org/CTAN/fonts/lxfonts/doc/fonts/lxfonts/LXfonts-demo.pdf Günter
Re: tab through eqnarray environment - bug in 1.6rc1?
On 29.08.08, Abdelrazak Younes wrote: > James Sutherland wrote: >> Shift-Tab cycles in reverse as it has in the past, but Tab does not >> cycle forward... > This is a known problem that we intend to fix before 1.6.0. The problem > is that the completion framework monopolize the tab key for requesting > completion. Just courious: * even if the completion feature is switched off? * is the Tab binding hard-coded or configurable? > We need to find a good key in replacement for tab but we > didn't reach a consensus yet. Feel free to suggest something. In my favourite text editor, I use Ctrl-A for completion and Tab for indenting. But IMO, there is need for "configurable adaptive" keybindings: user configurable: This is already possible (via the *.bind files and since 1.6 also via GUI) adaptive: "smart" bindings that take into account the context, e.g. the same key should be configurable to different lfuns in math and text mode. There are simply too few keys for too many actions, so we should avoid bindings that result in "command disabled". Günter
Re: Times Roman vs Latin Modern Roman Font
On 28.08.08, Paul A. Rubin wrote:
> Rich Shepard wrote:
>> My default typeface is Palatino. It's a combination of
>> traditional and modern and always evokes a positive response.
> The LyX font dialog lists Palatino but not Palatino Sans.
There is no Palatino Sans (there is no Times-Sans either). Actually, only
few font "brands" inclode both a serif and sans-serif family.
> What do you use for sans serif (and for typewriter), "default"?
Sans-Serif: default, because I do not use sans serifs in the document.
Otherwise, depending on the audience
I'd take one of Iwona, Helvetica, Avant-Garde or a
Vera-Sans variant (Bera or Arev).
There are TeX-Gyre extensions for Helvetica and Avant-Garde
as well (but not via the GUI).
Typewriter: txtt (nice font with bold, slanted and
small-caps, part of the txfonts bundle)
"default" in the GUI and
\renewcommand{\ttdefault}{txtt}
in the LaTeX preamble.
(see also http://bugzilla.lyx.org/show_bug.cgi?id=4979)
Although I am by far not a font-guru, I spend some amount of time and
effort into the topic and compiled an up-to-date survey about "Free math
fonts for LaTeX" (in German) with > 40 samples of both serif and
sans-serif text-math font combinations. I just wonder, where to publish
it.
Günter
Re: Times Roman vs Latin Modern Roman Font
On 28.08.08, Paul A. Rubin wrote:
> G. Milde wrote:
>> For on-screen viewing (e.g. of generated PDF) I'd recommend the Vera
>> family ("Bera Serif" in the Document>Settings).
> I tried this in a beamer presentation (originally Latin Modern, default
> size). Apparently the Bera fonts are bigger, because some text was
> driven off the slide.
Different metrics for different fonts is perfectly normal.
(Times is especially narrow, Bookman especially wide, Palatino and CM in the
middle. Also, the x-hight varies.)
> I had to change the document default to 10 pt to
> get things right. Is this normal?
No, in a beamer presentation you should rather put less text on a slide than
decrease the script size so that the audience still has a chance to
recognise what is written ;-)
An example for an especially wide font intended for presentations are the
lxfonts http://dante.ctan.org/CTAN/help/Catalogue/entries/lxfonts.html
with discussion of the topic in
http://dante.ctan.org/CTAN/fonts/lxfonts/doc/fonts/lxfonts/LXfonts-demo.pdf
Günter
Re: Times Roman vs Latin Modern Roman Font
On 27.08.08, Rich Shepard wrote: On Wed, 27 Aug 2008, Bruce Pourciau wrote: Palatino is my default typeface. Now if it only had the \textservicemark symbol built in it would be fully complete. :-) Pagella, the extended version provided by the TeX-Gyre project, http://dante.ctan.org/CTAN/help/Catalogue/entries/tex-gyre.html has (amongst a lot of other additional letters and symbols) also a matching servicemark. See the attached files. Günter servicemark.lyx Description: application/lyx servicemark.pdf Description: Adobe PDF document
nomenclature not printed with 1.5.6
Dear LyX users, Attach: /home/milde/Texte/Test/LyX/nomencl.lyx did anyone else observe that since the switch to 1.5.6, the nomenclature is missing in the output? Or is this a special issue for me and my settings? How could I find out what is missing? (The nomenclature is printed if I export to LaTeX and run latex filename makeindex filename.nlo -s nomencl.ist -o filename.nls latex filename by hand. Attached a minimal example. Günter
Re: Times Roman vs Latin Modern Roman Font
On 27.08.08, Rich Shepard wrote: On Wed, 27 Aug 2008, Bruce Pourciau wrote: Palatino is my default typeface. Now if it only had the \textservicemark symbol built in it would be fully complete. :-) Pagella, the extended version provided by the TeX-Gyre project, http://dante.ctan.org/CTAN/help/Catalogue/entries/tex-gyre.html has (amongst a lot of other additional letters and symbols) also a matching servicemark. See the attached files. Günter servicemark.lyx Description: application/lyx servicemark.pdf Description: Adobe PDF document
nomenclature not printed with 1.5.6
Dear LyX users, Attach: /home/milde/Texte/Test/LyX/nomencl.lyx did anyone else observe that since the switch to 1.5.6, the nomenclature is missing in the output? Or is this a special issue for me and my settings? How could I find out what is missing? (The nomenclature is printed if I export to LaTeX and run latex filename makeindex filename.nlo -s nomencl.ist -o filename.nls latex filename by hand. Attached a minimal example. Günter
Re: Times Roman vs Latin Modern Roman Font
On 27.08.08, Rich Shepard wrote: > On Wed, 27 Aug 2008, Bruce Pourciau wrote: > Palatino is my default typeface. Now if it only had the \textservicemark > symbol built in it would be fully complete. :-) Pagella, the extended version provided by the TeX-Gyre project, http://dante.ctan.org/CTAN/help/Catalogue/entries/tex-gyre.html has (amongst a lot of other additional letters and symbols) also a matching servicemark. See the attached files. Günter servicemark.lyx Description: application/lyx servicemark.pdf Description: Adobe PDF document
nomenclature not printed with 1.5.6
Dear LyX users, Attach: /home/milde/Texte/Test/LyX/nomencl.lyx did anyone else observe that since the switch to 1.5.6, the nomenclature is missing in the output? Or is this a special issue for me and my settings? How could I find out what is missing? (The nomenclature is printed if I export to LaTeX and run latex filename makeindex filename.nlo -s nomencl.ist -o filename.nls latex filename by hand. Attached a minimal example. Günter
Re: Times Roman vs Latin Modern Roman Font
On 27.08.08, Bruce Pourciau wrote: On Aug 27, 2008, at 8:44 AM, Les Denham wrote: On Wednesday 27 August 2008, Abe Lau wrote: Hi all, I am wondering what's the difference between Times Roman and Latin Modern Roman font. I have read from the mailing list that the Latin Modern Roman (lmodern) package is preferred over the default Computer Modern Roman. Latin Modern can be thought of as the successor of Computer Modern. It is a reimplementation as outline font. It covers a wide range of characters and symbols including true small caps and fits well with the mathematical fonts used by LaTeX (which might be a problem for any other font). OTOH, I find the Latin Modern fonts too light in print (if printed with a laser printer) and not very nice for on-screen rendering. The Times Roman font looks much better on screen and this is the only difference I could tell from a brief look. For on-screen viewing (e.g. of generated PDF) I'd recommend the Vera family (Bera Serif in the DocumentSettings). Günter
Re: Times Roman vs Latin Modern Roman Font
On 27.08.08, Bruce Pourciau wrote: On Aug 27, 2008, at 8:44 AM, Les Denham wrote: On Wednesday 27 August 2008, Abe Lau wrote: Hi all, I am wondering what's the difference between Times Roman and Latin Modern Roman font. I have read from the mailing list that the Latin Modern Roman (lmodern) package is preferred over the default Computer Modern Roman. Latin Modern can be thought of as the successor of Computer Modern. It is a reimplementation as outline font. It covers a wide range of characters and symbols including true small caps and fits well with the mathematical fonts used by LaTeX (which might be a problem for any other font). OTOH, I find the Latin Modern fonts too light in print (if printed with a laser printer) and not very nice for on-screen rendering. The Times Roman font looks much better on screen and this is the only difference I could tell from a brief look. For on-screen viewing (e.g. of generated PDF) I'd recommend the Vera family (Bera Serif in the DocumentSettings). Günter
Re: Times Roman vs Latin Modern Roman Font
On 27.08.08, Bruce Pourciau wrote:
> On Aug 27, 2008, at 8:44 AM, Les Denham wrote:
>> On Wednesday 27 August 2008, Abe Lau wrote:
>>> Hi all, I am wondering what's the difference between Times Roman and
>>> Latin Modern Roman font.
>>> I have read from the mailing list that the Latin Modern Roman
>>> (lmodern) package is preferred over the default Computer Modern
>>> Roman.
Latin Modern can be thought of as the successor of Computer Modern.
It is a "reimplementation" as outline font. It covers a wide range of
characters and symbols including true small caps and fits well with
the mathematical fonts used by LaTeX (which might be a problem for
any other font).
OTOH, I find the Latin Modern fonts too light in print (if printed
with a laser printer) and not very nice for on-screen rendering.
>>> The Times Roman font looks much better on screen and this is the only
>>> difference I could tell from a brief look.
For on-screen viewing (e.g. of generated PDF) I'd recommend the Vera
family ("Bera Serif" in the Document>Settings).
Günter
Re: Memoir/hyperref conflict is a known issue PARTIALLY SOLVED
On 25.08.08, Steve Litt wrote: What remains now is to find a different way to code my list compressions, and test everything else to make sure there are no other problems. I have in my layout extensions definitions for Dense versions of Enumerate, Itemize, and Description. They work well with the KOMA classes, I cannot tell about memoire. Another point is that the vertical space between items is too big if you set the paragraph separator to Vertical Space in DocumentSettings. So applying the workaround in http://bugzilla.lyx.org/show_bug.cgi?id=4796 might help in this case. Günter
Re: Memoir/hyperref conflict is a known issue PARTIALLY SOLVED
On 25.08.08, Steve Litt wrote: What remains now is to find a different way to code my list compressions, and test everything else to make sure there are no other problems. I have in my layout extensions definitions for Dense versions of Enumerate, Itemize, and Description. They work well with the KOMA classes, I cannot tell about memoire. Another point is that the vertical space between items is too big if you set the paragraph separator to Vertical Space in DocumentSettings. So applying the workaround in http://bugzilla.lyx.org/show_bug.cgi?id=4796 might help in this case. Günter
Re: Memoir/hyperref conflict is a known issue
On 25.08.08, Steve Litt wrote: > What remains now is to find a different way to code my list > compressions, and test everything else to make sure there are no other > problems. I have in my layout extensions definitions for "Dense" versions of Enumerate, Itemize, and Description. They work well with the KOMA classes, I cannot tell about memoire. Another point is that the vertical space between items is too big if you set the paragraph separator to "Vertical Space" in Document>Settings. So applying the workaround in http://bugzilla.lyx.org/show_bug.cgi?id=4796 might help in this case. Günter
Re: Floating Table Objects Error
On 22.08.08, Nico wrote:
Hello Günter,
I don't think that some unbalanced brackets are in my float... It's the
same effect if I insert just an empty tabular-float-environment.
It works with figure-float-environment...
OK, to a table-float triggers the error but does not produce it.
Might have to do with tablecaption settings...
I've realized now, that it must have s.th. to do with the declarations I
did in the preamble, because it works without it. I tried to take parts
out to recognize the guilty lines.
Yes, this is the recommended way.
With the first lines, the float is generated:
%Definition des Absatz-Abstandes
\setlength{\parskip}{0pt}
...[36 more lines]
... But when I insert these Lines, the error appears:
%Realisierung der Hyperref-Attribute unter verschiedenen Voraussetzungen
\usepackage{ifpdf} % part of the hyperref bundle
... [116 more lines]
Does s.o. see the reason for my problem in these lines?
This are far too many line for me to spot an error in restricted time.
I'd recommend to try further by divide and conquer.
Keep an eye on settings that have to do with table floats.
Günter
Re: Float placement
On 22.08.08, Guillaume Larocque wrote:
Guillaume Larocque wrote:
Ok, here are the exact symptoms of the problem. If I have a few floats
inserted in a sequence in Lyx, as soon as Latex decides that one float
will be on a separate page, all the floats following it will also be
placed on a separate page, regardless of their size.
Are you saying that after the first float gets a separate page, each of
the subsequent floats sits alone on a page?
Yes. What I have in a few places in my document is something like: one
large float, 4 smaller floats, one other large float and then 3
smaller floats again.
Latex decides to put the one large float on a separate page and then
it puts all the rest of the floats on seperate pages
**also at the end of the Chapter.**
It looks to me as if your documentclass (or some loaded package or
preamble setting) creates a page of floats only **at the end of a
chapter**.
As the order of floats is never changed, subsequent floats in this
chapter are placed behind this page of floats. As a new chapter starts
on a new page, these floats will also be alone on a page.
Its probably deciding that there are too many floats that will break
the text. I get that behaviour even if I select 'top of page' for all
the floats.
What happens, if you activate the ignore LaTeX rules button?
I managed to get the floats pretty much where I want them with info
from this website: http://people.cs.uu.nl/piet/floats/node1.html
Particularly with the use of:
\afterpage{\clearpage}
and by moving some floats between paragraphs. I was just hoping that
Latex would figure all this out for me.
As good layout (and font-placing) is a matter of taste, LaTeX cannot
please all without some configuration efforts from the side of users
that have a different taste from the documentclass designers.
This is why typesetting with LaTeX/LyX is straightforward if you find a
documentstyle you happen to like (or which fullfills the requirements
of the institution you write for) but is a pain, if you do not like the
default output.
Günter
Re: \textservicemark vs. \texttrademark
On 22.08.08, Rich Shepard wrote: On Fri, 22 Aug 2008, Jürgen Spitzmüller wrote: The problem is that the font you're using does not provide the appropriate glyph (for SM). Thus textcomp bails out. That occurred to me, but I neglected to ask. I'm surprised that the Palatino fonts don't contain that glyph since this family is one of those provided by LaTeX. There is no font provided by LaTeX. There is one font that comes with TeX -- Computer Modern. There are many fonts that are made accessible for LaTeX, e.g. the standard Postscript fonts. The free versions of these standard font families are mostly scaled down (missing expert cuts like real small caps as well as not-so-common glyphs and symbols). Additional symbols for LaTeX are mostly designed to match Computer Modern. Günter
Re: Does anyone know how to import WIKI pages into lyx.
On 23.08.08, wangyq wrote: Currently I am preparing teaching materials for students. I found there are some wonderful things in WIKI. I hope I can directly import them into my materials. But the wiki page is not completely same as latex. There are many many Wiki dialects, so there is no definitive answer. Two cases that come to my mind: The Wikipedia, e.g. uses LaTeX markup for math, so it should be easy to import from the text source (open as edit and drag-and-drop from the text widget, then in LyX mark the math and press Ctrl-m). Some Wikis use reStructuredText as markup language. This can be converted to LaTeX with rst2latex.py from http://docutils.sf.net. Günter
