Re: conflict with good font for Acroread and Lyx-code quotes
Andrew Harrington wrote:
I am not managing to get two things I want with fonts:
I want English text + .png graphics to look decent in Acroread. I get
complete output using pdflatex, but as the Extended Features Guide
5.3.6.2 mentions, the fonts look awful, so I followed the suggestion and
put in my preamble
\usepackage{ae,aecompl}
Then I get a decent font in Acroread.
\usepackage{lmodern}
(the Latin Modern fonts) is a much better choice nowadays.
However, when I put a double quote character in Lyx-code, I get a black
square as output for the quotes. (Single quotes are OK, though two
single quotes together gives the same problem.) I do not know how many
other characters would give the same problem.
This is a known limitation of the ae package. You might try
\usepackage{aeguill}
but I'd still recommend Latin Modern.
HTH,
Jürgen
Re: layout and template from LaTeX class.
Date: Thu, 15 Jun 2006 19:30:05 -0700 (PDT)
From: Michael McNeil Forbes [EMAIL PROTECTED]
To: lyx-users@lists.lyx.org
Subject: layout and template from LaTeX class.
Hi,
I have developed a LaTeX thesis class for UBC and have received questions
about how to use it with LyX. As I know very little about LyX, I am not
sure how to proceed.
All of the LaTeX class files and templates can be found below:
http://alum.mit.edu/www/mforbes/projects/ubcthesis/
I am trying to make the ubcthesis.cls compliant with UBC standards, and so
have provided a sample file ubcsample.tex that contains many comments
about the ordering of content, formatting issues etc. as required by the
university. These must be presented to users: I assume that this would be
done through a template for LyX users.
What is the best way to make this class available to LyX users?
The ubcthesis.cls is a modification of the standard book.cls.
I have tried making a simple ubcthesis.layout file:
-
#% Do not delete the line below; configure depends on this
# \DeclareLaTeXClass[ubcthesis]{University of British Columbia Theses}
# Read the definitions from book.layout
Input book.layout
-
It seems to work, but importing the ubcsample.tex renders most of the
comments in an extremely usless format. Many of the comments are about
ways of doing things in LaTeX or required stuff, and the resulting file
seems almost useless for someone starting a thesis in LyX. (I think
it would be easier for them to use LaTeX!)
Any suggestions on how to best make this class available to LyX users?
I've been through this kind of problems: in sample files, you find two
kinds of information:
- instructions about how to use the class (various commands available), often
alternating
piece of code and example of result;
- complements of instructions about layout (e.g. appearance of tables, space
around figures, etc.).
The pieces of code are not needed in the LyX case if the layout implements all
particularities
of the class: the sample can be restricted to an illustration of the specific
styles.
So the template/example (i.e. a template which is not empty, but filled with
examples of use)
can be much simpler than the LaTeX equivalent.
The complementary instructions are normally not needed as they are a remaining
of the time where
publishers sent to authors the description of the desired layout: if the class
is correctly
built, these layout instructions should not exist anymore.
However as the class can be incomplete (e.g. for tables layout), parts of the
LaTeX code
can be included in ERT to produce the explanations in screen or paper versions.
HTH
--
Jean-Pierre
Re: layout and template from LaTeX class.
On Fri, 16 Jun 2006, Jean-Pierre Chretien wrote: I've been through this kind of problems: in sample files, you find two kinds of information: - instructions about how to use the class (various commands available), often alternating piece of code and example of result; - complements of instructions about layout (e.g. appearance of tables, space around figures, etc.). The pieces of code are not needed in the LyX case if the layout implements all particularities of the class: the sample can be restricted to an illustration of the specific styles. So the template/example (i.e. a template which is not empty, but filled with examples of use) can be much simpler than the LaTeX equivalent. My design philosophy for the thesis class was to keep to a standard LaTeX idiom. It is possible to force the user to use a particular layout by having the class place the text in the appropriate order etc. but this would probably break many packages etc. Also, requirements are often not rigid when strange situations are encountered, and having a rigid class would prevent some people from using it. Thus, the comments are required to give users the freedom to do what they need, but the information they need to meet with approval if everything is standard. The complementary instructions are normally not needed as they are a remaining of the time where publishers sent to authors the description of the desired layout: if the class is correctly built, these layout instructions should not exist anymore. However as the class can be incomplete (e.g. for tables layout), parts of the LaTeX code can be included in ERT to produce the explanations in screen or paper versions. I have only a vague idea about what ERT is and how it fits in with the typical LyX experience, nor how to put the required information in the layout/template files. Apart from generating a simple layout file, I have not found clear documentation about what needs to be done. I want to avoid having to maintain two sets of files: one for LaTeX users and one for LyX users. Ideally, I would like to be able to specify enough information in the .cls and example files that the appropriate LyX stuff could be extracted, but I don't want to make life ore difficult for LaTeX users by cluttering up the sample files with LyX specific commands. Is this possible, or do I essentially have to maintain two separate projects: a LaTeX project (.cls + sample.tex) and a separate LyX project (.layout + template)? If not, I will have to wait until a LyX guru wants to volunteer to maintain the latter project before I can offer LyX support for the thesis templates. Thanks, Michael.
Errors
While generating the output of my document, the following errors are
presented:
... septiembre de 1964 \citep{RepsolYPF2005a}
, se inaugura la
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
...\jburluse {RepsolYPF2005a}} {\bibhowcited}
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
I'm using Jurabib, Miktex and LyX 1.4.1 on WinXP... I still cannot be able
to properly use Jurabib in WinLyX, citations are repalced by ? (before
these errors appeared)... If I export the documento to LaTeX and process it
with TeXnicCenter I can see the whole path for Jurabib is added. If I remove
it, Jurabib works fine. This is the 3rd time I ask for a solution to this
problem within LyX. Hope somebody can help me.
--
-
Julio Rojas
[EMAIL PROTECTED]
Re: Layout copyright; was: Re: Sharing layout files
On Thursday 15 June 2006 06:06 pm, [EMAIL PROTECTED] wrote: On Mon, 12 Jun 2006, David Neeley wrote: Comments within On 6/12/06, Steve Litt [EMAIL PROTECTED] wrote: Why can't the original author label his or her contribution as Licensed under the GNU General Public License, Version 2, or similar. Layout files are code, so the GPL fits them well. Speaking for myself, I'd be hesitant to contribute anything without GPL'ling it, because some licenses leave open the door for a big bad company to change my layout just a little bit and take it proprietary, and who knows, some day sue me for using code derived from their code, and then I have to prove that mine preceded theirs. snip There is a considerable debate, as you probably know, about whether the GPL is a good idea for areas such as these in which a layout may be used to create commercial documents. That is why I would suggest something like the BSD approach that permits commercial use. snip Finally, it is unlikely that layout files themselves would be an issue--since the objective is the documents created with that layout file and not the layout file itself. I really think that this discussion is largely the result of worry over what is very unlikely to happen to begin with--but a reasonable application of a license is certainly not a bad idea at all. This is issue is apparently a bit complicated. However, I think it was a good idea to emphasize that wiki authors are free to license their work as they see fit, especially any files they upload. So, for the page http://wiki.lyx.org/Site/Copyrights What do you about adding a paragraph such as this: Please note that contributors are free to license uploaded material as they see fit. So if you wish to upload layout examples under some specific license, please do so. I HUGELY like this. License has always been important to me. I believe the VimOutliner project evolved so well in part because of my original choice to license it GPL. I felt funny about putting my stuff up there with a license chosen by others, so this is a good thing. In a related thread somebody mentioned GPL wouldn't be good because some people use LyX for commercial purposes. I'd imagine the only thing being sold are the pdf or paper output (please let me know if you think I'm wrong), and I'd imagine (please let me know if you think I'm wrong) that the pdf or paper output would be like a report made by the software, not a compiled version of the software. If I'm wrong, my whole business is illegal, as I sell proprietary books assembled with various free software, including GPL. Thanks SteveT Steve Litt Author: * Universal Troubleshooting Process courseware * Troubleshooting Techniques of the Successful Technologist * Manager's Guide to Technical Troubleshooting * Twenty Eight Tales of Troubleshooting * Rapid Learning: Secret Weapon of the Successful Technologist http://www.troubleshooters.com/bookstore http://www.troubleshooters.com/utp/tcourses.htm
typing Lyx-code quotes
Thanks, Jurgen, for the updated font!
That still leaves a Lyx question.
To put quotes in Lyx-code, I know plain quote does not work. I tried
both C-quotekey and C-S-quotekey, and each gives me a *single* quote. I
could copy the typewrite double quote character from the UserGuide
example, and it looks fine, but I do not know how to enter it directly.
Thanks,
Andy Harrington
Juergen Spitzmueller wrote:
Andrew Harrington wrote:
I am not managing to get two things I want with fonts:
I want English text + .png graphics to look decent in Acroread. I get
complete output using pdflatex, but as the Extended Features Guide
5.3.6.2 mentions, the fonts look awful, so I followed the suggestion and
put in my preamble
\usepackage{ae,aecompl}
Then I get a decent font in Acroread.
\usepackage{lmodern}
(the Latin Modern fonts) is a much better choice nowadays.
HTH,
Jürgen
--
Andrew N. Harrington
Computer Science Department Undergraduate Program Director
Loyola University Chicagohttp://www.cs.luc.edu/~anh
512B Lewis Towers (office) Office Phone: 312-915-7982
Snail mail to Lewis Towers 416 Dept. Fax:312-915-7998
820 North Michigan Avenue[EMAIL PROTECTED]
Chicago, Illinois 60611
Re: typing Lyx-code quotes
Andrew Harrington wrote: To put quotes in Lyx-code, I know plain quote does not work. I tried both C-quotekey and C-S-quotekey, and each gives me a *single* quote. I could copy the typewrite double quote character from the UserGuide example, and it looks fine, but I do not know how to enter it directly. I can't remember if the key shortcut has changed between LyX 1.3 and LyX 1.4, but it should be either C-S-quotekey or M-S-quotekey. Jürgen
Re: Layout copyright; was: Re: Sharing layout files
The real first question is whether a layout file can be covered by copyright to begin with. As I pointed out before, one good example is fonts. While their names can be copyrighted, the actual outline and metric files cannot be. I have no doubt that in the current state of the law, the application code can be copyright material; I am not so sanguine about layout files. I should add that I have not practiced law in about fifteen years, and intellectual property law has changed a good bit in that time. Finally, I do believe that if you wish to be covered, the wiki should have a copyright statement something like: Files submitted to the wiki for general download are covered by the XXX license in the name of their respective author, unless specified otherwise by the contributing authors. I would suggest something like the BSD license as the basic one, so there are no real limitations or questions about use--commercial or otherwise--but giving the contributor the option of choosing another one if he or she desires. That way, if the files can be copyrighted, they would be covered in all cases. It would also cover those that are submitted when the author doesn't want to go to the trouble of figuring all of this out, but does not wish for others to claim copyright to his or her work. David On 6/16/06, Steve Litt [EMAIL PROTECTED] wrote: On Thursday 15 June 2006 06:06 pm, [EMAIL PROTECTED] wrote: On Mon, 12 Jun 2006, David Neeley wrote: Comments within On 6/12/06, Steve Litt [EMAIL PROTECTED] wrote: Why can't the original author label his or her contribution as Licensed under the GNU General Public License, Version 2, or similar. Layout files are code, so the GPL fits them well. Speaking for myself, I'd be hesitant to contribute anything without GPL'ling it, because some licenses leave open the door for a big bad company to change my layout just a little bit and take it proprietary, and who knows, some day sue me for using code derived from their code, and then I have to prove that mine preceded theirs. snip There is a considerable debate, as you probably know, about whether the GPL is a good idea for areas such as these in which a layout may be used to create commercial documents. That is why I would suggest something like the BSD approach that permits commercial use. snip Finally, it is unlikely that layout files themselves would be an issue--since the objective is the documents created with that layout file and not the layout file itself. I really think that this discussion is largely the result of worry over what is very unlikely to happen to begin with--but a reasonable application of a license is certainly not a bad idea at all. This is issue is apparently a bit complicated. However, I think it was a good idea to emphasize that wiki authors are free to license their work as they see fit, especially any files they upload. So, for the page http://wiki.lyx.org/Site/Copyrights What do you about adding a paragraph such as this: Please note that contributors are free to license uploaded material as they see fit. So if you wish to upload layout examples under some specific license, please do so. I HUGELY like this. License has always been important to me. I believe the VimOutliner project evolved so well in part because of my original choice to license it GPL. I felt funny about putting my stuff up there with a license chosen by others, so this is a good thing. In a related thread somebody mentioned GPL wouldn't be good because some people use LyX for commercial purposes. I'd imagine the only thing being sold are the pdf or paper output (please let me know if you think I'm wrong), and I'd imagine (please let me know if you think I'm wrong) that the pdf or paper output would be like a report made by the software, not a compiled version of the software. If I'm wrong, my whole business is illegal, as I sell proprietary books assembled with various free software, including GPL. Thanks SteveT Steve Litt Author: * Universal Troubleshooting Process courseware * Troubleshooting Techniques of the Successful Technologist * Manager's Guide to Technical Troubleshooting * Twenty Eight Tales of Troubleshooting * Rapid Learning: Secret Weapon of the Successful Technologist http://www.troubleshooters.com/bookstore http://www.troubleshooters.com/utp/tcourses.htm
Bibliography Style apalike
The closest bib style to what a certain journal want seems to be apalike2, while apalike is not as close but OK. LyX supports apalike (Can it be made to support apalike2?) Suppose then I use apalike. Does anyone know how I can find out what fields are supported in apalike style? For example, does it have a field called Translator and if so, does that mean I should define a custom field in BibDesk called Translator? Thanks for any help the list can provide. Bruce
Re: Layout copyright; was: Re: Sharing layout files
On Friday 16 June 2006 11:50 am, you wrote: The real first question is whether a layout file can be covered by copyright to begin with. As I pointed out before, one good example is fonts. While their names can be copyrighted, the actual outline and metric files cannot be. I didn't know that. In that case, how can a font foundary legally prevent their fonts from being copied willy nilly around the world? If protected only by a trademark, one could copy the outline and metric files and call them StevesSansSerif for instance. If protected by patent, what would be so novel from one font to another that a patent would be issued? SteveT Steve Litt Author: * Universal Troubleshooting Process courseware * Troubleshooting Techniques of the Successful Technologist * Manager's Guide to Technical Troubleshooting * Twenty Eight Tales of Troubleshooting * Rapid Learning: Secret Weapon of the Successful Technologist http://www.troubleshooters.com/bookstore http://www.troubleshooters.com/utp/tcourses.htm
Re: Layout copyright; was: Re: Sharing layout files
On Friday 16 June 2006 11:50 am, David Neeley wrote: Finally, I do believe that if you wish to be covered, the wiki should have a copyright statement something like: Files submitted to the wiki for general download are covered by the XXX license in the name of their respective author, unless specified otherwise by the contributing authors. That sounds good. I would suggest something like the BSD license as the basic one, so there are no real limitations or questions about use--commercial or otherwise--but giving the contributor the option of choosing another one if he or she desires. That way, if the files can be copyrighted, they would be covered in all cases. That also sounds good, at least for most stuff, including what I emailed a couple days ago. If it were something I worked 60 hours on I might go GPL to prevent a Microsoft Kerberos type situation, but my layout files aren't that type of work. Thanks for the clarification and good idea. SteveT Steve Litt Author: * Universal Troubleshooting Process courseware * Troubleshooting Techniques of the Successful Technologist * Manager's Guide to Technical Troubleshooting * Twenty Eight Tales of Troubleshooting * Rapid Learning: Secret Weapon of the Successful Technologist http://www.troubleshooters.com/bookstore http://www.troubleshooters.com/utp/tcourses.htm
Re: Bibliography Style apalike
Look at the file apalike.bst, which will tell you want fields are defined. (There is no field translator, by the way.) And you can use apalike2, if you wish. Just hit the browse button in the dialog where you choose a bibliography style, and then go find the file apalike2.bst. It is, by the way, not that terribly hard to modify these styles once you get the hang of it. Richard Bruce Pourciau wrote: The closest bib style to what a certain journal want seems to be apalike2, while apalike is not as close but OK. LyX supports apalike (Can it be made to support apalike2?) Suppose then I use apalike. Does anyone know how I can find out what fields are supported in apalike style? For example, does it have a field called Translator and if so, does that mean I should define a custom field in BibDesk called Translator? Thanks for any help the list can provide. Bruce
Re: Bibliography Style apalike
Thanks, Richard. That helps. When you say Just hit the browse button in the dialog where you choose a bibliography style, and then go find the file apalike2.bst. do you mean find it in my tex installation or find it on the web and donwnload it? What field would normally be used for additional information -- translator, privately published, an add-on to the title, etc? Bruce On Jun 16, 2006, at 1:58 PM, Richard Heck wrote: Look at the file apalike.bst, which will tell you want fields are defined. (There is no field translator, by the way.) And you can use apalike2, if you wish. Just hit the browse button in the dialog where you choose a bibliography style, and then go find the file apalike2.bst. It is, by the way, not that terribly hard to modify these styles once you get the hang of it. Richard Bruce Pourciau wrote: The closest bib style to what a certain journal want seems to be apalike2, while apalike is not as close but OK. LyX supports apalike (Can it be made to support apalike2?) Suppose then I use apalike. Does anyone know how I can find out what fields are supported in apalike style? For example, does it have a field called Translator and if so, does that mean I should define a custom field in BibDesk called Translator? Thanks for any help the list can provide. Bruce
Re: Layout copyright; was: Re: Sharing layout files
Steve Litt wrote: On Friday 16 June 2006 11:50 am, David Neeley wrote: Finally, I do believe that if you wish to be covered, the wiki should have a copyright statement something like: Files submitted to the wiki for general download are covered by the XXX license in the name of their respective author, unless specified otherwise by the contributing authors. That sounds good. I would suggest something like the BSD license as the basic one, so there are no real limitations or questions about use--commercial or otherwise--but giving the contributor the option of choosing another one if he or she desires. That way, if the files can be copyrighted, they would be covered in all cases. That also sounds good, at least for most stuff, including what I emailed a couple days ago. If it were something I worked 60 hours on I might go GPL to prevent a Microsoft Kerberos type situation, but my layout files aren't that type of work. Thanks for the clarification and good idea. http://www.c4.net/Index.cfm?Method=NewsStories.NewsStoryNewsStory_ID=143 This article at the Register discusses one of the major hurtles confronting would be challengers to the Microsoft throne, fonts. It may seem like an insignificant part of the whole, but it is important enough that current U.S. law actually makes an exception for copyrighting the shape and design of fonts in the name of free press. This means that, for all intents and purposes, you could rename a font and redistribute it…in the States. Other countries are not so forgiving, and that's where trouble comes into paradise.
Re: Bibliography Style apalike
That file should be on your TeX installation. Use whatever find-a-file stuff you have available to locate it. I tend to put translator info in the Note field. Whatever you put there will be set at the end of the entry, using apalike (and probably apalike2). It's not a great solution. I should modify apalike so that it does have a translator field that is put in a sensible place. I'd guess it's already been done, however. Richard Bruce Pourciau wrote: Thanks, Richard. That helps. When you say Just hit the browse button in the dialog where you choose a bibliography style, and then go find the file apalike2.bst. do you mean find it in my tex installation or find it on the web and donwnload it? What field would normally be used for additional information -- translator, privately published, an add-on to the title, etc? Bruce On Jun 16, 2006, at 1:58 PM, Richard Heck wrote: Look at the file apalike.bst, which will tell you want fields are defined. (There is no field translator, by the way.) And you can use apalike2, if you wish. Just hit the browse button in the dialog where you choose a bibliography style, and then go find the file apalike2.bst. It is, by the way, not that terribly hard to modify these styles once you get the hang of it. Richard Bruce Pourciau wrote: The closest bib style to what a certain journal want seems to be apalike2, while apalike is not as close but OK. LyX supports apalike (Can it be made to support apalike2?) Suppose then I use apalike. Does anyone know how I can find out what fields are supported in apalike style? For example, does it have a field called Translator and if so, does that mean I should define a custom field in BibDesk called Translator? Thanks for any help the list can provide. Bruce
Re: Layout copyright; was: Re: Sharing layout files
Steve Litt wrote: On Friday 16 June 2006 11:50 am, David Neeley wrote: Finally, I do believe that if you wish to be covered, the wiki should have a copyright statement something like: Files submitted to the wiki for general download are covered by the XXX license in the name of their respective author, unless specified otherwise by the contributing authors. That sounds good. I would suggest something like the BSD license as the basic one, so there are no real limitations or questions about use--commercial or otherwise--but giving the contributor the option of choosing another one if he or she desires. That way, if the files can be copyrighted, they would be covered in all cases. That also sounds good, at least for most stuff, including what I emailed a couple days ago. If it were something I worked 60 hours on I might go GPL to prevent a Microsoft Kerberos type situation, but my layout files aren't that type of work. I've been reading about this some more. It turns out to be a very complex legal issue, especially regarding fonts, which do not have the same legal status as layout files. http://www-personal.umich.edu/~pfs/essay2.html Though I think your copyright rights, if they are weak, will extend to whoever tries to steal your work. If they can get away with stealing yours, then someone can steal from them too. Also obtaining a license for some fonts doesn't give you the same rights to use those fonts as if you had bought them.
jurabib question
I'm having a difficult time getting jurabib set-up the way that I want. I
have it close, but there are still a couple of issues.
First, I have the 'titleformat=italic command in the preamble, but am still
not getting my titles italicized (in either the original references or the
bibliography). I thought that was the purpose of that command. I have the
oxford option enabled as well--is that the problem? Any ideas?
I also have the 'bibformat=ibidem' command set. It works well, but I am
getting duplicate authors listed with 'idem' and would like that replaced
with the standard '---'. The documentation seems to be saying that the dash
should be the default, so I'm not sure what I can do to fix it.
Finally, I'm can't seem to get the 'chicago' format command to work. This
isn't a huge deal since oxford is close enough, but I'd like to know what
I'm doing wrong. I've included the jurabib section from my preamble below
(it is just a modified version of the suggested format suggested in the
humanities section of the lyxwiki---so the credit lies there, and the blame
is mine.
\jurabibsetup{%
titleformat=italic%
titleformat=commasep,%
bibformat=ibidem,%
commabeforerest,%
ibidem=strict,%
citefull=first,%
lookat,%
oxford,%
pages=format,%
human=true,%
idem=strict%
}
Any help would be greatly appreciated.
John Ward
Graduate Assistant
Department of Philosophy
University of Utah
Zref package expands reference system flexibility
The zref package Heiko Oberdiek 2006/05/25 v1.2
Abstract
Package zref tries to get rid of the restriction in LATEX's
reference system that only two properties are supported. The
package implements an extensible referencing system, where
properties are handled in a more flexible way. It offers an
interface for macro programmers for the access to the system
and some applications that uses the new reference scheme.
http://www.informatik.uni-freiburg.de/~oberdiek/tmp/zref.pdf
(temporary location until I find time for a CTAN upload)
Chapter 7 and 7.1 include installation details.
pdftk zref.pdf unpack_files output produces zref.dtx
which is unpacked with tex zref.dtx
pdftk is a free download available from AccessPDF
http://www.accesspdf.com/article.php/20041130153545577
There are several files produced by tex zref.dtx
which need to be copied to their appropriate directory on
your system. Most of the Oberdiek directories already
existed on my system with the execption of the source
path for /Oberdiek which will contain the zref.dtx file.
-
6.2.10 Compatibility with babel
[EMAIL PROTECTED]@babel
430 [EMAIL PROTECTED]@babel#1#2{%
431 \begingroup
432 \csname @[EMAIL PROTECTED]
433 \edef\x{#2}%
434 \expandafter\endgroup
435 [EMAIL PROTECTED]@babel\expandafter{\x}{#1}%
436 }
437 [EMAIL PROTECTED]@babel#1#2{%
438 #2{#1}%
439 }
---
SH: I figure this package will benefit someone, sometime.
Regards,
--
Stephen
Topic ontology recapitulates entropic philology.
Re: conflict with good font for Acroread and Lyx-code quotes
Andrew Harrington wrote:
I am not managing to get two things I want with fonts:
I want English text + .png graphics to look decent in Acroread. I get
complete output using pdflatex, but as the Extended Features Guide
5.3.6.2 mentions, the fonts look awful, so I followed the suggestion and
put in my preamble
\usepackage{ae,aecompl}
Then I get a decent font in Acroread.
\usepackage{lmodern}
(the Latin Modern fonts) is a much better choice nowadays.
However, when I put a double quote character in Lyx-code, I get a black
square as output for the quotes. (Single quotes are OK, though two
single quotes together gives the same problem.) I do not know how many
other characters would give the same problem.
This is a known limitation of the ae package. You might try
\usepackage{aeguill}
but I'd still recommend Latin Modern.
HTH,
Jürgen
Re: layout and template from LaTeX class.
Date: Thu, 15 Jun 2006 19:30:05 -0700 (PDT)
From: Michael McNeil Forbes [EMAIL PROTECTED]
To: lyx-users@lists.lyx.org
Subject: layout and template from LaTeX class.
Hi,
I have developed a LaTeX thesis class for UBC and have received questions
about how to use it with LyX. As I know very little about LyX, I am not
sure how to proceed.
All of the LaTeX class files and templates can be found below:
http://alum.mit.edu/www/mforbes/projects/ubcthesis/
I am trying to make the ubcthesis.cls compliant with UBC standards, and so
have provided a sample file ubcsample.tex that contains many comments
about the ordering of content, formatting issues etc. as required by the
university. These must be presented to users: I assume that this would be
done through a template for LyX users.
What is the best way to make this class available to LyX users?
The ubcthesis.cls is a modification of the standard book.cls.
I have tried making a simple ubcthesis.layout file:
-
#% Do not delete the line below; configure depends on this
# \DeclareLaTeXClass[ubcthesis]{University of British Columbia Theses}
# Read the definitions from book.layout
Input book.layout
-
It seems to work, but importing the ubcsample.tex renders most of the
comments in an extremely usless format. Many of the comments are about
ways of doing things in LaTeX or required stuff, and the resulting file
seems almost useless for someone starting a thesis in LyX. (I think
it would be easier for them to use LaTeX!)
Any suggestions on how to best make this class available to LyX users?
I've been through this kind of problems: in sample files, you find two
kinds of information:
- instructions about how to use the class (various commands available), often
alternating
piece of code and example of result;
- complements of instructions about layout (e.g. appearance of tables, space
around figures, etc.).
The pieces of code are not needed in the LyX case if the layout implements all
particularities
of the class: the sample can be restricted to an illustration of the specific
styles.
So the template/example (i.e. a template which is not empty, but filled with
examples of use)
can be much simpler than the LaTeX equivalent.
The complementary instructions are normally not needed as they are a remaining
of the time where
publishers sent to authors the description of the desired layout: if the class
is correctly
built, these layout instructions should not exist anymore.
However as the class can be incomplete (e.g. for tables layout), parts of the
LaTeX code
can be included in ERT to produce the explanations in screen or paper versions.
HTH
--
Jean-Pierre
Re: layout and template from LaTeX class.
On Fri, 16 Jun 2006, Jean-Pierre Chretien wrote: I've been through this kind of problems: in sample files, you find two kinds of information: - instructions about how to use the class (various commands available), often alternating piece of code and example of result; - complements of instructions about layout (e.g. appearance of tables, space around figures, etc.). The pieces of code are not needed in the LyX case if the layout implements all particularities of the class: the sample can be restricted to an illustration of the specific styles. So the template/example (i.e. a template which is not empty, but filled with examples of use) can be much simpler than the LaTeX equivalent. My design philosophy for the thesis class was to keep to a standard LaTeX idiom. It is possible to force the user to use a particular layout by having the class place the text in the appropriate order etc. but this would probably break many packages etc. Also, requirements are often not rigid when strange situations are encountered, and having a rigid class would prevent some people from using it. Thus, the comments are required to give users the freedom to do what they need, but the information they need to meet with approval if everything is standard. The complementary instructions are normally not needed as they are a remaining of the time where publishers sent to authors the description of the desired layout: if the class is correctly built, these layout instructions should not exist anymore. However as the class can be incomplete (e.g. for tables layout), parts of the LaTeX code can be included in ERT to produce the explanations in screen or paper versions. I have only a vague idea about what ERT is and how it fits in with the typical LyX experience, nor how to put the required information in the layout/template files. Apart from generating a simple layout file, I have not found clear documentation about what needs to be done. I want to avoid having to maintain two sets of files: one for LaTeX users and one for LyX users. Ideally, I would like to be able to specify enough information in the .cls and example files that the appropriate LyX stuff could be extracted, but I don't want to make life ore difficult for LaTeX users by cluttering up the sample files with LyX specific commands. Is this possible, or do I essentially have to maintain two separate projects: a LaTeX project (.cls + sample.tex) and a separate LyX project (.layout + template)? If not, I will have to wait until a LyX guru wants to volunteer to maintain the latter project before I can offer LyX support for the thesis templates. Thanks, Michael.
Errors
While generating the output of my document, the following errors are
presented:
... septiembre de 1964 \citep{RepsolYPF2005a}
, se inaugura la
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
...\jburluse {RepsolYPF2005a}} {\bibhowcited}
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
I'm using Jurabib, Miktex and LyX 1.4.1 on WinXP... I still cannot be able
to properly use Jurabib in WinLyX, citations are repalced by ? (before
these errors appeared)... If I export the documento to LaTeX and process it
with TeXnicCenter I can see the whole path for Jurabib is added. If I remove
it, Jurabib works fine. This is the 3rd time I ask for a solution to this
problem within LyX. Hope somebody can help me.
--
-
Julio Rojas
[EMAIL PROTECTED]
Re: Layout copyright; was: Re: Sharing layout files
On Thursday 15 June 2006 06:06 pm, [EMAIL PROTECTED] wrote: On Mon, 12 Jun 2006, David Neeley wrote: Comments within On 6/12/06, Steve Litt [EMAIL PROTECTED] wrote: Why can't the original author label his or her contribution as Licensed under the GNU General Public License, Version 2, or similar. Layout files are code, so the GPL fits them well. Speaking for myself, I'd be hesitant to contribute anything without GPL'ling it, because some licenses leave open the door for a big bad company to change my layout just a little bit and take it proprietary, and who knows, some day sue me for using code derived from their code, and then I have to prove that mine preceded theirs. snip There is a considerable debate, as you probably know, about whether the GPL is a good idea for areas such as these in which a layout may be used to create commercial documents. That is why I would suggest something like the BSD approach that permits commercial use. snip Finally, it is unlikely that layout files themselves would be an issue--since the objective is the documents created with that layout file and not the layout file itself. I really think that this discussion is largely the result of worry over what is very unlikely to happen to begin with--but a reasonable application of a license is certainly not a bad idea at all. This is issue is apparently a bit complicated. However, I think it was a good idea to emphasize that wiki authors are free to license their work as they see fit, especially any files they upload. So, for the page http://wiki.lyx.org/Site/Copyrights What do you about adding a paragraph such as this: Please note that contributors are free to license uploaded material as they see fit. So if you wish to upload layout examples under some specific license, please do so. I HUGELY like this. License has always been important to me. I believe the VimOutliner project evolved so well in part because of my original choice to license it GPL. I felt funny about putting my stuff up there with a license chosen by others, so this is a good thing. In a related thread somebody mentioned GPL wouldn't be good because some people use LyX for commercial purposes. I'd imagine the only thing being sold are the pdf or paper output (please let me know if you think I'm wrong), and I'd imagine (please let me know if you think I'm wrong) that the pdf or paper output would be like a report made by the software, not a compiled version of the software. If I'm wrong, my whole business is illegal, as I sell proprietary books assembled with various free software, including GPL. Thanks SteveT Steve Litt Author: * Universal Troubleshooting Process courseware * Troubleshooting Techniques of the Successful Technologist * Manager's Guide to Technical Troubleshooting * Twenty Eight Tales of Troubleshooting * Rapid Learning: Secret Weapon of the Successful Technologist http://www.troubleshooters.com/bookstore http://www.troubleshooters.com/utp/tcourses.htm
typing Lyx-code quotes
Thanks, Jurgen, for the updated font!
That still leaves a Lyx question.
To put quotes in Lyx-code, I know plain quote does not work. I tried
both C-quotekey and C-S-quotekey, and each gives me a *single* quote. I
could copy the typewrite double quote character from the UserGuide
example, and it looks fine, but I do not know how to enter it directly.
Thanks,
Andy Harrington
Juergen Spitzmueller wrote:
Andrew Harrington wrote:
I am not managing to get two things I want with fonts:
I want English text + .png graphics to look decent in Acroread. I get
complete output using pdflatex, but as the Extended Features Guide
5.3.6.2 mentions, the fonts look awful, so I followed the suggestion and
put in my preamble
\usepackage{ae,aecompl}
Then I get a decent font in Acroread.
\usepackage{lmodern}
(the Latin Modern fonts) is a much better choice nowadays.
HTH,
Jürgen
--
Andrew N. Harrington
Computer Science Department Undergraduate Program Director
Loyola University Chicagohttp://www.cs.luc.edu/~anh
512B Lewis Towers (office) Office Phone: 312-915-7982
Snail mail to Lewis Towers 416 Dept. Fax:312-915-7998
820 North Michigan Avenue[EMAIL PROTECTED]
Chicago, Illinois 60611
Re: typing Lyx-code quotes
Andrew Harrington wrote: To put quotes in Lyx-code, I know plain quote does not work. I tried both C-quotekey and C-S-quotekey, and each gives me a *single* quote. I could copy the typewrite double quote character from the UserGuide example, and it looks fine, but I do not know how to enter it directly. I can't remember if the key shortcut has changed between LyX 1.3 and LyX 1.4, but it should be either C-S-quotekey or M-S-quotekey. Jürgen
Re: Layout copyright; was: Re: Sharing layout files
The real first question is whether a layout file can be covered by copyright to begin with. As I pointed out before, one good example is fonts. While their names can be copyrighted, the actual outline and metric files cannot be. I have no doubt that in the current state of the law, the application code can be copyright material; I am not so sanguine about layout files. I should add that I have not practiced law in about fifteen years, and intellectual property law has changed a good bit in that time. Finally, I do believe that if you wish to be covered, the wiki should have a copyright statement something like: Files submitted to the wiki for general download are covered by the XXX license in the name of their respective author, unless specified otherwise by the contributing authors. I would suggest something like the BSD license as the basic one, so there are no real limitations or questions about use--commercial or otherwise--but giving the contributor the option of choosing another one if he or she desires. That way, if the files can be copyrighted, they would be covered in all cases. It would also cover those that are submitted when the author doesn't want to go to the trouble of figuring all of this out, but does not wish for others to claim copyright to his or her work. David On 6/16/06, Steve Litt [EMAIL PROTECTED] wrote: On Thursday 15 June 2006 06:06 pm, [EMAIL PROTECTED] wrote: On Mon, 12 Jun 2006, David Neeley wrote: Comments within On 6/12/06, Steve Litt [EMAIL PROTECTED] wrote: Why can't the original author label his or her contribution as Licensed under the GNU General Public License, Version 2, or similar. Layout files are code, so the GPL fits them well. Speaking for myself, I'd be hesitant to contribute anything without GPL'ling it, because some licenses leave open the door for a big bad company to change my layout just a little bit and take it proprietary, and who knows, some day sue me for using code derived from their code, and then I have to prove that mine preceded theirs. snip There is a considerable debate, as you probably know, about whether the GPL is a good idea for areas such as these in which a layout may be used to create commercial documents. That is why I would suggest something like the BSD approach that permits commercial use. snip Finally, it is unlikely that layout files themselves would be an issue--since the objective is the documents created with that layout file and not the layout file itself. I really think that this discussion is largely the result of worry over what is very unlikely to happen to begin with--but a reasonable application of a license is certainly not a bad idea at all. This is issue is apparently a bit complicated. However, I think it was a good idea to emphasize that wiki authors are free to license their work as they see fit, especially any files they upload. So, for the page http://wiki.lyx.org/Site/Copyrights What do you about adding a paragraph such as this: Please note that contributors are free to license uploaded material as they see fit. So if you wish to upload layout examples under some specific license, please do so. I HUGELY like this. License has always been important to me. I believe the VimOutliner project evolved so well in part because of my original choice to license it GPL. I felt funny about putting my stuff up there with a license chosen by others, so this is a good thing. In a related thread somebody mentioned GPL wouldn't be good because some people use LyX for commercial purposes. I'd imagine the only thing being sold are the pdf or paper output (please let me know if you think I'm wrong), and I'd imagine (please let me know if you think I'm wrong) that the pdf or paper output would be like a report made by the software, not a compiled version of the software. If I'm wrong, my whole business is illegal, as I sell proprietary books assembled with various free software, including GPL. Thanks SteveT Steve Litt Author: * Universal Troubleshooting Process courseware * Troubleshooting Techniques of the Successful Technologist * Manager's Guide to Technical Troubleshooting * Twenty Eight Tales of Troubleshooting * Rapid Learning: Secret Weapon of the Successful Technologist http://www.troubleshooters.com/bookstore http://www.troubleshooters.com/utp/tcourses.htm
Bibliography Style apalike
The closest bib style to what a certain journal want seems to be apalike2, while apalike is not as close but OK. LyX supports apalike (Can it be made to support apalike2?) Suppose then I use apalike. Does anyone know how I can find out what fields are supported in apalike style? For example, does it have a field called Translator and if so, does that mean I should define a custom field in BibDesk called Translator? Thanks for any help the list can provide. Bruce
Re: Layout copyright; was: Re: Sharing layout files
On Friday 16 June 2006 11:50 am, you wrote: The real first question is whether a layout file can be covered by copyright to begin with. As I pointed out before, one good example is fonts. While their names can be copyrighted, the actual outline and metric files cannot be. I didn't know that. In that case, how can a font foundary legally prevent their fonts from being copied willy nilly around the world? If protected only by a trademark, one could copy the outline and metric files and call them StevesSansSerif for instance. If protected by patent, what would be so novel from one font to another that a patent would be issued? SteveT Steve Litt Author: * Universal Troubleshooting Process courseware * Troubleshooting Techniques of the Successful Technologist * Manager's Guide to Technical Troubleshooting * Twenty Eight Tales of Troubleshooting * Rapid Learning: Secret Weapon of the Successful Technologist http://www.troubleshooters.com/bookstore http://www.troubleshooters.com/utp/tcourses.htm
Re: Layout copyright; was: Re: Sharing layout files
On Friday 16 June 2006 11:50 am, David Neeley wrote: Finally, I do believe that if you wish to be covered, the wiki should have a copyright statement something like: Files submitted to the wiki for general download are covered by the XXX license in the name of their respective author, unless specified otherwise by the contributing authors. That sounds good. I would suggest something like the BSD license as the basic one, so there are no real limitations or questions about use--commercial or otherwise--but giving the contributor the option of choosing another one if he or she desires. That way, if the files can be copyrighted, they would be covered in all cases. That also sounds good, at least for most stuff, including what I emailed a couple days ago. If it were something I worked 60 hours on I might go GPL to prevent a Microsoft Kerberos type situation, but my layout files aren't that type of work. Thanks for the clarification and good idea. SteveT Steve Litt Author: * Universal Troubleshooting Process courseware * Troubleshooting Techniques of the Successful Technologist * Manager's Guide to Technical Troubleshooting * Twenty Eight Tales of Troubleshooting * Rapid Learning: Secret Weapon of the Successful Technologist http://www.troubleshooters.com/bookstore http://www.troubleshooters.com/utp/tcourses.htm
Re: Bibliography Style apalike
Look at the file apalike.bst, which will tell you want fields are defined. (There is no field translator, by the way.) And you can use apalike2, if you wish. Just hit the browse button in the dialog where you choose a bibliography style, and then go find the file apalike2.bst. It is, by the way, not that terribly hard to modify these styles once you get the hang of it. Richard Bruce Pourciau wrote: The closest bib style to what a certain journal want seems to be apalike2, while apalike is not as close but OK. LyX supports apalike (Can it be made to support apalike2?) Suppose then I use apalike. Does anyone know how I can find out what fields are supported in apalike style? For example, does it have a field called Translator and if so, does that mean I should define a custom field in BibDesk called Translator? Thanks for any help the list can provide. Bruce
Re: Bibliography Style apalike
Thanks, Richard. That helps. When you say Just hit the browse button in the dialog where you choose a bibliography style, and then go find the file apalike2.bst. do you mean find it in my tex installation or find it on the web and donwnload it? What field would normally be used for additional information -- translator, privately published, an add-on to the title, etc? Bruce On Jun 16, 2006, at 1:58 PM, Richard Heck wrote: Look at the file apalike.bst, which will tell you want fields are defined. (There is no field translator, by the way.) And you can use apalike2, if you wish. Just hit the browse button in the dialog where you choose a bibliography style, and then go find the file apalike2.bst. It is, by the way, not that terribly hard to modify these styles once you get the hang of it. Richard Bruce Pourciau wrote: The closest bib style to what a certain journal want seems to be apalike2, while apalike is not as close but OK. LyX supports apalike (Can it be made to support apalike2?) Suppose then I use apalike. Does anyone know how I can find out what fields are supported in apalike style? For example, does it have a field called Translator and if so, does that mean I should define a custom field in BibDesk called Translator? Thanks for any help the list can provide. Bruce
Re: Layout copyright; was: Re: Sharing layout files
Steve Litt wrote: On Friday 16 June 2006 11:50 am, David Neeley wrote: Finally, I do believe that if you wish to be covered, the wiki should have a copyright statement something like: Files submitted to the wiki for general download are covered by the XXX license in the name of their respective author, unless specified otherwise by the contributing authors. That sounds good. I would suggest something like the BSD license as the basic one, so there are no real limitations or questions about use--commercial or otherwise--but giving the contributor the option of choosing another one if he or she desires. That way, if the files can be copyrighted, they would be covered in all cases. That also sounds good, at least for most stuff, including what I emailed a couple days ago. If it were something I worked 60 hours on I might go GPL to prevent a Microsoft Kerberos type situation, but my layout files aren't that type of work. Thanks for the clarification and good idea. http://www.c4.net/Index.cfm?Method=NewsStories.NewsStoryNewsStory_ID=143 This article at the Register discusses one of the major hurtles confronting would be challengers to the Microsoft throne, fonts. It may seem like an insignificant part of the whole, but it is important enough that current U.S. law actually makes an exception for copyrighting the shape and design of fonts in the name of free press. This means that, for all intents and purposes, you could rename a font and redistribute it…in the States. Other countries are not so forgiving, and that's where trouble comes into paradise.
Re: Bibliography Style apalike
That file should be on your TeX installation. Use whatever find-a-file stuff you have available to locate it. I tend to put translator info in the Note field. Whatever you put there will be set at the end of the entry, using apalike (and probably apalike2). It's not a great solution. I should modify apalike so that it does have a translator field that is put in a sensible place. I'd guess it's already been done, however. Richard Bruce Pourciau wrote: Thanks, Richard. That helps. When you say Just hit the browse button in the dialog where you choose a bibliography style, and then go find the file apalike2.bst. do you mean find it in my tex installation or find it on the web and donwnload it? What field would normally be used for additional information -- translator, privately published, an add-on to the title, etc? Bruce On Jun 16, 2006, at 1:58 PM, Richard Heck wrote: Look at the file apalike.bst, which will tell you want fields are defined. (There is no field translator, by the way.) And you can use apalike2, if you wish. Just hit the browse button in the dialog where you choose a bibliography style, and then go find the file apalike2.bst. It is, by the way, not that terribly hard to modify these styles once you get the hang of it. Richard Bruce Pourciau wrote: The closest bib style to what a certain journal want seems to be apalike2, while apalike is not as close but OK. LyX supports apalike (Can it be made to support apalike2?) Suppose then I use apalike. Does anyone know how I can find out what fields are supported in apalike style? For example, does it have a field called Translator and if so, does that mean I should define a custom field in BibDesk called Translator? Thanks for any help the list can provide. Bruce
Re: Layout copyright; was: Re: Sharing layout files
Steve Litt wrote: On Friday 16 June 2006 11:50 am, David Neeley wrote: Finally, I do believe that if you wish to be covered, the wiki should have a copyright statement something like: Files submitted to the wiki for general download are covered by the XXX license in the name of their respective author, unless specified otherwise by the contributing authors. That sounds good. I would suggest something like the BSD license as the basic one, so there are no real limitations or questions about use--commercial or otherwise--but giving the contributor the option of choosing another one if he or she desires. That way, if the files can be copyrighted, they would be covered in all cases. That also sounds good, at least for most stuff, including what I emailed a couple days ago. If it were something I worked 60 hours on I might go GPL to prevent a Microsoft Kerberos type situation, but my layout files aren't that type of work. I've been reading about this some more. It turns out to be a very complex legal issue, especially regarding fonts, which do not have the same legal status as layout files. http://www-personal.umich.edu/~pfs/essay2.html Though I think your copyright rights, if they are weak, will extend to whoever tries to steal your work. If they can get away with stealing yours, then someone can steal from them too. Also obtaining a license for some fonts doesn't give you the same rights to use those fonts as if you had bought them.
jurabib question
I'm having a difficult time getting jurabib set-up the way that I want. I
have it close, but there are still a couple of issues.
First, I have the 'titleformat=italic command in the preamble, but am still
not getting my titles italicized (in either the original references or the
bibliography). I thought that was the purpose of that command. I have the
oxford option enabled as well--is that the problem? Any ideas?
I also have the 'bibformat=ibidem' command set. It works well, but I am
getting duplicate authors listed with 'idem' and would like that replaced
with the standard '---'. The documentation seems to be saying that the dash
should be the default, so I'm not sure what I can do to fix it.
Finally, I'm can't seem to get the 'chicago' format command to work. This
isn't a huge deal since oxford is close enough, but I'd like to know what
I'm doing wrong. I've included the jurabib section from my preamble below
(it is just a modified version of the suggested format suggested in the
humanities section of the lyxwiki---so the credit lies there, and the blame
is mine.
\jurabibsetup{%
titleformat=italic%
titleformat=commasep,%
bibformat=ibidem,%
commabeforerest,%
ibidem=strict,%
citefull=first,%
lookat,%
oxford,%
pages=format,%
human=true,%
idem=strict%
}
Any help would be greatly appreciated.
John Ward
Graduate Assistant
Department of Philosophy
University of Utah
Zref package expands reference system flexibility
The zref package Heiko Oberdiek 2006/05/25 v1.2
Abstract
Package zref tries to get rid of the restriction in LATEX's
reference system that only two properties are supported. The
package implements an extensible referencing system, where
properties are handled in a more flexible way. It offers an
interface for macro programmers for the access to the system
and some applications that uses the new reference scheme.
http://www.informatik.uni-freiburg.de/~oberdiek/tmp/zref.pdf
(temporary location until I find time for a CTAN upload)
Chapter 7 and 7.1 include installation details.
pdftk zref.pdf unpack_files output produces zref.dtx
which is unpacked with tex zref.dtx
pdftk is a free download available from AccessPDF
http://www.accesspdf.com/article.php/20041130153545577
There are several files produced by tex zref.dtx
which need to be copied to their appropriate directory on
your system. Most of the Oberdiek directories already
existed on my system with the execption of the source
path for /Oberdiek which will contain the zref.dtx file.
-
6.2.10 Compatibility with babel
[EMAIL PROTECTED]@babel
430 [EMAIL PROTECTED]@babel#1#2{%
431 \begingroup
432 \csname @[EMAIL PROTECTED]
433 \edef\x{#2}%
434 \expandafter\endgroup
435 [EMAIL PROTECTED]@babel\expandafter{\x}{#1}%
436 }
437 [EMAIL PROTECTED]@babel#1#2{%
438 #2{#1}%
439 }
---
SH: I figure this package will benefit someone, sometime.
Regards,
--
Stephen
Topic ontology recapitulates entropic philology.
Re: conflict with good font for Acroread and Lyx-code quotes
Andrew Harrington wrote:
> I am not managing to get two things I want with fonts:
> I want English text + .png graphics to look decent in Acroread. I get
> complete output using pdflatex, but as the Extended Features Guide
> 5.3.6.2 mentions, the fonts look awful, so I followed the suggestion and
> put in my preamble
> \usepackage{ae,aecompl}
> Then I get a decent font in Acroread.
\usepackage{lmodern}
(the Latin Modern fonts) is a much better choice nowadays.
> However, when I put a double quote character in Lyx-code, I get a black
> square as output for the quotes. (Single quotes are OK, though two
> single quotes together gives the same problem.) I do not know how many
> other characters would give the same problem.
This is a known limitation of the ae package. You might try
\usepackage{aeguill}
but I'd still recommend Latin Modern.
HTH,
Jürgen
Re: layout and template from LaTeX class.
>>Date: Thu, 15 Jun 2006 19:30:05 -0700 (PDT)
>>From: Michael McNeil Forbes <[EMAIL PROTECTED]>
>>To: lyx-users@lists.lyx.org
>>Subject: layout and template from LaTeX class.
>>
>>Hi,
>>
>>I have developed a LaTeX thesis class for UBC and have received questions
>>about how to use it with LyX. As I know very little about LyX, I am not
>>sure how to proceed.
>>
>>All of the LaTeX class files and templates can be found below:
>>http://alum.mit.edu/www/mforbes/projects/ubcthesis/
>>
>>I am trying to make the ubcthesis.cls compliant with UBC standards, and so
>>have provided a sample file ubcsample.tex that contains many comments
>>about the ordering of content, formatting issues etc. as required by the
>>university. These must be presented to users: I assume that this would be
>>done through a "template" for LyX users.
>>
>>What is the best way to make this class available to LyX users?
>>
>>The ubcthesis.cls is a modification of the standard book.cls.
>>
>>I have tried making a simple ubcthesis.layout file:
>>-
>>#% Do not delete the line below; configure depends on this
>># \DeclareLaTeXClass[ubcthesis]{University of British Columbia Theses}
>>
>># Read the definitions from book.layout
>>Input book.layout
>>-
>>It seems to work, but importing the ubcsample.tex renders most of the
>>comments in an extremely usless format. Many of the comments are about
>>ways of doing things in LaTeX or required stuff, and the resulting file
>>seems almost useless for someone starting a thesis in LyX. (I think
>>it would be easier for them to use LaTeX!)
>>
>>Any suggestions on how to best make this class available to LyX users?
I've been through this kind of problems: in sample files, you find two
kinds of information:
- instructions about how to use the class (various commands available), often
alternating
piece of code and example of result;
- complements of instructions about layout (e.g. appearance of tables, space
around figures, etc.).
The pieces of code are not needed in the LyX case if the layout implements all
particularities
of the class: the sample can be restricted to an illustration of the specific
styles.
So the template/example (i.e. a template which is not empty, but filled with
examples of use)
can be much simpler than the LaTeX equivalent.
The complementary instructions are normally not needed as they are a remaining
of the time where
publishers sent to authors the description of the desired layout: if the class
is correctly
built, these layout instructions should not exist anymore.
However as the class can be incomplete (e.g. for tables layout), parts of the
LaTeX code
can be included in ERT to produce the explanations in screen or paper versions.
HTH
--
Jean-Pierre
Re: layout and template from LaTeX class.
On Fri, 16 Jun 2006, Jean-Pierre Chretien wrote: > I've been through this kind of problems: in sample files, you find two > kinds of information: > - instructions about how to use the class (various commands available), >often alternating piece of code and example of result; > - complements of instructions about layout (e.g. appearance of tables, >space around figures, etc.). > > The pieces of code are not needed in the LyX case if the layout > implements all particularities of the class: the sample can be > restricted to an illustration of the specific styles. So the > template/example (i.e. a template which is not empty, but filled with > examples of use) can be much simpler than the LaTeX equivalent. My design philosophy for the thesis class was to keep to a standard LaTeX idiom. It is possible to force the user to use a particular layout by having the class place the text in the appropriate order etc. but this would probably break many packages etc. Also, "requirements" are often not rigid when strange situations are encountered, and having a rigid class would prevent some people from using it. Thus, the comments are required to give users the freedom to do what they need, but the information they need to meet with approval if everything is standard. > The complementary instructions are normally not needed as they are a > remaining of the time where publishers sent to authors the description > of the desired layout: if the class is correctly built, these layout > instructions should not exist anymore. However as the class can be > incomplete (e.g. for tables layout), parts of the LaTeX code can be > included in ERT to produce the explanations in screen or paper versions. I have only a vague idea about what ERT is and how it fits in with the typical LyX experience, nor how to put the required information in the layout/template files. Apart from generating a simple layout file, I have not found clear documentation about what needs to be done. I want to avoid having to maintain two sets of files: one for LaTeX users and one for LyX users. Ideally, I would like to be able to specify enough information in the .cls and example files that the appropriate LyX stuff could be extracted, but I don't want to make life ore difficult for LaTeX users by cluttering up the sample files with LyX specific commands. Is this possible, or do I essentially have to maintain two separate projects: a LaTeX project (.cls + sample.tex) and a separate LyX project (.layout + template)? If not, I will have to wait until a LyX guru wants to volunteer to maintain the latter project before I can offer LyX support for the thesis templates. Thanks, Michael.
Errors
While generating the output of my document, the following errors are
presented:
... septiembre de 1964 \citep{RepsolYPF2005a}
, se inaugura la
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
...\jburluse {RepsolYPF2005a}} {\bibhowcited}
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
I'm using Jurabib, Miktex and LyX 1.4.1 on WinXP... I still cannot be able
to properly use Jurabib in WinLyX, citations are repalced by "?" (before
these errors appeared)... If I export the documento to LaTeX and process it
with TeXnicCenter I can see the whole path for Jurabib is added. If I remove
it, Jurabib works fine. This is the 3rd time I ask for a solution to this
problem within LyX. Hope somebody can help me.
--
-
Julio Rojas
[EMAIL PROTECTED]
Re: Layout copyright; was: Re: Sharing layout files
On Thursday 15 June 2006 06:06 pm, [EMAIL PROTECTED] wrote: > On Mon, 12 Jun 2006, David Neeley wrote: > > Comments within > > > > On 6/12/06, Steve Litt > > > > <[EMAIL PROTECTED]> wrote: > >> Why can't the original author label his or her contribution as "Licensed > >> under the GNU General Public License, Version 2", or similar. Layout > >> files are code, so the GPL fits them well. Speaking for myself, I'd be > >> hesitant to contribute anything without GPL'ling it, because some > >> licenses leave open the door for a big bad company to change my layout > >> just a little bit and take it proprietary, and who knows, some day sue > >> me for using code derived from their code, and then I have to prove that > >> mine preceded theirs. > > > > > There is a considerable debate, as you probably know, about whether the > > GPL is a good idea for areas such as these in which a layout may be used > > to create commercial documents. That is why I would suggest something > > like the BSD approach that permits commercial use. > > > > > Finally, it is unlikely that layout files themselves would be an > > issue--since the objective is the documents created with that layout > > file and not the layout file itself. I really think that this discussion > > is largely the result of worry over what is very unlikely to happen to > > begin with--but a reasonable application of a license is certainly not a > > bad idea at all. > > This is issue is apparently a bit complicated. However, I think it was a > good idea to emphasize that wiki authors are free to license their work > as they see fit, especially any files they upload. So, for the page > > http://wiki.lyx.org/Site/Copyrights > > What do you about adding a paragraph such as this: > > Please note that contributors are free to license uploaded > material as they see fit. So if you wish to upload layout examples > under some specific license, please do so. I HUGELY like this. License has always been important to me. I believe the VimOutliner project evolved so well in part because of my original choice to license it GPL. I felt funny about putting my stuff up there with a license chosen by others, so this is a good thing. In a related thread somebody mentioned GPL wouldn't be good because some people use LyX for commercial purposes. I'd imagine the only thing being sold are the pdf or paper output (please let me know if you think I'm wrong), and I'd imagine (please let me know if you think I'm wrong) that the pdf or paper output would be like a report made by the software, not a compiled version of the software. If I'm wrong, my whole business is illegal, as I sell proprietary books assembled with various free software, including GPL. Thanks SteveT Steve Litt Author: * Universal Troubleshooting Process courseware * Troubleshooting Techniques of the Successful Technologist * Manager's Guide to Technical Troubleshooting * Twenty Eight Tales of Troubleshooting * Rapid Learning: Secret Weapon of the Successful Technologist http://www.troubleshooters.com/bookstore http://www.troubleshooters.com/utp/tcourses.htm
typing Lyx-code quotes
Thanks, Jurgen, for the updated font!
That still leaves a Lyx question.
To put quotes in Lyx-code, I know plain quote does not work. I tried
both C-quotekey and C-S-quotekey, and each gives me a *single* quote. I
could copy the typewrite double quote character from the UserGuide
example, and it looks fine, but I do not know how to enter it directly.
Thanks,
Andy Harrington
Juergen Spitzmueller wrote:
Andrew Harrington wrote:
I am not managing to get two things I want with fonts:
I want English text + .png graphics to look decent in Acroread. I get
complete output using pdflatex, but as the Extended Features Guide
5.3.6.2 mentions, the fonts look awful, so I followed the suggestion and
put in my preamble
\usepackage{ae,aecompl}
Then I get a decent font in Acroread.
\usepackage{lmodern}
(the Latin Modern fonts) is a much better choice nowadays.
HTH,
Jürgen
--
Andrew N. Harrington
Computer Science Department Undergraduate Program Director
Loyola University Chicagohttp://www.cs.luc.edu/~anh
512B Lewis Towers (office) Office Phone: 312-915-7982
Snail mail to Lewis Towers 416 Dept. Fax:312-915-7998
820 North Michigan Avenue[EMAIL PROTECTED]
Chicago, Illinois 60611
Re: typing Lyx-code quotes
Andrew Harrington wrote: > To put quotes in Lyx-code, I know plain quote does not work. I tried > both C-quotekey and C-S-quotekey, and each gives me a *single* quote. I > could copy the typewrite double quote character from the UserGuide > example, and it looks fine, but I do not know how to enter it directly. I can't remember if the key shortcut has changed between LyX 1.3 and LyX 1.4, but it should be either C-S-quotekey or M-S-quotekey. Jürgen
Re: Layout copyright; was: Re: Sharing layout files
The real first question is whether a layout file can be covered by copyright to begin with. As I pointed out before, one good example is fonts. While their names can be copyrighted, the actual outline and metric files cannot be. I have no doubt that in the current state of the law, the application code can be copyright material; I am not so sanguine about layout files. I should add that I have not practiced law in about fifteen years, and intellectual property law has changed a good bit in that time. Finally, I do believe that if you wish to be covered, the wiki should have a copyright statement something like: "Files submitted to the wiki for general download are covered by the XXX license in the name of their respective author, unless specified otherwise by the contributing authors." I would suggest something like the BSD license as the basic one, so there are no real limitations or questions about use--commercial or otherwise--but giving the contributor the option of choosing another one if he or she desires. That way, if the files can be copyrighted, they would be covered in all cases. It would also cover those that are submitted when the author doesn't want to go to the trouble of figuring all of this out, but does not wish for others to claim copyright to his or her work. David On 6/16/06, Steve Litt <[EMAIL PROTECTED]> wrote: On Thursday 15 June 2006 06:06 pm, [EMAIL PROTECTED] wrote: > On Mon, 12 Jun 2006, David Neeley wrote: > > Comments within > > > > On 6/12/06, Steve Litt > > > > <[EMAIL PROTECTED]> wrote: > >> Why can't the original author label his or her contribution as "Licensed > >> under the GNU General Public License, Version 2", or similar. Layout > >> files are code, so the GPL fits them well. Speaking for myself, I'd be > >> hesitant to contribute anything without GPL'ling it, because some > >> licenses leave open the door for a big bad company to change my layout > >> just a little bit and take it proprietary, and who knows, some day sue > >> me for using code derived from their code, and then I have to prove that > >> mine preceded theirs. > > > > > There is a considerable debate, as you probably know, about whether the > > GPL is a good idea for areas such as these in which a layout may be used > > to create commercial documents. That is why I would suggest something > > like the BSD approach that permits commercial use. > > > > > Finally, it is unlikely that layout files themselves would be an > > issue--since the objective is the documents created with that layout > > file and not the layout file itself. I really think that this discussion > > is largely the result of worry over what is very unlikely to happen to > > begin with--but a reasonable application of a license is certainly not a > > bad idea at all. > > This is issue is apparently a bit complicated. However, I think it was a > good idea to emphasize that wiki authors are free to license their work > as they see fit, especially any files they upload. So, for the page > > http://wiki.lyx.org/Site/Copyrights > > What do you about adding a paragraph such as this: > > Please note that contributors are free to license uploaded > material as they see fit. So if you wish to upload layout examples > under some specific license, please do so. I HUGELY like this. License has always been important to me. I believe the VimOutliner project evolved so well in part because of my original choice to license it GPL. I felt funny about putting my stuff up there with a license chosen by others, so this is a good thing. In a related thread somebody mentioned GPL wouldn't be good because some people use LyX for commercial purposes. I'd imagine the only thing being sold are the pdf or paper output (please let me know if you think I'm wrong), and I'd imagine (please let me know if you think I'm wrong) that the pdf or paper output would be like a report made by the software, not a compiled version of the software. If I'm wrong, my whole business is illegal, as I sell proprietary books assembled with various free software, including GPL. Thanks SteveT Steve Litt Author: * Universal Troubleshooting Process courseware * Troubleshooting Techniques of the Successful Technologist * Manager's Guide to Technical Troubleshooting * Twenty Eight Tales of Troubleshooting * Rapid Learning: Secret Weapon of the Successful Technologist http://www.troubleshooters.com/bookstore http://www.troubleshooters.com/utp/tcourses.htm
Bibliography Style apalike
The closest bib style to what a certain journal want seems to be apalike2, while apalike is not as close but OK. LyX supports apalike (Can it be made to support apalike2?) Suppose then I use apalike. Does anyone know how I can find out what fields are supported in apalike style? For example, does it have a field called Translator and if so, does that mean I should define a custom field in BibDesk called Translator? Thanks for any help the list can provide. Bruce
Re: Layout copyright; was: Re: Sharing layout files
On Friday 16 June 2006 11:50 am, you wrote: > The real first question is whether a layout file can be covered by > copyright to begin with. > > As I pointed out before, one good example is fonts. While their names > can be copyrighted, the actual outline and metric files cannot be. I didn't know that. In that case, how can a font foundary legally prevent their fonts from being copied willy nilly around the world? If protected only by a trademark, one could copy the outline and metric files and call them "StevesSansSerif" for instance. If protected by patent, what would be so novel from one font to another that a patent would be issued? SteveT Steve Litt Author: * Universal Troubleshooting Process courseware * Troubleshooting Techniques of the Successful Technologist * Manager's Guide to Technical Troubleshooting * Twenty Eight Tales of Troubleshooting * Rapid Learning: Secret Weapon of the Successful Technologist http://www.troubleshooters.com/bookstore http://www.troubleshooters.com/utp/tcourses.htm
Re: Layout copyright; was: Re: Sharing layout files
On Friday 16 June 2006 11:50 am, David Neeley wrote: > Finally, I do believe that if you wish to be covered, the wiki should > have a copyright statement something like: > > "Files submitted to the wiki for general download are covered by the > XXX license in the name of their respective author, unless specified > otherwise by the contributing authors." That sounds good. > > I would suggest something like the BSD license as the basic one, so > there are no real limitations or questions about use--commercial or > otherwise--but giving the contributor the option of choosing another > one if he or she desires. That way, if the files can be copyrighted, > they would be covered in all cases. That also sounds good, at least for most stuff, including what I emailed a couple days ago. If it were something I worked 60 hours on I might go GPL to prevent a Microsoft Kerberos type situation, but my layout files aren't that type of work. Thanks for the clarification and good idea. SteveT Steve Litt Author: * Universal Troubleshooting Process courseware * Troubleshooting Techniques of the Successful Technologist * Manager's Guide to Technical Troubleshooting * Twenty Eight Tales of Troubleshooting * Rapid Learning: Secret Weapon of the Successful Technologist http://www.troubleshooters.com/bookstore http://www.troubleshooters.com/utp/tcourses.htm
Re: Bibliography Style apalike
Look at the file apalike.bst, which will tell you want fields are defined. (There is no field "translator", by the way.) And you can use apalike2, if you wish. Just hit the "browse" button in the dialog where you choose a bibliography style, and then go find the file apalike2.bst. It is, by the way, not that terribly hard to modify these styles once you get the hang of it. Richard Bruce Pourciau wrote: > The closest bib style to what a certain journal want seems to be > apalike2, while apalike is not as close but OK. LyX supports apalike > (Can it be made to support apalike2?) Suppose then I use apalike. Does > anyone know how I can find out what fields are supported in apalike > style? For example, does it have a field called Translator and if so, > does that mean I should define a custom field in BibDesk called > Translator? > > Thanks for any help the list can provide. > > Bruce
Re: Bibliography Style apalike
Thanks, Richard. That helps. When you say Just hit the "browse" button in the dialog where you choose a bibliography style, and then go find the file apalike2.bst. do you mean find it in my tex installation or find it on the web and donwnload it? What field would normally be used for additional information -- translator, privately published, an add-on to the title, etc? Bruce On Jun 16, 2006, at 1:58 PM, Richard Heck wrote: Look at the file apalike.bst, which will tell you want fields are defined. (There is no field "translator", by the way.) And you can use apalike2, if you wish. Just hit the "browse" button in the dialog where you choose a bibliography style, and then go find the file apalike2.bst. It is, by the way, not that terribly hard to modify these styles once you get the hang of it. Richard Bruce Pourciau wrote: The closest bib style to what a certain journal want seems to be apalike2, while apalike is not as close but OK. LyX supports apalike (Can it be made to support apalike2?) Suppose then I use apalike. Does anyone know how I can find out what fields are supported in apalike style? For example, does it have a field called Translator and if so, does that mean I should define a custom field in BibDesk called Translator? Thanks for any help the list can provide. Bruce
Re: Layout copyright; was: Re: Sharing layout files
Steve Litt wrote: On Friday 16 June 2006 11:50 am, David Neeley wrote: Finally, I do believe that if you wish to be covered, the wiki should have a copyright statement something like: "Files submitted to the wiki for general download are covered by the XXX license in the name of their respective author, unless specified otherwise by the contributing authors." That sounds good. I would suggest something like the BSD license as the basic one, so there are no real limitations or questions about use--commercial or otherwise--but giving the contributor the option of choosing another one if he or she desires. That way, if the files can be copyrighted, they would be covered in all cases. That also sounds good, at least for most stuff, including what I emailed a couple days ago. If it were something I worked 60 hours on I might go GPL to prevent a Microsoft Kerberos type situation, but my layout files aren't that type of work. Thanks for the clarification and good idea. http://www.c4.net/Index.cfm?Method=NewsStories.NewsStory_ID=143 "This article at the Register discusses one of the major hurtles confronting would be challengers to the Microsoft throne, fonts. It may seem like an insignificant part of the whole, but it is important enough that current U.S. law actually makes an exception for copyrighting the shape and design of fonts in the name of free press. This means that, for all intents and purposes, you could rename a font and redistribute it…in the States. Other countries are not so forgiving, and that's where trouble comes into paradise."
Re: Bibliography Style apalike
That file should be on your TeX installation. Use whatever find-a-file stuff you have available to locate it. I tend to put translator info in the Note field. Whatever you put there will be set at the end of the entry, using apalike (and probably apalike2). It's not a great solution. I should modify apalike so that it does have a translator field that is put in a sensible place. I'd guess it's already been done, however. Richard Bruce Pourciau wrote: > Thanks, Richard. That helps. When you say >> Just hit the "browse" button in the dialog where >> you choose a bibliography style, and then go find the file apalike2.bst. > do you mean find it in my tex installation or find it on the web and > donwnload it? What field would normally be used for additional > information -- translator, privately published, an add-on to the > title, etc? > > Bruce > > > > On Jun 16, 2006, at 1:58 PM, Richard Heck wrote: > >> >> Look at the file apalike.bst, which will tell you want fields are >> defined. (There is no field "translator", by the way.) And you can use >> apalike2, if you wish. Just hit the "browse" button in the dialog where >> you choose a bibliography style, and then go find the file apalike2.bst. >> >> It is, by the way, not that terribly hard to modify these styles once >> you get the hang of it. >> >> Richard >> >> Bruce Pourciau wrote: >>> The closest bib style to what a certain journal want seems to be >>> apalike2, while apalike is not as close but OK. LyX supports apalike >>> (Can it be made to support apalike2?) Suppose then I use apalike. Does >>> anyone know how I can find out what fields are supported in apalike >>> style? For example, does it have a field called Translator and if so, >>> does that mean I should define a custom field in BibDesk called >>> Translator? >>> >>> Thanks for any help the list can provide. >>> >>> Bruce >>
Re: Layout copyright; was: Re: Sharing layout files
Steve Litt wrote: On Friday 16 June 2006 11:50 am, David Neeley wrote: Finally, I do believe that if you wish to be covered, the wiki should have a copyright statement something like: "Files submitted to the wiki for general download are covered by the XXX license in the name of their respective author, unless specified otherwise by the contributing authors." That sounds good. I would suggest something like the BSD license as the basic one, so there are no real limitations or questions about use--commercial or otherwise--but giving the contributor the option of choosing another one if he or she desires. That way, if the files can be copyrighted, they would be covered in all cases. That also sounds good, at least for most stuff, including what I emailed a couple days ago. If it were something I worked 60 hours on I might go GPL to prevent a Microsoft Kerberos type situation, but my layout files aren't that type of work. I've been reading about this some more. It turns out to be a very complex legal issue, especially regarding fonts, which do not have the same legal status as layout files. http://www-personal.umich.edu/~pfs/essay2.html Though I think your copyright rights, if they are weak, will extend to whoever tries to steal your "work". If they can get away with stealing yours, then someone can steal from them too. Also obtaining a license for some fonts doesn't give you the same rights to use those fonts as if you had bought them.
jurabib question
I'm having a difficult time getting jurabib set-up the way that I want. I
have it close, but there are still a couple of issues.
First, I have the 'titleformat=italic" command in the preamble, but am still
not getting my titles italicized (in either the original references or the
bibliography). I thought that was the purpose of that command. I have the
"oxford" option enabled as well--is that the problem? Any ideas?
I also have the 'bibformat=ibidem' command set. It works well, but I am
getting duplicate authors listed with 'idem' and would like that replaced
with the standard '---'. The documentation seems to be saying that the dash
should be the default, so I'm not sure what I can do to fix it.
Finally, I'm can't seem to get the 'chicago' format command to work. This
isn't a huge deal since oxford is close enough, but I'd like to know what
I'm doing wrong. I've included the jurabib section from my preamble below
(it is just a modified version of the suggested format suggested in the
humanities section of the lyxwiki---so the credit lies there, and the blame
is mine.
\jurabibsetup{%
titleformat=italic%
titleformat=commasep,%
bibformat=ibidem,%
commabeforerest,%
ibidem=strict,%
citefull=first,%
lookat,%
oxford,%
pages=format,%
human=true,%
idem=strict%
}
Any help would be greatly appreciated.
John Ward
Graduate Assistant
Department of Philosophy
University of Utah
Zref package expands reference system flexibility
The zref package Heiko Oberdiek 2006/05/25 v1.2
Abstract
"Package zref tries to get rid of the restriction in LATEX's
reference system that only two properties are supported. The
package implements an extensible referencing system, where
properties are handled in a more flexible way. It offers an
interface for macro programmers for the access to the system
and some applications that uses the new reference scheme."
"http://www.informatik.uni-freiburg.de/~oberdiek/tmp/zref.pdf
(temporary location until I find time for a CTAN upload)"
Chapter 7 and 7.1 include installation details.
"pdftk zref.pdf unpack_files output" produces zref.dtx
which is unpacked with "tex zref.dtx"
pdftk is a free download available from AccessPDF
http://www.accesspdf.com/article.php/20041130153545577
There are several files produced by "tex zref.dtx"
which need to be copied to their appropriate directory on
your system. Most of the "Oberdiek" directories already
existed on my system with the execption of the "source"
path for /Oberdiek which will contain the zref.dtx file.
-
6.2.10 Compatibility with babel
[EMAIL PROTECTED]@babel
430 [EMAIL PROTECTED]@babel#1#2{%
431 \begingroup
432 \csname @[EMAIL PROTECTED]
433 \edef\x{#2}%
434 \expandafter\endgroup
435 [EMAIL PROTECTED]@babel\expandafter{\x}{#1}%
436 }
437 [EMAIL PROTECTED]@babel#1#2{%
438 #2{#1}%
439 }
---
SH: I figure this package will benefit someone, sometime.
Regards,
--
Stephen
Topic ontology recapitulates entropic philology.
