Re: Minor upgrade Issue

[gordon cooper]

On 04/07/16 03:17, Guillaume Munch wrote:

Le 03/07/2016 04:35, gordon cooper a écrit :

My colleague on
this project commented :

" --a hundred or more red hard return icons in the lyx file that
showed up as "\begin_inset Separator latexpar\end_inset" in
the html (took me over an hour to find and delete them!) "


As explained in , your
colleague can remove all latexpar separators using the command:

  inset-forall Separator:latexpar char-delete-forward

to be input in the command bar (Alt-x)



Thanks for all the replies. Neither of us had read the release info,
which is one disadvantage of having a packaging team who do the hard
work, leaving us with a simple download and install from the MX repository.
Will be more careful and read the notes next time.

Apart from the separator issue, 2.2 is working well.

Gordon.
Tauranga NZ.

Re: Minor upgrade Issue

[Guillaume Munch]

Le 03/07/2016 04:35, gordon cooper a écrit :

My colleague on
this project commented :

" --a hundred or more red hard return icons in the lyx file that
showed up as "\begin_inset Separator latexpar\end_inset" in
the html (took me over an hour to find and delete them!) "


As explained in , your
colleague can remove all latexpar separators using the command:

  inset-forall Separator:latexpar char-delete-forward

to be input in the command bar (Alt-x)

Re: Minor upgrade Issue

[Richard Heck]

On 07/03/2016 03:12 AM, gordon cooper wrote:
>
>
> On 03/07/16 17:45, Richard Heck wrote:
>> On 07/02/2016 10:35 PM, gordon cooper wrote:
>>> Been using Lyx 2.2.0 without any real problems but a small issue
>>> appeared in a  Koma article that had been upgraded from 2.1.
>>>
>>> Whenever a nesting level was changed, a hyperlink inserted
>>> into a nested list, or we went from nesting back to normal text
>>> layout, Lyx inserted an arrow head with a red vertical curly tail
>>> at the end of the last line before the change.
>> This is due to the change from a Separator paragraph style to a
>> Separator inset, as explained in the release notes.
>>
>>> This had no effect
>>> on the formatting in the Lyx file nor on the pdf's derived from it
>> Good. That was our intention.
>>
>>> but did give some strife in the conversion to html. My colleague on
>>> this project commented :
>>>
>>> " --a hundred or more red hard return icons in the lyx file that
>>> showed up as "\begin_inset Separator latexpar\end_inset" in
>>> the html (took me over an hour to find and delete them!) "
>> How was this HTML produced?
>>
>>> They were not apparent in the Lyx source pane.
>> Possibly because you used a different method to produce the HTML
>> from the one displayed in the source pane?
>>
>> Richard
>>
> Many thanks for that response Richard. I will admit to not reading
> the release notes. Not too sure about the html conversion but think
> that elyxer was being used.

Then the problem is in elyxer, which is not associated with LyX.

Richard

Re: Minor upgrade Issue

[gordon cooper]

On 03/07/16 17:45, Richard Heck wrote:

On 07/02/2016 10:35 PM, gordon cooper wrote:

Been using Lyx 2.2.0 without any real problems but a small issue
appeared in a  Koma article that had been upgraded from 2.1.

Whenever a nesting level was changed, a hyperlink inserted
into a nested list, or we went from nesting back to normal text
layout, Lyx inserted an arrow head with a red vertical curly tail
at the end of the last line before the change.

This is due to the change from a Separator paragraph style to a
Separator inset, as explained in the release notes.


This had no effect
on the formatting in the Lyx file nor on the pdf's derived from it

Good. That was our intention.


but did give some strife in the conversion to html. My colleague on
this project commented :

" --a hundred or more red hard return icons in the lyx file that
showed up as "\begin_inset Separator latexpar\end_inset" in
the html (took me over an hour to find and delete them!) "

How was this HTML produced?


They were not apparent in the Lyx source pane.

Possibly because you used a different method to produce the HTML
from the one displayed in the source pane?

Richard


Many thanks for that response Richard. I will admit to not reading
the release notes. Not too sure about the html conversion but think
that elyxer was being used.

Gordon
Tauranga N.Z.

Re: Minor upgrade Issue

[Richard Heck]

On 07/02/2016 10:35 PM, gordon cooper wrote:
> Been using Lyx 2.2.0 without any real problems but a small issue
> appeared in a  Koma article that had been upgraded from 2.1.
>
> Whenever a nesting level was changed, a hyperlink inserted
> into a nested list, or we went from nesting back to normal text
> layout, Lyx inserted an arrow head with a red vertical curly tail
> at the end of the last line before the change.  

This is due to the change from a Separator paragraph style to a
Separator inset, as explained in the release notes.

> This had no effect
> on the formatting in the Lyx file nor on the pdf's derived from it 

Good. That was our intention.

> but did give some strife in the conversion to html. My colleague on
> this project commented :
>
> " --a hundred or more red hard return icons in the lyx file that
> showed up as "\begin_inset Separator latexpar\end_inset" in
> the html (took me over an hour to find and delete them!) "

How was this HTML produced?

> They were not apparent in the Lyx source pane.

Possibly because you used a different method to produce the HTML
from the one displayed in the source pane?

Richard

Minor upgrade Issue

[gordon cooper]

Been using Lyx 2.2.0 without any real problems but a small issue
appeared in a  Koma article that had been upgraded from 2.1.

Whenever a nesting level was changed, a hyperlink inserted
into a nested list, or we went from nesting back to normal text
layout, Lyx inserted an arrow head with a red vertical curly tail
at the end of the last line before the change.  This had no effect
on the formatting in the Lyx file nor on the pdf's derived from it but
did give some strife in the conversion to html. My colleague on
this project commented :

" --a hundred or more red hard return icons in the lyx file that
showed up as "\begin_inset Separator latexpar\end_inset" in
the html (took me over an hour to find and delete them!) "

They were not apparent in the Lyx source pane.

We hope we have deleted them all and that, now we are using 2.2.
for all authoring and editing,  they will not return.

Gordon
Tauranga N.Z.