Re: Google Docs to LaTeX
Dear Charles,
It is very cool grasping how to use sed in however a primitive way. But on
further investigation it seems one needs it for a LyX friendly use of
``writer2latex'' only if the document has tables, math, images ... or French.
With a fairly wide but unscientifically chosen variety of English documents, I
found that the desiderata of:
(a) retaining crucial formatting that an English language Word or OpenOffice or
docs.google user would likely employ
and:
(b) avoiding a demoralizing film of ERT
by messing with the preferences in writer2latex.xml.
The accursed red {}- is what remains, though the obvious expedient of a find and
replace in the latex file before importing into LyX is clearly the way to go if
that's all there is. I think it has to do with the ucs.sty that is used in
connection with the choice of utf8 among the 'inputencoding' options. But this
is way over my head.
I don't know how far this depends on how various things are adjusted on the (mac
)computer I was using - doc-odt-latex-lyx involves a lot of adjustments - but
for the heck of it I will list the alterations from the defaults that seemed to
maximize what is preserved subject to the principle of ERT avoidance:
option name=inputencoding value=utf8 /
option name=multilingual value=false /
in place of
option name=inputencoding value=ascii /
option name=multilingual value=true /
option name=formatting value=ignore_most /
option name=page_formatting value=ignore_all /
option name=ignore_hard_page_breaks value=true /
option name=ignore_hard_line_breaks value=true /
option name=ignore_empty_paragraphs value=true /
option name=ignore_double_spaces value=true /
in place of
option name=formatting value=convert_basic /
option name=page_formatting value=convert_all /
option name=ignore_hard_page_breaks value=false /
option name=ignore_hard_line_breaks value=false /
option name=ignore_empty_paragraphs value=false /
option name=ignore_double_spaces value=false /
These choices keep the amount of junk in the preamble to a minimum too. The
more I fiddle with it the sounder writer2latex seems to be; I wouldn't have
thought it was possible. Again, this is all over my head, though now primitive
text-altering script-composition isn't, to my amazement - so,
or rather, {}- so,
thanks,
Michael
Re: Google Docs to LaTeX
Dear Charles,
It is very cool grasping how to use sed in however a primitive way. But on
further investigation it seems one needs it for a LyX friendly use of
``writer2latex'' only if the document has tables, math, images ... or French.
With a fairly wide but unscientifically chosen variety of English documents, I
found that the desiderata of:
(a) retaining crucial formatting that an English language Word or OpenOffice or
docs.google user would likely employ
and:
(b) avoiding a demoralizing film of ERT
by messing with the preferences in writer2latex.xml.
The accursed red {}- is what remains, though the obvious expedient of a find and
replace in the latex file before importing into LyX is clearly the way to go if
that's all there is. I think it has to do with the ucs.sty that is used in
connection with the choice of utf8 among the 'inputencoding' options. But this
is way over my head.
I don't know how far this depends on how various things are adjusted on the (mac
)computer I was using - doc-odt-latex-lyx involves a lot of adjustments - but
for the heck of it I will list the alterations from the defaults that seemed to
maximize what is preserved subject to the principle of ERT avoidance:
option name=inputencoding value=utf8 /
option name=multilingual value=false /
in place of
option name=inputencoding value=ascii /
option name=multilingual value=true /
option name=formatting value=ignore_most /
option name=page_formatting value=ignore_all /
option name=ignore_hard_page_breaks value=true /
option name=ignore_hard_line_breaks value=true /
option name=ignore_empty_paragraphs value=true /
option name=ignore_double_spaces value=true /
in place of
option name=formatting value=convert_basic /
option name=page_formatting value=convert_all /
option name=ignore_hard_page_breaks value=false /
option name=ignore_hard_line_breaks value=false /
option name=ignore_empty_paragraphs value=false /
option name=ignore_double_spaces value=false /
These choices keep the amount of junk in the preamble to a minimum too. The
more I fiddle with it the sounder writer2latex seems to be; I wouldn't have
thought it was possible. Again, this is all over my head, though now primitive
text-altering script-composition isn't, to my amazement - so,
or rather, {}- so,
thanks,
Michael
Re: Google Docs to LaTeX
Dear Charles,
It is very cool grasping how to use sed in however a primitive way. But on
further investigation it seems one needs it for a LyX friendly use of
``writer2latex'' only if the document has tables, math, images ... or French.
With a fairly wide but unscientifically chosen variety of English documents, I
found that the desiderata of:
(a) retaining crucial formatting that an English language Word or OpenOffice or
docs.google user would likely employ
and:
(b) avoiding a demoralizing film of ERT
by messing with the preferences in writer2latex.xml.
The accursed red {}- is what remains, though the obvious expedient of a find and
replace in the latex file before importing into LyX is clearly the way to go if
that's all there is. I think it has to do with the ucs.sty that is used in
connection with the choice of utf8 among the 'inputencoding' options. But this
is way over my head.
I don't know how far this depends on how various things are adjusted on the (mac
)computer I was using - doc->odt->latex->lyx involves a lot of adjustments - but
for the heck of it I will list the alterations from the defaults that seemed to
maximize what is preserved subject to the principle of ERT avoidance:
in place of
in place of
These choices keep the amount of junk in the preamble to a minimum too. The
more I fiddle with it the sounder writer2latex seems to be; I wouldn't have
thought it was possible. Again, this is all over my head, though now primitive
text-altering script-composition isn't, to my amazement - so,
or rather, {}- so,
thanks,
Michael
Re: Google Docs to LaTeX
Charles de Miramon [EMAIL PROTECTED] writes: It uses sed (a command line searchreplace that is standard on Unix). I guess it will work on Mac OS/X. sh w2lclean Myconvertedfile.tex will create a temp-Myconvertedfile.tex that you can then import into LyX. Dear Charles your naive confidence that anyone can do this has emboldened me to study script composition. There is indeed sed in os x and it seems to follow the rules you are using, as I could verify easily with the simplest uses of it, the ones that simply print the modified text to the screen. And cp and the use of obnoxiously so-called variables seems to be the same: the framing you use to capture the modified text (which I don't quite understand yet) does make a quasi-copy of zeta.tex called temp-zeta.tex. Things go well as long as the find-and-replace-like actions I put into your framing are like s/me/you/g or s/Athens/Jerusalem/g . But the use of / and \ and ' in tex and in the scripting language, if that's what you call it - each wanting to use them both as its own proper symbols and as 'escaped' or however you put it - inevitably leads to an impenetrable salad of slashes, and the solution that works for you seems to lead to misunderstanding here. I sort of follow the difficulty as long as I am thinking of latex only. So I am studying, but must give up for the night. This is hard! I will get back to you if I fall into despair. It's exam week, so I will have ample raw materials when the .doc term papers hit my electronic mailbox late Friday afternoon. Perhaps by then I will be able, with the application of a few skillfully executed keystrokes, to convert the whole directory-full of them into a handsomely decorated volume in the Memoir class, each as a subordinate chapter. yours ever Michael
Re: Google Docs to LaTeX
Charles de Miramon [EMAIL PROTECTED] writes: It uses sed (a command line searchreplace that is standard on Unix). I guess it will work on Mac OS/X. sh w2lclean Myconvertedfile.tex will create a temp-Myconvertedfile.tex that you can then import into LyX. Dear Charles your naive confidence that anyone can do this has emboldened me to study script composition. There is indeed sed in os x and it seems to follow the rules you are using, as I could verify easily with the simplest uses of it, the ones that simply print the modified text to the screen. And cp and the use of obnoxiously so-called variables seems to be the same: the framing you use to capture the modified text (which I don't quite understand yet) does make a quasi-copy of zeta.tex called temp-zeta.tex. Things go well as long as the find-and-replace-like actions I put into your framing are like s/me/you/g or s/Athens/Jerusalem/g . But the use of / and \ and ' in tex and in the scripting language, if that's what you call it - each wanting to use them both as its own proper symbols and as 'escaped' or however you put it - inevitably leads to an impenetrable salad of slashes, and the solution that works for you seems to lead to misunderstanding here. I sort of follow the difficulty as long as I am thinking of latex only. So I am studying, but must give up for the night. This is hard! I will get back to you if I fall into despair. It's exam week, so I will have ample raw materials when the .doc term papers hit my electronic mailbox late Friday afternoon. Perhaps by then I will be able, with the application of a few skillfully executed keystrokes, to convert the whole directory-full of them into a handsomely decorated volume in the Memoir class, each as a subordinate chapter. yours ever Michael
Re: Google Docs to LaTeX
Charles de Miramon <[EMAIL PROTECTED]> writes: >It uses sed (a command line search that is standard on > Unix). I guess it will work on Mac OS/X. > sh w2lclean Myconvertedfile.tex will create a temp-Myconvertedfile.tex that > you can then import into LyX. Dear Charles your naive confidence that anyone can do this has emboldened me to study script composition. There is indeed sed in os x and it seems to follow the rules you are using, as I could verify easily with the simplest uses of it, the ones that simply print the modified text to the screen. And cp and the use of obnoxiously so-called variables seems to be the same: the framing you use to capture the modified text (which I don't quite understand yet) does make a quasi-copy of zeta.tex called temp-zeta.tex. Things go well as long as the "find-and-replace"-like actions I put into your framing are like s/me/you/g or s/Athens/Jerusalem/g . But the use of / and \ and ' in tex and in the scripting language, if that's what you call it - each wanting to use them both as its own proper symbols and as 'escaped' or however you put it - inevitably leads to an impenetrable salad of slashes, and the solution that works for you seems to lead to misunderstanding here. I sort of follow the difficulty as long as I am thinking of latex only. So I am studying, but must give up for the night. This is hard! I will get back to you if I fall into despair. It's exam week, so I will have ample raw materials when the .doc term papers hit my electronic mailbox late Friday afternoon. Perhaps by then I will be able, with the application of a few skillfully executed keystrokes, to convert the whole directory-full of them into a handsomely decorated volume in the Memoir class, each as a subordinate chapter. yours ever Michael
Re: Google Docs to LaTeX
[EMAIL PROTECTED] writes: I would try to export to ODF and then use writer2latex to convert it to LaTeX. You clean the LaTeX with a script to take away all the Wysiwyg cruft and then convert it to LyX. I can't tell from the note whether you are a skillful composer of scripts, as Charles is kindly thinking you must be. If you are not, but have NeoOffice installed, notice that writer2latex is already installed under File -- Export -- FileFormat. I take it this is true of all versions of OpenOffice. The default preferences may not be ideal; they are in writer2latex.xml, which is easy to find and fairly humanly readable - even if it is a script - and can be adjusted according to the principles in the user's manual http://www.hj-gym.dk/~hj/writer2latex/index7.html Since you are writing in google docs, you will have control over how much of a hash the result is. I use NeoOffice to open Word documents, and if I have to print a long student term paper, the temptation to export is overwhelming, of course, if only to save paper and ink. If you delete all of the garbage that appears in the preamble under Document -- Settings, the results are not too bad. (Once someone figures out how to have a handsome Powered by LyX figure printed at the bottom of the last page, or maybe every page, which might be mentioned in the preamble, I'd be bold enough to return the text to the student that way.) It is surprising how rapid the steps are; it was much more complicated when I was first using LyX and LaTeX a year or so ago, and thus converting lots of stuff. If you have to study and alter a document, and thus stare at paragraphs in the LyX user interface, there may be some ugly ERT, especially if the preferences are too kind to what Charles calls the 'wysiwyg cruft'. If you find a solution to the problem with em-dashes that doesn't involve a find-and-replace in the .tex file, tell me.
Re: Google Docs to LaTeX
[EMAIL PROTECTED] writes: I would try to export to ODF and then use writer2latex to convert it to LaTeX. You clean the LaTeX with a script to take away all the Wysiwyg cruft and then convert it to LyX. I can't tell from the note whether you are a skillful composer of scripts, as Charles is kindly thinking you must be. If you are not, but have NeoOffice installed, notice that writer2latex is already installed under File -- Export -- FileFormat. I take it this is true of all versions of OpenOffice. The default preferences may not be ideal; they are in writer2latex.xml, which is easy to find and fairly humanly readable - even if it is a script - and can be adjusted according to the principles in the user's manual http://www.hj-gym.dk/~hj/writer2latex/index7.html Since you are writing in google docs, you will have control over how much of a hash the result is. I use NeoOffice to open Word documents, and if I have to print a long student term paper, the temptation to export is overwhelming, of course, if only to save paper and ink. If you delete all of the garbage that appears in the preamble under Document -- Settings, the results are not too bad. (Once someone figures out how to have a handsome Powered by LyX figure printed at the bottom of the last page, or maybe every page, which might be mentioned in the preamble, I'd be bold enough to return the text to the student that way.) It is surprising how rapid the steps are; it was much more complicated when I was first using LyX and LaTeX a year or so ago, and thus converting lots of stuff. If you have to study and alter a document, and thus stare at paragraphs in the LyX user interface, there may be some ugly ERT, especially if the preferences are too kind to what Charles calls the 'wysiwyg cruft'. If you find a solution to the problem with em-dashes that doesn't involve a find-and-replace in the .tex file, tell me.
Re: Google Docs to LaTeX
<[EMAIL PROTECTED]> writes: > I would try to export to ODF and then use writer2latex to convert it to > LaTeX. You clean the LaTeX with a script to take away all the Wysiwyg cruft > and then convert it to LyX. I can't tell from the note whether you are a skillful composer of scripts, as Charles is kindly thinking you must be. If you are not, but have NeoOffice installed, notice that writer2latex is already installed under File --> Export --> FileFormat. I take it this is true of all versions of OpenOffice. The default preferences may not be ideal; they are in writer2latex.xml, which is easy to find and fairly humanly readable - even if it is a script - and can be adjusted according to the principles in the user's manual http://www.hj-gym.dk/~hj/writer2latex/index7.html Since you are writing in google docs, you will have control over how much of a hash the result is. I use NeoOffice to open Word documents, and if I have to print a long student term paper, the temptation to export is overwhelming, of course, if only to save paper and ink. If you delete all of the garbage that appears in the preamble under Document --> Settings, the results are not too bad. (Once someone figures out how to have a handsome "Powered by LyX" figure printed at the bottom of the last page, or maybe every page, which might be mentioned in the preamble, I'd be bold enough to return the text to the student that way.) It is surprising how rapid the steps are; it was much more complicated when I was first using LyX and LaTeX a year or so ago, and thus converting lots of stuff. If you have to study and alter a document, and thus stare at paragraphs in the LyX user interface, there may be some ugly ERT, especially if the preferences are too kind to what Charles calls the 'wysiwyg cruft'. If you find a solution to the problem with em-dashes that doesn't involve a find-and-replace in the .tex file, tell me.
Re: Visual Tour (Was: New LyX website)
Man, the website is amazing! I just wish the cool playground block letters of the old website could replace this incoherent three lets-have-fun-colors + Times Roman silliness. On the question of screenshots, a) it bugs me that the illustrations are all in a serif font, which should never be used on a screen, unless it's maybe old courier. I have found that WYSIWYG cretinism is at once so powerful and so superficial, that it is exploded as soon this simple distinction is made. This is the point of entry for getting regular people to grasp the difference between an editor and a typesetter. Even when I can't convince people to take up LyX or LaTeX, I at least convince them to use font substitution in Word ... with months of expressions of gratitude following. b) Also the text is justified in the screenshots, which is conceptually regressive and medically dangerous, and violates every principle LyX stands for. The LyX UI is not a typesetter; Word is 1000x better at screen-typesetting than LyX; it is pure Word wannabe-ism) c)It is obvious that the fancy mathematical illustrations come too soon, unless y'all are thinking of the TeX-using public as the principal market. One ought to have a few screens of simple documents that fit on the screen - AND the typeset version alongside them, no? Here's a couple of examples I sent to a friend. Actually the LyX screen doesn't show the whole document, but one gets the idea. ((Pay no attention to the content of the would-have-been class handout!)) http://www.pitt.edu/~mthompso/lyx.ui.example.png http://www.pitt.edu/~mthompso/lyx.typeset.example.png best, Michael T ((Maybe what I am really thinking of is a second link to screenshots in which the WYSIWYG v. WYSIWYM contrast is developed. By the way, I think that WYSIWYM is doubtful English. One should just say WYSIWYT(think). WYSIWYT is what I experienced in wordperfect 5.1 which I continued to use til two years ago, not capable of writing a damn thing in Word, though I couldnt understand why til I hit the Wikipedia page on LyX... Incredibly, I used Word, not Latex, as my typesetting engine.))
Re: Visual Tour (Was: New LyX website)
Michael, feel free to re-create pictures in screenshot section and/or graphical tour. the screenshots you sent are fine, just use standard colors and composition of toolbars. pavel Sorry, the lyx background was the strong light, back porch version, which looks pretty goofy. I have been studying the tour and screenshot bits, thinking how I could make a better pitch to my fellow technical idiots.
Re: Visual Tour (Was: New LyX website)
Man, the website is amazing! I just wish the cool playground block letters of the old website could replace this incoherent three lets-have-fun-colors + Times Roman silliness. On the question of screenshots, a) it bugs me that the illustrations are all in a serif font, which should never be used on a screen, unless it's maybe old courier. I have found that WYSIWYG cretinism is at once so powerful and so superficial, that it is exploded as soon this simple distinction is made. This is the point of entry for getting regular people to grasp the difference between an editor and a typesetter. Even when I can't convince people to take up LyX or LaTeX, I at least convince them to use font substitution in Word ... with months of expressions of gratitude following. b) Also the text is justified in the screenshots, which is conceptually regressive and medically dangerous, and violates every principle LyX stands for. The LyX UI is not a typesetter; Word is 1000x better at screen-typesetting than LyX; it is pure Word wannabe-ism) c)It is obvious that the fancy mathematical illustrations come too soon, unless y'all are thinking of the TeX-using public as the principal market. One ought to have a few screens of simple documents that fit on the screen - AND the typeset version alongside them, no? Here's a couple of examples I sent to a friend. Actually the LyX screen doesn't show the whole document, but one gets the idea. ((Pay no attention to the content of the would-have-been class handout!)) http://www.pitt.edu/~mthompso/lyx.ui.example.png http://www.pitt.edu/~mthompso/lyx.typeset.example.png best, Michael T ((Maybe what I am really thinking of is a second link to screenshots in which the WYSIWYG v. WYSIWYM contrast is developed. By the way, I think that WYSIWYM is doubtful English. One should just say WYSIWYT(think). WYSIWYT is what I experienced in wordperfect 5.1 which I continued to use til two years ago, not capable of writing a damn thing in Word, though I couldnt understand why til I hit the Wikipedia page on LyX... Incredibly, I used Word, not Latex, as my typesetting engine.))
Re: Visual Tour (Was: New LyX website)
Michael, feel free to re-create pictures in screenshot section and/or graphical tour. the screenshots you sent are fine, just use standard colors and composition of toolbars. pavel Sorry, the lyx background was the strong light, back porch version, which looks pretty goofy. I have been studying the tour and screenshot bits, thinking how I could make a better pitch to my fellow technical idiots.
Re: Visual Tour (Was: New LyX website)
Man, the website is amazing! I just wish the cool playground block letters of the old website could replace this incoherent three lets-have-fun-colors + Times Roman silliness. On the question of screenshots, a) it bugs me that the illustrations are all in a serif font, which should never be used on a screen, unless it's maybe old courier. I have found that WYSIWYG cretinism is at once so powerful and so superficial, that it is exploded as soon this simple distinction is made. This is the point of entry for getting regular people to grasp the difference between an editor and a typesetter. Even when I can't convince people to take up LyX or LaTeX, I at least convince them to use font substitution in Word ... with months of expressions of gratitude following. b) Also the text is justified in the screenshots, which is conceptually regressive and medically dangerous, and violates every principle LyX stands for. The LyX UI is not a typesetter; Word is 1000x better at screen-typesetting than LyX; it is pure Word wannabe-ism) c)It is obvious that the fancy mathematical illustrations come too soon, unless y'all are thinking of the TeX-using public as the principal market. One ought to have a few screens of simple documents that fit on the screen - AND the typeset version alongside them, no? Here's a couple of examples I sent to a friend. Actually the LyX screen doesn't show the whole document, but one gets the idea. ((Pay no attention to the content of the would-have-been class handout!)) http://www.pitt.edu/~mthompso/lyx.ui.example.png http://www.pitt.edu/~mthompso/lyx.typeset.example.png best, Michael T ((Maybe what I am really thinking of is a second link to screenshots in which the WYSIWYG v. WYSIWYM contrast is developed. By the way, I think that WYSIWYM is doubtful English. One should just say WYSIWYT(think). WYSIWYT is what I experienced in wordperfect 5.1 which I continued to use til two years ago, not capable of writing a damn thing in Word, though I couldnt understand why til I hit the Wikipedia page on LyX... Incredibly, I used Word, not Latex, as my "typesetting engine".))
Re: Visual Tour (Was: New LyX website)
> Michael, feel free to re-create pictures in screenshot section and/or > graphical tour. the screenshots you sent are fine, just use standard > colors and composition of toolbars. > > pavel > Sorry, the lyx background was the strong light, back porch version, which looks pretty goofy. I have been studying the tour and screenshot bits, thinking how I could make a better pitch to my fellow technical idiots.
Re: Name of the Mascot (Was: New splash screen (Was: LyX logo))
I dont know what the name of the mascot critter is, but its species was identified by Donn Ingle http://article.gmane.org/gmane.editors.lyx.general/45224/ It is an ERT-eater best, Michael T, ERT- and ERROR-maker
Re: Name of the Mascot (Was: New splash screen (Was: LyX logo))
I dont know what the name of the mascot critter is, but its species was identified by Donn Ingle http://article.gmane.org/gmane.editors.lyx.general/45224/ It is an ERT-eater best, Michael T, ERT- and ERROR-maker
Re: Name of the Mascot (Was: New splash screen (Was: LyX logo))
I dont know what the name of the mascot critter is, but its species was identified by Donn Ingle http://article.gmane.org/gmane.editors.lyx.general/45224/ It is an ERT-eater best, Michael T, ERT- and ERROR-maker
Re: LyX won't compile my document any more
I am having similar problems with the lyx/tex connection.
For example if I export a default article to tex, which shows
up in Texshop as this:
%% LyX 1.5.4 created this file. For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass[english]{article}
\usepackage[T1]{fontenc}
\makeatletter
%% User specified LaTeX commands.
\usepackage{babel}
\makeatother
\begin{document}
All the king's horses...
\end{document}
Then Lyx says:
...text2.lyx is from a different version of Lyx
but the lyx2lyx script failed to convert it
There are also frequent refusals to typeset the PDF
without any explanation, though I cant figure out
what and when. The PDF button just darkens for a bit
and then it's like nothing had happened between us.
Re: LyX won't compile my document any more
I am having similar problems with the lyx/tex connection.
For example if I export a default article to tex, which shows
up in Texshop as this:
%% LyX 1.5.4 created this file. For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass[english]{article}
\usepackage[T1]{fontenc}
\makeatletter
%% User specified LaTeX commands.
\usepackage{babel}
\makeatother
\begin{document}
All the king's horses...
\end{document}
Then Lyx says:
...text2.lyx is from a different version of Lyx
but the lyx2lyx script failed to convert it
There are also frequent refusals to typeset the PDF
without any explanation, though I cant figure out
what and when. The PDF button just darkens for a bit
and then it's like nothing had happened between us.
Re: LyX won't compile my document any more
I am having similar problems with the lyx/tex connection.
For example if I export a default article to tex, which shows
up in Texshop as this:
%% LyX 1.5.4 created this file. For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass[english]{article}
\usepackage[T1]{fontenc}
\makeatletter
%% User specified LaTeX commands.
\usepackage{babel}
\makeatother
\begin{document}
All the king's horses...
\end{document}
Then Lyx says:
...text2.lyx is from a different version of Lyx
but the lyx2lyx script failed to convert it
There are also frequent refusals to typeset the PDF
without any explanation, though I cant figure out
what and when. The PDF button just darkens for a bit
and then it's like nothing had happened between us.
Re: Initial Newbie Questions
(Fellow semi-beginner's response:) I tried this with the different ways of viewing text available to me on the mac with no problem. I notice the LyX manual says, discussing the text styles dialogue, (3.6.4): Color: You can adjust the color of the text with this control. Notice that not all dvi-viewers are are able to display colors. ... Then googling Yap color text I promptly got http://www.gnustep.it/marko/GPSText/index.html saying: Getting colored output: Set PostScript Device to 24 bit color for color previews; use the style sheet color to get colored a2ps output. This only works if the color style sheet is installed on your system (/usr/bin/a2ps --list=style-sheets). Note that mutally contradictory options to a2ps may cancel each other out. So it looks like its to do with Yap, which is bundled with Miktex. It would probably be easiest to set something else as a viewer, through the general LyX preferences: Preferences -- File Formats -- DVI then look whats listed as the viewer - and try to change it. I don't know what else you may have to view it, but there is plenty about this sort of thing if you search these posts, for example.
Re: Initial Newbie Questions
I see that you were trying to change the color of a Chapter Heading, in particular. This does seem like a mess, easily reproducible by me; titles and sections seem to work, though. Evidently a problem for the masters.
Re: Initial Newbie Questions
(Fellow semi-beginner's response:) I tried this with the different ways of viewing text available to me on the mac with no problem. I notice the LyX manual says, discussing the text styles dialogue, (3.6.4): Color: You can adjust the color of the text with this control. Notice that not all dvi-viewers are are able to display colors. ... Then googling Yap color text I promptly got http://www.gnustep.it/marko/GPSText/index.html saying: Getting colored output: Set PostScript Device to 24 bit color for color previews; use the style sheet color to get colored a2ps output. This only works if the color style sheet is installed on your system (/usr/bin/a2ps --list=style-sheets). Note that mutally contradictory options to a2ps may cancel each other out. So it looks like its to do with Yap, which is bundled with Miktex. It would probably be easiest to set something else as a viewer, through the general LyX preferences: Preferences -- File Formats -- DVI then look whats listed as the viewer - and try to change it. I don't know what else you may have to view it, but there is plenty about this sort of thing if you search these posts, for example.
Re: Initial Newbie Questions
I see that you were trying to change the color of a Chapter Heading, in particular. This does seem like a mess, easily reproducible by me; titles and sections seem to work, though. Evidently a problem for the masters.
Re: Initial Newbie Questions
(Fellow semi-beginner's response:)
I tried this with the different ways of viewing text
available to me on the mac with no problem.
I notice the LyX manual says, discussing the
text styles dialogue, (3.6.4):
Color: You can adjust the color of the
text with this control. Notice that not all dvi-viewers
are are able to display colors. ...
Then googling Yap color text I promptly got
http://www.gnustep.it/marko/GPSText/index.html
saying:
Getting colored output:
Set "PostScript Device" to "24 bit color"
for color previews; use the style sheet "color"
to get colored a2ps output.
This only works if the color style sheet
is installed on your system
("/usr/bin/a2ps --list=style-sheets").
Note that mutally contradictory options
to a2ps may cancel each other out.
So it looks like its to do with Yap, which is
bundled with Miktex. It would probably be
easiest to set something else as a viewer,
through the general LyX preferences:
Preferences --> File Formats --> DVI
then look whats listed as the viewer - and
try to change it. I don't know what else
you may have to view it, but there is
plenty about this sort of thing if you
search these posts, for example.
Re: Initial Newbie Questions
I see that you were trying to change the color of a Chapter Heading, in particular. This does seem like a mess, easily reproducible by me; titles and sections seem to work, though. Evidently a problem for the masters.
Re: smarten up quotation marks
I import a lot of text from online sources and databases, and often end up with straight quotation marks. Can anyone suggest an efficient searchreplace or macro to replace them all with proper quotation marks (i.e., 66 and 99)? If your problem is the one familiar to me, then it isn't really a LyX problem, but a sort of geometric one. On the principle that most initial quotes are preceded by a space, but few final ones are, a partial solution is to find and replace, searching for SPACE + straight quote and replacing with SPACE plus the left, or initial, quotes you want. The remaining straight quotes will be final or right quotes, and you can search and replace them with proper right hand quotes without worrying about spaces. Obviously some things will fall between the cracks. But perhaps your difficulty is more technical than I am thinking. Best, Michael
Re: smarten up quotation marks
I import a lot of text from online sources and databases, and often end up with straight quotation marks. Can anyone suggest an efficient searchreplace or macro to replace them all with proper quotation marks (i.e., 66 and 99)? If your problem is the one familiar to me, then it isn't really a LyX problem, but a sort of geometric one. On the principle that most initial quotes are preceded by a space, but few final ones are, a partial solution is to find and replace, searching for SPACE + straight quote and replacing with SPACE plus the left, or initial, quotes you want. The remaining straight quotes will be final or right quotes, and you can search and replace them with proper right hand quotes without worrying about spaces. Obviously some things will fall between the cracks. But perhaps your difficulty is more technical than I am thinking. Best, Michael
Re: smarten up quotation marks
I import a lot of text from online sources and databases, and often end > up with straight quotation marks. > > Can anyone suggest an efficient search or macro to replace them > all with proper quotation marks (i.e., 66 and 99)? If your problem is the one familiar to me, then it isn't really a LyX problem, but a sort of geometric one. On the principle that most initial quotes are preceded by a space, but few final ones are, a partial solution is to find and replace, searching for "SPACE + straight quote" and replacing with SPACE plus the left, or initial, quotes you want. The remaining straight quotes will be final or right quotes, and you can search and replace them with proper right hand quotes without worrying about spaces. Obviously some things will fall between the cracks. But perhaps your difficulty is more technical than I am thinking. Best, Michael
Re: A few other issues
Richard Heck [EMAIL PROTECTED] writes: bigblop wrote: 1) I am using justified text, which I prefer when I print. But I get seasick when all the text moves when I write. Is there someway to disable justification in LyX, but still keep it in the final pdf? No. But you can set left justification while writing and then turn it back to full justification when exporting. This does solve the seasickness problem beautifully, as does a microscopic screen font -- but there is the annoyance, or am I wrong?, that this has to be done for each paragraph, which promptly produces chaos. Or are you thinking of some way of turning off right justification other than through Edit--Paragraph Settings?
Re: A few other issues
Hmm, yes, I see. Well, here's a better way, perhaps, and it might even solve your problem more globally. Find the file stdclass.inc and copy it to your local LyX directory. Then change the line that says Align Block, under Style Standard, to Align Left. This may just get you exactly the result you want: Left-aligned on screen, but justified in the output. If so, and if you want to edit other layouts, then you can do the same with stdlayouts.inc and change e.g. the Quote environment. Richard Dear Richard: Wonderful! So far everything is working as you predicted. It makes the writing environment much more humane, (given whatever it is about me and some others.) I recommend giving it look to those who might think it is a matter of indifference. I have not yet tried it on the quotes via stdlayouts.inc. -Michael
Re: A few other issues
Richard Heck [EMAIL PROTECTED] writes: bigblop wrote: 1) I am using justified text, which I prefer when I print. But I get seasick when all the text moves when I write. Is there someway to disable justification in LyX, but still keep it in the final pdf? No. But you can set left justification while writing and then turn it back to full justification when exporting. This does solve the seasickness problem beautifully, as does a microscopic screen font -- but there is the annoyance, or am I wrong?, that this has to be done for each paragraph, which promptly produces chaos. Or are you thinking of some way of turning off right justification other than through Edit--Paragraph Settings?
Re: A few other issues
Hmm, yes, I see. Well, here's a better way, perhaps, and it might even solve your problem more globally. Find the file stdclass.inc and copy it to your local LyX directory. Then change the line that says Align Block, under Style Standard, to Align Left. This may just get you exactly the result you want: Left-aligned on screen, but justified in the output. If so, and if you want to edit other layouts, then you can do the same with stdlayouts.inc and change e.g. the Quote environment. Richard Dear Richard: Wonderful! So far everything is working as you predicted. It makes the writing environment much more humane, (given whatever it is about me and some others.) I recommend giving it look to those who might think it is a matter of indifference. I have not yet tried it on the quotes via stdlayouts.inc. -Michael
Re: A few other issues
Richard Heck <[EMAIL PROTECTED]> writes: > > bigblop wrote: > > 1) I am using justified text, which I prefer when I print. But I get seasick > > when all the text moves when I write. Is there someway to disable > > justification in LyX, but still keep it in the final pdf? > > > No. But you can set left justification while writing and then turn it > back to full justification when exporting. This does solve the seasickness problem beautifully, as does a microscopic screen font -- but there is the annoyance, or am I wrong?, that this has to be done for each paragraph, which promptly produces chaos. Or are you thinking of some way of turning off right justification other than through Edit-->Paragraph Settings?
Re: A few other issues
> Hmm, yes, I see. Well, here's a better way, perhaps, and it might even > solve your problem more globally. Find the file stdclass.inc and copy it > to your local LyX directory. Then change the line that says "Align > Block", under Style Standard, to "Align Left". This may just get you > exactly the result you want: Left-aligned on screen, but justified in > the output. If so, and if you want to edit other layouts, then you can > do the same with stdlayouts.inc and change e.g. the Quote environment. > > Richard > Dear Richard: Wonderful! So far everything is working as you predicted. It makes the writing environment much more humane, (given whatever it is about me and some others.) I recommend giving it look to those who might think it is a matter of indifference. I have not yet tried it on the quotes via stdlayouts.inc. -Michael
LyX 1.5.2 on intel Macbook, as on iBookG4 - Problems
Dear Bennett, (Sorry, this is not in sequence, I couldnt evade accusations of 'top posting' I have had the same problem with Lyx 1.5..2 on an Intel macbook. I didn't have this problem with the earlier 1.5 When I open most of the help documents I get: No information for converting xpm format files to png. Define a converter in the preferences. When I really needed something a while back, I got rid of some diagrams or images in the help document in question, and then it worked. It is an obnoxious error, since you have to do a forced quit of LyX get out. UPDATE... WHILE I WAS GOING THROUGH THE FILES JUST NOW TO SEE WHICH WORKED, THE PROBLEM CORRECTED ITSELF; strange it's been there for weeks, but it hasnt made a problem for me, since I dont need the converters. I didnt do anything just now but open the files in sequence, press DVI or PDF, get error, force LyX to quit, and then go on to the next one; then suddenly it worked with one it shouldn't have worked with; now it works with all. best, Michael
LyX 1.5.2 on intel Macbook - same Problems
Bjorn and Bennett: In my brief moment of joy with well-working converters, I tried to see if the trouble I had had with rtf2latex2e had disappeared. It hadn't, but when I closed LyX and reopened, all of Bjorn's and my trouble came back. This time, my method of just trying them all seems not to have worked. Best, Michael
LyX 1.5.2 on intel Macbook, as on iBookG4 - Problems
Dear Bennett, (Sorry, this is not in sequence, I couldnt evade accusations of 'top posting' I have had the same problem with Lyx 1.5..2 on an Intel macbook. I didn't have this problem with the earlier 1.5 When I open most of the help documents I get: No information for converting xpm format files to png. Define a converter in the preferences. When I really needed something a while back, I got rid of some diagrams or images in the help document in question, and then it worked. It is an obnoxious error, since you have to do a forced quit of LyX get out. UPDATE... WHILE I WAS GOING THROUGH THE FILES JUST NOW TO SEE WHICH WORKED, THE PROBLEM CORRECTED ITSELF; strange it's been there for weeks, but it hasnt made a problem for me, since I dont need the converters. I didnt do anything just now but open the files in sequence, press DVI or PDF, get error, force LyX to quit, and then go on to the next one; then suddenly it worked with one it shouldn't have worked with; now it works with all. best, Michael
LyX 1.5.2 on intel Macbook - same Problems
Bjorn and Bennett: In my brief moment of joy with well-working converters, I tried to see if the trouble I had had with rtf2latex2e had disappeared. It hadn't, but when I closed LyX and reopened, all of Bjorn's and my trouble came back. This time, my method of just trying them all seems not to have worked. Best, Michael
LyX 1.5.2 on intel Macbook, as on iBookG4 - Problems
Dear Bennett, (Sorry, this is not in sequence, I couldnt evade accusations of 'top posting' I have had the same problem with Lyx 1.5..2 on an Intel macbook. I didn't have this problem with the earlier 1.5 When I open most of the help documents I get: No information for converting xpm format files to png. Define a converter in the preferences. When I really needed something a while back, I got rid of some diagrams or images in the help document in question, and then it worked. It is an obnoxious error, since you have to do a forced quit of LyX get out. UPDATE... WHILE I WAS GOING THROUGH THE FILES JUST NOW TO SEE WHICH WORKED, THE PROBLEM CORRECTED ITSELF; strange it's been there for weeks, but it hasnt made a problem for me, since I dont need the converters. I didnt do anything just now but open the files in sequence, press DVI or PDF, get error, force LyX to quit, and then go on to the next one; then suddenly it worked with one it shouldn't have worked with; now it works with all. best, Michael
LyX 1.5.2 on intel Macbook - same Problems
Bjorn and Bennett: In my brief moment of joy with well-working converters, I tried to see if the trouble I had had with rtf2latex2e had disappeared. It hadn't, but when I closed LyX and reopened, all of Bjorn's and my trouble came back. This time, my method of just trying them all seems not to have worked. Best, Michael
Re: two questions on numbering - NEWBIE
Yitzhak Zangi [EMAIL PROTECTED] writes: 1) How to number the paragrphs without order (e.g. answer question 2 before question 1) such that the paragraphs will look like in the Enumarate environment? In the default Article class, the standard indentation for List is pretty deep. You can also use Description, which, when the paragraph continues beyond the first line, indents the rest like Enumerate (if you stick to the defaults). Your number will appear in bold (as the thing 'described'). Also, the first line will not be 'indented' enough and you will have to introduce four protected spaces (or fewer if its a two or more digit number) at the beginning (Insert--Formatting--Protected space.) I just mention this in case, as an inexpert user like me, you are averse to messing with the Document Settings, as I am. It is possible that this expedient would make problems if you moved from Article to IEEE-Article, or whatever. And maybe there is a simple solution to the deep indent of List.
Re: two questions on numbering - NEWBIE
Yitzhak Zangi [EMAIL PROTECTED] writes: 1) How to number the paragrphs without order (e.g. answer question 2 before question 1) such that the paragraphs will look like in the Enumarate environment? In the default Article class, the standard indentation for List is pretty deep. You can also use Description, which, when the paragraph continues beyond the first line, indents the rest like Enumerate (if you stick to the defaults). Your number will appear in bold (as the thing 'described'). Also, the first line will not be 'indented' enough and you will have to introduce four protected spaces (or fewer if its a two or more digit number) at the beginning (Insert--Formatting--Protected space.) I just mention this in case, as an inexpert user like me, you are averse to messing with the Document Settings, as I am. It is possible that this expedient would make problems if you moved from Article to IEEE-Article, or whatever. And maybe there is a simple solution to the deep indent of List.
Re: two questions on numbering - NEWBIE
Yitzhak Zangi <[EMAIL PROTECTED]> writes: > 1) How to number the paragrphs without order (e.g. answer question 2 before > question 1) such that the paragraphs will look like in the "Enumarate" > environment? In the default Article class, the standard indentation for List is pretty deep. You can also use Description, which, when the paragraph continues beyond the first line, indents the rest like Enumerate (if you stick to the defaults). Your number will appear in bold (as the thing 'described'). Also, the first line will not be 'indented' enough and you will have to introduce four protected spaces (or fewer if its a two or more digit number) at the beginning (Insert-->Formatting-->Protected space.) I just mention this in case, as an inexpert user like me, you are averse to messing with the Document Settings, as I am. It is possible that this expedient would make problems if you moved from Article to IEEE-Article, or whatever. And maybe there is a simple solution to the deep indent of List.
justification vs. 'ragged right' in the user interface?
Dear comrades I am a subliterate user, and was wondering if it was possible to set user preferences so that the screen one is working on is not justified on the right, but rather ragged. I noticed much discussion of justification in the past for the printed material, but none for the screen. It seems to me that with hyphenation and Tex, right justification is great for printed material. But on the screen we do not look at hypenated or texified material, so there is a lot of expanding and contracting between lines - just the loathesome phenomenon Tex gets past. I may be the only one on the planet, but this tends to make me slightly ill, sort of seasick. I would prefer then to see a ragged right document in the user interface, if it is possible. (I always tell students using Word and the like to turn off right justification, though Word's typesetting seems better now, though hardly latexlike.) It may be that this is easy and I'm just not seeing how; or it may be a deep consequence of the program that we get right justification. Yours Michael University of Pittsburgh, Pittsburgh PA practical.wisdom at gmail
justification vs. 'ragged right' in the user interface?
Dear comrades I am a subliterate user, and was wondering if it was possible to set user preferences so that the screen one is working on is not justified on the right, but rather ragged. I noticed much discussion of justification in the past for the printed material, but none for the screen. It seems to me that with hyphenation and Tex, right justification is great for printed material. But on the screen we do not look at hypenated or texified material, so there is a lot of expanding and contracting between lines - just the loathesome phenomenon Tex gets past. I may be the only one on the planet, but this tends to make me slightly ill, sort of seasick. I would prefer then to see a ragged right document in the user interface, if it is possible. (I always tell students using Word and the like to turn off right justification, though Word's typesetting seems better now, though hardly latexlike.) It may be that this is easy and I'm just not seeing how; or it may be a deep consequence of the program that we get right justification. Yours Michael University of Pittsburgh, Pittsburgh PA practical.wisdom at gmail
justification vs. 'ragged right' in the user interface?
Dear comrades I am a subliterate user, and was wondering if it was possible to set user preferences so that the screen one is working on is not justified on the right, but rather "ragged". I noticed much discussion of justification in the past for the printed material, but none for the screen. It seems to me that with hyphenation and Tex, right justification is great for printed material. But on the screen we do not look at hypenated or texified material, so there is a lot of expanding and contracting between lines - just the loathesome phenomenon Tex gets past. I may be the only one on the planet, but this tends to make me slightly ill, sort of seasick. I would prefer then to see a ragged right document in the user interface, if it is possible. (I always tell students using Word and the like to turn off right justification, though Word's typesetting seems better now, though hardly latexlike.) It may be that this is easy and I'm just not seeing how; or it may be a deep consequence of the program that we get right justification. Yours Michael University of Pittsburgh, Pittsburgh PA practical.wisdom at gmail
