Re: Opening beamer with Lyx 2.1
Am Donnerstag 04 September 2014, 18:07:03 schrieb David L. Johnson: > On 09/04/2014 03:34 PM, Rudi Gaelzer wrote: > > I'm facing the same problem with a beamer presentation created with LyX > > 2.0 (\lyxformat 413). Now, I have version 2.1.1 but I get the same crash > > message. > > I have had several similar incidents, but I have also managed to > successfully convert dozens of older beamer files to 2.1 --- usually > with no problems at all. > > Here is what I found: The files that I had trouble with all had > hand-built blocks in them (such as adding a Remark block or something > like that, to the ones that are available by default). The old format > for blocks does not get translated to the new one. > > I could get the files to load by eliminating the old blocks. There is a > new block environment, so you could put them back into the format that > you want. > > The old beamer class was quite a hack. This new one does seem to be > more reasonable, although it takes some getting used to, and the nesting > issues could be handled better. Given the variability of how blocks may > have been built up on your old files, getting a converter to handle them > all may be difficult. Please send any such files to me (in PM, if it is confident). We have already solved many problems for 2.1.2, more is scheduled for 2.1.3. You would help me a lot if you could strip the example files down to the relevant slide (bisecting). Thanks Jürgen
Re: Opening beamer with Lyx 2.1
On 09/04/2014 03:34 PM, Rudi Gaelzer wrote: I'm facing the same problem with a beamer presentation created with LyX 2.0 (\lyxformat 413). Now, I have version 2.1.1 but I get the same crash message. I have had several similar incidents, but I have also managed to successfully convert dozens of older beamer files to 2.1 --- usually with no problems at all. Here is what I found: The files that I had trouble with all had hand-built blocks in them (such as adding a Remark block or something like that, to the ones that are available by default). The old format for blocks does not get translated to the new one. I could get the files to load by eliminating the old blocks. There is a new block environment, so you could put them back into the format that you want. The old beamer class was quite a hack. This new one does seem to be more reasonable, although it takes some getting used to, and the nesting issues could be handled better. Given the variability of how blocks may have been built up on your old files, getting a converter to handle them all may be difficult. -- David L. Johnson Department of Mathematics Lehigh University
Re: Opening beamer with Lyx 2.1
I'm facing the same problem with a beamer presentation created with LyX 2.0 (\lyxformat 413). Now, I have version 2.1.1 but I get the same crash message. On Tuesday 17 June 2014 09:48:02 Richard Heck wrote: > On 06/17/2014 07:56 AM, Fabio Fiorelli wrote: > > Hello everyone > > I have several beamer files that I generated from lyx 2.0.6 . We had > > to change from XP to something else, and we went for CentOS. I managed > > to install and run 2.1, after a brief period using 1.6 (the version > > present in the repositories). It seems to run smoothly. However when I > > try to open the old beamer files I get the following message > > > > > > /tmp/lyx_tmpdir.qDvxspUv9932/Buffer_convertLyXFormatXX.lyx.zKzSulrV993 > > ended unexpectedly, which means that it is probably corrupted > > > > I've looked around, and I think this might be an existing > > incompatibility, but I did not find any lyx 2.1-specific answer. > > Is there a solution to this? > > There are some known issues with Beamer conversion, which we hope are > solved for 2.1.1. If you want, you can download the lyx2lyx files from > git.lyx.org and replace the existing ones, or just compile the 2.1.x > branch for yourself. Failing that, 2.1.1 should be out in about two weeks. > > Richard > -- Rudi Gaelzer Institute of Physics Federal University of Rio Grande do Sul BRAZIL Registered linux user # 153741
RE: Hyphenating a hyphenated word at a line break
Sorry for arriving late to this party. Here are a few things I've noticed.
**Type of dash**
In LaTeX, and therefore also in LyX, there are two types of en dash (and
also two types of em dash). In LaTeX the first is entered by -- and the
second is entered with \textendash. In LyX the first is entered with -- and
the second is entered by putting the unicode en dash in (in my reply to Rich
I listed three ways to do this, and Jerry's Mac technique is doing the same
thing). It's not quite clear to me which is the "correct" way to do this. --
is older, and \textendash was introduced so that it can work with more fonts
(or something like that).
But as Jerry has noticed, they also have different line breaking properties.
It sounds like the ability of -- to create a line break was just a side
effect of its implementation rather than intended. Maybe it was suppressed
from \textendash because it's so easy to turn back on when needed (see next
point).
**Changing the breaking behaviour**
Allow \textendash to break: in the position you want to allow a break
(almost certainly after the dash) insert a zero width space. In LaTeX this
is \hspace{0cm}, and in LyX use insert->formatting->horizontal space, then
choose custom and put in zero. This is the same philosophy as Unicode, where
you'd put in a zero-width space to allow a line break.
Stop -- allowing a line break: I'm not sure whether this is a "correct"
solution, but putting it in an \mbox seems to work (as in:
"Heine\mbox{--}Borel theorem"). Unfortunately LyX doesn't support mboxes, so
you'd need to enter it in ERT.
**Which type of line break is correct?**
I know of three ways of using an en dash in English:
1. The original purpose is for numeric ranges in text: "see pp. 40-87".
2. For hyphenating words when they are proper nouns of equal importance: so
in "Heine-Borel theorem" but not in "mean-value theorem".
3. In place of em dashes for parenthetical remarks, with spaces on either
side. This is not traditional but has become fashionable in recent decades.
It seems to me that you do not want breaking for the first usage and you do
for the second (and you'll always get it for the third because of the
spaces), so neither type of dash is better in general. Since \textendash
works with more fonts (so it's said), this seems to me to be the best thing
to output.
Jim
> -Original Message-
> From: lyx-users@lists.lyx.org [mailto:lyx-users@lists.lyx.org] On Behalf
Of
> Jerry
> Sent: 4 September 2014 12:15 AM
> To: LyX users' list
> Subject: Re: Hyphenating a hyphenated word at a line break
>
> On Aug 28, 2014, at 4:03 AM, Jerry wrote:
>
> > I have a fancy hyphenated word, crosstalk-cancelled, where I spell it
with (I
> believe) the proper - which is an n-dash. When this is rendered in the
vicinity
> of a line wrap, the entire thing gets pushed to the next line, leaving a
lot of
> ugly white space in the first line. So I inserted a hyphenation point
after the -.
> This shows on the LyX screen as sort of -- which is my original n-dash and
a
> shorter blue dash, probably supposed to represent a hyphen. This is all
great,
> but when this version is rendered, the line break now appears after
> crosstalk--, that is, both the n-dash _and_ the hyphenation point are
> rendered which looks very wrong. What is the typographer's say on this,
and
> is LyX doing the right thing. Also, is this a LyX problem or a TeX
problem? My
> guess the typographer would say, let the n-dash stand alone if it occurs
at a
> line break.
> >
> > Jerry
>
> Thanks for all your kind responses.
>
> I need to clear up this thread for a few reasons.
>
> I started it with a muddle-headed premise--that the n-dash is
appropriately
> used in places such as crosstalk-cancelled; it is not. A hyphen should be
used
> there. I've known this since grammar school and for some reason a bit in
my
> brain flipped (bit rot's a bitch) a couple months ago and I started doing
it
> wrong. So the best thing would be to ignore this whole thread. However...
>
> LyX, apparently like LaTeX and I suppose TeX, denotes the hyphen as an
> actual hyphen -, the n-dash as two hyphens --, and the m-dash as three
> hyphens ---. When entered this way in LyX, line breaking, if necessary,
> happens as expected, after the hyphen or dash. However...
>
> Something curious happens on my computer which is a Macintosh. I don't
> know if it happens on other computers but it would be interesting to know.
> (Hint.) Specifically, on Macs the n-dash is entered with Option-hyphen and
> the m-dash with Shift-Option-hyphen; this has been the case since 1984 and
> my fingers know it well. The LyX documentation says that the - -- ---
method
> should be used. (It does not say _not_ to do the Mac-like thing.) Being
> contrary (and a newish LyX user) I tried the traditional Mac way, and it
works-
> -the desired character is displayed on the LyX window and also is rendered
> correctly in printed output. So that is the habit I continued fo
RE: Hyphenating a hyphenated word at a line break
> From: lyx-users@lists.lyx.org [mailto:lyx-users@lists.lyx.org] On Behalf Of > Rich Shepard > Sent: 4 September 2014 12:28 AM > > On Wed, 3 Sep 2014, Jerry wrote: > > > Something curious happens on my computer which is a Macintosh. I don't > > know if it happens on other computers but it would be interesting to know. > > (Hint.) > > Jerry, > >On linux running on Intel and AMD processors the only way to enter a > hyphen, n-dash, and m-dash is to use -, --, and ---. Never had a problem with > incorrect line breaks with any of 'em over the years. > > Rich Are you sure it's "the only way"? It's easy to prove something is possible - just say how to do it - but proving something is impossible is notoriously difficult! I suspect one of these three options will let you do the same thing on Linux as Jerry was doing on the Mac: 1. Maybe there is some way to input unicode characters directly. For example, on Windows you can type Alt+0150 to get an en dash. 2. There is probably some equivalent of the Windows character map on Linux. You could search in that for en dash or em dash and copy and paste the result to LyX. 3. Within LyX there is the insert->special character dialogue. Under the "general punctuation" section you will find several dashes (which could really do with labelling). The fifth one (which says "code point: 2013" when you hover over it) is an en dash, and the one after is an em dash. Jim
