Re: Making first paragraphs not indented in exported HTML
Dr Eberhard W Lisse via lyx-users said on Tue, 12 Apr 2022 14:22:21 +0200 >Because I am right and you are unnecessarily annoying? A simple "Thank you" would have sufficed. SteveT Steve Litt March 2022 featured book: Making Mental Models: Advanced Edition http://www.troubleshooters.com/mmm -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Making first paragraphs not indented in exported HTML
Dr Eberhard Lisse via lyx-users said on Mon, 11 Apr 2022 18:22:54 +0200 >If you think other people have the time you don't maybe you >also not waste their time by posting this. Now how did I know that *you'd* be the guy to say this. SteveT Steve Litt March 2022 featured book: Making Mental Models: Advanced Edition http://www.troubleshooters.com/mmm -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Making first paragraphs not indented in exported HTML
Daniel via lyx-users said on Mon, 11 Apr 2022 08:13:43 +0200
>On 2022-04-11 03:44, Steve Litt via lyx-users wrote:
>> Hi all,
>>
>> In the past, some exporters have implemented the custom of not
>> indenting the first of several successive paragraphs by using a
>> different class of paragraph for the first of a series of paragraphs.
>> This way of doing things makes more work for the person writing the
>> export, and more work for the person converting the export to
>> acceptable ePub, because those special classes will need to be backed
>> out or otherwise specially handled.
>>
>> Not indenting the first of a series of paragraphs is easily
>> accomplished by the following two lines of CSS:
>>
>> p::first-letter{margin-left: 3em;}
>> :not(p) + p::first-letter{margin-left:0.0001em;}
>>
>> Let CSS decide which is the first of several consecutive paragraphs,
>> and let CSS define what to do with that paragraph. Make it easy on
>> everybody.
>>
>> I took an hour to figure this out. Could somebody please take 3
>> minutes to forward it to the developer's list and also the person
>> who is writing the HTML export?
>>
>> Thanks,
>>
>> SteveT
>>
>> Steve Litt
>> March 2022 featured book: Making Mental Models: Advanced Edition
>> http://www.troubleshooters.com/mmm
>
>I'd suggest that you file a bug/enhancement report at
>https://www.lyx.org/trac/wiki/BugTrackerHome (including the LyX
>version you are using and exact steps to reproduce the problem).
Like I said, I spent an hour getting that code just right. I did the
hard part, I did my part. In the time you took to respond to me, you
could have forwarded my email.
I don't have time to learn the quirks of every project's bugtracker,
type in information that's not relevant, and hope somebody looks at it.
At a lot of projects, the bugtracker is where requests go to die
(Bluefish, you listening?).
If I could change one thing about FOSS it would be to get rid of
bugtrackers and work directly with the user. That's what we did at
VimOutliner, and bugs got solved and requests got implemented very
quickly.
SteveT
Steve Litt
March 2022 featured book: Making Mental Models: Advanced Edition
http://www.troubleshooters.com/mmm
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Making first paragraphs not indented in exported HTML
Hi all,
In the past, some exporters have implemented the custom of not
indenting the first of several successive paragraphs by using a
different class of paragraph for the first of a series of paragraphs.
This way of doing things makes more work for the person writing the
export, and more work for the person converting the export to
acceptable ePub, because those special classes will need to be backed
out or otherwise specially handled.
Not indenting the first of a series of paragraphs is easily
accomplished by the following two lines of CSS:
p::first-letter{margin-left: 3em;}
:not(p) + p::first-letter{margin-left:0.0001em;}
Let CSS decide which is the first of several consecutive paragraphs,
and let CSS define what to do with that paragraph. Make it easy on
everybody.
I took an hour to figure this out. Could somebody please take 3 minutes
to forward it to the developer's list and also the person who is
writing the HTML export?
Thanks,
SteveT
Steve Litt
March 2022 featured book: Making Mental Models: Advanced Edition
http://www.troubleshooters.com/mmm
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Re: [Important] New behavior for spam handling on this list
Jean-Marc Lasgouttes via lyx-users said on Thu, 7 Apr 2022 12:23:13 +0200 >> And what's the supposed upside? So non-subscribers can post. Look at >> any netiquette guide and they'll roundly catcall the clowns who begin >> or end their message with "please CC me because I'm not on the >> list." > >The upside is to try to be more welcoming to new users. It is not like >we have too many users, do we? As in my answer above, I agree that we >shall reconsider if things become unpleasant. I'm on tons and tons of FOSS mailing lists. From my perspective, the LyX list is one of the most welcoming to users new and old, and has one of the most constructive attitudes of all mailing lists. In my opinion, this list is so welcoming that there's little remaining low hanging fruit remaining to make the list even more welcoming, so I still think enabling non-subscribers to post is unnecessary and has downsides. If we want to grow LyX usage and membership, and I'm not necessarily saying we should, I think the way to do it is to grow the world's impression of LyX beyond its perceived niche of scholarly thesis production. As long as we speak only of PDF output, LyX is spectacularly suitable for any consistent document beyond five a4 or letter pages. When used with its defaults, *IT'S JUST EASY*. With creative custom layouts, it can do almost anything. One of my fiction books, which jumps all around in time, has the current date of the plot printed in the header. Don't try this with Libreoffice. Somebody could make a list of all types of possible long documents. Legal documents. Books, articles. Specifications. Make a flowchart of which document class to start out with. Like every other free software project, LyX is underdocumented. The lowest hanging fruit you have is to make a single index for all the documents available under LyX' help menu. Every time I go there to look something up, I spend 25 minutes going from document to document looking for the subject. I'm sure I'm not alone. Armed with this index, the project could credibly claim to have some of the FOSS world's best documentation. Make the documentation good enough, and newbies will quickly become evangelists. But wait: There's more... I never learned to use LyX modules, and have always simply made complex and detailed local layout files. Others should not follow in my footsteps, because, from what I've heard, modules are a much easier way to add specific document capabilities than layout files. There should be a help=>modules, split into descriptions of how to use every project-curated module, and how to make your own. I can see value in a publicity campaign, beamed to the general populace rather than current LyX users, explaining what fingerpainting is, why it's bad, why styles-based authoring is good, what styles-based authoring looks like in general, and how easy it is to do in LyX. In this section I've merely scratched the surface of ways LyX could become an everyday tool for millions of people. Just doing a few of these things would go beyond making LyX welcoming --- they'd make LyX extremely attractive for the general population. SteveT Steve Litt March 2022 featured book: Making Mental Models: Advanced Edition http://www.troubleshooters.com/mmm -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: [Important] New behavior for spam handling on this list
Jean-Marc Lasgouttes via lyx-users said on Wed, 6 Apr 2022 16:01:16 +0200 >Dear all, > >Until now, the handling of the list was like: messages from >subscribers go through, other messages get discarded. > >There is actually a way to filter e-mails marked as spam, and I have >already changed all our other lists to take advantage of this >information. > >Today it is lyx-users' turn. The new behavior is: >* spams are automatically discarded; please notify the list if a >message of yours just disappears. It seems to work correctly on the >other lists that we have; >* members posts not qualified as spam go through as usual; >* remaining non-member posts are held for moderation. > >The big advantage is that now non-subscribers will be able to post >messages (with a low amount of manual moderation from my side). > >Comments welcome. I'd suggest you put it back the way it was. I'm on 30+ FOSS mailing lists, and can't police everything to see that it goes through. If some AI algorithm somewhere decides I'm spam because of my email provider or whatever, I'm just writing into the wind, wasting a lot of time. And what's the supposed upside? So non-subscribers can post. Look at any netiquette guide and they'll roundly catcall the clowns who begin or end their message with "please CC me because I'm not on the list." Let's not inconvenience valuable list members to accommodate those so lazy they can't take 5 minutes to join the mailing list. SteveT Steve Litt March 2022 featured book: Making Mental Models: Advanced Edition http://www.troubleshooters.com/mmm -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: EPUB converter
Steve Litt via lyx-users said on Fri, 25 Mar 2022 18:09:56 -0400
>And please make the output well-formed XML as well as HTML5. HTML5 can,
>but doesn't have to be, well formed XML. It's a couple orders of
>magnitude easier to deal with if the exported HTML has all opening tags
>accompanied by closing tags, and for tags that both open and close
>( for instance), be sure to put the trailing slash.
The following simple Python3 program checks to make sure the file that
is its argument is well-formed XML. It's also attached as an
attachment. By using this program on LyX' HTML exports, you can verify
that the HTML is also well formed XML.
==
#!/usr/bin/python3
# Copyright 2017 by Steve Litt
# Expat license: https://directory.fsf.org/wiki/License:Expat
import sys
import re
import xml.etree.ElementTree as ET
fname = sys.argv[1]
print('\nTesting for well formedness {} ...\n'.format(fname))
try:
tree = ET.parse(fname)
except ET.ParseError as err:
(line, col) = err.position
code = str(err.code)
errmsg = 'ERROR: {}'.format(str(err))
print(errmsg)
if re.search(' ', errmsg):
print('Replace all with to solve problem.')
print('\n')
sys.exit(1)
else:
print('Congrats, {} is well formed!'.format(fname))
print('')
==
SteveT
Steve Litt
March 2022 featured book: Making Mental Models: Advanced Edition
http://www.troubleshooters.com/mmm
#!/usr/bin/python3
# Copyright 2017 by Steve Litt
# Expat license: https://directory.fsf.org/wiki/License:Expat
import sys
import re
import xml.etree.ElementTree as ET
fname = sys.argv[1]
print('\nTesting for well formedness {} ...\n'.format(fname))
try:
tree = ET.parse(fname)
except ET.ParseError as err:
(line, col) = err.position
code = str(err.code)
errmsg = 'ERROR: {}'.format(str(err))
print(errmsg)
if re.search(' ', errmsg):
print('Replace all with to solve problem.')
print('\n')
sys.exit(1)
else:
print('Congrats, {} is well formed!'.format(fname))
print('')
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Re: EPUB converter
Pavel Sanda via lyx-users said on Fri, 25 Mar 2022 09:20:15 +0100 >That said, the unfortunate news is that speedy prototyping in external >python script is probably going to share the fate of other scripts of >this sort (elyxer being last but not the only one): cool and perhaps >better than the output we currently have, but in long-term >uncompatible and abandoned, because it does not internally share the >codebase with LyX itself. Or, the LyX project could fulfill their goal of making LyX' native format an XML dialect, and then any developer could convert a LyX doc to any other format quite easily. The trouble is, in the early 00's, the LyX project decided to make the LyX native format an XML dialect, which greatly increased the difficulty of parsing a LyX file, but did not carry through in making LyX files well formed XML. If they'd carried through with making it XML, converting it to anything else would be relatively simple. As of now, it's the worst of both worlds: Difficult parsing because of some XMLisms, but not parsable by an XML parser because it's not well formed XML. One more thing. In my opinion LyX' HTML export suffers not from technical deficiencies, but from deficiencies of specification. Please, don't do us the "favor" of adding appearances to the HTML. Instead, just pass the styles through as-is, and let people like Ken Kopelson and me handle conversion of style to appearance, which is done simply with CSS. When you pass appearances instead of styles into the HTML, you're doing extra work, and sabotaging us. And please make the output well-formed XML as well as HTML5. HTML5 can, but doesn't have to be, well formed XML. It's a couple orders of magnitude easier to deal with if the exported HTML has all opening tags accompanied by closing tags, and for tags that both open and close ( for instance), be sure to put the trailing slash. Also, please either give the output file an XML DTD/schema that defines HTML characters like , or else just output their numeric equivalents, eg. . Ken Kopelson, do you agree with this paragraph? If you want to go the extra mile in making things easier for people writing LyXHTML to ePub converters, a nice but by no means necessary favor you could do us is to output a CSS file listing all the styles in the document, and perhaps giving some best-guess appearances for each. Or else make them all big and red, so the self-published author can easily specify each later on. But please, please, PLEASE, do not throw in an all-possible-styles CSS file that bloats up our books and is extremely difficult to deal with. I'd rather personally write an XML parser that looks at the XHTML5 file and outputs the CSS. All previous attempts have considered the exported HTML to be the final file for reading. This is clearly false: It's an intermediate file, and as such, should be very easy to parse (do the slight extra work to make it well-formed XML), and pass ONLY styles into it, no appearances. And this thing where standard paragraph environment translated to two different , one for the first line and one for all the rest so that the first line isn't indented, please don't. This is easily done in CSS, and even if it weren't, we converter makers could easily write a converter program to change it to two different , AT THE VERY LAST PASS before outputting the file intended for the reader. And please, don't throw in all sorts of extraneous elements like previous attempts have done. If fifteen consecutive paragraphs are in the, let's say for example, "story" environment, just begin each paragraph of the output with instead of putting them all in a . I've seen past LyXHTML go several levels deep in unnecessary elements. Life shouldn't be that difficult. Once again, all past attempts at LyXHTML have unnecessarily bitten off way more than they could chew. Just pass us the styles, and we'll take care of the style to appearance translation, *at the right time*! SteveT Steve Litt March 2022 featured book: Making Mental Models: Advanced Edition http://www.troubleshooters.com/mmm -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: search in master
Wolfgang Engelmann via lyx-users said on Mon, 7 Mar 2022 19:16:09 +0100 >Am 07.03.22 um 19:11 schrieb Steve Litt via lyx-users: >> Wolfgang Engelmann via lyx-users said on Mon, 7 Mar 2022 18:46:39 >> +0100 >>> It seems that I can't search for items in child documents in the >>> master, but have to go to the various childs in the master and >>> repeat there the search. Or is there something I missed? >>> Wolfgang >> >> grep >> >> >> SteveT >do you mean I can use the grep in lyx?? How? >Wolfgang Not in LyX, from the command prompt. It will tell you which child file(s) has the target string. Then you load that child file into LyX. SteveT Steve Litt March 2022 featured book: Making Mental Models: Advanced Edition http://www.troubleshooters.com/mmm -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: search in master
Wolfgang Engelmann via lyx-users said on Mon, 7 Mar 2022 18:46:39 +0100 >It seems that I can't search for items in child documents in the >master, but have to go to the various childs in the master and repeat >there the search. Or is there something I missed? >Wolfgang grep SteveT Steve Litt March 2022 featured book: Making Mental Models: Advanced Edition http://www.troubleshooters.com/mmm -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: EPUB converter
Dr Eberhard Lisse via lyx-users said on Sun, 6 Mar 2022 21:24:57 +0200 >Steve, > >Since it such a schlepp, why don't you participate in the development >or support the developers? LyX is great software by a great project. Great projects can be very bad in certain respects, and that doesn't prevent them from being great projects. As you read my response to your question, please keep in mind that I'm very grateful to LyX for being the tool that created at least 8 of the books I currently offer. My responses merely point out how LyX could be much better in the area of exports. Here are, my answers are enumerated below. 1) The converter must be semantic. It must keep styles as styles til the very end, not prematurely convert to appearance. The LyX native format is hostile to that goal, and since 2007 the LyX devs have shown little interest in that goal. 2) File conversion software has no business being written in C++ plus Qt. Python, Lua, Ruby, Perl or *maybe* simple C are the right way to go, at least for version 1. If performance became a problem, and I doubt it would, it could be rewritten in C. Years ago I stopped using both C++ and Java because, in my opinion, they both suck. 3) Simplicity is an asset. Conceptually all that need be done is create Xhtml5 tags with the same names as the environments and insets. But that's not what I've seen from the LyX (X)HTML exports in the past decade. Simplicity is an asset: The conversion software should be separate and distinct from LyX, with a very thin interface. 3.1: Content in semantic Xhtml5 can be converted to anything. 4) If I had time to help the LyX devs, I'd have time to singlehandedly create a Markdown=>Xhtml=>ePub and Markdown=>Xhtml=>PlainTeX=>PDF software stack. The QOwnNotes software is already a great typing front end for Markdown, which is why I chose Markdown. With the Markdown based converter done, I could turn around and easily create an Asciidoc version. 5) I could have, offered to, and would have written the converter for the LyX project, if only they had followed through with their mid 00's plan of making LyX an XML dialect. They refused to do so. Bottom line, in my opinion, the LyX project is the wrong project to build the LyX to ePub (or to (X)HTML) converter. Alex Fernandez was right about that when he built eLyXer, and IMHO eLyXer was better than the native LyX converter at that time, but eLyXer was only half semantic. If the LyX project can export to some completely semantic XML, I'll be glad to join the team who does the conversion from there. >Never mind that LyX seems to predate the Kindle, this is a LaTeX issue >rather than a LyX one (which, after all, just a front end). Tragically, you've just uncovered the main problem. As long as LyX is considered a front end to *LaTeX*, there will never be a good, robust LyX=>ePub. Only when LyX is considered a front end to *everything* will semantic ePub, as well as conversions to formats we haven't yet dreamed of, be possible. >As written numerous times I am very keen on on the new DocBook format >but since I use LyX in production in my practice, I can't use two >different formats, and my staff can't cope with alpha software. If it's DocBook *xml* as opposed to sgml, and if the DocBook XML is merely a representation of the environments and insets of LyX, that's a perfect point of demarkation between LyX and (HTML | ePub | other). You'd probably use Pandoc for DocBook=>ePub, I'd probably write my own, but either way, it could work if DocBook *XML* and styles are kept as styles. SteveT Steve Litt March 2022 featured book: Making Mental Models: Advanced Edition http://www.troubleshooters.com/mmm -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: EPUB converter
Hi Ken,
I suggest you put it out. The LyX project has a 15 year history of
outputting pidgeon HTML incapable of building a *semantic* ePub,
claiming what they've done is good enough, and treating with hostility
my observations that they're prematurely converting style to appearance.
The LyX project is the wrong project to do LyX=>ePub; ePub isn't in
their DNA, and until I'm shown otherwise, I'm treating any LyX=>ePub
capabilities from the LyX project as vaporware.
Where can I download your converter with instructions?
Thanks,
SteveT
Ken Kopelson via lyx-users said on Sat, 5 Mar 2022 12:47:52 -0800
> Does anyone know how I can get in touch with the people who are
> working
>on the EPUB export in version 2.4? I want to gauge if it will be worth
>it for me to put my converter out. This will depend on:
>
>1) When 2.4 will be released
>2) How good the EPUB export will be
>
>Any help on this would be appreciated. Even telling who I can contact
>about this.
>
>Many thanks,
>*Ken Kopelson*
>(619) 733-3374
>
>
>On Thu, Mar 3, 2022 at 5:29 AM Dr Eberhard Lisse via lyx-users <
>lyx-users@lists.lyx.org> wrote:
>
>> Ken,
>>
>> where is the missing link :-)-O?
>>
>>
>> This is great news.
>>
>> I am actually waiting for 2.4 and DocBook to convert my 859
>> page "handbook" to EPUB so my staff and I can carry it around on our
>> Kindles (App on iPad actually).
>>
>> But, I would be very keen to see how your package works.
>>
>> My little handbook doesn't really need anything fancier than a few
>> images (JPG, PNG and PDF).
>>
>> I also use (in one (common) "include.tex") something like
>>
>> \usepackage{etoolbox}
>> \newbool{business}
>> \boolfalse{business}
>> \newbool{private}
>> \booltrue{private}
>>
>> but if that (see your below remark) were not to work I can address
>> that via a Makefile and different include (front matter) files as
>> you seem to be doing.
>>
>> Maybe you can look into that, because then you can have a single
>> include file by putting something like this into a Makefile
>>
>> bus:
>> @perl -i -p \
>> -e
>> 's/\\boolfalse\{business\}/\\booltrue\{business\}/g;' \
>> -e
>> 's/\\booltrue\{private\}/\\boolfalse\{private\}/g;' \ include.tex
>> @lyx -f -e pdf5 handbook.lyx
>>
>> priv:
>> @perl -i -p \
>> -e
>> 's/\\booltrue\{business\}/\\boolfalse\{business\}/g;' \
>> -e
>> 's/\\boolfalse\{private\}/\\booltrue\{private\}/g;' \ include.tex
>> @lyx -f -e pdf5 handbook.lyx
>>
>> and then use something like
>>
>> \ifbool{business}{}{\include{business.tex}}
>> \ifbool{private}{\include{private.tex}}{}
>>
>> as ERT.
>>
>> Looks complicated, is complicated, but once it works no further
>> touching required.
>>
>>
>>
>> In the meantime I have pulled
>>
>> http://www.editorium.com/ftp/LyXBookSampler.zip
>>
>> from
>>
>> https://wiki.lyx.org/Layouts/Layouts
>>
>> and will start some RTFM :-)-O
>>
>> greetings, el
>>
>>
>> On 03/03/2022 00:58, Ken Kopelson via lyx-users wrote:
>> > Hello LyX users,
>> >
>> > I am sending this email to let people know that I have produced a
>> > converter for LyX that produces an excellent quality EPUB/Kindle
>> > file.
>> [...]
>> > I love using LyX with the LyXBook theme (as it has the greatest
>> > number of paragraph formats), and I am able to set up a system of
>> > files, having different Front Matter versions.
>> [...]
>> > I know that the next version of LyX is supposed to produce EPUB,
>> [...]
>> > As one final problem, the LyXHTML export fails to include anything
>> > in the LaTeK code blocks,
>> --
>> To email me replace 'nospam' with 'el'
>>
>> --
>> lyx-users mailing list
>> lyx-users@lists.lyx.org
>> http://lists.lyx.org/mailman/listinfo/lyx-users
>>
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Help! How do I get the File-Edit-View....Help menu back
Kornel Benko via lyx-users said on Thu, 24 Feb 2022 18:03:27 +0100 >The next test would be to start lyx with different userdir > $ lyx -userdir ~/.newlyx I wish I'd known about -userdir 21 years ago when I started using LyX. Thanks for telling me now. SteveT Steve Litt March 2022 featured book: Making Mental Models: Advanced Edition http://www.troubleshooters.com/mmm -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Help! How do I get the File-Edit-View....Help menu back
Wolfgang Engelmann via lyx-users said on Thu, 24 Feb 2022 14:55:48 +0100 >did not help. >Shall I wait for further proposals or use Kornels proposal to remove >the confugure? >Wolfgang Move it, don't REmove it. You might need it later. SteveT Steve Litt March 2022 featured book: Making Mental Models: Advanced Edition http://www.troubleshooters.com/mmm -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Help! How do I get the File-Edit-View....Help menu back
Kornel Benko via lyx-users said on Thu, 24 Feb 2022 14:47:04 +0100 >Am Thu, 24 Feb 2022 14:43:25 +0100 >schrieb Wolfgang Engelmann via lyx-users : > >> Would like to add: >> >> I worked with this lyx before and it worked alright. >> >> Should I use the git-lyx for the lyx2.0.4dev version and compile >> again? >> >> Wolfgang > >No. But you could try to remove > ~/.config/LyX/lyx*.conf I'd suggest moving those files rather than RE-moving them, because they might be needed later for "exploit the differences" type troubleshooting, or just to restore the parts of the configuration that work. SteveT Steve Litt March 2022 featured book: Making Mental Models: Advanced Edition http://www.troubleshooters.com/mmm -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Inkscape Presentation at OCLUG 2/19/2022
Hi all, Many of you have various graphics and diagrams in your books, papers, magazines, etc. If you've ever wondered about using Inkscape to make them, I'm giving another Beginning and Intermediate Inkscape online (Jitsi) presentation at the monthly Orange County (California USA) LUG (OCLUG) meeting 2/19/2022 at 10am **Pacific Time** (California USA time). You can see details and URL at: http://troubleshooters.com/lugs/oclug/ Thanks, SteveT Steve Litt March 2022 featured book: Making Mental Models: Advanced Edition http://www.troubleshooters.com/mmm -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: question about "itemize"
Paul A. Rubin via lyx-users said on Sat, 5 Feb 2022 16:04:28 -0500 >On 2/5/22 15:57, Daniel via lyx-users wrote: >> On 2022-02-05 16:23, Daniel via lyx-users wrote: >>> On 2022-02-05 16:21, Daniel via lyx-users wrote: On 2022-02-05 07:25, Tom Goldring via lyx-users wrote: > Suppose I have an itemized list like > > paragraph 1 > > - paragraph 2 > > paragraph 3 > > where paragraph 2 is nested. If I enter this by choosing the > "itemize" environment, then typing [snip] Try setting paragraph 3 with the Standard layout and indent it. Hope I understood what you meant. >>> >>> By "indent it", I meant "increase the depth" (by pressing the tab >>> key, for example). >> >> Paul's answer makes me think that my answer wasn't fully clear. So, >> I'll attach an example document. Looks reasonable in LyX' work area >> too. >> >> Daniel >> >I grafted my answer onto Daniel's example (as paragraphs 4 through 6), >and the PDF output shows no differences that I can see between the two >approaches. > >Paul The OP's question was ambiguous because he showed no bullets at level 1. He's received an easy and correct answer from three different people, in a timely manner. The OP has not responded. This was the OP's one and only post to this list. At this point I think we can mark this issue as closed. SteveT Steve Litt Spring 2021 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: question about "itemize"
Tom Goldring via lyx-users said on Sat, 5 Feb 2022 01:25:33 -0500 >Suppose I have an itemized list like > > paragraph 1 > > - paragraph 2 > > paragraph 3 > >where paragraph 2 is nested. If I enter this by choosing the "itemize" >environment, then typing > >paragraph 1 paragraph 2 paragraph 3 > >LyX creates paragraph 3 as a new item. Is there a way to have >paragraph 3 not be a new item? Yes. In the LyX environment, press the Enter key twice, and you'll start a new paragraph. If for some reason that doesn't work, go to the Environment dropdown and chooose Standard. SteveT Steve Litt Spring 2021 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Inkscape Presentation at Phoenix LUG 1/13/2022
Hi all, Many of you have various graphics and diagrams in your books, papers, magazines, etc. If you've ever wondered about using Inkscape to make them, I'm giving an Beginning and Intermediate Inkscape online (Jitsi) presentation at the monthly Phoenix (Arizona USA) LUG (PLUG) meeting 1/13/2022 at 7pm **Mountain Time** (Phoenix, Denver, and Salt Lake City USA time). You can see details at http://troubleshooters.com/lugs/phoenixlug/ Thanks, SteveT Steve Litt Spring 2021 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: How would LyX perform?
Herbert Voss via lyx-users said on Fri, 31 Dec 2021 11:36:44 +0100 >Am 31.12.21 um 01:41 schrieb Steve Litt via lyx-users: >> Herbert Voss via lyx-users said on Thu, 30 Dec 2021 14:52:15 +0100 >> >>> Am 30.12.21 um 14:46 schrieb Steve Litt via lyx-users: >>>> Wolfgang Engelmann via lyx-users said on Mon, 27 Dec 2021 11:31:55 >>>> +0100 >>>>> This has shocked me >>>>> https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0115069 >>>>> >>>>> Would be interesting to see how LyX performs >>>> Plain TeX would be much better than LaTeX, as a native format, if >>>> it could handle fonts well. Does anyone know of a Plain TeX to >>>> LuaTeX or XeTeX converter? >>> What do you want to convert?? Every Plain TeX document runs with >>> LuaTeX or XeTeX, >>> but, of course, not vice versa! >> My thought is that I need to convert because I need to use the >> tex-gyre-schola font, and as far as I know, Plain TeX won't >> accommodate this font. So, as I understand it, my process would need >> to be: >> >> 1: Write in Plain TeX with whatever font is available >> >> 2: Convert Plain TeX to LuaTeX > > >You only have to load the font, tha's all ... > >\input luaotfload.sty >\font\rm="[texgyreschola-regular.otf]:+lnum;+dlig" >\font\bf="TeXGyre Schola/B:+lnum;+dlig" >\font\it="TeXGyre Schola/I:+lnum;+dlig" >\font\bfit="TeXGyre Schola/BI:+lnum;+dlig" at 15pt > >\rm >TeX Gyre Schola regular > >\bf TeX Gyre Schola bold > >\it TeX Gyre Schola italic > >\bfit TeX Gyre Schola bolditalic >\bye > > >Herbert Thanks Herbert! This opens a whole new world for me. I'll experiment with it next year. Happy New Years all! SteveT Steve Litt Spring 2021 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: How would LyX perform?
Herbert Voss via lyx-users said on Thu, 30 Dec 2021 14:52:15 +0100 >Am 30.12.21 um 14:46 schrieb Steve Litt via lyx-users: >> Wolfgang Engelmann via lyx-users said on Mon, 27 Dec 2021 11:31:55 >> +0100 >>> This has shocked me >>> https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0115069 >>> >>> Would be interesting to see how LyX performs >> >> Plain TeX would be much better than LaTeX, as a native format, if it >> could handle fonts well. Does anyone know of a Plain TeX to LuaTeX or >> XeTeX converter? > >What do you want to convert?? Every Plain TeX document runs with >LuaTeX or XeTeX, >but, of course, not vice versa! My thought is that I need to convert because I need to use the tex-gyre-schola font, and as far as I know, Plain TeX won't accommodate this font. So, as I understand it, my process would need to be: 1: Write in Plain TeX with whatever font is available 2: Convert Plain TeX to LuaTeX 3: Use AWK to replace the font with tex-gyre-schola 4: Compile to PDF The reason I need this is I could *easily* convert from (X)HTML5 to Plain TeX. If I can go the rest of the way I can make a nice PDF from XHTML5. But I have neither the programming skills nor the LaTeX knowledge to create LaTeX from XHTML5. Thanks, SteveT Steve Litt Spring 2021 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: How would LyX perform?
Wolfgang Engelmann via lyx-users said on Mon, 27 Dec 2021 11:31:55 +0100 >This has shocked me >https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0115069 > >Would be interesting to see how LyX performs My first two books were written in WordPerfect 5.1. The next one was written in MS Word. All the rest were written in LyX. I was happy with all of them. My worst nightmare would be authoring in raw LaTeX. By the time I remembered the necessary LaTeX tag, I would have forgotten the point I was trying to make in my writing. LaTeX is a *lousy* native format for a document. It's suitable only for fixed line PDF/paper. It's extremely difficult to convert to flowing text HTML or ePub, unless you want to (urk) use Pandoc, with all the implied compromises on appearance. In my opinion LaTeX should be only an intermediate component in the authoring stack, that component being for creating fixed-line PDF/paper. Plain TeX would be much better than LaTeX, as a native format, if it could handle fonts well. Does anyone know of a Plain TeX to LuaTeX or XeTeX converter? I'm working on an authoring tool whose native format is a Markdown superset, with complete support of arbitrary styles. It's pretty easy to go from that format to HTML or ePub, but to go from there to fixed-line PDF/paper without using (urk) Pandoc is a challenge. But not nearly as big of a challenge as going from LaTeX to semantic HTML. Getting back to LyX, one of my books, "Key to Everyday Excellence", could not have been written in WordPerfect or MSWord because the (fictional) plot is so date driven that the current plot date appears in the header. And although I used styles-based authoring in WordPerfect and MSWord, I like that LyX enforces styles-based authoring. LyX is quite a fast authoring environment --- the only way it could be faster is to get rid of mouse usage. In my opinion, for a document over 10K words, LyX beats the authoring speed and ease of MSWord. This discussion wouldn't be complete without including LibreOffice. LibreOffice is a style-losing piece of junk fit only for fingerpainting. Those who characterize LibreOffice as a substitute for MSWord either don't use styles-based authoring, or they're fooling themselves, or they know something I don't know. By the way, my new book, "Making Mental Models: Advanced Edition", just came out yesterday. It's made almost exclusively with LyX, Inkscape, and shellscripts. A big thank you goes out to the LyX team who made this possible. SteveT Steve Litt Spring 2021 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: LuaTeX vs XeTeX
Scott Kostyshak via lyx-users said on Wed, 22 Dec 2021 07:55:24 -0500 >On Wed, Dec 22, 2021 at 07:26:57AM -0500, Steve Litt via lyx-users >wrote: >> Scott Kostyshak via lyx-users said on Mon, 20 Dec 2021 20:55:18 -0500 >> >> >On Mon, Dec 20, 2021 at 03:49:33PM -0500, Steve Litt via lyx-users >> >wrote: >> > >> >> Because I >> >> personalize every book, I need to recompile for every order, so I >> >> might research using PDFTeX. Thanks for the tip. >> > >> >Does the personalization change every page or just a few? >> >> Almost every page. There's a command defined in the doc's preamble, >> and before compilation, the person's name is substituted for a token >> in the name. That command prints in the page footers on every >> mainmatter page that isn't the first page of a chapter. >> >> The footer says "Prepared exclusively for Scott Kostyshak", >> discretely, in a red/maroon bar. > >Thanks for those details. If the footer is in the same x,y location of >every page, it might be fast to use a program like pdftk to overlay a >"stamp" on each page, rather than recompiling. I might be able to do it that way, but if I could, somebody else could easily use the same technique to undo it. SteveT Steve Litt Spring 2021 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: LuaTeX vs XeTeX
Scott Kostyshak via lyx-users said on Mon, 20 Dec 2021 20:55:18 -0500 >On Mon, Dec 20, 2021 at 03:49:33PM -0500, Steve Litt via lyx-users >wrote: > >> Because I >> personalize every book, I need to recompile for every order, so I >> might research using PDFTeX. Thanks for the tip. > >Does the personalization change every page or just a few? Almost every page. There's a command defined in the doc's preamble, and before compilation, the person's name is substituted for a token in the name. That command prints in the page footers on every mainmatter page that isn't the first page of a chapter. The footer says "Prepared exclusively for Scott Kostyshak", discretely, in a red/maroon bar. SteveT Steve Litt Spring 2021 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Forest beyond basics
Herbert Voss via lyx-users said on Mon, 20 Dec 2021 09:30:54 +0100 >Am 19.12.21 um 22:24 schrieb Steve Litt via lyx-users: >> LyX and LaTeX were never intended to make drawings or diagrams. Not >> really. > >That is not true! From the beginning of LaTeX there was the picture >environment with, of course, limited capability. But it was good enough >for simple diagrams/graphics. ^^ And I'm pretty sure that just drawing it in Inkscape is a faster workflow than repeatedly changing a number, compiling, and looking at the result. I think the text based trial and error method would take an awful lot of time for the following diagram: http://troubleshooters.com/linux/presentations/golug_runit/images/runsv_supervision.svg SteveT Steve Litt Spring 2021 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: LuaTeX vs XeTeX
Dr Eberhard Lisse via lyx-users said on Mon, 20 Dec 2021 08:49:24 +0200 >PDFLaTeX is much faster that LuaLaTeX but to be hoest, nowadays the >day to day stuff is so fast anyway that that doesn't matter. I noticed that my new book, which is much shorter than most, took about triple the time, like about 20 seconds on a very fast machine, to compile that books with LaTeX, XeTeX, and PDFTeX took. Because I personalize every book, I need to recompile for every order, so I might research using PDFTeX. Thanks for the tip. SteveT Steve Litt Spring 2021 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Forest beyond basics
Maria Gouskova via lyx-users said on Sun, 19 Dec 2021 12:20:15 -0500 >Dear LyX users, > >(Actually, I suspect this is a question for Jürgen S., but on the off >chance that someone else knows the answer...) > >I need to produce a diagram with the structure shown here. It was >produced using the obsolete xyling package Hi Maria, LyX and LaTeX were never intended to make drawings or diagrams. Not really. Just take 20 minutes to make your drawing in Inkscape, then put it in your LyX document just like you'd put any old .png or more to the point .svg. LyX automatically recompiles your Inscape-produced .svg into a PDF suitable for LyX/LaTeX upon finding that the .svg has changed. You know what it's supposed to look like, so you can draw it yourself. For new work where you need a new "forest", whatever this "forest" thing is, find a forest making software that can export to .svg, and then you can either use that .svg, or modify it a little in Inkscape. SteveT Steve Litt Spring 2021 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
What does tools=>reconfigure actually do?
Hi all, Exactly what is the difference between performing Tools=>Reconfigure within the LyX IDE environment, and performing /usr/local/share/lyx/configure.py at the command prompt? The former makes LyX aware of new environments I've put in the layout file, the latter for some reason does not. Are there some arguments I need to add to the configure.py command line? Does it need to be done in a specific directory? Are there any environment variables that effect configure.py? configure.py --help didn't appear to tell me anything useful. I really need a way to do a proper reconfigure that makes new environments from the layout file available within LyX, and I need to do it from a shellscript. Thanks, SteveT Steve Litt Spring 2021 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: User list server settings
Paul A. Rubin via lyx-users said on Thu, 16 Dec 2021 12:23:48 -0500 >In any case, while I would prefer to have the proper sender display >back, if that can't be done I can accept the "new normal" as the price >of avoiding your being spammed. :-) I know it's a lost cause but I'll say it anyway: A better cost would have been just to ban email from yahoo and its ilk right from the beginning. As a user, I've found Dmarc has been nothing but trouble from the very beginning. SteveT Steve Litt Spring 2021 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: LuaTeX vs XeTeX
Herbert Voss via lyx-users said on Thu, 16 Dec 2021 15:31:15 +0100 >- no more fiddling around with the encoding, everything is UTF-8 >- no more restrictions in using fonts, all current types are supported, > like pfb, ttf, utf, ttc, ... >- easy integration of the script language Lua into a document That's what brought me to LuaTeX and LuaLaTeX: The ability to use TeX Gyre Schola font, which looks better than everything except its lookalike Century Schoolbook, but somehow, about 6 years ago, Century Schoolbook stopped working for me. Since beginning to use LuaTeX, I've enjoyed that it does everything the others do, and by using it all the time, I gain expertise and everything's easier. SteveT Steve Litt Spring 2021 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Word wrap in a cell?
Hi All,
If I remember correctly, you can specify that a column or a cell can
word-wrap, but I can't find a way to do it.
I faked it by Ert'ing \\{} in the text, but this made all the vertical
lines in the row incomplete and looked really ugly.
How do I enable word-wrap within a cell?
Thanks,
SteveT
Steve Litt
Spring 2021 featured book: Troubleshooting Techniques of the Successful
Technologist
http://www.troubleshooters.com/techniques
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Bibliography not in ToC [RESOLVED]
Rich Shepard via lyx-users said on Tue, 14 Dec 2021 13:23:05 -0800 (PST) >Why it did not take when I changed the bibliography style I've no >idea. But the reconfigure forced lyx to show me there were errors in >the .bib file. When troubleshooting, I always texhash;reconfigure; and then do whatever. The extra 90 seconds is well worth it, because a misleading diagnostic test can cost hours. By doing it this way, I never need to tax my brain wondering whether a texhash and/or reconfigure is necessary. My troubleshooting is usually done from a looping shellscript. SteveT Steve Litt Spring 2021 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
I think we need a better name than "MWE"
Hi all, Here on the LyX list we use the word MWE to mean the simplest example that still exhibits the symptom. But MWE stands for Minimum *Working* Example, and by definition, the file that exhibits the symptom does not "work". Also, I think I've seen MWE used on various LaTeX venues to mean the smallest file that works, for a specific feature you want to incorporate. Can anyone think of a better name for the tiniest file that exhibits a symptom? Thanks, SteveT Steve Litt Spring 2021 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Glitch (bug?) in 2.3.6.1 [FIXED]
Dr Eberhard Lisse via lyx-users said on Tue, 14 Dec 2021 13:53:48 +0200
>Or use curly braces.
>
>But why would you do this with ERT in the first place?
>
>Instead of \textdegree{} I just used the first character from
>
> Insert -> Symbols -> Superscripts
>
>and Subscripts and get ⁰C.
Maybe because he didn't know about Insert -> Symbols -> Superscripts. I
didn't know it either, but now I do, and will use it. Thanks for the
information!
SteveT
Steve Litt
Spring 2021 featured book: Troubleshooting Techniques of the Successful
Technologist http://www.troubleshooters.com/techniques
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Re: MWE showing one of my indexing problems [ALL PROBLEMS SOLVED]
Herbert Voss said on Fri, 10 Dec 2021 10:14:29 +0100
>Steve Litt via lyx-users schrieb:
>> Attached please find mwe.lyx and mwe.pdf, which was created by
>> mwe.lyx. This document is standard book class, sized 6 inches high
>> by 4 inches wide to fit on reasonably sized mobile devices. The
>> symptom is that index item "Incremental/Differential Learning" spans
>> about 35 pages, but there's no index begin tag on the first of those
>> pages, or anywhere near it. You can read the rest of the symptom
>> description as chapter 1 of the actual document.
>>
>> I could have refined it further, but after 3 days I'm so punch drunk
>> I was afraid I'd make the symptom vanish and have to start all over
>> again, so if some of you could take a look at it, I'd be very
>> grateful.
>
>do not write an \index command into a sectioning command. Use it after
>such a command. See image
>
>Herbert
Thanks Herbert,
Moving all index commands from the headline to the text immediately
following solved most of of the problems.
And thanks to all the rest of you who helped me.
Stephan Witt recommended looking at the .ilg file. Unfortunately, for
some reason I haven't figured out yet, my shellscript didn't create a
.ilg file, so I just figured there were no warnings (bzzt, wrong).
Then I compiled using el's command:
lyx -f -e luatex lawnmower.lyx && latexmk -lualatex lawnmower.tex
The preceding command gave me a .ilg file with tens or maybe over 100
warnings, and I just didn't think that was possible, because I hadn't
wrongly interlaced anything or used a |( where I was supposed to use a
|).
After I fixed the MWE according to Herbert's advice and compiled with
el's command, I got no warnings in the .ilg.
Armed with such knowledge, I pulled up the real file and, chapter by
chapter, moved any \index commands on headlines to the start of the
text immediately below them. With each chapter so fixed, there were
less and less warnings in the .ilg. Once I'd fixed all the chapters,
the .ilg contained no warnings.
But wait, there's more. Once I got to that point, I had to uncomment
the \input{./seealso.inc} from the layout file. This immediately
produced several warnings of the type:
"Conflicting entries: multiple encaps for the same page under same key"
Ugh! A suitable period of web searching and experimentation brought me
to the conclusion that the following seealso.inc lines, although they
appear logical and correct, produce the preceding error message:
\index{Mental Model!Runit|see{Runit}}
\index{Mental Model!Runit|seealso{ runsv}}
You can't have one lookup phrase produce multiple references. So
instead, you need to incorporate this one inobvious command to replace
the preceding two:
\index{Mental Model!Runit|see {Runit,}, \seealso{runsv}}
Notice the following:
* "Runit," contains a comma that shows through in the index.
* The comma after the closing brace on "{Runit,}," is necessary
* The space after the comma after the closing brace prevents the
seealso from butting up against the comma in "Runit,"
* The seealso must be in command form (\seealso)
Ugly, but it works.
A slightly less challenging requirement is what seems like would be
expressed like the following:
\index{Runit|seealso{runsv}}
\index{Runit|seealso{Runit=>lessons learned}}
But once again, "Conflicting entries: multiple encaps for the same page
under same key", for the exact same reasons: One lookup phrase with
multiple references. Fortunately, because these are both seealso instead
of one of each, the solution is simpler:
\index{Runit|seealso{runsv, Runit=>lessons learned}}
For some reason I'll never understand, the following produces some, but
not all, pages that are off by a page or two:
lyx -f --export luatex lawnmower.lyx
lualatex lawnmower.tex
makeindex lawnmower.idx
luatex lawnmower.tex
So instead I use el's method, which appears to give correct page
numbers every time:
lyx -f --export luatex lawnmower.lyx
latexmk -gg -lualatex lawnmower.tex
One thing I learned the hard way is what Stephan Witt told me: From the
very first index mark or index range, look at your .ilg file and get
rid of all errors and warnings before going on. When warnings get too
numerous, debugging becomes like swimming through molasses.
I put this all into a shellscript, which repeatedly deletes all
intermediate files, does a texhash, a LyX reconfigure, lyx export and
latexmk, displaying the .ilg file with line numbering in the less
command on the CLI, and displaying the resulting PDF in the GUI. Each
compile takes a little longer with all that stuff in there, but I'm
gu
Re: MWE showing one of my indexing problems
Herbert Voss said on Fri, 10 Dec 2021 10:14:29 +0100 >Steve Litt via lyx-users schrieb: >> Attached please find mwe.lyx and mwe.pdf, which was created by >> mwe.lyx. This document is standard book class, sized 6 inches high >> by 4 inches wide to fit on reasonably sized mobile devices. The >> symptom is that index item "Incremental/Differential Learning" spans >> about 35 pages, but there's no index begin tag on the first of those >> pages, or anywhere near it. You can read the rest of the symptom >> description as chapter 1 of the actual document. >> >> I could have refined it further, but after 3 days I'm so punch drunk >> I was afraid I'd make the symptom vanish and have to start all over >> again, so if some of you could take a look at it, I'd be very >> grateful. > >do not write an \index command into a sectioning command. Use it after >such a command. See image > >Herbert Confirmed! Thank you Herbert. I moved the two index opening commands from the end of the sectioning command to the start of the standard text that follows the sectioning command, which eliminated the symptom. My one remaining worry is that, with bad luck and just the wrong vertical alignment, the section header might fall at the bottom of the page *before* the page pointed to by the index entry. But so far, I seem to be having the opposite problem (section header falling *after* the page pointed to by the index entry, but only with my compile script, not with eyeballs) so I have to do more research. Thanks for your help on this. It solved the worst of my two index problems. SteveT Steve Litt Spring 2021 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Graphic file formats
Rich Shepard said on Wed, 8 Dec 2021 09:53:55 -0800 (PST) >On Wed, 8 Dec 2021, Steve Litt wrote: > >> There are ways to shrink PDF size: >> Web search: linux shrink pdf size > >SteveT, > >First hit uses ghostscript; I never dove deep into gs and didn't know >that it can effectively compress a PDF file. It compressed the >original 3,704,503 byte file to 897,417 bytes; a reduction of 76%. >That's impressive. Hi Rich, Did the shrunken PDF have a material effect on timing? SteveT Steve Litt Spring 2021 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: How to find LyX' compile strategy?
Stephan Witt said on Wed, 8 Dec 2021 18:49:07 +0100 >Am 08.12.2021 um 18:16 schrieb Steve Litt : >> >> Dr Eberhard Lisse said on Wed, 8 Dec 2021 17:22:34 +0200 >> >>> What's wrong with >>> >>> lyx -f -e pdf5 lawnmower.lyx >>> >>> or if you must, with >>> >>> lyx -f -e luatex lawnmower.lyx && latexmk lawnmower.tex Thanks Stephan! The .ilg file revealed 125 lines of indexing errors, so that's probably something like 40-50 errors. I'll fix those and see what happens. It's been about 8 years since I indexed a book, and I'd forgotten about the .ilg file. Thanks, SteveT Steve Litt Spring 2021 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
