Re: Lyx to Booksurge Success
On Mon, 22 Dec 2008, Steve Litt wrote: I have a question about the "search inside the book". A publishing mailing list of which I'm also a member is extremely upset about Google's plan to scan all books from the libraries. The thought is that why should customers buy the cow if the milk is free -- if you can view it online, why should you pay for the book? I'd definitely like your thoughts on this. Hi Steve, Perhaps you can gain some insight by considering a somewhat related situation, namely that of the 'Baen free library' that Eric Flint started ( http://www.baen.com/library/ ). At that site, Eric has blogged about these issues and by chance I recentely read #7 (from 2002). http://www.baen.com/library/palaver_index.htm In that blog he discusses the economics of providing some books for free. Perhaps that reasoning can be adapted to this situation? best regards /Christian PS. The Baen free library is a web site where Baen books have made available about a 100 books for free by (mostly Baen) authors who've given their permission. I believe Eric Flint is an author as well as some kind of editor at Baen books. -- Christian Ridderström, +46-8-768 39 44http://www.md.kth.se/~chr
Re: LyX 1.6.x branch and MikTex
Yes. Wen Robert Orr wrote: Do I need MikTex 2.7 for the LyX 1.6.x branch? It seems to be working with 2.6
Re: unable to open lyx-file
Hello, after starting lyx with lyx.exe instead of lyxlauncher.exe I got an console. There I can found an error message, that the import for the unicodedata dll fails. What can I do? Many thanks - Tino Tino Langer schrieb: Hello, I want to open an lyx-file (created based on the version 1.6.0 beta) in the actual version of lyx 1.6.1. But when I try to open the file I got the error that lyx2lyx can not convert the file. Where I can look for error messages? Is this an known problem? How to prevent this error or is there some workaround? Many thanks for help - Tino
unable to open lyx-file
Hello, I want to open an lyx-file (created based on the version 1.6.0 beta) in the actual version of lyx 1.6.1. But when I try to open the file I got the error that lyx2lyx can not convert the file. Where I can look for error messages? Is this an known problem? How to prevent this error or is there some workaround? Many thanks for help - Tino
Re: Lyx to Booksurge Success
On Monday 22 December 2008 12:46:10 pm Jonathan Kroner wrote: > I just published a book through Booksurge created from a lyx generated PDF. > Setting aside pros and cons of that particular publisher, despite their > lengthy and (to me) incomprehensible requirements regarding embedded fonts > etc., they accepted my lyx generated PDF as is. > > The book is all text except for line text boxes (simple frame) and a custom > bullet specified from the document settings menu. > > If you would like to see the interior, within a week or so Amazon claims it > will display interior text using its "search inside the book" feature. > This will "scanned" from the same Lyx generated PDF document. Search for > "Dorothy's Oz Dream: A Guide to Enchantment and Empowerment." > > Miscellaneous specs listed below. > > A big THANK YOU to Uwe and other Lyz developers, > > Jonathan Kroner Congratulations Jonathan!!! Please keep us updated on the progress and sales of your book. I have a question about the "search inside the book". A publishing mailing list of which I'm also a member is extremely upset about Google's plan to scan all books from the libraries. The thought is that why should customers buy the cow if the milk is free -- if you can view it online, why should you pay for the book? I'd definitely like your thoughts on this. Thanks SteveT Steve Litt Recession Relief Package http://www.recession-relief.US
Re: Question on whitespace at the end of raw TeX - inserts
Hi folks, first of all: thank you for all your replies. And yes, after hearing what you came up with I think ERT should remain ERT and inserting an automatic blank _within_ the ERT is not a good idea. But wait: what is LyX saying about itself, WYSIWYM? Hey, if I put a whitespace after the end of an ERT you tell me we see it but we won't protect it because you put it there but because you've been working with an ERT before we are sure you did not mean to see a whitespace there ... sorry. This is nothing related to "other text processing systems". This is related to "I would expect to see what I mean". I can remember quite a while ago when I told you that I had my wife working with LyX (she still does, by the way ... :-) ) and in the meantime she's much happier because if she states now "I want this text to be in this and that type of font" it is now. Simply wonderful. There is one very basic question I am rising here for discussion: is the target beauty or understandability? I think all of you spend hours and hours (I _really_ appreciate, don't get me wrong) in making LyX to what it is: highly usuable, extremely configurable and with a very nice user interface. However, I think all we are TeXnicians to some extent, aren't we? And that's the measure LyX will be checked against: the "native" user not being that familiar with TeX. According to my understanding he should be protected against the oddities of TeX by the help of LyX. Well, I hear you say, the native user will not use TeX inserts - maybe - but he might do so. And that's were my point starts. I would say that if someone puts whitespace after an ERT, why would he do this? I'd say he does this because he want's it to be there. But these are just my 2 cents ... I do not want to rise a large discussion on a probably small item ... maybe you like to rethink, maybe not - thank you for all of your work anyway, and have a nice Christmas Eve and Happy New Year, I hope you'll find the time to continue your work on LyX! Take care Dieter Jurzitza P.S. and I was ignoring backward compatibility issues - this might be of heavier impact ... -- --- | \ /\_/\ | | ~x~ |/-\ / \ /- \_/ ^^__ _/ _ / <°°__ \- \_/ | |/| | || || _| _|_| _| if you really want to see the pictures above - use some font with constant spacing like courier! :-) ---Am Montag, 22. Dezember 2008 18:18:02 schrieb Steve Litt: > On Monday 22 December 2008 11:58:24 am David Mertens wrote: **
LyX 1.6.x branch and MikTex
Do I need MikTex 2.7 for the LyX 1.6.x branch? It seems to be working with 2.6
bug: need alt-P in index inset
Hi, in Lyx 1.6.1, when in a Lyx-Code paragraph, inserting an index entry (Alt-I,D) puts the font selection into a somewhat undefined state. Just typing produces roman font, but hitting Ctrl-Alt-P still produces roman font; only issuing Ctrl-Alt-P once again finally gives typewriter font inside the inset.
Lyx to Booksurge Success
I just published a book through Booksurge created from a lyx generated PDF.
Setting aside pros and cons of that particular publisher, despite their
lengthy and (to me) incomprehensible requirements regarding embedded fonts
etc., they accepted my lyx generated PDF as is.
The book is all text except for line text boxes (simple frame) and a custom
bullet specified from the document settings menu.
If you would like to see the interior, within a week or so Amazon claims it
will display interior text using its "search inside the book" feature. This
will "scanned" from the same Lyx generated PDF document. Search for
"Dorothy's Oz Dream: A Guide to Enchantment and Empowerment."
Miscellaneous specs listed below.
A big THANK YOU to Uwe and other Lyz developers,
Jonathan Kroner
Lyz Specifications
Lyx 1.6.0 and Miktex 2.7
Koma script book class, 12 pt palatino font,
Layout: custom 9.5 x 6.25 inches.
margins (inches):
top 1.0625
bottom .75
inner .75
outer .875
head sep .31
The 9.5 x 6.25 inches layout was driven by trying to fit ~40,000 words on
fewer than 150 pages. Why did I care? Because Booksurge has a wholesale
price point jump at 150 pp.
Otherwise, 9 x 6 inches is a more standard dimension for US trade
publications.
I used two ERTs
\date{} to get rid of the title page's date
\setlist{nolistsep} to get rid of space between rown in list enviros (I
used this with the preamble entry "\usepackage{enumitem}", see below.
Excerpt from Preamble:
\usepackage{ifpdf} % part of the hyperref bundle
\ifpdf % if pdflatex is used
% set fonts for nicer pdf view
\IfFileExists{lmodern.sty}{\usepackage{lmodern}}{}
% link all cross references and URLs in pdf output
\usepackage[colorlinks=true, bookmarks, bookmarksnumbered,
linkcolor=black, citecolor=black, urlcolor=blue, filecolor=blue,
pdfpagelayout=OneColumn, pdfnewwindow=true,
pdfstartview=XYZ, plainpages=false, pdfpagelabels,
pdfauthor={Jonathan Kroner}, pdftex,
pdftitle={Dorothy's Oz Dream},pdfsubject={Guide to Enchantment and
Empowermentl},
pdfkeywords={Dorothy, Oz, Enchantment, Empowerment}]{hyperref}
\else % if dvi or ps is produced
% link all cross references and URLs in dvi output
\usepackage[ps2pdf]{hyperref}
\fi % end if pdflatex is used
% define page head line
\usepackage{scrpage2}
\pagestyle{scrheadings}
\lehead{\pagemark}
\rehead{\leftmark}
\rohead{\pagemark}
\lohead{\rightmark}
\ifoot{}
\cfoot{}
\ofoot{}
% don't number chapter pages
\renewcommand*{\chapterpagestyle}{empty}
\usepackage{microtype}
\usepackage{enumitem}
%this is for elimnitaing rows b/t items with setlist nolistsep
% the pages of the TOC are numbered roman
% and a pdf-bookmark for the TOC is added
\pagenumbering{roman}
\let\myTOC\tableofcontents
\renewcommand\tableofcontents{%
\pdfbookmark[1]{Contents}{}
\myTOC
\cleardoublepage
\pagenumbering{arabic} }
% redefine the \LyX macro for PDF bookmarks
\def\LyX{\texorpdfstring{%
l\kern-.1667em\lower.25em\hbox{y}\kern-.125e...@}
{LyX }}
Problems: The book included a works cited and recommended reading appendix
which I created manually. I would have liked to have used Lyx's
bibliography feature, but I could not figure out how to make a bibliography
entry and have it appear only in the bibliography, but not in the text.
Because it is a nonacademic text, I did not want to disrupt the text's flow
with citations. But I did want to tie the references to the text because I
did a lot of cutting and pasting sections from one chapter to another, which
then required me to manually correct the works cited section.
The "microtype" solved a lot of problems with margins. And I think it
improved the book's look.
--
Jonathan Kroner
http://jonathankroner.com/
http://floridafalseclaim.com/
Miami, Florida USA
Re: Question on whitespace at the end of raw TeX - inserts
On Monday 22 December 2008 11:58:24 am David Mertens wrote:
> > What Dieter refers to is that TeX is interpreting a blank as the end of a
> > command. I.e., "\TeX and friends" will be parsed as
> > "TeXand
> > friends". If you want a blank after the command, you must either write
> > "\TeX\ and friends" or "\TeX{} and friends" (in ordinary LaTeX), and I
> > think
> > Dieter wants us to automatically insert "\ " at the end of each ERT (or
> > transform subsequent blanks to "\ " automatically). However, as I argued
> > earlier, I think such magic will fall back on us, since ERT is used in
> > many different ways (not mentioning all the backwards compatibility
> > issues involved).
>
> Jürgen and Steve -
>
> You are correct that I misunderstood.
I wasn't even commenting on anyone's LyX wishes. I was just agreeing with the
general principle laid out by Jürgen, that ERT should be completely literal.
Thanks
SteveT
Steve Litt
Recession Relief Package
http://www.recession-relief.US
Re: Question on whitespace at the end of raw TeX - inserts
"David Mertens" writes: > Perhaps we could add an option to ERT boxes to "respect spaces afer this > ert", in which case a space after the close of an ert would be replaced with > a '\ '? Do you really think that checking this box is easier than adding '\ ' at the end of your ERT? ERT is raw, and I think it should stay like that. JMarc
Re: Question on whitespace at the end of raw TeX - inserts
>
> What Dieter refers to is that TeX is interpreting a blank as the end of a
> command. I.e., "\TeX and friends" will be parsed as
> "TeXand
> friends". If you want a blank after the command, you must either write
> "\TeX\ and friends" or "\TeX{} and friends" (in ordinary LaTeX), and I
> think
> Dieter wants us to automatically insert "\ " at the end of each ERT (or
> transform subsequent blanks to "\ " automatically). However, as I argued
> earlier, I think such magic will fall back on us, since ERT is used in many
> different ways (not mentioning all the backwards compatibility issues
> involved).
>
Jürgen and Steve -
You are correct that I misunderstood. So I guess I sympathise with Dieter,
in as much as what follows:
As far as I am concerned by
abc\TeX def
I *mean*
abc\TeX\ def
However, when I tyop a command in powerdot like
\twocolumns{ my first column }{ my second column
}
I *mean*
\twocolumns{ my first column }{ my second column }
Perhaps we could add an option to ERT boxes to "respect spaces afer this
ert", in which case a space after the close of an ert would be replaced with
a '\ '?
David
Re: word wrap and \use_geometry
pol writes: > Anyway, should one expect any problems justifying text in the 'item' > environment, due to lines containing math expressions not being properly > wrapped up? It might happen, I think. And I also think that 'use_geometry' changes the default margins. JMarc
Re: Problems with wrapfigure TeX-code
Dear Jürgen, On Monday 22 December 2008 16:06, Jürgen Spitzmüller wrote: > The good news is that we (Jean-Marc Lasgouttes, for that matter) are now > seriously addressing this issue and that tex2lyx is handling unicode more > or less now (i.e., in forthcoming LyX 1.6.2). This means that we will be > able to subsequently add native support for the newer features Thanks for the quick reaction! In the meantime I will try not to bother about the way Lyx treats thsi code. Ther is even a good side at it. In the Lyx dropdown box the position parameter is only given as lowercase r, l, i or o. but according to some documentation the uppercase characters should be used if one wants the figure to float. So now I can bypass the dropdown box and specify upprecase characters. Sincerely, Hubert -- Hubert Christiaen Bloesemlaan 17 3360 Korbeek-Lo Belgium
Re: word wrap and \use_geometry
Jean-Marc Lasgouttes wrote: > Could you send a small example file? I am not sure what you mean. I had been experimenting a few days ago, with lyx 1.4.3, but i cannot arrange a test now. Anyway, should one expect any problems justifying text in the 'item' environment, due to lines containing math expressions not being properly wrapped up? > >> I do not remember what the use of the \use_geometry option and how it can >> be >> set off from the lyx interface. I > > Just check > Document>Settings|Margins|default margin thanks -- Pol
Re: word wrap and \use_geometry
pol writes: > Text cannot be properly justified in the 'item' environment, if > \use_geometry is set 'true'. Both the lyx interface and the pdf output > appear to be affected by that switch. Could you send a small example file? I am not sure what you mean. > I do not remember what the use of the \use_geometry option and how it can be > set off from the lyx interface. I Just check Document>Settings|Margins|default margin JMarc
word wrap and \use_geometry
Text cannot be properly justified in the 'item' environment, if \use_geometry is set 'true'. Both the lyx interface and the pdf output appear to be affected by that switch. I do not remember what the use of the \use_geometry option and how it can be set off from the lyx interface. I I have just found that, as \use_geometry is set 'false' by editing the lyx character text file, word wrapping is ok. Is that a bug? Should \use_geometry be set to 'false' by default? Thank you -- Pol
Re: Problems with wrapfigure TeX-code
Hubert Christiaen wrote: > I am writing a conversion program which should generate floating and > wrapped image, what you get in Lyx by 'insert -> Float -> wrap text'. this > works fine in Lyx, but when I import the same code as handwritten TeX code, > Lyx complains and does not recognize it as a block. Even worse, if I export > the Lyx code as .tex and re-import it, Lyx also complains! So Lyx does not > even recognize its own code! The switch of LyX to unicode somewhat stalled the development of the tex2lyx converter, since tex2lyx itself needed to be prepared for unicode, and no one volunteered for this task. Thus, all newer features are currently imported as TeX code instead of proper LyX stuff. This was a major problem we were aware of as of LyX 1.5.0. The good news is that we (Jean-Marc Lasgouttes, for that matter) are now seriously addressing this issue and that tex2lyx is handling unicode more or less now (i.e., in forthcoming LyX 1.6.2). This means that we will be able to subsequently add native support for the newer features (which may itself take some additional time, so do not expect too much wrt 1.6.2). Jürgen
Re: Question on whitespace at the end of raw TeX - inserts
I agree 100% with Jürgen here. As a guy who regularly does funny things with LyX, I don't need my job made harder by working around oddities put in as "user friendliness". And he's right, ERT is and always should be raw LaTeX. SteveT On Monday 22 December 2008 04:17:53 am Jürgen Spitzmüller wrote: > I think LyX should not try to be more clever than the user. We know from > other Word processors where this ends. Particularly, ERT is supposed to > pass code _as is_ without any addition or modification. Doing clever tricks > is impossible to get right. > > Dieter Jurzitza wrote: > > 1.) put automatically a blank as whitespace at the end of each TeX-insert > > before closing it. > > For instance, inserting active babel characters will most likely break with > your proposal, e.g. German "Weihnachtstage und "~nächte" or > "(Wunsch-)""zettel" must not be followed by a blank. > > > 2.) protect a whitespace follwing a TeX-insert if there is one - assume > > that the user intentionally puts a whitespace there. > > And if the assumption is wrong? How is the user supposed to get rid of the > whitespace again? > > Jürgen
Re: Question on whitespace at the end of raw TeX - inserts
David Mertens wrote:
> I completely agree, for reasons that you pointed out, that Dieter's first
> suggested solution would break many things. However, I think you and I are
> interpreting the second suggestion differently.
>
> Here's how I understand things. Presently, lyx would translate the
> following lyx input (in the editor) to the following tex:
> abcdef ghi --> abcdef ghi
> abcdef ghi --> abcdefghi
No, I think this is a misunderstanding. Both what you describe above will be
output in the same way by LyX, i.e.
abcdef ghi --> abcdef ghi
abcdef ghi --> abcdef ghi
A blank in and outside ERT is identical.
What Dieter refers to is that TeX is interpreting a blank as the end of a
command. I.e., "\TeX and friends" will be parsed as "TeXand
friends". If you want a blank after the command, you must either write
"\TeX\ and friends" or "\TeX{} and friends" (in ordinary LaTeX), and I think
Dieter wants us to automatically insert "\ " at the end of each ERT (or
transform subsequent blanks to "\ " automatically). However, as I argued
earlier, I think such magic will fall back on us, since ERT is used in many
different ways (not mentioning all the backwards compatibility issues
involved).
Jürgen
Problems with wrapfigure TeX-code
Hi!
I am writing a conversion program which should generate floating and wrapped
image, what you get in Lyx by 'insert -> Float -> wrap text'. this works fine
in Lyx, but when I import the same code as handwritten TeX code, Lyx
complains and does not recognize it as a block. Even worse, if I export the
Lyx code as .tex and re-import it, Lyx also complains! So Lyx does not even
recognize its own code!
The good news is that the dvi viewer has no problem with that code and
executes as intended.
TeX code:
\begin{wrapfigure}{O}{0.5\columnwidth}
\includegraphics{NewtonKogelA}\caption{bol op kegel}
\end{wrapfigure}
Lyx splits this up several ERT pieces '\begin{wrapfigure}{' followed by normal
text O, followed by ERT '}{', followed by normal text 0.5 \bakslash ...
While the correct Lyx generated code is starts with:
\begin_layout Standard
\begin_inset Wrap figure
placement O
width "50col%"
status open
\begin_layout Standard
\begin_inset Graphics
filename /windows/D/hubert/mechan/Wikibooks/NewtonKogelA.png
BoundingBox 0bp 0bp 265bp 119bp
\end_inset
What's causing the problem?
Sincerely,
Hubert
--
Hubert Christiaen
Bloesemlaan 17
3360 Korbeek-Lo
Belgium
Re: Problem with Lyx
José Vargas wrote: Hi, I'm using the lastest version... 1.6.1 And I have this problem: http://img149.imageshack.us/img149/2048/lyxmb2.png I get that error when I click "See PostScript". It's in spanish, but the error is something like "There isn't information to see the postscript". If I click "See PDF" and "See DVI".. It worls fine... Please helpme!! I have installed and uninstalled it twice..!! LyX needs to know what program to use to view the Postscript output. The configuration script looks for a Postscript viewer but may not have found one. Do you have GSView (or some other PS viewer) installed? If so, go to Tools > Preferences... > File Handling > File formats and pick Postscript in the drop-down list. Look at the viewer entry. By default, it says 'auto', which I believe means open the Postscript output file in the default viewer registered with Windows (the one that would be run if you double-clicked a file with a .ps extension). You can change that to point directly to the executable file for your favorite Postscript viewer (and then click Save). Note that if the viewer is not on the system command path, you'll need either to put a full path to it in the viewer entry or add the path to Tools > Preferences... > Paths > PATH prefix (which is what I did with the path to GSview on my system). /Paul
Re: Question on whitespace at the end of raw TeX - inserts
I think LyX should not try to be more clever than the user. We know from other Word processors where this ends. Particularly, ERT is supposed to pass code _as is_ without any addition or modification. Doing clever tricks is impossible to get right. Dieter Jurzitza wrote: > 1.) put automatically a blank as whitespace at the end of each TeX-insert > before closing it. For instance, inserting active babel characters will most likely break with your proposal, e.g. German "Weihnachtstage und "~nächte" or "(Wunsch-)""zettel" must not be followed by a blank. > 2.) protect a whitespace follwing a TeX-insert if there is one - assume > that the user intentionally puts a whitespace there. And if the assumption is wrong? How is the user supposed to get rid of the whitespace again? Jürgen
