nroff to LyX
Hi there: My platform: Linux Fedora Core 3 LyX 1.3.6 with change bar patch Our project of building all of the compiler docs with the compiler software is going really well. We're shaking out the last of the bugs (building with change bars vs. building without and with covers) at the moment. I have another question: I include the compiler man pages as a reference appendix in the User Guide. Currently I'm doing this by including the man pages as a PDF. Can you recommend a reliable converter to get man pages from troff/nroff into TeX/LyX? Has anyone tried this? Recommendations? Tips? Things to watch out for? Many thanks, --jane -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED]
nroff to LyX
Hi there: My platform: Linux Fedora Core 3 LyX 1.3.6 with change bar patch Our project of building all of the compiler docs with the compiler software is going really well. We're shaking out the last of the bugs (building with change bars vs. building without and with covers) at the moment. I have another question: I include the compiler man pages as a reference appendix in the User Guide. Currently I'm doing this by including the man pages as a PDF. Can you recommend a reliable converter to get man pages from troff/nroff into TeX/LyX? Has anyone tried this? Recommendations? Tips? Things to watch out for? Many thanks, --jane -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED]
nroff to LyX
Hi there: My platform: Linux Fedora Core 3 LyX 1.3.6 with change bar patch Our project of building all of the compiler docs with the compiler software is going really well. We're shaking out the last of the bugs (building with change bars vs. building without and with covers) at the moment. I have another question: I include the compiler man pages as a reference appendix in the User Guide. Currently I'm doing this by including the man pages as a PDF. Can you recommend a reliable converter to get man pages from troff/nroff into TeX/LyX? Has anyone tried this? Recommendations? Tips? Things to watch out for? Many thanks, --jane -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED]
Building 1.3.6 on SuSE 9 and SLES 8
Hi there:
We're working on building all of our LyX docs with the daily compiler
builds, which we do for a number of Linux platforms. The engineer who is
helping me with LyX here at PathScale tells me that the LyX part of
build failed on the SuSE 9 and SLES 8 platforms.
Here is the change he needed to make to get LyX 1.3.6 to compile on SuSE
(from the BitKeeper check in):
= src/frontends/qt2/QPrefs.C 1.2 vs edited =
--- 1.2/src/frontends/qt2/QPrefs.C 2005-07-14 01:42:49 -07:00
+++ edited/src/frontends/qt2/QPrefs.C 2005-09-08 11:54:20 -07:00
@@ -347,7 +347,7 @@
string const default_font_name = tmp.first;
for (int i = cb-count() - 1; i = 0; --i) {
- if (cb-text(i) == default_font_name) {
+ if (fromqstr(cb-text(i)) == default_font_name) {
cb-setCurrentItem(i);
return;
}
Hope this is helpful and useful.
Thanks!
--jane
--
Jane McKean
Technical Documentation
PathScale, Inc.
[EMAIL PROTECTED]
Building 1.3.6 64-bit with change tracking patch...
Hi there (again):
We're discovering a few things as we get our build system up and running
(to build the compiler docs along with our 64-bit compiler (optimized
for an Opteron system). The goal is to build LyX 1.3.6 with the change
bar patch on a 64-bit Opteron system for a number of LyX distributions.
Are you using LyX on a 64-bit system (specifically Opteron)? Can we
expect it to just work? Any hints you might pass along?
Thanks!
--jane
Here's the note from Jeremy, the engineer who's created the change
tracking patch and is now sorting out the build:
-
The change tracking patch added a boolean argument to many of the
editing functions that specified if the change was to be tracked. In
about every case, this has the default value of true. I have
discovered a possible ambiguity that needs to be resolved. In
paragraph.C, erase() was originally defined as:
void erase(lyx::pos_type pos);
The change tracking patch modified this and added another erase() call
that allowed the caller to specify a range:
void erase(lyx::pos_type pos, bool flag=true);
bool erase(lyx::pos_type start, lyx::pos_type end, bool flag=true);
lyx::pos_type is defined in src/support/types.h as
std::vectorchar::difference_type. On a system on which this type
matches the bool type, erase (11, 1) can appear to be either a call to
erase the character range from 11 to 1, or to erase the character at
11, with change tracking on.
I'm not certain I like this design choice, but it can be worked around
with this patch:
--- 1.3/src/CutAndPaste.C 2005-07-18 17:17:30 -07:00
+++ 1.4/src/CutAndPaste.C 2005-09-08 13:58:47 -07:00
@@ -92,7 +92,7 @@
}
if (!endpar || startpar == *endpar) {
- if (startpar-erase(start, end)) {
+ if (startpar-erase(start, end, true)) {
// Some chars were erased, go to start to be
safe
end = start;
}
@@ -103,7 +103,7 @@
// clear end/begin fragments of the first/last par in selection
actually_erased |= (startpar)-erase(start, startpar-size());
- if ((*endpar)-erase(0, end)) {
+ if ((*endpar)-erase(0, end, true)) {
actually_erased = true;
end = 0;
}
@@ -121,7 +121,7 @@
// erase the contents of the par
if (pit != *endpar) {
- actually_erased |= pit-erase(0, pit-size());
+ actually_erased |= pit-erase(0, pit-size(),
true);
// remove the par if it's now empty
if (actually_erased) {
--
Jane McKean
Technical Documentation
PathScale, Inc.
[EMAIL PROTECTED]
Building 1.3.6 on SuSE 9 and SLES 8
Hi there:
We're working on building all of our LyX docs with the daily compiler
builds, which we do for a number of Linux platforms. The engineer who is
helping me with LyX here at PathScale tells me that the LyX part of
build failed on the SuSE 9 and SLES 8 platforms.
Here is the change he needed to make to get LyX 1.3.6 to compile on SuSE
(from the BitKeeper check in):
= src/frontends/qt2/QPrefs.C 1.2 vs edited =
--- 1.2/src/frontends/qt2/QPrefs.C 2005-07-14 01:42:49 -07:00
+++ edited/src/frontends/qt2/QPrefs.C 2005-09-08 11:54:20 -07:00
@@ -347,7 +347,7 @@
string const default_font_name = tmp.first;
for (int i = cb-count() - 1; i = 0; --i) {
- if (cb-text(i) == default_font_name) {
+ if (fromqstr(cb-text(i)) == default_font_name) {
cb-setCurrentItem(i);
return;
}
Hope this is helpful and useful.
Thanks!
--jane
--
Jane McKean
Technical Documentation
PathScale, Inc.
[EMAIL PROTECTED]
Building 1.3.6 64-bit with change tracking patch...
Hi there (again):
We're discovering a few things as we get our build system up and running
(to build the compiler docs along with our 64-bit compiler (optimized
for an Opteron system). The goal is to build LyX 1.3.6 with the change
bar patch on a 64-bit Opteron system for a number of LyX distributions.
Are you using LyX on a 64-bit system (specifically Opteron)? Can we
expect it to just work? Any hints you might pass along?
Thanks!
--jane
Here's the note from Jeremy, the engineer who's created the change
tracking patch and is now sorting out the build:
-
The change tracking patch added a boolean argument to many of the
editing functions that specified if the change was to be tracked. In
about every case, this has the default value of true. I have
discovered a possible ambiguity that needs to be resolved. In
paragraph.C, erase() was originally defined as:
void erase(lyx::pos_type pos);
The change tracking patch modified this and added another erase() call
that allowed the caller to specify a range:
void erase(lyx::pos_type pos, bool flag=true);
bool erase(lyx::pos_type start, lyx::pos_type end, bool flag=true);
lyx::pos_type is defined in src/support/types.h as
std::vectorchar::difference_type. On a system on which this type
matches the bool type, erase (11, 1) can appear to be either a call to
erase the character range from 11 to 1, or to erase the character at
11, with change tracking on.
I'm not certain I like this design choice, but it can be worked around
with this patch:
--- 1.3/src/CutAndPaste.C 2005-07-18 17:17:30 -07:00
+++ 1.4/src/CutAndPaste.C 2005-09-08 13:58:47 -07:00
@@ -92,7 +92,7 @@
}
if (!endpar || startpar == *endpar) {
- if (startpar-erase(start, end)) {
+ if (startpar-erase(start, end, true)) {
// Some chars were erased, go to start to be
safe
end = start;
}
@@ -103,7 +103,7 @@
// clear end/begin fragments of the first/last par in selection
actually_erased |= (startpar)-erase(start, startpar-size());
- if ((*endpar)-erase(0, end)) {
+ if ((*endpar)-erase(0, end, true)) {
actually_erased = true;
end = 0;
}
@@ -121,7 +121,7 @@
// erase the contents of the par
if (pit != *endpar) {
- actually_erased |= pit-erase(0, pit-size());
+ actually_erased |= pit-erase(0, pit-size(),
true);
// remove the par if it's now empty
if (actually_erased) {
--
Jane McKean
Technical Documentation
PathScale, Inc.
[EMAIL PROTECTED]
Building 1.3.6 on SuSE 9 and SLES 8
Hi there:
We're working on building all of our LyX docs with the daily compiler
builds, which we do for a number of Linux platforms. The engineer who is
helping me with LyX here at PathScale tells me that the LyX part of
build failed on the SuSE 9 and SLES 8 platforms.
Here is the change he needed to make to get LyX 1.3.6 to compile on SuSE
(from the BitKeeper check in):
= src/frontends/qt2/QPrefs.C 1.2 vs edited =
--- 1.2/src/frontends/qt2/QPrefs.C 2005-07-14 01:42:49 -07:00
+++ edited/src/frontends/qt2/QPrefs.C 2005-09-08 11:54:20 -07:00
@@ -347,7 +347,7 @@
string const & default_font_name = tmp.first;
for (int i = cb->count() - 1; i >= 0; --i) {
- if (cb->text(i) == default_font_name) {
+ if (fromqstr(cb->text(i)) == default_font_name) {
cb->setCurrentItem(i);
return;
}
Hope this is helpful and useful.
Thanks!
--jane
--
Jane McKean
Technical Documentation
PathScale, Inc.
[EMAIL PROTECTED]
Building 1.3.6 64-bit with change tracking patch...
Hi there (again):
We're discovering a few things as we get our build system up and running
(to build the compiler docs along with our 64-bit compiler (optimized
for an Opteron system). The goal is to build LyX 1.3.6 with the change
bar patch on a 64-bit Opteron system for a number of LyX distributions.
Are you using LyX on a 64-bit system (specifically Opteron)? Can we
expect it to "just work"? Any hints you might pass along?
Thanks!
--jane
Here's the note from Jeremy, the engineer who's created the change
tracking patch and is now sorting out the build:
-
The change tracking patch added a boolean argument to many of the
editing functions that specified if the change was to be tracked. In
about every case, this has the default value of true. I have
discovered a possible ambiguity that needs to be resolved. In
paragraph.C, erase() was originally defined as:
void erase(lyx::pos_type pos);
The change tracking patch modified this and added another erase() call
that allowed the caller to specify a range:
void erase(lyx::pos_type pos, bool flag=true);
bool erase(lyx::pos_type start, lyx::pos_type end, bool flag=true);
lyx::pos_type is defined in src/support/types.h as
std::vector::difference_type. On a system on which this type
matches the bool type, erase (11, 1) can appear to be either a call to
erase the character range from 11 to 1, or to erase the character at
11, with change tracking on.
I'm not certain I like this design choice, but it can be worked around
with this patch:
--- 1.3/src/CutAndPaste.C 2005-07-18 17:17:30 -07:00
+++ 1.4/src/CutAndPaste.C 2005-09-08 13:58:47 -07:00
@@ -92,7 +92,7 @@
}
if (!endpar || startpar == *endpar) {
- if (startpar->erase(start, end)) {
+ if (startpar->erase(start, end, true)) {
// Some chars were erased, go to start to be
safe
end = start;
}
@@ -103,7 +103,7 @@
// clear end/begin fragments of the first/last par in selection
actually_erased |= (startpar)->erase(start, startpar->size());
- if ((*endpar)->erase(0, end)) {
+ if ((*endpar)->erase(0, end, true)) {
actually_erased = true;
end = 0;
}
@@ -121,7 +121,7 @@
// "erase" the contents of the par
if (pit != *endpar) {
- actually_erased |= pit->erase(0, pit->size());
+ actually_erased |= pit->erase(0, pit->size(),
true);
// remove the par if it's now empty
if (actually_erased) {
--
Jane McKean
Technical Documentation
PathScale, Inc.
[EMAIL PROTECTED]
Re: Generating LyX docs in a build
Jose': This is perfect. Thank you so much for the build information. Will keep you posted about how it works out. --jane
Re: Generating LyX docs in a build
Jose': This is perfect. Thank you so much for the build information. Will keep you posted about how it works out. --jane
Re: Generating LyX docs in a build
Jose': This is perfect. Thank you so much for the build information. Will keep you posted about how it works out. --jane
Generating LyX docs in a build
Hi there: I have a question that I hope you can help me with. I'm using LyX 1.3.6 on Fedora Core 4 (Linux) with the change bar patch (using dvipost). I create all of the user documentation for our compiler suite (except for the README and man pages) in LyX, and up until now, I've generated PDFs and checked them into our build tree. We automatically build the compiler environment software daily and those PDFs get picked up as a final step in the build. Our buildmaster would like to have the build process generate the final PDFs and only have the .lyx files (and possibly the .tex files) checked in. This way the build process could generate the most current daily PDFs that would be up-to-date with the software. During our production cycle, I use change bars on the docs and generate the PDF using PDF (dvipdfm) from the LyX menu bar, and then about a week before release, I turn the change bars off and generate the PDF using PDF (pdflatex). To accomplish this as part of the build, I need a command line equivalent (and it could be multiple command lines) for each of these methods. - The command-line equivalent for View PDF (dvipdfm) - The command-line equivalent for View PDF (latexpdf) Has anyone tried doing something like this? Is anyone currently generating their docs as part of a source code build with build script? Many thanks in advance, --jane -- Jane McKean Technical Documentation PathScale, Inc. jane at pathscale.com
Generating LyX docs in a build
Hi there: I have a question that I hope you can help me with. I'm using LyX 1.3.6 on Fedora Core 4 (Linux) with the change bar patch (using dvipost). I create all of the user documentation for our compiler suite (except for the README and man pages) in LyX, and up until now, I've generated PDFs and checked them into our build tree. We automatically build the compiler environment software daily and those PDFs get picked up as a final step in the build. Our buildmaster would like to have the build process generate the final PDFs and only have the .lyx files (and possibly the .tex files) checked in. This way the build process could generate the most current daily PDFs that would be up-to-date with the software. During our production cycle, I use change bars on the docs and generate the PDF using PDF (dvipdfm) from the LyX menu bar, and then about a week before release, I turn the change bars off and generate the PDF using PDF (pdflatex). To accomplish this as part of the build, I need a command line equivalent (and it could be multiple command lines) for each of these methods. - The command-line equivalent for View PDF (dvipdfm) - The command-line equivalent for View PDF (latexpdf) Has anyone tried doing something like this? Is anyone currently generating their docs as part of a source code build with build script? Many thanks in advance, --jane -- Jane McKean Technical Documentation PathScale, Inc. jane at pathscale.com
Generating LyX docs in a build
Hi there: I have a question that I hope you can help me with. I'm using LyX 1.3.6 on Fedora Core 4 (Linux) with the change bar patch (using dvipost). I create all of the user documentation for our compiler suite (except for the README and man pages) in LyX, and up until now, I've generated PDFs and checked them into our build tree. We automatically build the compiler environment software daily and those PDFs get picked up as a final step in the build. Our buildmaster would like to have the build process generate the final PDFs and only have the .lyx files (and possibly the .tex files) checked in. This way the build process could generate the most current daily PDFs that would be up-to-date with the software. During our production cycle, I use change bars on the docs and generate the PDF using PDF (dvipdfm) from the LyX menu bar, and then about a week before release, I turn the change bars off and generate the PDF using PDF (pdflatex). To accomplish this as part of the build, I need a command line equivalent (and it could be multiple command lines) for each of these methods. - The command-line equivalent for View > PDF (dvipdfm) - The command-line equivalent for View > PDF (latexpdf) Has anyone tried doing something like this? Is anyone currently generating their docs as part of a source code build with build script? Many thanks in advance, --jane -- Jane McKean Technical Documentation PathScale, Inc. jane at pathscale.com
Re: How to print change bars
Roger:
I don't call dvipost in my preamble, I set in my converters.
Go to the menu bar and choose Edit Preferences Converters DVI -
Postscript and set the converter to /usr/bin/dvipspost $$i $$o
See if that does the trick for you. There are more details on setting
this all up on the Wiki page -
http://wiki.lyx.org/Tips/ChangeTrackingLyx1-3-2 .
Let me know if this works.
thanks,
--jane
On Fri, 2005-08-05 at 13:30 +1000, Roger McMurtrie wrote:
Jane,
I checked the dvipost version using the command line. It shows version
1.0.
Following is my preamble, in case you can spot something amiss there.
\usepackage{ae,aecompl}
\usepackage{dvipost}
\makeatletter
[EMAIL PROTECTED]
\makeatother
\lhead{}
\renewcommand{\headrulewidth}{0pt}
%Set fixed vertical justification
\raggedbottom
I'm wondering if this problem may be due to an attempt to upgrade teTex that
I
made awhile ago. As the upgrade was unsuccessful (many things wouldn't work)
I reverted to the original version. I think that it was after that episode
that just a few problems arose to do with conversion such as having to run
View twice for a first printing during a Lyx session.
Its not only that the change bars are not shown. Deleted text (strike
throughs) print but without the strike through.
Seems like dvipost isn't being invoked.
If I ever discover what's causing the problem I'll let you know.
I wonder what will happen with Lyx 1.4?
Regards
Roger
--
Jane McKean
Technical Documentation
PathScale, Inc.
[EMAIL PROTECTED]
Re: How to print change bars
Roger:
I don't call dvipost in my preamble, I set in my converters.
Go to the menu bar and choose Edit Preferences Converters DVI -
Postscript and set the converter to /usr/bin/dvipspost $$i $$o
See if that does the trick for you. There are more details on setting
this all up on the Wiki page -
http://wiki.lyx.org/Tips/ChangeTrackingLyx1-3-2 .
Let me know if this works.
thanks,
--jane
On Fri, 2005-08-05 at 13:30 +1000, Roger McMurtrie wrote:
Jane,
I checked the dvipost version using the command line. It shows version
1.0.
Following is my preamble, in case you can spot something amiss there.
\usepackage{ae,aecompl}
\usepackage{dvipost}
\makeatletter
[EMAIL PROTECTED]
\makeatother
\lhead{}
\renewcommand{\headrulewidth}{0pt}
%Set fixed vertical justification
\raggedbottom
I'm wondering if this problem may be due to an attempt to upgrade teTex that
I
made awhile ago. As the upgrade was unsuccessful (many things wouldn't work)
I reverted to the original version. I think that it was after that episode
that just a few problems arose to do with conversion such as having to run
View twice for a first printing during a Lyx session.
Its not only that the change bars are not shown. Deleted text (strike
throughs) print but without the strike through.
Seems like dvipost isn't being invoked.
If I ever discover what's causing the problem I'll let you know.
I wonder what will happen with Lyx 1.4?
Regards
Roger
--
Jane McKean
Technical Documentation
PathScale, Inc.
[EMAIL PROTECTED]
Re: How to print change bars
Roger:
I don't call dvipost in my preamble, I set in my converters.
Go to the menu bar and choose Edit > Preferences > Converters > DVI ->
Postscript and set the converter to /usr/bin/dvipspost $$i $$o
See if that does the trick for you. There are more details on setting
this all up on the Wiki page -
http://wiki.lyx.org/Tips/ChangeTrackingLyx1-3-2 .
Let me know if this works.
thanks,
--jane
On Fri, 2005-08-05 at 13:30 +1000, Roger McMurtrie wrote:
> Jane,
> I checked the dvipost version using the command line. It shows version
> 1.0.
>
> Following is my preamble, in case you can spot something amiss there.
>
> \usepackage{ae,aecompl}
> \usepackage{dvipost}
> \makeatletter
> [EMAIL PROTECTED]
> \makeatother
> \lhead{}
> \renewcommand{\headrulewidth}{0pt}
> %Set fixed vertical justification
> \raggedbottom
>
> I'm wondering if this problem may be due to an attempt to upgrade teTex that
> I
> made awhile ago. As the upgrade was unsuccessful (many things wouldn't work)
> I reverted to the original version. I think that it was after that episode
> that just a few problems arose to do with conversion such as having to run
> View twice for a first printing during a Lyx session.
>
> Its not only that the change bars are not shown. Deleted text (strike
> throughs) print but without the strike through.
>
> Seems like dvipost isn't being invoked.
>
> If I ever discover what's causing the problem I'll let you know.
> I wonder what will happen with Lyx 1.4?
>
> Regards
>
> Roger
--
Jane McKean
Technical Documentation
PathScale, Inc.
[EMAIL PROTECTED]
Re: How to print change bars
Roger: Hmm. I'm not sure what to suggest. If you have dvipost installed, you've reset the outer margin, and you are creating the PDF from View PDF (dvipdfm) then I'm stumped. I would doublecheck the installation and review the Wiki page, be sure that change bars are on, and try it again. Let us know what you find. I'm curious. I know the margin thing stumped me for awhile, but that doesn't seem to be what's happening with you. thanks, --jane On Thu, 2005-08-04 at 10:06 +1000, Roger McMurtrie wrote: Jane Thanks for the suggestion. I tried changing the out margin to quite a large value but still no sign of change bars. Roger On Thu, 4 Aug 2005 02:47 am, Jane McKean wrote: Roger: I've found that you need to change the outer margins so that the change bars show. With my normal, printing margins the change bars were off the page. Go to Layout Document Margins and change the outer margins to something like 2.25 and see if they show up when you print them. --jane
Re: How to print change bars
Roger: Hmm. I'm not sure what to suggest. If you have dvipost installed, you've reset the outer margin, and you are creating the PDF from View PDF (dvipdfm) then I'm stumped. I would doublecheck the installation and review the Wiki page, be sure that change bars are on, and try it again. Let us know what you find. I'm curious. I know the margin thing stumped me for awhile, but that doesn't seem to be what's happening with you. thanks, --jane On Thu, 2005-08-04 at 10:06 +1000, Roger McMurtrie wrote: Jane Thanks for the suggestion. I tried changing the out margin to quite a large value but still no sign of change bars. Roger On Thu, 4 Aug 2005 02:47 am, Jane McKean wrote: Roger: I've found that you need to change the outer margins so that the change bars show. With my normal, printing margins the change bars were off the page. Go to Layout Document Margins and change the outer margins to something like 2.25 and see if they show up when you print them. --jane
Re: How to print change bars
Roger: Hmm. I'm not sure what to suggest. If you have dvipost installed, you've reset the outer margin, and you are creating the PDF from View > PDF (dvipdfm) then I'm stumped. I would doublecheck the installation and review the Wiki page, be sure that change bars are on, and try it again. Let us know what you find. I'm curious. I know the margin thing stumped me for awhile, but that doesn't seem to be what's happening with you. thanks, --jane On Thu, 2005-08-04 at 10:06 +1000, Roger McMurtrie wrote: > Jane > > Thanks for the suggestion. > > I tried changing the out margin to quite a large value but still no sign of > change bars. > > Roger > > > On Thu, 4 Aug 2005 02:47 am, Jane McKean wrote: > > Roger: > > > > I've found that you need to change the outer margins so that the change > > bars show. With my normal, printing margins the change bars were off the > > page. > > > > Go to Layout > Document > Margins and change the outer margins to > > something like 2.25 and see if they show up when you print them. > > > > --jane >
behaviour of changebars (tracking changes)
Martin: ok - i cleared the preamble and tracking changes works. however, i observe strange behavior: 1) i generated a new document, entered some text, enabled tracking changes, and addied some more text and deleted some. this shows nicely in lyx. hoever, in dvi it shows in black white only. in postscript it shows in colors, but there is no vertical bars in the margin. 2) using tracking changes with my paper. i cleared the preamble (as first stated). tracking changed shows well in lyx, but not at all in dvi. it does show in postscript, but still no vertical bars in the margins. ideas? martin To see the vertical change bars in my PDFs, I have to adjust the margins. In my docs I set the outer margins to 2.75 in. (Layout Document Margins). I set them back to 1.75 for my final PDFs. Yes, it is annoying that accepting all the changes bounces you to the end of the doc, but it's something I found I can live with. Deleting a space will only show up as the vertical change bar, which is probably being displayed outside of your page margins now. Hope this helps. I have found the change bars to be very helpful in our documentation production cycle (I wouldn't be able to use LyX for our doc tool without them) and I'm anxious to see the 1.4 change bar feature. Thank LyX team! --jane -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED]
behaviour of changebars (tracking changes)
Martin: ok - i cleared the preamble and tracking changes works. however, i observe strange behavior: 1) i generated a new document, entered some text, enabled tracking changes, and addied some more text and deleted some. this shows nicely in lyx. hoever, in dvi it shows in black white only. in postscript it shows in colors, but there is no vertical bars in the margin. 2) using tracking changes with my paper. i cleared the preamble (as first stated). tracking changed shows well in lyx, but not at all in dvi. it does show in postscript, but still no vertical bars in the margins. ideas? martin To see the vertical change bars in my PDFs, I have to adjust the margins. In my docs I set the outer margins to 2.75 in. (Layout Document Margins). I set them back to 1.75 for my final PDFs. Yes, it is annoying that accepting all the changes bounces you to the end of the doc, but it's something I found I can live with. Deleting a space will only show up as the vertical change bar, which is probably being displayed outside of your page margins now. Hope this helps. I have found the change bars to be very helpful in our documentation production cycle (I wouldn't be able to use LyX for our doc tool without them) and I'm anxious to see the 1.4 change bar feature. Thank LyX team! --jane -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED]
behaviour of changebars (tracking changes)
Martin: > ok - i cleared the preamble and tracking changes works. however, i > observe strange behavior: > 1) i generated a new document, entered some text, enabled tracking changes, > and > addied some more text and deleted some. this shows nicely in lyx. hoever, in > dvi it shows in black & white only. in postscript it shows in colors, but > there > is no vertical bars in the margin. > > 2) using tracking changes with my paper. i cleared the preamble (as > first stated). tracking changed shows well in lyx, but not at all in > dvi. it does show in postscript, but still no vertical bars in the margins. > > > ideas? > > martin To see the vertical change bars in my PDFs, I have to adjust the margins. In my docs I set the outer margins to 2.75 in. (Layout > Document > Margins). I set them back to 1.75 for my final PDFs. Yes, it is annoying that accepting all the changes bounces you to the end of the doc, but it's something I found I can live with. Deleting a space will only show up as the vertical change bar, which is probably being displayed outside of your page margins now. Hope this helps. I have found the change bars to be very helpful in our documentation production cycle (I wouldn't be able to use LyX for our doc tool without them) and I'm anxious to see the 1.4 change bar feature. Thank LyX team! --jane -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED]
Creating HTML docs from LyX
Hi there: I am using LyX 1.3.5 on Fedora Core 3 to create our compiler documentation set (now up to six volumes or so). I've been creating PDFs from LyX as the final output (pdflatex), with included PDFs for the covers (artwork from Marketing). I have figures, tables, an index, the works. Everyone has been very pleased with the output and the documentation set. Now they want an HTML version of the docs to post on our website, not just the PDFs. My question: Has anybody created a volume of documentation (300-500 pages) in LyX and converted it to HTML? Do you have any recommendations, suggestions, things to avoid? Are there other converters/tools/packages you might recommend? Would I be better off generating from the .tex files that LyX creates? I understand that tables can be problematic. I'm a one-person doc team; though I can bug the engineers for some help with LyX/configuration/installing packages. Other than that I need to be able to implement the solution pretty much on my own, while still hitting our rather aggressive release dates. I love LyX and have been very happy with it as a documentation tool. This list has helped me solve many problems this past two years. Many thanks in advance for your help with this. --jane -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED]
Creating HTML docs from LyX
Hi there: I am using LyX 1.3.5 on Fedora Core 3 to create our compiler documentation set (now up to six volumes or so). I've been creating PDFs from LyX as the final output (pdflatex), with included PDFs for the covers (artwork from Marketing). I have figures, tables, an index, the works. Everyone has been very pleased with the output and the documentation set. Now they want an HTML version of the docs to post on our website, not just the PDFs. My question: Has anybody created a volume of documentation (300-500 pages) in LyX and converted it to HTML? Do you have any recommendations, suggestions, things to avoid? Are there other converters/tools/packages you might recommend? Would I be better off generating from the .tex files that LyX creates? I understand that tables can be problematic. I'm a one-person doc team; though I can bug the engineers for some help with LyX/configuration/installing packages. Other than that I need to be able to implement the solution pretty much on my own, while still hitting our rather aggressive release dates. I love LyX and have been very happy with it as a documentation tool. This list has helped me solve many problems this past two years. Many thanks in advance for your help with this. --jane -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED]
Creating HTML docs from LyX
Hi there: I am using LyX 1.3.5 on Fedora Core 3 to create our compiler documentation set (now up to six volumes or so). I've been creating PDFs from LyX as the final output (pdflatex), with included PDFs for the covers (artwork from Marketing). I have figures, tables, an index, the works. Everyone has been very pleased with the output and the documentation set. Now they want an HTML version of the docs to post on our website, not just the PDFs. My question: Has anybody created a volume of documentation (300-500 pages) in LyX and converted it to HTML? Do you have any recommendations, suggestions, things to avoid? Are there other converters/tools/packages you might recommend? Would I be better off generating from the .tex files that LyX creates? I understand that tables can be problematic. I'm a one-person doc team; though I can bug the engineers for some help with LyX/configuration/installing packages. Other than that I need to be able to implement the solution pretty much on my own, while still hitting our rather aggressive release dates. I love LyX and have been very happy with it as a documentation tool. This list has helped me solve many problems this past two years. Many thanks in advance for your help with this. --jane -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED]
Re: Setting the version of PDF from LyX
Uwe: I'm getting this error even with files that don't have included PDFs. Also, I've generated the included files (where I use them) with Acrobat so that they are PDF version 1.4. I'm using this version of pdflatex (running on Fedora Core 3): $ pdflatex -v pdfTeX (Web2C 7.4.5) 3.14159-1.10b kpathsea version 3.4.5 So are you saying that I should install a new version of pdflatex? Any other ideas what could be causing this? Thanks in advance, --jane On Sat, 2005-03-05 at 02:58 +0100, Uwe Sthr wrote: Jane McKean wrote: When I generate my PDFs using View PDF(pdflatex), I get the following warning during the generation: Error: PDF version 1.5 -- xpdf supports version 1.4 (continuing anyway) Is there some mechanism for setting the PDF version from within LyX, so that it would generate PDF version 1.4? No it isn't. The pdf-version depends on the pdflatex-version, because pdflatex uses internally xpdf. The error occurs when you use external pdf's (in pdf 1.5 format) in your document. Possibly you inserted a pdf image. To get rid of this error, reduce the pdf version using a pdf editor (e.g. Acrobat) or update pdflatex. xpdf version 3 supports pdf 1.5. And this version is used in pdflatex since version 1.2x. The new teTeX 3 comes with pdflatex 1.21a. regards Uwe
Re: Setting the version of PDF from LyX
Uwe: I'm getting this error even with files that don't have included PDFs. Also, I've generated the included files (where I use them) with Acrobat so that they are PDF version 1.4. I'm using this version of pdflatex (running on Fedora Core 3): $ pdflatex -v pdfTeX (Web2C 7.4.5) 3.14159-1.10b kpathsea version 3.4.5 So are you saying that I should install a new version of pdflatex? Any other ideas what could be causing this? Thanks in advance, --jane On Sat, 2005-03-05 at 02:58 +0100, Uwe Sthr wrote: Jane McKean wrote: When I generate my PDFs using View PDF(pdflatex), I get the following warning during the generation: Error: PDF version 1.5 -- xpdf supports version 1.4 (continuing anyway) Is there some mechanism for setting the PDF version from within LyX, so that it would generate PDF version 1.4? No it isn't. The pdf-version depends on the pdflatex-version, because pdflatex uses internally xpdf. The error occurs when you use external pdf's (in pdf 1.5 format) in your document. Possibly you inserted a pdf image. To get rid of this error, reduce the pdf version using a pdf editor (e.g. Acrobat) or update pdflatex. xpdf version 3 supports pdf 1.5. And this version is used in pdflatex since version 1.2x. The new teTeX 3 comes with pdflatex 1.21a. regards Uwe
Re: Setting the version of PDF from LyX
Uwe: I'm getting this error even with files that don't have included PDFs. Also, I've generated the included files (where I use them) with Acrobat so that they are PDF version 1.4. I'm using this version of pdflatex (running on Fedora Core 3): $ pdflatex -v pdfTeX (Web2C 7.4.5) 3.14159-1.10b kpathsea version 3.4.5 So are you saying that I should install a new version of pdflatex? Any other ideas what could be causing this? Thanks in advance, --jane On Sat, 2005-03-05 at 02:58 +0100, Uwe StÃhr wrote: > Jane McKean wrote: > > > When I generate my PDFs using View > PDF(pdflatex), I get the following > > warning during the generation: > > > > Error: PDF version 1.5 -- xpdf supports version 1.4 (continuing anyway) > > > > Is there some mechanism for setting the PDF version from within LyX, so > > that it would generate PDF version 1.4? > > No it isn't. The pdf-version depends on the pdflatex-version, because > pdflatex uses internally xpdf. > The error occurs when you use external pdf's (in pdf 1.5 format) in your > document. Possibly you inserted a pdf image. > To get rid of this error, reduce the pdf version using a pdf editor > (e.g. Acrobat) or update pdflatex. > xpdf version 3 supports pdf 1.5. And this version is used in pdflatex > since version 1.2x. The new teTeX 3 comes with pdflatex 1.21a. > > regards Uwe
Setting the version of PDF from LyX
Hi there: When I generate my PDFs using View PDF(pdflatex), I get the following warning during the generation: Error: PDF version 1.5 -- xpdf supports version 1.4 (continuing anyway) Error: PDF version 1.5 -- xpdf supports version 1.4 (continuing anyway) Error: PDF version 1.5 -- xpdf supports version 1.4 (continuing anyway) Error: PDF version 1.5 -- xpdf supports version 1.4 (continuing anyway) Error: PDF version 1.5 -- xpdf supports version 1.4 (continuing anyway) Is there some mechanism for setting the PDF version from within LyX, so that it would generate PDF version 1.4? Thanks in advance for your help, --jane -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED] Details: Linux, Fedora Core 3 LyX 1.3.5 of Wed. Oct. 6, 2004 (with change bar patch installed)
Setting the version of PDF from LyX
Hi there: When I generate my PDFs using View PDF(pdflatex), I get the following warning during the generation: Error: PDF version 1.5 -- xpdf supports version 1.4 (continuing anyway) Error: PDF version 1.5 -- xpdf supports version 1.4 (continuing anyway) Error: PDF version 1.5 -- xpdf supports version 1.4 (continuing anyway) Error: PDF version 1.5 -- xpdf supports version 1.4 (continuing anyway) Error: PDF version 1.5 -- xpdf supports version 1.4 (continuing anyway) Is there some mechanism for setting the PDF version from within LyX, so that it would generate PDF version 1.4? Thanks in advance for your help, --jane -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED] Details: Linux, Fedora Core 3 LyX 1.3.5 of Wed. Oct. 6, 2004 (with change bar patch installed)
Setting the version of PDF from LyX
Hi there: When I generate my PDFs using View > PDF(pdflatex), I get the following warning during the generation: Error: PDF version 1.5 -- xpdf supports version 1.4 (continuing anyway) Error: PDF version 1.5 -- xpdf supports version 1.4 (continuing anyway) Error: PDF version 1.5 -- xpdf supports version 1.4 (continuing anyway) Error: PDF version 1.5 -- xpdf supports version 1.4 (continuing anyway) Error: PDF version 1.5 -- xpdf supports version 1.4 (continuing anyway) Is there some mechanism for setting the PDF version from within LyX, so that it would generate PDF version 1.4? Thanks in advance for your help, --jane -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED] Details: Linux, Fedora Core 3 LyX 1.3.5 of Wed. Oct. 6, 2004 (with change bar patch installed)
[Fwd: Re: Adding a second index to document]
Steve: I haven't a clue about how to add a second table of contents, but I'll bet the list might have some ideas. I'm forwarding your question to them. I hadn't thought about a second TofC; I'd be interested in that too... thanks, --jane -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED] ---BeginMessage--- I have a related question. How do you have 2 tables of contents. I'd like to do what the Unleashed books do -- have one table of contents that goes down to the chapter level, and another that goes down to the subsection. SteveT On Tuesday 18 January 2005 08:40 pm, Jane McKean wrote: Hi there: I'm running LyX 1.3.5 on Fedora Core 3 (thank you for your help with the move from Red Hat 9 to FC3; it's working great). I'm creating and expanding our compiler and debugger documentation set using LyX. A request has been made to add a second index to the User Guide consisting of all of the compiler flags (there are hundreds). The users would like to have all of the options listed in one place in the docs. I have an existing index that I've created using the Index entry option (Insert Index entry). How would I enter or tag the compiler options to create a second index? (I'm not sure what you would call it, but it would be two column, sorted alphabetically and linked back to the page on which the term occurred) Has anyone created something like this using LyX/LaTeX? I searched the archives and Herbert's Tips and Tricks, but because I don't know exactly what you'd call it, I couldn't find what I was looking for. Thanks in advance for your help with this. Jane ---End Message---
[Fwd: Re: Adding a second index to document]
Steve: I haven't a clue about how to add a second table of contents, but I'll bet the list might have some ideas. I'm forwarding your question to them. I hadn't thought about a second TofC; I'd be interested in that too... thanks, --jane -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED] ---BeginMessage--- I have a related question. How do you have 2 tables of contents. I'd like to do what the Unleashed books do -- have one table of contents that goes down to the chapter level, and another that goes down to the subsection. SteveT On Tuesday 18 January 2005 08:40 pm, Jane McKean wrote: Hi there: I'm running LyX 1.3.5 on Fedora Core 3 (thank you for your help with the move from Red Hat 9 to FC3; it's working great). I'm creating and expanding our compiler and debugger documentation set using LyX. A request has been made to add a second index to the User Guide consisting of all of the compiler flags (there are hundreds). The users would like to have all of the options listed in one place in the docs. I have an existing index that I've created using the Index entry option (Insert Index entry). How would I enter or tag the compiler options to create a second index? (I'm not sure what you would call it, but it would be two column, sorted alphabetically and linked back to the page on which the term occurred) Has anyone created something like this using LyX/LaTeX? I searched the archives and Herbert's Tips and Tricks, but because I don't know exactly what you'd call it, I couldn't find what I was looking for. Thanks in advance for your help with this. Jane ---End Message---
[Fwd: Re: Adding a second "index" to document]
Steve: I haven't a clue about how to add a second table of contents, but I'll bet the list might have some ideas. I'm forwarding your question to them. I hadn't thought about a second TofC; I'd be interested in that too... thanks, --jane -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED] --- Begin Message --- I have a related question. How do you have 2 tables of contents. I'd like to do what the Unleashed books do -- have one table of contents that goes down to the chapter level, and another that goes down to the subsection. SteveT On Tuesday 18 January 2005 08:40 pm, Jane McKean wrote: > Hi there: > > I'm running LyX 1.3.5 on Fedora Core 3 (thank you for your help with the > move from Red Hat 9 to FC3; it's working great). > > I'm creating and expanding our compiler and debugger documentation set > using LyX. A request has been made to add a second index to the User > Guide consisting of all of the compiler flags (there are hundreds). The > users would like to have all of the options listed in one place in the > docs. > > I have an existing index that I've created using the Index entry option > (Insert > Index entry). How would I enter or tag the compiler options to > create a second "index"? (I'm not sure what you would call it, but it > would be two column, sorted alphabetically and linked back to the page > on which the term occurred) > > Has anyone created something like this using LyX/LaTeX? I searched the > archives and Herbert's Tips and Tricks, but because I don't know exactly > what you'd call it, I couldn't find what I was looking for. > > Thanks in advance for your help with this. > > Jane --- End Message ---
Changing PDF version generated
Hi: I'm running LyX 1.3.4 on Linux Red Hat 9 and generating our documentation set using the View PDF (pdflatex) option from the menu. (I use the View PDF option when I'm generating review copies with change bars.) The final docs include separate PDF covers. The final PDFs are PDF version 1.5. Some of our users use xpdf to view the docs and xpdf supports version 1.4 not version 1.5. The PDFs look very bad when viewed with xpdf. I need to change PDF generation process to produce PDF version 1.4. How would I go about doing this? What do I need to change? Many thanks in advance! --jane -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED] Phone: 408-746-9100 x227 Fax: 408-746-9150
Changing PDF version generated
Hi: I'm running LyX 1.3.4 on Linux Red Hat 9 and generating our documentation set using the View PDF (pdflatex) option from the menu. (I use the View PDF option when I'm generating review copies with change bars.) The final docs include separate PDF covers. The final PDFs are PDF version 1.5. Some of our users use xpdf to view the docs and xpdf supports version 1.4 not version 1.5. The PDFs look very bad when viewed with xpdf. I need to change PDF generation process to produce PDF version 1.4. How would I go about doing this? What do I need to change? Many thanks in advance! --jane -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED] Phone: 408-746-9100 x227 Fax: 408-746-9150
Changing PDF version generated
Hi: I'm running LyX 1.3.4 on Linux Red Hat 9 and generating our documentation set using the View > PDF (pdflatex) option from the menu. (I use the View > PDF option when I'm generating review copies with change bars.) The final docs include separate PDF covers. The final PDFs are PDF version 1.5. Some of our users use xpdf to view the docs and xpdf supports version 1.4 not version 1.5. The PDFs look very bad when viewed with xpdf. I need to change PDF generation process to produce PDF version 1.4. How would I go about doing this? What do I need to change? Many thanks in advance! --jane -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED] Phone: 408-746-9100 x227 Fax: 408-746-9150
Re: Change bar patch for 1.3.5
OK. I think I've posted the two files here: http://wiki.lyx.org/pmwiki.php/Tips/ChangeTrackingLyx1-3-2 Hope this helps. --jane (Someone might want to check my work. :-) On Tue, 2004-11-16 at 00:06, Jean-Marc Lasgouttes wrote: John == John Levon [EMAIL PROTECTED] writes: John A pity that there's nowhere we can put these patches and John officially release them... Huh? We have a web site and a ftp site, after all... JMarc
Re: Change bar patch for 1.3.5
OK. I think I've posted the two files here: http://wiki.lyx.org/pmwiki.php/Tips/ChangeTrackingLyx1-3-2 Hope this helps. --jane (Someone might want to check my work. :-) On Tue, 2004-11-16 at 00:06, Jean-Marc Lasgouttes wrote: John == John Levon [EMAIL PROTECTED] writes: John A pity that there's nowhere we can put these patches and John officially release them... Huh? We have a web site and a ftp site, after all... JMarc
Re: Change bar patch for 1.3.5
OK. I think I've posted the two files here: http://wiki.lyx.org/pmwiki.php/Tips/ChangeTrackingLyx1-3-2 Hope this helps. --jane (Someone might want to check my work. :-) On Tue, 2004-11-16 at 00:06, Jean-Marc Lasgouttes wrote: > > "John" == John Levon <[EMAIL PROTECTED]> writes: > > John> A pity that there's nowhere we can put these patches and > John> officially release them... > > Huh? We have a web site and a ftp site, after all... > > JMarc
Change bar patch for 1.3.5
Greetigs: Mea culpa for the delay in posting this patch back to the group. It is several months overdue! We've just put a beta version of our 64-compiler with OpenMP for Fortran into the testing queue, and finished a week of demos at Supercomputing in Pittsburgh. All of the compiler and debugger docs are written in LyX! So now, finally, I have the change bar patches for LyX 1.3.5. I've been using them with great success with 1.3.4, and (with the help of an engineer here) I have them ported into the 1.3.5 release of LyX. This is the patch that Johnathan Burchill adapted from John Levon's change tracking code. 99.9% of the work was done by the original author(s). We incorporated the change bars into the 1.3.4 and then the 1.3.5 version and made a couple of small bug fixes. The patches were too large to this email. I have a zip file of the patch plus a plain text file of the diffs. Can someone point me to the appropriate Wiki page to post them there? Or tell me how and were to post them? Many thanks again to this group for all its help. I love using LyX and you all make it possible. Thanks! --jane -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED]
Change bar patch for 1.3.5
Greetigs: Mea culpa for the delay in posting this patch back to the group. It is several months overdue! We've just put a beta version of our 64-compiler with OpenMP for Fortran into the testing queue, and finished a week of demos at Supercomputing in Pittsburgh. All of the compiler and debugger docs are written in LyX! So now, finally, I have the change bar patches for LyX 1.3.5. I've been using them with great success with 1.3.4, and (with the help of an engineer here) I have them ported into the 1.3.5 release of LyX. This is the patch that Johnathan Burchill adapted from John Levon's change tracking code. 99.9% of the work was done by the original author(s). We incorporated the change bars into the 1.3.4 and then the 1.3.5 version and made a couple of small bug fixes. The patches were too large to this email. I have a zip file of the patch plus a plain text file of the diffs. Can someone point me to the appropriate Wiki page to post them there? Or tell me how and were to post them? Many thanks again to this group for all its help. I love using LyX and you all make it possible. Thanks! --jane -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED]
Change bar patch for 1.3.5
Greetigs: Mea culpa for the delay in posting this patch back to the group. It is several months overdue! We've just put a beta version of our 64-compiler with OpenMP for Fortran into the testing queue, and finished a week of demos at Supercomputing in Pittsburgh. All of the compiler and debugger docs are written in LyX! So now, finally, I have the change bar patches for LyX 1.3.5. I've been using them with great success with 1.3.4, and (with the help of an engineer here) I have them ported into the 1.3.5 release of LyX. This is the patch that Johnathan Burchill adapted from John Levon's change tracking code. 99.9% of the work was done by the original author(s). We incorporated the change bars into the 1.3.4 and then the 1.3.5 version and made a couple of small bug fixes. The patches were too large to this email. I have a zip file of the patch plus a plain text file of the diffs. Can someone point me to the appropriate Wiki page to post them there? Or tell me how and were to post them? Many thanks again to this group for all its help. I love using LyX and you all make it possible. Thanks! --jane -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED]
Re: last page odd
Jean-Pierre:
Thank you for this suggestion. I want to be sure I understand what you
are saying here.
I would put this in the preamble:
% redfinition of \cleardoublepage w an empty page
\cleardoublepage
\hbox{}
\thispagestyle{empty}
\newpage
%
\AtEndDocument{\cleardoublepage}
Then would I need to insert anything into the text to be sure the empty page is
before the ERT for including the PDF that is the back cover?
Many thanks,
--jane
--
Jane McKean
Technical Documentation
PathScale, Inc.
Re: last page odd
Jean-Pierre:
Thank you for this suggestion. I want to be sure I understand what you
are saying here.
I would put this in the preamble:
% redfinition of \cleardoublepage w an empty page
\cleardoublepage
\hbox{}
\thispagestyle{empty}
\newpage
%
\AtEndDocument{\cleardoublepage}
Then would I need to insert anything into the text to be sure the empty page is
before the ERT for including the PDF that is the back cover?
Many thanks,
--jane
--
Jane McKean
Technical Documentation
PathScale, Inc.
Re: last page odd
Jean-Pierre:
Thank you for this suggestion. I want to be sure I understand what you
are saying here.
I would put this in the preamble:
% redfinition of \cleardoublepage w an empty page
\cleardoublepage
\hbox{}
\thispagestyle{empty}
\newpage
%
\AtEndDocument{\cleardoublepage}
Then would I need to insert anything into the text to be sure the empty page is
before the ERT for including the PDF that is the back cover?
Many thanks,
--jane
--
Jane McKean
Technical Documentation
PathScale, Inc.
Re: last page odd Fedora Core 1 (follow-up)
To answer some of my own questions:
Two questions -
(1) I want to have LyX generate PDFs where the last page is odd (e.g.
the back cover in a two-sided document). I'm using \usepackage{pdfpages}
to include PDFs for the front and back covers for our compiler manuals,
and the content is set up as two-sided. Do I need to add some ERT to
make this happen?
This is what I did: (I'm using the book layout)
I added (in ERT)
\newpage
\thispagestyle{empty}
then in regular type, a protected space (C-space)
then in ERT:
\clear page
This gave me a blank, empty page, so that I can have my PDF back cover end up
on an even page (think about how it would print out, for this to make sense).
More elegant solutions will be gratefully accepted.
(2) I want to keep up with our engineering team and move from RedHat 9
to RedHat Fedora Core 2. Are any of you using that? And what packages
will I need to install in addition to the LyX 1.3.4?
I have gotten one of the engineers to re-build the RPMs for Fedora Core 1.
I'll be testing this tomorrow, but I don't expect any snags. Will keep you
posted. (Thanks Jose for pointing out it's not Red Hat Fedora Core 1. Good
catch.)
* I do still have the patched fixes for the change bars for 1.3.4. I'd
like to post back to the community. Can someone give me a pointer as to
where those should go?
I'm promised the patched from previously mentioned engineer in the next day, two
at most. I apologize for the delay, but we've been busy putting released out.
Soon. Really. This week. And thanks for the pointer Angus.
--jane
--
Jane McKean
Technical Documentation
PathScale, Inc.
Re: last page odd Fedora Core 1 (follow-up)
To answer some of my own questions:
Two questions -
(1) I want to have LyX generate PDFs where the last page is odd (e.g.
the back cover in a two-sided document). I'm using \usepackage{pdfpages}
to include PDFs for the front and back covers for our compiler manuals,
and the content is set up as two-sided. Do I need to add some ERT to
make this happen?
This is what I did: (I'm using the book layout)
I added (in ERT)
\newpage
\thispagestyle{empty}
then in regular type, a protected space (C-space)
then in ERT:
\clear page
This gave me a blank, empty page, so that I can have my PDF back cover end up
on an even page (think about how it would print out, for this to make sense).
More elegant solutions will be gratefully accepted.
(2) I want to keep up with our engineering team and move from RedHat 9
to RedHat Fedora Core 2. Are any of you using that? And what packages
will I need to install in addition to the LyX 1.3.4?
I have gotten one of the engineers to re-build the RPMs for Fedora Core 1.
I'll be testing this tomorrow, but I don't expect any snags. Will keep you
posted. (Thanks Jose for pointing out it's not Red Hat Fedora Core 1. Good
catch.)
* I do still have the patched fixes for the change bars for 1.3.4. I'd
like to post back to the community. Can someone give me a pointer as to
where those should go?
I'm promised the patched from previously mentioned engineer in the next day, two
at most. I apologize for the delay, but we've been busy putting released out.
Soon. Really. This week. And thanks for the pointer Angus.
--jane
--
Jane McKean
Technical Documentation
PathScale, Inc.
Re: last page odd & Fedora Core 1 (follow-up)
To answer some of my own questions:
> Two questions -
>
> (1) I want to have LyX generate PDFs where the last page is odd (e.g.
> the back cover in a two-sided document). I'm using \usepackage{pdfpages}
> to include PDFs for the front and back covers for our compiler manuals,
> and the content is set up as two-sided. Do I need to add some ERT to
> make this happen?
This is what I did: (I'm using the book layout)
I added (in ERT)
\newpage
\thispagestyle{empty}
then in regular type, a protected space (C-space)
then in ERT:
\clear page
This gave me a blank, empty page, so that I can have my PDF back cover end up
on an even page (think about how it would print out, for this to make sense).
More elegant solutions will be gratefully accepted.
> (2) I want to keep up with our engineering team and move from RedHat 9
> to RedHat Fedora Core 2. Are any of you using that? And what packages
> will I need to install in addition to the LyX 1.3.4?
I have gotten one of the engineers to re-build the RPMs for Fedora Core 1.
I'll be testing this tomorrow, but I don't expect any snags. Will keep you
posted. (Thanks Jose for pointing out it's not Red Hat Fedora Core 1. Good
catch.)
>
> * I do still have the patched fixes for the change bars for 1.3.4. I'd
> like to post back to the community. Can someone give me a pointer as to
> where those should go?
I'm promised the patched from previously mentioned engineer in the next day, two
at most. I apologize for the delay, but we've been busy putting released out.
Soon. Really. This week. And thanks for the pointer Angus.
--jane
--
Jane McKean
Technical Documentation
PathScale, Inc.
last page odd Fedora Core 1
Hi again:
My setup -
Linux RedHat 9, LyX 1.3.4 (with change bar patch - yay!)*
Using book document class
Two questions -
(1) I want to have LyX generate PDFs where the last page is odd (e.g.
the back cover in a two-sided document). I'm using \usepackage{pdfpages}
to include PDFs for the front and back covers for our compiler manuals,
and the content is set up as two-sided. Do I need to add some ERT to
make this happen?
(2) I want to keep up with our engineering team and move from RedHat 9
to RedHat Fedora Core 2. Are any of you using that? And what packages
will I need to install in addition to the LyX 1.3.4?
* I do still have the patched fixes for the change bars for 1.3.4. I'd
like to post back to the community. Can someone give me a pointer as to
where those should go?
Many thanks for your patience and help with these questions. And thanks
for a tool that I really enjoy using.
(I'm holding off the Framemaker advocates here for the time being.)
--jane
--
Jane McKean
Technical Documentation
PathScale, Inc.
[EMAIL PROTECTED]
last page odd Fedora Core 1
Hi again:
My setup -
Linux RedHat 9, LyX 1.3.4 (with change bar patch - yay!)*
Using book document class
Two questions -
(1) I want to have LyX generate PDFs where the last page is odd (e.g.
the back cover in a two-sided document). I'm using \usepackage{pdfpages}
to include PDFs for the front and back covers for our compiler manuals,
and the content is set up as two-sided. Do I need to add some ERT to
make this happen?
(2) I want to keep up with our engineering team and move from RedHat 9
to RedHat Fedora Core 2. Are any of you using that? And what packages
will I need to install in addition to the LyX 1.3.4?
* I do still have the patched fixes for the change bars for 1.3.4. I'd
like to post back to the community. Can someone give me a pointer as to
where those should go?
Many thanks for your patience and help with these questions. And thanks
for a tool that I really enjoy using.
(I'm holding off the Framemaker advocates here for the time being.)
--jane
--
Jane McKean
Technical Documentation
PathScale, Inc.
[EMAIL PROTECTED]
last page odd & Fedora Core 1
Hi again:
My setup -
Linux RedHat 9, LyX 1.3.4 (with change bar patch - yay!)*
Using book document class
Two questions -
(1) I want to have LyX generate PDFs where the last page is odd (e.g.
the back cover in a two-sided document). I'm using \usepackage{pdfpages}
to include PDFs for the front and back covers for our compiler manuals,
and the content is set up as two-sided. Do I need to add some ERT to
make this happen?
(2) I want to keep up with our engineering team and move from RedHat 9
to RedHat Fedora Core 2. Are any of you using that? And what packages
will I need to install in addition to the LyX 1.3.4?
* I do still have the patched fixes for the change bars for 1.3.4. I'd
like to post back to the community. Can someone give me a pointer as to
where those should go?
Many thanks for your patience and help with these questions. And thanks
for a tool that I really enjoy using.
(I'm holding off the Framemaker advocates here for the time being.)
--jane
--
Jane McKean
Technical Documentation
PathScale, Inc.
[EMAIL PROTECTED]
help in controlling heads
My system: Linux RedHat 9, LyX 1.3.4 (with change bar patch - yay!)* Using book document class with standard defaults Hi: I'm back with more newbie questions. (Many thanks for the help with change bars and manual covers, especially to Guy Hindell for sharing what he's done with his documentation set.) This list is a lifesaver. Thanks in advance. I want to accomplish the following in my technical manuals (under deadline of course): - make the running heads upper and lowercase (not all uppercase) and sans serif font. [remove \MakeUppercase from the book.cls file?] - make the chapter heads sans serif font (leave the body font as is) [I'm not sure how or where to do this.] - extend the length of the page (I'm outputting to 8.5 x 11 paper) so I want to make the bottom margin smaller. [How do I do this for the whole file? ] I've modified the book.cls file in my local .lyx directory (deleting \MakeUppercase) and done an Edit--Reconfigure. The changes are not showing up. Are these the files I need to change? Do I want to move them? I haven't figured out where to set the chapter font yet. Is it in my local book.cls file? I know these are fairly simple fixes, but I don't have time to delve into the files at this point, so I'm asking you for help. When I have time, I want to carefully modify the book.layout and book.cls files.(Thank you Guy for your excellent example files.) Because of this deadline, I'm looking for the quick work around to solve these problems. Ideas? * P.S. As soon as this release is out (1-2 weeks), I'll post the RPMs for the LyX 1.3.4 patch for RedHat 9. It seems to be working great! Many thanks, --jane -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED] Phone: 408-746-9100 x227 Fax: 408-746-9150
help in controlling heads
My system: Linux RedHat 9, LyX 1.3.4 (with change bar patch - yay!)* Using book document class with standard defaults Hi: I'm back with more newbie questions. (Many thanks for the help with change bars and manual covers, especially to Guy Hindell for sharing what he's done with his documentation set.) This list is a lifesaver. Thanks in advance. I want to accomplish the following in my technical manuals (under deadline of course): - make the running heads upper and lowercase (not all uppercase) and sans serif font. [remove \MakeUppercase from the book.cls file?] - make the chapter heads sans serif font (leave the body font as is) [I'm not sure how or where to do this.] - extend the length of the page (I'm outputting to 8.5 x 11 paper) so I want to make the bottom margin smaller. [How do I do this for the whole file? ] I've modified the book.cls file in my local .lyx directory (deleting \MakeUppercase) and done an Edit--Reconfigure. The changes are not showing up. Are these the files I need to change? Do I want to move them? I haven't figured out where to set the chapter font yet. Is it in my local book.cls file? I know these are fairly simple fixes, but I don't have time to delve into the files at this point, so I'm asking you for help. When I have time, I want to carefully modify the book.layout and book.cls files.(Thank you Guy for your excellent example files.) Because of this deadline, I'm looking for the quick work around to solve these problems. Ideas? * P.S. As soon as this release is out (1-2 weeks), I'll post the RPMs for the LyX 1.3.4 patch for RedHat 9. It seems to be working great! Many thanks, --jane -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED] Phone: 408-746-9100 x227 Fax: 408-746-9150
help in controlling heads
My system: Linux RedHat 9, LyX 1.3.4 (with change bar patch - yay!)* Using book document class with standard defaults Hi: I'm back with more newbie questions. (Many thanks for the help with change bars and manual covers, especially to Guy Hindell for sharing what he's done with his documentation set.) This list is a lifesaver. Thanks in advance. I want to accomplish the following in my technical manuals (under deadline of course): - make the running heads upper and lowercase (not all uppercase) and sans serif font. [remove \MakeUppercase from the book.cls file?] - make the chapter heads sans serif font (leave the body font as is) [I'm not sure how or where to do this.] - extend the length of the page (I'm outputting to 8.5 x 11 paper) so I want to make the bottom margin smaller. [How do I do this for the whole file? ] I've modified the book.cls file in my local .lyx directory (deleting \MakeUppercase) and done an Edit-->Reconfigure. The changes are not showing up. Are these the files I need to change? Do I want to move them? I haven't figured out where to set the chapter font yet. Is it in my local book.cls file? I know these are fairly simple fixes, but I don't have time to delve into the files at this point, so I'm asking you for help. When I have time, I want to carefully modify the book.layout and book.cls files.(Thank you Guy for your excellent example files.) Because of this deadline, I'm looking for the quick work around to solve these problems. Ideas? * P.S. As soon as this release is out (1-2 weeks), I'll post the RPMs for the LyX 1.3.4 patch for RedHat 9. It seems to be working great! Many thanks, --jane -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED] Phone: 408-746-9100 x227 Fax: 408-746-9150
changebar patch with 1.3.3
Nirmal: I checked with the developer here who did the patch for me (our build person) and he said he ended up only running autogen.sh to get all the makefiles happy. Does this make sense? I can try and get more information if you like. So far I'm running fine with the patch. Once my confidence returns, I'll have the patch put into 1.3.4. thanks, --jane On Tue, 2004-02-24 at 22:17, Nirmal Govind wrote: Hi Jane, Glad to see that you got the patch to work.. First off, many thanks for all your help with changebars, especially Nirmal Govind and Johnathan Burchill. With your help (and help on this Actually, John Levon and Johnathan deserve the thanks... John is the LyX developer who wrote the change-tracking code. So thank you (again) John! :-) Qn: Did you have to modify the patch in any way or did it compile fine with the 1.3.3 code? Thanks, nirmal -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED] Phone: 408-746-9100 x227 Fax: 408-746-9150
changebar patch with 1.3.3
Nirmal: I checked with the developer here who did the patch for me (our build person) and he said he ended up only running autogen.sh to get all the makefiles happy. Does this make sense? I can try and get more information if you like. So far I'm running fine with the patch. Once my confidence returns, I'll have the patch put into 1.3.4. thanks, --jane On Tue, 2004-02-24 at 22:17, Nirmal Govind wrote: Hi Jane, Glad to see that you got the patch to work.. First off, many thanks for all your help with changebars, especially Nirmal Govind and Johnathan Burchill. With your help (and help on this Actually, John Levon and Johnathan deserve the thanks... John is the LyX developer who wrote the change-tracking code. So thank you (again) John! :-) Qn: Did you have to modify the patch in any way or did it compile fine with the 1.3.3 code? Thanks, nirmal -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED] Phone: 408-746-9100 x227 Fax: 408-746-9150
changebar patch with 1.3.3
Nirmal: I checked with the developer here who did the patch for me (our build person) and he said he ended up only running autogen.sh to get all the makefiles happy. Does this make sense? I can try and get more information if you like. So far I'm running fine with the patch. Once my confidence returns, I'll have the patch put into 1.3.4. thanks, --jane On Tue, 2004-02-24 at 22:17, Nirmal Govind wrote: > Hi Jane, > > Glad to see that you got the patch to work.. > > > First off, many thanks for all your help with changebars, especially > > Nirmal Govind and Johnathan Burchill. With your help (and help on > this > > Actually, John Levon and Johnathan deserve the thanks... John is the > LyX developer who wrote the change-tracking code. So thank you > (again) John! :-) > > Qn: Did you have to modify the patch in any way or did it compile > fine with the 1.3.3 code? > > Thanks, > nirmal -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED] Phone: 408-746-9100 x227 Fax: 408-746-9150
manual covers?
Details: Current setup Red Hat Linux release 9 (Shrike) LyX 1.3.3 (with changbar patch - yay!) Hi again: First off, many thanks for all your help with changebars, especially Nirmal Govind and Johnathan Burchill. With your help (and help on this end), I now have a version of 1.3.3 with the changebars patched in that I'm experimenting with. If that goes well (and I feel brave in the midst of a software release) I'll have the engineers put the patch in the new 1.3.4 release. Only so much change at once! Another new user question: I'm using the standard book document class for our suite of technical manuals (compilers). I want to create covers with our logo (in color if possible) and some other graphics. - Is the book class the best class to use for technical manuals? (I hunted briefly around CTAN and nothing jumped out at me.) Has someone done technical manuals with a particular class that worked well? - What would be the easiest way to create a custom cover for a manual? This is a big issue, as management wants a look and feel to the suite. Any hints or ideas? After this release passes, I plan to write up what I've discovered and post it for others. Would http://wiki.lyx.org be the best spot? Again, many thanks in advance for your help. --jane -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED]
manual covers?
Details: Current setup Red Hat Linux release 9 (Shrike) LyX 1.3.3 (with changbar patch - yay!) Hi again: First off, many thanks for all your help with changebars, especially Nirmal Govind and Johnathan Burchill. With your help (and help on this end), I now have a version of 1.3.3 with the changebars patched in that I'm experimenting with. If that goes well (and I feel brave in the midst of a software release) I'll have the engineers put the patch in the new 1.3.4 release. Only so much change at once! Another new user question: I'm using the standard book document class for our suite of technical manuals (compilers). I want to create covers with our logo (in color if possible) and some other graphics. - Is the book class the best class to use for technical manuals? (I hunted briefly around CTAN and nothing jumped out at me.) Has someone done technical manuals with a particular class that worked well? - What would be the easiest way to create a custom cover for a manual? This is a big issue, as management wants a look and feel to the suite. Any hints or ideas? After this release passes, I plan to write up what I've discovered and post it for others. Would http://wiki.lyx.org be the best spot? Again, many thanks in advance for your help. --jane -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED]
manual covers?
Details: Current setup Red Hat Linux release 9 (Shrike) LyX 1.3.3 (with changbar patch - yay!) Hi again: First off, many thanks for all your help with changebars, especially Nirmal Govind and Johnathan Burchill. With your help (and help on this end), I now have a version of 1.3.3 with the changebars patched in that I'm experimenting with. If that goes well (and I feel brave in the midst of a software release) I'll have the engineers put the patch in the new 1.3.4 release. Only so much change at once! Another new user question: I'm using the standard book document class for our suite of technical manuals (compilers). I want to create covers with our logo (in color if possible) and some other graphics. - Is the book class the best class to use for technical manuals? (I hunted briefly around CTAN and nothing jumped out at me.) Has someone done technical manuals with a particular class that worked well? - What would be the easiest way to create a custom cover for a manual? This is a big issue, as management wants a "look and feel" to the suite. Any hints or ideas? After this release passes, I plan to write up what I've discovered and post it for others. Would http://wiki.lyx.org be the best spot? Again, many thanks in advance for your help. --jane -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED]
Change bars
Details: Current setup Red Hat Linux release 9 (Shrike) LyX 1.3.3 Hi: I hope someone on this list can help (or at least clarify what's going on). I'm a fairly new user of LyX (about 6 months now); one-person tech writing department at a startup. I've won the battle to use LyX for our documentation, until we hit this snag. Management wants changebars in the PDFs of the docs (we're in the midst of beta release). I've gotten the 1.4 development version of LyX, which has this feature (with help from our engineers) and installed it, but I get this error: The document uses a missing TeX class article. LyX will not be able to produce output. [OK] I can see the file on screen, but can't output it at all. The earlier version (1.3.3) works just fine (except that it doesn't have change bars). Any ideas? Workarounds? Thanks in advance for any help or suggestions you might have. I really love LyX and want to continue using it. -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED]
Change bars
Details: Current setup Red Hat Linux release 9 (Shrike) LyX 1.3.3 Hi: I hope someone on this list can help (or at least clarify what's going on). I'm a fairly new user of LyX (about 6 months now); one-person tech writing department at a startup. I've won the battle to use LyX for our documentation, until we hit this snag. Management wants changebars in the PDFs of the docs (we're in the midst of beta release). I've gotten the 1.4 development version of LyX, which has this feature (with help from our engineers) and installed it, but I get this error: The document uses a missing TeX class article. LyX will not be able to produce output. [OK] I can see the file on screen, but can't output it at all. The earlier version (1.3.3) works just fine (except that it doesn't have change bars). Any ideas? Workarounds? Thanks in advance for any help or suggestions you might have. I really love LyX and want to continue using it. -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED]
Change bars
Details: Current setup Red Hat Linux release 9 (Shrike) LyX 1.3.3 Hi: I hope someone on this list can help (or at least clarify what's going on). I'm a fairly new user of LyX (about 6 months now); one-person tech writing department at a startup. I've won the battle to use LyX for our documentation, until we hit this snag. Management wants changebars in the PDFs of the docs (we're in the midst of beta release). I've gotten the 1.4 development version of LyX, which has this feature (with help from our engineers) and installed it, but I get this error: "The document uses a missing TeX class "article". LyX will not be able to produce output. [OK] I can see the file on screen, but can't output it at all. The earlier version (1.3.3) works just fine (except that it doesn't have change bars). Any ideas? Workarounds? Thanks in advance for any help or suggestions you might have. I really love LyX and want to continue using it. -- Jane McKean Technical Documentation PathScale, Inc. [EMAIL PROTECTED]
