Re: Strange Pacer Question

[Dr Eberhard W Lisse]

John,

Have a look at https://writer2latex.sourceforge.net/index.html

I have used Writer2LaTeX a few years ago and found it very
helpful when using what was then called the "Ultraclean"
Option, which I don't see on this much more current version
on cursory look.

Install both writer2latex.oxt and writer2latex-config.oxt.
Then play with the Configuration in Tools -> Options (which
on my Mac only appear of an ODT is open).

You would need to save as ODT first, then export to LaTeX,
from which you would be able to use tex2lyx (the -m option
canbehelpful), and then you could pull into LyX.

If the Word format you are getting is always the same (per
lawyer) which is likely, because they would use some sort of
"template" much of this could be automated :-)-O

The PDF5 might look like

File -> Export -> Export [PDF (LuaTeX)]

which I have tied to Command-R on my Mac(s).

greetings, el

On 29/12/2023 00:59, John White wrote:
> Hi el,
> 
> 
> If I get a Word doc, it opens in libreoffice, which allows
> for export to pdf.  If I recall, I generally either
> highlight the words involved while in libreoffice and paste
> directly to lyx or instead export to pdf, highlight the
> relevant portions of the pdf and paste to lyx.
> 
> 
> It took me forever to get the ps2pdf right (so it would
> become pleading paper, with a vertical line followed by line
> numbers to the left of the page.  When I use anything else I
> have to load pleading paper and use that.
> 
> 
> I plan to try your PDF5 trick this weekend.
> 
> 
> John
[...]

-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Strange Pacer Question

[John White]

I don't think so.  What I am looking into is this:  Pacer will only accept pdf 
files. If those who 
export to pdf from within a word document don't have to "flatten" the document 
before 
uploading to Pacer, while those who use lyx are forced to flatten any document 
imported from a 
Word doc before uploading to Pacer, I want to let the Pacer folks know this and 
suggest that 
Pacer not default to Word.  

Word is so dominant that even in Nevada State Courts we are required to convert 
any editable 
document to Word before the judge will even look at it. If there must be a 
standard here, I think 
it should be an open source standard.  Courts should not be in the business of 
requiring 
everyone to use Word (or any other proprietary product).

John 

On Thursday, December 28, 2023 2:08:18 PM PST Dr Eberhard W Lisse wrote:
> Ever looked at Pandoc?
> 
> el
> 
> On 28/12/2023 21:57, Rich Shepard wrote:
> [...]
> 
> > When I have a .doc/.docx file sent that I want to
> > incorporate into a LyX document I'll do either of two
> > things:
> > 
> > 1.  Highlight the desired text in the Word document then use
> > Edit -> Paste Special -> Join Lines to put it in the LyX
> > doc.
> > 
> > 2.  [...]  If it's a .doc/.docx file I load it in
> > LibreOffice Writer then save as a text file before inserting
> > it.
> > 
> > Since your LyX document is set to include line numbers I
> > think these actions would work for you.
> > 
> > Regards,
> > 
> > Rich

-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Strange Pacer Question

[John White]

Hi el,

If I get a Word doc, it opens in libreoffice, which allows for export to pdf.  
If I recall, I generally 
either highlight the words involved while in libreoffice and paste directly to 
lyx or instead export 
to pdf, highlight the relevant portions of the pdf and paste to lyx. 

It took me forever to get the ps2pdf right (so it would become pleading paper, 
with a vertical 
line followed by line numbers to the left of the page.  When I use anything 
else I have to load 
pleading paper and use that.

I plan to try your PDF5 trick this weekend.

John

On Thursday, December 28, 2023 2:04:54 PM PST Dr Eberhard W Lisse wrote:
> John,
> 
> did you ever try to export using PDF5 (LuaLaTeX)?
> 
> Recent PSTricks should load
> https://github.com/zauguin/luapstricks when using LuaLaTeX. If
> that works for the "normal" way try and upload into Pacer and
> see what happens. If Pacer accepts that see what happens when
> you import a Word document and generate the PDF with LuaLaTeX.
> 
> How do you "import" Word documents?
> 
> el
> 
> On 28/12/2023 21:28, John White wrote:
> [...]
> 
> > Normally, I just do regular lyx stuff and once the file is
> > ready, export with pst2pdf (to insure that line numbers
> > exist at the left side of each page) and upload to Pacer.
> 
> [...]
> 
> > To file in Pacer, the document must be "flattened."  This poses no
> > problem with files created in lyx.  However, whenever I import a Word
> > file and convert it to lyx, Pacer balks and refuses to accept the
> > document unless I "flatten" it.
> 
> [...]

-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Strange Pacer Question

[Dr Eberhard W Lisse]

Ever looked at Pandoc?

el

On 28/12/2023 21:57, Rich Shepard wrote:
[...]
> When I have a .doc/.docx file sent that I want to
> incorporate into a LyX document I'll do either of two
> things:
> 
> 1.  Highlight the desired text in the Word document then use
> Edit -> Paste Special -> Join Lines to put it in the LyX
> doc.
> 
> 2.  [...]  If it's a .doc/.docx file I load it in
> LibreOffice Writer then save as a text file before inserting
> it.
> 
> Since your LyX document is set to include line numbers I
> think these actions would work for you.
> 
> Regards,
> 
> Rich
> 
> 
> 

-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Strange Pacer Question

[Dr Eberhard W Lisse]

John,

did you ever try to export using PDF5 (LuaLaTeX)?

Recent PSTricks should load
https://github.com/zauguin/luapstricks when using LuaLaTeX. If
that works for the "normal" way try and upload into Pacer and
see what happens. If Pacer accepts that see what happens when
you import a Word document and generate the PDF with LuaLaTeX.

How do you "import" Word documents?

el

On 28/12/2023 21:28, John White wrote:
[...]
> Normally, I just do regular lyx stuff and once the file is
> ready, export with pst2pdf (to insure that line numbers
> exist at the left side of each page) and upload to Pacer.
[...]
> To file in Pacer, the document must be "flattened."  This poses no
> problem with files created in lyx.  However, whenever I import a Word
> file and convert it to lyx, Pacer balks and refuses to accept the
> document unless I "flatten" it.
[...]

-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Strange Pacer Question

[Rich Shepard]

On Thu, 28 Dec 2023, John White wrote:


To file in Pacer, the document must be "flattened."  This poses no problem
with files created in lyx. However, whenever I import a Word file and
convert it to lyx, Pacer balks and refuses to accept the document unless I
"flatten" it. If I am at the office, I "flatten" it by printing out the
lyx document and, using the copier, scan it back to me. I then can upload
that scanned file to pacer. If I am at home, I "flatten" it by using "$
pdf2ps orig.pdf - | ps2pdf - flattened.pdf", which usually works.



My question is this: Do those who use Microsoft Word also have to
"flatten" files before filing in the federal courts or does Pacer just
accept Microsoft Word files "as is"? If so, there might be some sort of
anti-trust implications in all this.


John,

I defenstrated from Microsoft 26 years ago so cannot directly answer your
question. However, I might help reduce the time and effort to 'flatten' Word
docs without running them over in your car.

When I have a .doc/.docx file sent that I want to incorporate into a LyX
document I'll do either of two things:

1. Highlight the desired text in the Word document then use Edit -> Paste
Special -> Join Lines to put it in the LyX doc.

2. When I need the entire Word doc and it's sent as a PDF I use pdftotext,
then Insert -> Plain Text, Join Lines. If it's a .doc/.docx file I load it
in LibreOffice Writer then save as a text file before inserting it.

Since your LyX document is set to include line numbers I think these actions
would work for you.

Regards,

Rich



--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Strange Pacer Question

[John White]

I use lyx 2.3.6 on my debian (bullseye) system  I often file in Pacer, the 
database used by the US 
federal court system.  Normally, I just do regular lyx stuff and once the file 
is ready, export with 
pst2pdf (to insure that line numbers exist at the left side of each page) and 
upload to Pacer.  

HOWEVER, I often get files from other attorneys who use microsoft Word, which I 
import into lyx 
and reformat. 

To file in Pacer, the document must be "flattened."  This poses no problem with 
files created in 
lyx.  However, whenever I import a Word file and convert it to lyx, Pacer balks 
and refuses to 
accept the document unless I "flatten" it.  If  I am at the office, I "flatten" 
it  by printing out the 
lyx document and, using the copier, scan it back to me.  I then can upload that 
scanned file to 
pacer.  If I am at home, I "flatten" it by using "$ pdf2ps orig.pdf - | ps2pdf 
- flattened.pdf", which 
usually works.

Pacer itself uses Microsoft Word and brags about it incessantly.  

My question is this:  Do those who use Microsoft Word also have to "flatten" 
files before filing in 
the federal courts or does Pacer just accept Microsoft Word files "as is"?  If 
so, there might be 
some sort of anti-trust implications in all this.

John White Jr.

-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Strange hyphenation with English (UK)

[Herbert Voss]

Am 10.09.23 um 06:53 schrieb Daniel:

On 2023-09-09 23:02, Richard Kimberly Heck wrote:

On 9/9/23 14:41, Daniel wrote:

Hi!

I noticed that setting "English (UK)" as language under Document 
Settings, leads to some strange hyphenation. For example, 
"import-ant" and "theor-ethical". Is that a common issue with that 
language dictionary or do I have a faulty setup?


The latter, assuming you mean "theor-etical", looks acceptable to me, 
if not ideal. The former is apparently wrong, according to what I 
looked up online, though it actually sounds right to me. Or, perhaps 
better, morphologically, it feels right.


I find I do sometimes have to override LaTeX's own choices in final 
preparation of documents.


Riki


I see, I wasn't aware that hyphenation is a style choice in English. 
(In German there are fixed rules.)


No, there is no difference in handling the hyphenation rules.




How do I override LaTeX's choices? I tried

\hyphenation{im-por-tant the-o-re-ti-cal}

But that seemed not to have helped.



It looks like you are using polyglossia.

For document->settings->language  choose babel and then write into
the preamble

\AtBeginDocument{\hyphenation{im-por-tant the-o-re-ti-cal}}

Herbert

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Strange hyphenation with English (UK)

[Daniel]

On 2023-09-09 23:02, Richard Kimberly Heck wrote:

On 9/9/23 14:41, Daniel wrote:

Hi!

I noticed that setting "English (UK)" as language under Document 
Settings, leads to some strange hyphenation. For example, "import-ant" 
and "theor-ethical". Is that a common issue with that language 
dictionary or do I have a faulty setup?


The latter, assuming you mean "theor-etical", looks acceptable to me, if 
not ideal. The former is apparently wrong, according to what I looked up 
online, though it actually sounds right to me. Or, perhaps better, 
morphologically, it feels right.


I find I do sometimes have to override LaTeX's own choices in final 
preparation of documents.


Riki


I see, I wasn't aware that hyphenation is a style choice in English. (In 
German there are fixed rules.)


How do I override LaTeX's choices? I tried

\hyphenation{im-por-tant the-o-re-ti-cal}

But that seemed not to have helped.

Daniel

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Strange hyphenation with English (UK)

[Richard Kimberly Heck]

On 9/9/23 14:41, Daniel wrote:

Hi!

I noticed that setting "English (UK)" as language under Document 
Settings, leads to some strange hyphenation. For example, "import-ant" 
and "theor-ethical". Is that a common issue with that language 
dictionary or do I have a faulty setup?


The latter, assuming you mean "theor-etical", looks acceptable to me, if 
not ideal. The former is apparently wrong, according to what I looked up 
online, though it actually sounds right to me. Or, perhaps better, 
morphologically, it feels right.


I find I do sometimes have to override LaTeX's own choices in final 
preparation of documents.


Riki


--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Strange hyphenation with English (UK)

[Daniel]

Hi!

I noticed that setting "English (UK)" as language under Document 
Settings, leads to some strange hyphenation. For example, "import-ant" 
and "theor-ethical". Is that a common issue with that language 
dictionary or do I have a faulty setup?


Best,
Daniel

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Permanence of strange .tex file

[Rich Shepard]

On Sat, 28 Aug 2021, Stephan Witt wrote:


Ok, I mentioned it because you said you’ve killed LyX. If you’ve quit LyX
regularly then the temporary files are removed and you cannot find them anymore.
The running process has this open and therefore you can see it. It’s on disk
present until you kill the background process and then the disk space is freed.


LyX is always exited with Ctrl-Q. The .tex processes that remained and
consumed 100% of the CPUs (according to top) were killed by root with the
command
kill -9 

FWIW I've run only linux since 1997 and am quite familiar with it.

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Permanence of strange .tex file

[Stephan Witt]

Am 28.08.2021 um 14:36 schrieb Rich Shepard :
> 
> On Sat, 28 Aug 2021, Stephan Witt wrote:
> 
>> on quit LyX removes it’s temporary files and directories. This doesn’t
>> happen on sudden death of LyX. The question now is: is /tmp the location
>> for temporary files and directories?
>> 
>> On MacOS it’s not /tmp if you don’t set the path explicitly to /tmp.
> 
> Stephan,
> 
> Yes, LyX has always stored temporary files in /tmp (appropriately enough)
> which is a default directory in linux. And I've not had LyX crash in
> decades; it's closed properly.

Ok, I mentioned it because you said you’ve killed LyX. If you’ve quit LyX
regularly then the temporary files are removed and you cannot find them anymore.
The running process has this open and therefore you can see it. It’s on disk
present until you kill the background process and then the disk space is freed.

BR, Stephan
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Permanence of strange .tex file

[Rich Shepard]

On Sat, 28 Aug 2021, Stephan Witt wrote:


on quit LyX removes it’s temporary files and directories. This doesn’t
happen on sudden death of LyX. The question now is: is /tmp the location
for temporary files and directories?

On MacOS it’s not /tmp if you don’t set the path explicitly to /tmp.


Stephan,

Yes, LyX has always stored temporary files in /tmp (appropriately enough)
which is a default directory in linux. And I've not had LyX crash in
decades; it's closed properly.

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Permanence of strange .tex file

[Stephan Witt]

Am 27.08.2021 um 22:51 schrieb Rich Shepard :
> 
> On Fri, 27 Aug 2021, Paul A. Rubin wrote:
> 
>> Do you by any chance have instant preview turned on in Tools > Preferences > 
>> Look & Feel > Display.
> 
> Paul,
> 
> Huh! It was turned on, but I've no recollection of ever doing this. And, as
> I wrote, it's never before been an issue. So I turned it off.
> 
>> The presence of "preview" in the file name suggests to me that LyX might
>> have been compiling something for instant preview.
> 
> Could be. I opened LyX, looked in preferences (but not Display), exited,
> then found Display and turned off instant preview. There were to *.tex files
> using the CPUs after I exited the second time. Killed both processes.
> 
>> As far as the undead process, if LyX spawns a latex / pdflatex / whatever
>> process to compile something and then you kill LyX, the child process does
>> not get killed automatically (at least in my experience). You have to nuke
>> it manually. I would expect the lyxpreviewN17596.tex file to be stashed in
>> the LyX temporary directory for the parent document.
> 
> If yesterday's files were in /tmp find should have found them. It didn’t.

Hi Rich,

on quit LyX removes it’s temporary files and directories. This doesn’t happen 
on sudden death of LyX. The question now is: is /tmp the location for temporary 
files and directories?

On MacOS it’s not /tmp if you don’t set the path explicitly to /tmp.

Stephan

> 
> Anyway, however the instant preview became active it's now off. Must be
> pandemic related, eh? :-)
> 
> Stay well,
> 
> Rich
> -- 
> 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: Permanence of strange .tex file

[Paul A. Rubin]

On 8/27/21 4:51 PM, Rich Shepard wrote:

On Fri, 27 Aug 2021, Paul A. Rubin wrote:

Do you by any chance have instant preview turned on in Tools > 
Preferences > Look & Feel > Display.


Paul,

Huh! It was turned on, but I've no recollection of ever doing this. 
And, as

I wrote, it's never before been an issue. So I turned it off.


The presence of "preview" in the file name suggests to me that LyX might
have been compiling something for instant preview.


Could be. I opened LyX, looked in preferences (but not Display), exited,
then found Display and turned off instant preview. There were to *.tex 
files

using the CPUs after I exited the second time. Killed both processes.

As far as the undead process, if LyX spawns a latex / pdflatex / 
whatever
process to compile something and then you kill LyX, the child process 
does
not get killed automatically (at least in my experience). You have to 
nuke
it manually. I would expect the lyxpreviewN17596.tex file to be 
stashed in

the LyX temporary directory for the parent document.


If yesterday's files were in /tmp find should have found them. It didn't.

Anyway, however the instant preview became active it's now off. Must be
pandemic related, eh? :-)

Stay well,

Rich

Rich,

The seldom benevolent digital deities have been on a bit of a rampage 
lately, based on personal experience. I don't know if it's caused by the 
pandemic, global warming, a surfeit of politicians (note that I'm 
listing disasters in ascending order of severity) or just random timing.


Anyway, hopefully the issue is fixed. The (presumed) fact that instant 
preview produced LaTeX processes that spun their digital wheels 
indefinitely might, however, indicate that you have something (math 
inset? other sort of inset?) that is indigestible to LaTeX, in which 
case the same problem may arise if and when you actually do compile the 
parent document.


Or maybe not. I've given up predicting the outcome of anything digital.

Paul

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Permanence of strange .tex file

[Rich Shepard]

On Fri, 27 Aug 2021, Paul A. Rubin wrote:

Do you by any chance have instant preview turned on in Tools > Preferences > 
Look & Feel > Display.


Paul,

Huh! It was turned on, but I've no recollection of ever doing this. And, as
I wrote, it's never before been an issue. So I turned it off.


The presence of "preview" in the file name suggests to me that LyX might
have been compiling something for instant preview.


Could be. I opened LyX, looked in preferences (but not Display), exited,
then found Display and turned off instant preview. There were to *.tex files
using the CPUs after I exited the second time. Killed both processes.


As far as the undead process, if LyX spawns a latex / pdflatex / whatever
process to compile something and then you kill LyX, the child process does
not get killed automatically (at least in my experience). You have to nuke
it manually. I would expect the lyxpreviewN17596.tex file to be stashed in
the LyX temporary directory for the parent document.


If yesterday's files were in /tmp find should have found them. It didn't.

Anyway, however the instant preview became active it's now off. Must be
pandemic related, eh? :-)

Stay well,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Permanence of strange .tex file

[Paul A. Rubin]

On 8/26/21 3:27 PM, Rich Shepard wrote:

Here's another new experience for me. When I kill the lyx process there
remains a file, for example lyxpreviewN17596.tex, which shows up in the
process list as 'latex lyxpreviewN17596.tex' and consumes 100% of the 
CPUs

most of the time.

Root cannot find this file anywhere, and it persists after I close 
lyx, even

when I did not open the compiled PDF or look at a preview within lyx.

I kill the process but haven't seen this before and would like to 
understand

what might be behind this behavior.

Regards,

Rich
Do you by any chance have instant preview turned on in Tools > 
Preferences > Look & Feel > Display. The presence of "preview" in the 
file name suggests to me that LyX might have been compiling something 
for instant preview. As far as the undead process, if LyX spawns a latex 
/ pdflatex / whatever process to compile something and then you kill 
LyX, the child process does not get killed automatically (at least in my 
experience). You have to nuke it manually. I would expect the 
lyxpreviewN17596.tex file to be stashed in the LyX temporary directory 
for the parent document.


Paul

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Permanence of strange .tex file

[Rich Shepard]

Here's another new experience for me. When I kill the lyx process there
remains a file, for example lyxpreviewN17596.tex, which shows up in the
process list as 'latex lyxpreviewN17596.tex' and consumes 100% of the CPUs
most of the time.

Root cannot find this file anywhere, and it persists after I close lyx, even
when I did not open the compiled PDF or look at a preview within lyx.

I kill the process but haven't seen this before and would like to understand
what might be behind this behavior.

Regards,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: What is this strange arrow?

[John Beattie]

On 2019-01-23 18:20 +0100, Daniel wrote:
> On 2019-01-23 18:10, Daniel CLEMENT wrote:
> >Hello,
> >
> >I'm still new to LyX 2.3 (from 2.1) so I'm not ashamed of asking a trivial
> >question:
> >
> >As I open my old documents, in various places I'm can see this
> >(non-printing) symbol which I had never met before:
> >
> >
> >
> >What does it mean? I can't see any difference in preview if I erase it.
> >
> >TIA - Daniel
> 
> Hi,
> 
> It's an indicator of additional blank lines that were automatically inserted
> in LyX 2.1 but not anymore in >2.2. See
> 
> https://wiki.lyx.org/LyX/NewInLyX22#parbreak
> 
> Most of the times you can just remove them.
> 
> Best,
> Daniel


Many thanks to both. I have been using LyX since 2010; I didn't know the answer;
I find the answer interesting and enlightening.

Thanks again,
John

Re: What is this strange arrow?

[Daniel]

On 2019-01-23 18:10, Daniel CLEMENT wrote:

Hello,

I'm still new to LyX 2.3 (from 2.1) so I'm not ashamed of asking a 
trivial question:


As I open my old documents, in various places I'm can see this 
(non-printing) symbol which I had never met before:




What does it mean? I can't see any difference in preview if I erase it.

TIA - Daniel


Hi,

It's an indicator of additional blank lines that were automatically 
inserted in LyX 2.1 but not anymore in >2.2. See


https://wiki.lyx.org/LyX/NewInLyX22#parbreak

Most of the times you can just remove them.

Best,
Daniel

What is this strange arrow?

[Daniel CLEMENT]

Hello,

I'm still new to LyX 2.3 (from 2.1) so I'm not ashamed of asking a
trivial question:

As I open my old documents, in various places I'm can see this (non-
printing) symbol which I had never met before:


What does it mean? I can't see any difference in preview if I erase it.

TIA - Daniel

Re: Strange screen problem in LyX Version 2.3.1-1

[Murat Yildizoglu]

Hello again,
Closing all open buffers and reopening a new document has corrected this
issue, but if I can help you to find the source of this bug, I would be
happy to do it.
I use LyX under OSX 10.13.6

Le sam. 27 oct. 2018 à 17:14, Murat Yildizoglu <
murat.yildizo...@u-bordeaux.fr> a écrit :

> Hello,
> I am puzzled by a problem I get in Lyx now.
> I have just closed the outline panel and Lyx screen became very weird (see
> the screenshot), and I cannot find how I can reset it to its normal
> appearance with the documents bar on the top of the editing panel and the
> Lyx screen fully usable. Any idea what is going on.
> Closing and reopening Lyx does not solve the problem.
>
> After the first appearance of this problem I have got a SIGSEV:
>
> (  1) 1   lyx 0x00010757bd7f
> _ZN3lyx8frontend5Alert7doErrorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwSA_b
> : 1   lyx 0x00010757bd7f
> _ZN3lyx8frontend5Alert7doErrorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwSA_b
> + 190
> (  2) 2   lyx 0x00010757c2b5
> _ZN3lyx8frontend5Alert5errorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwSA_b
> : 2   lyx 0x00010757c2b5
> _ZN3lyx8frontend5Alert5errorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwSA_b
> + 149
> (  3) 3   lyx 0x000107312e2b
> _ZN3lyx13error_handlerEi : 3   lyx
> 0x000107312e2b _ZN3lyx13error_handlerEi + 506
> (  4) 4   libsystem_platform.dylib0x7fff6970cf5a _sigtramp
> : 4   libsystem_platform.dylib0x7fff6970cf5a _sigtramp + 26
> (  5) 5   lyx 0x000107e91f7f
> LinkBackServers : 5   lyx
> 0x000107e91f7f LinkBackServers + 314679
> (  6) 6   QtWidgets   0x000108cc6fba
> _ZN15QDockAreaLayout20deleteAllLayoutItemsEv : 6   QtWidgets
> 0x000108cc6fba _ZN15QDockAreaLayout20deleteAllLayoutItemsEv
> + 42
> (  7) 7   QtWidgets   0x000108cf3d74
> _ZN17QMainWindowLayoutD2Ev : 7   QtWidgets
> 0x000108cf3d74 _ZN17QMainWindowLayoutD2Ev + 52
> (  8) 8   QtWidgets   0x000108cf3fde
> _ZN17QMainWindowLayoutD0Ev : 8   QtWidgets
> 0x000108cf3fde _ZN17QMainWindowLayoutD0Ev + 14
> (  9) 9   QtWidgets   0x000108badaee
> _ZN7QWidgetD2Ev : 9   QtWidgets
> 0x000108badaee _ZN7QWidgetD2Ev + 414
> ( 10) 10  lyx 0x000107723de2
> _ZN3lyx8frontend7GuiViewD0Ev : 10  lyx
> 0x000107723de2 _ZN3lyx8frontend7GuiViewD0Ev + 14
> ( 11) 11  QtCore  0x00010872b050
> _ZN7QObject5eventEP6QEvent : 11  QtCore
>  0x00010872b050 _ZN7QObject5eventEP6QEvent + 128
> ( 12) 12  QtWidgets   0x000108bc054b
> _ZN7QWidget5eventEP6QEvent : 12  QtWidgets
> 0x000108bc054b _ZN7QWidget5eventEP6QEvent + 5787
> ( 13) 13  QtWidgets   0x000108ceaee5
> _ZN11QMainWindow5eventEP6QEvent : 13  QtWidgets
> 0x000108ceaee5 _ZN11QMainWindow5eventEP6QEvent + 1733
> ( 14) 14  lyx 0x00010772828d
> _ZN3lyx8frontend7GuiView5eventEP6QEvent : 14  lyx
>   0x00010772828d _ZN3lyx8frontend7GuiView5eventEP6QEvent + 249
> ( 15) 15  QtWidgets   0x000108b85b2d
> _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent : 15  QtWidgets
> 0x000108b85b2d
> _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent + 301
> ( 16) 16  QtWidgets   0x000108b86ea7
> _ZN12QApplication6notifyEP7QObjectP6QEvent : 16  QtWidgets
>   0x000108b86ea7 _ZN12QApplication6notifyEP7QObjectP6QEvent +
> 391
> ( 17) 17  lyx 0x00010758c3e0
> _ZN3lyx8frontend14GuiApplication6notifyEP7QObjectP6QEvent : 17  lyx
> 0x00010758c3e0
> _ZN3lyx8frontend14GuiApplication6notifyEP7QObjectP6QEvent + 22
> ( 18) 18  QtCore  0x000108701414
> _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent : 18  QtCore
>0x000108701414
> _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent + 164
> ( 19) 19  QtCore  0x00010870259b
> _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData :
> 19  QtCore  0x00010870259b
> _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData +
> 891
> ( 20) 20  QtCore  0x000108701b2d
> _ZN16QCoreApplication4execEv : 20  QtCore
>  0x000108701b2d _ZN16QCoreApplication4execEv + 509
> ( 21) 21  lyx 0x00010730e65c
> _ZN3lyx3LyX4execERiPPc : 21  lyx
> 0x00010730e65c 

Re: Strange problem of which I have difficulty to locate the origin

[Murat Yildizoglu]

Me again,

Sometime, Writing a message helps us to solve the problem I imagine.
I have solved the problem I think. turkish in Babe need ,shorthands=:! as
an option (to neutralize babel rules for =, it seems that they pose a
problem for xkeyval used by includegraphics). I was adding it in custom
options for the document, but it was not working it seems. I have thought
of trying to put it in the preamble by putting
\usepackage[shorthands=:!]{babel}
and it worked. Both figures compile now.
I was not well aware of this possibility of adding supplementary options
through the preamble. It works very well.

Thank you very much!

2017-10-02 11:32 GMT+02:00 Murat Yildizoglu <myi...@gmail.com>:

> Dear list members,
>
> I have been using LyX for many years but I currently meet a strange
> problem: I am writing my first article in Turkish and I use turkish as a
> babel mode (with english) and I cannot scale or resize any included PDF
> figure (I typeset with pdflatex). In the attached example file the fisr
> figure has a scaling instruction, but the second has not; You can see in
> the resulting PDF that the first figure is not included and we see a bit of
> the scaling instruction given to \includegraphics instead. The second is
> correctly included.
> Is this a feature or a bug?
>
> FYI: If I export to latex, I can compile the file with both figures.
>
> Any idea why I get this problem, and how I can solve it?
>
> Thank you very much.
>
> Murat
>
> --
> Prof. Murat Yildizoglu
>
> Université Montesquieu Bordeaux IV
> GREThA (UMR CNRS 5113)
> Avenue Léon Duguit
> 33608 Pessac cedex
> France
>
> Bureau : E-331
>
> mail: murat.yildizoglu at u-bordeaux.fr
>
> web: http://yildizoglu.fr
>



-- 
Prof. Murat Yildizoglu

Université Montesquieu Bordeaux IV
GREThA (UMR CNRS 5113)
Avenue Léon Duguit
33608 Pessac cedex
France

Bureau : E-331

mail: murat.yildizoglu at u-bordeaux.fr

web: http://yildizoglu.fr

Strange problem of which I have difficulty to locate the origin

[Murat Yildizoglu]

Dear list members,

I have been using LyX for many years but I currently meet a strange
problem: I am writing my first article in Turkish and I use turkish as a
babel mode (with english) and I cannot scale or resize any included PDF
figure (I typeset with pdflatex). In the attached example file the fisr
figure has a scaling instruction, but the second has not; You can see in
the resulting PDF that the first figure is not included and we see a bit of
the scaling instruction given to \includegraphics instead. The second is
correctly included.
Is this a feature or a bug?

FYI: If I export to latex, I can compile the file with both figures.

Any idea why I get this problem, and how I can solve it?

Thank you very much.

Murat

-- 
Prof. Murat Yildizoglu

Université Montesquieu Bordeaux IV
GREThA (UMR CNRS 5113)
Avenue Léon Duguit
33608 Pessac cedex
France

Bureau : E-331

mail: murat.yildizoglu at u-bordeaux.fr

web: http://yildizoglu.fr


evolcomplexecon-test.lyx
Description: Binary data


evolcomplexecon-test.pdf
Description: Adobe PDF document

Re: Strange compile error

[Steve Hnizdur]

On 03/09/17 21:20, Paul A. Rubin wrote:

On 09/03/2017 04:10 PM, Steve Hnizdur wrote:

Hi

Thanks for replying. Ctrl-R  does pdflatex. Attached is the tex file 
produced by exporting from lyx, and I get the same error by running 
pdflatex directly on it. I'm running Ubuntu 16.04 with everything upto 
date.


By the way the error still happens if the superscripts are removed, it 
seems to be the \dots that are causing the problem.


Cheers
To facilitate others following the thread, it's preferred that we 
bottom-post.


I just ran pdflatex against your TeX, and again it compiled for me with 
no errors. I'm running Linux Mint 18.2 (based on Ubuntu 16.04), with LyX 
2.2.3 and TeXLive 2017. I've attached the pdflatex log file; maybe you 
can look for differences with yours and find out where yours deviates. 
It seems to be something on your system, not a LyX error.


Paul


I can confirm there is a problem with amsmath 2.15a. I have now updated 
to 2.16a and all is fine. Many thanks for comments and help.


--

Steve Hnizdur

Re: Strange compile error

[Guenter Milde]

On 2017-09-03, Steve Hnizdur wrote:

> Attached is a lyx file which when complied with ctrl-R gives the error 
> below copied from the error log. It also fails if I try to compile it as 
> a native .tex file.

I tried the example you posted later and it runs without problems here
(Debian/stable with pre-packaged TeXLive 2016).

> The error goes away if the \dots is removed and it also goes away if the 
> "Number Equations by Section" Module is removed.

> Any thoughts.

I know that amsmath re-defines \dots to be context sensitive. It may be
that \numberwithin{equation}{section} interferes with this re-definition in
some way (in the version used by you) and the bug is solved in current
versions.

You may try to use \ldots instead of \dots or to update your TeX installation.

Günter

Re: Strange compile error

[Paul A. Rubin]

On 09/03/2017 04:10 PM, Steve Hnizdur wrote:

Hi

Thanks for replying. Ctrl-R  does pdflatex. Attached is the tex file 
produced by exporting from lyx, and I get the same error by running 
pdflatex directly on it. I'm running Ubuntu 16.04 with everything upto 
date.


By the way the error still happens if the superscripts are removed, it 
seems to be the \dots that are causing the problem.


Cheers
To facilitate others following the thread, it's preferred that we 
bottom-post.


I just ran pdflatex against your TeX, and again it compiled for me with 
no errors. I'm running Linux Mint 18.2 (based on Ubuntu 16.04), with LyX 
2.2.3 and TeXLive 2017. I've attached the pdflatex log file; maybe you 
can look for differences with yours and find out where yours deviates. 
It seems to be something on your system, not a LyX error.


Paul

This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/Debian) (preloaded format=pdflatex 2017.8.2)  3 SEP 2017 16:14
entering extended mode
 restricted \write18 enabled.
 %&-line parsing enabled.
**test_error.tex
(./test_error.tex
LaTeX2e <2017-04-15>
Babel <3.12> and hyphenation patterns for 3 language(s) loaded.
(/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo
File: size10.clo 2014/09/29 v1.4h Standard LaTeX file (size option)
)
\c@part=\count79
\c@section=\count80
\c@subsection=\count81
\c@subsubsection=\count82
\c@paragraph=\count83
\c@subparagraph=\count84
\c@figure=\count85
\c@table=\count86
\abovecaptionskip=\skip41
\belowcaptionskip=\skip42
\bibindent=\dimen102
)
(/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty
Package: fontenc 2017/04/05 v2.0i Standard LaTeX package

(/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def
File: t1enc.def 2017/04/05 v2.0i Standard LaTeX file
LaTeX Font Info:Redeclaring font encoding T1 on input line 48.
))
(/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty
Package: inputenc 2015/03/17 v1.2c Input encoding file
\inpenc@prehook=\toks14
\inpenc@posthook=\toks15

(/usr/share/texlive/texmf-dist/tex/latex/base/latin9.def
File: latin9.def 2015/03/17 v1.2c Input encoding file
))
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty
Package: amsmath 2016/11/05 v2.16a AMS math features
\@mathmargin=\skip43

For additional information on amsmath, use the `?' option.
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty
Package: amstext 2000/06/29 v2.01 AMS text

(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty
File: amsgen.sty 1999/11/30 v2.0 generic functions
\@emptytoks=\toks16
\ex@=\dimen103
))
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty
Package: amsbsy 1999/11/29 v1.2d Bold Symbols
\pmbraise@=\dimen104
)
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty
Package: amsopn 2016/03/08 v2.02 operator names
)
\inf@bad=\count87
LaTeX Info: Redefining \frac on input line 213.
\uproot@=\count88
\leftroot@=\count89
LaTeX Info: Redefining \overline on input line 375.
\classnum@=\count90
\DOTSCASE@=\count91
LaTeX Info: Redefining \ldots on input line 472.
LaTeX Info: Redefining \dots on input line 475.
LaTeX Info: Redefining \cdots on input line 596.
\Mathstrutbox@=\box26
\strutbox@=\box27
\big@size=\dimen105
LaTeX Font Info:Redeclaring font encoding OML on input line 712.
LaTeX Font Info:Redeclaring font encoding OMS on input line 713.
\macc@depth=\count92
\c@MaxMatrixCols=\count93
\dotsspace@=\muskip10
\c@parentequation=\count94
\dspbrk@lvl=\count95
\tag@help=\toks17
\row@=\count96
\column@=\count97
\maxfields@=\count98
\andhelp@=\toks18
\eqnshift@=\dimen106
\alignsep@=\dimen107
\tagshift@=\dimen108
\tagwidth@=\dimen109
\totwidth@=\dimen110
\lineht@=\dimen111
\@envbody=\toks19
\multlinegap=\skip44
\multlinetaggap=\skip45
\mathdisplay@stack=\toks20
LaTeX Info: Redefining \[ on input line 2817.
LaTeX Info: Redefining \] on input line 2818.
)
(/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
Package: babel 2017/06/29 3.12 The Babel package

(/usr/share/texlive/texmf-dist/tex/generic/babel/switch.def
File: switch.def 2017/06/29 3.12 Babel switching mechanism
)
(/usr/share/texlive/texmf-dist/tex/generic/babel-english/british.ldf
Language: british 2017/06/06 v3.3r English support from the babel system

(/usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf
Language: english 2017/06/06 v3.3r English support from the babel system

(/usr/share/texlive/texmf-dist/tex/generic/babel/babel.def
File: babel.def 2017/06/29 3.12 Babel common definitions

(/usr/share/texlive/texmf-dist/tex/generic/babel/switch.def
File: switch.def 2017/06/29 3.12 Babel switching mechanism
)
\babel@savecnt=\count99
\U@D=\dimen112
)
\l@british = a dialect from \language\l@english 
\l@UKenglish = a dialect from \language\l@english 
\l@canadian = a dialect from \language\l@american 
\l@australian = a dialect from \language\l@british 
\l@newzealand = a 

Re: Strange compile error

[Steve Hnizdur]

Hi

Thanks for replying. Ctrl-R  does pdflatex. Attached is the tex file 
produced by exporting from lyx, and I get the same error by running 
pdflatex directly on it. I'm running Ubuntu 16.04 with everything upto date.


By the way the error still happens if the superscripts are removed, it 
seems to be the \dots that are causing the problem.


Cheers

On 03/09/17 21:00, Paul A. Rubin wrote:

On 09/03/2017 01:06 PM, Steve Hnizdur wrote:

Hi

Attached is a lyx file which when complied with ctrl-R gives the error 
below copied from the error log. It also fails if I try to compile it 
as a native .tex file.


The error goes away if the \dots is removed and it also goes away if 
the "Number Equations by Section" Module is removed.


Any thoughts.
What format does ctrl-R use in your configuration? In mine, it's 
pdflatex, and the document compiles just fine.


Paul



--

Steve Hnizdur
%% LyX 2.2.3 created this file.  For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass[british]{article}
\usepackage[T1]{fontenc}
\usepackage[latin9]{inputenc}
\usepackage{amsmath}

\makeatletter
%% Textclass specific LaTeX commands.
\numberwithin{equation}{section}

\makeatother

\usepackage{babel}
\begin{document}
aaa
\[
\left\Vert P_{1}\right\Vert ^{m_{1}}\dots\left\Vert P_{r}\right\Vert ^{m_{r}}
\]

xxx
\end{document}

Re: Strange compile error

[Paul A. Rubin]

On 09/03/2017 01:06 PM, Steve Hnizdur wrote:

Hi

Attached is a lyx file which when complied with ctrl-R gives the error 
below copied from the error log. It also fails if I try to compile it 
as a native .tex file.


The error goes away if the \dots is removed and it also goes away if 
the "Number Equations by Section" Module is removed.


Any thoughts.
What format does ctrl-R use in your configuration? In mine, it's 
pdflatex, and the document compiles just fine.


Paul

Strange compile error

[Steve Hnizdur]

Hi

Attached is a lyx file which when complied with ctrl-R gives the error 
below copied from the error log. It also fails if I try to compile it as 
a native .tex file.


The error goes away if the \dots is removed and it also goes away if the 
"Number Equations by Section" Module is removed.


Any thoughts.


Error
**

! Argument of \zap@to@space has an extra }.

\par
l.20 ...t\Vert P_{1}\right\Vert ^{m_{1}}\dots\left
  \Vert 
P_{r}\right\Vert ^{m...

I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.

Runaway argument?
\left..
! Paragraph ended before \zap@to@space was complete.

   \par
l.20 ...t\Vert P_{1}\right\Vert ^{m_{1}}\dots\left
  \Vert 
P_{r}\right\Vert ^{m...

I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.

Runaway argument?
! Paragraph ended before \macro@ was complete.

   \par
l.20 ...t\Vert P_{1}\right\Vert ^{m_{1}}\dots\left
  \Vert 
P_{r}\right\Vert ^{m...

I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.

! Missing $ inserted.

$
l.20 ...t\Vert P_{1}\right\Vert ^{m_{1}}\dots\left
  \Vert 
P_{r}\right\Vert ^{m...

I've inserted a begin-math/end-math symbol since I think
you left one out. Proceed, with fingers crossed.

! Display math should end with $$.

   \par
l.20 ...t\Vert P_{1}\right\Vert ^{m_{1}}\dots\left
  \Vert 
P_{r}\right\Vert ^{m...

The `$' that I just saw supposedly matches a previous `$$'.
So I shall assume that you typed `$$' both times.

Runaway argument?
\meaning@ \not@ \ifgtest@ \gdef \thedots@ {\dotsb@ }\else \@xp \DOTS@ \ETC.
! Paragraph ended before \macro@ was complete.

   \par
l.22

I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.


! LaTeX Error: \begin{equation*} on input line 19 ended by \end{document}.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H   for immediate help.
 ...

l.24 \end{document}

Your command was ignored.
Type  Ito replace it with another command,
orto continue without it.

[1

{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] (./test_error.aux) )
(\end occurred inside a group at level 1)

### semi simple group (level 1) entered at line 19 (\begingroup)
### bottom level
(\end occurred when \iffalse on line 20 was incomplete)
(\end occurred when \iffalse on line 20 was incomplete)
(\end occurred when \iffalse on line 20 was incomplete)
(\end occurred when \ifx on line 20 was incomplete)
(\end occurred when \ifx on line 20 was incomplete)
(\end occurred when \ifx on line 20 was incomplete)
Here is how much of TeX's memory you used:

--

Steve Hnizdur


test_error.lyx
Description: application/lyx

Re: strange bouncing of EMails

[Dr Eberhard Lisse]

To me these look like bounce messages which should go to the list-admin
if that was possible tho they can be removed from the list :-)-O

I am not getting these though :-)-O

I don't have Finnish (can someone who does contact the correct new
address of the two offered perhaps?), but the second one looks like
they don't like fli.bund.de any longer and want to be called fli.de, so
maybe Eildert must unsubscribe the old address and resubscribe under
the new (which is why he reads in copy)

What I do when I get a stubborn mail program, is to create a filter
that moves the file into my bounce folder.

el


On 2017-01-24 22:43, Wolfgang Engelmann wrote:
> I am using the lyx-users@lists.lyx.org and each time I am sending
> a mail to the list, I am getting the message shown below. I was
> told, that this happens to other members of the list too and it
> would be nice if the cause of the bouncing could be identified and
> removed. Thanks for your attention.
>
> Wolfgang Engelmann
> 
> When I am sending a mail to the Lyx User group lyx-users@lists.lyx.org I
> am getting
> 
> always this message:
> 
> Olen lomalla. Sähköpostia voi lähettää jollekin muulle henkilökunnastamme 
> etunimi.sukun...@vskonetarvike.com tai vaihtoehtoisesti 
> myy...@vskonetarvike.com
> 
> 
> Although I definetely do not use this address nor is it in my address
> book. In addition I got today this mail
> On 24.01.2017 18:06, mailmars...@fli.de wrote:
>> The following message was addressed to our organization using a
>> *domain name* that is being *retired*:
>>  
>>*From:*  engelm...@uni-tuebingen.de
>>*To:*eildert.groenev...@fli.bund.de
>>*Subject:*   getting rid of white space in graphic
>>
>> Please update your email address lists by changing any addresses that
>> refer to *fli.bund.de* to our new domain name of *fli.de*.
>>
>> This notification is for your information only - your original message
>> *has been delivered* to the intended recipient.
>>
>> FLI MailMarshal
>> *Email Content Security*
>>
>> Friedrich-Loeffler-Institut
>> Bundesforschungsinstitut für Tiergesundheit
>> Federal Research Institute for Animal Health
>>
> What could I do about it?
> Wolfgang

strange bouncing of EMails

[Wolfgang Engelmann]

I am using the  lyx-users@lists.lyx.org and each time I am sending a 
mail to the list, I am getting the message shown below. I was told, that 
this happens to other members of the list too and it would be nice if 
the cause of the bouncing could be identified and removed. Thanks for 
your attention.


Wolfgang Engelmann

When I am sending a mail to the Lyx User group lyx-users@lists.lyx.org I 
am getting


always this message:

Olen lomalla. Sähköpostia voi lähettää jollekin muulle 
henkilökunnastammeetunimi.sukun...@vskonetarvike.com  tai 
vaihtoehtoisestimyy...@vskonetarvike.com


Although I definetely do not use this address nor is it in my address 
book. In addition I got today this mail

On 24.01.2017 18:06, mailmars...@fli.de wrote:
The following message was addressed to our organization using a 
*domain name* that is being *retired*:


*From:* engelm...@uni-tuebingen.de
*To:* eildert.groenev...@fli.bund.de
*Subject:*   getting rid of white space in graphic

Please update your email address lists by changing any addresses that 
refer to *fli.bund.de* to our new domain name of *fli.de*.


This notification is for your information only - your original message 
*has been delivered* to the intended recipient.


FLI MailMarshal
*Email Content Security*

Friedrich-Loeffler-Institut
Bundesforschungsinstitut für Tiergesundheit
Federal Research Institute for Animal Health


What could I do about it?
Wolfgang

Re: strange

[Wolfgang Engelmann]

Perhaps you could also send an Email to the address below asking them to 
stop it. I will try tomorrow to phone them up. Wolfgang



On 24.01.2017 20:44, gordon cooper wrote:

  You are not alone Wolfgang, I have been getting them too.

Gordon.




eildert.groenev...@fli.bund.de

Re: strange

[gordon cooper]

  You are not alone Wolfgang, I have been getting them too.

Gordon.

Re: strange

[Jürgen Spitzmüller]

Am Dienstag, den 24.01.2017, 18:18 +0100 schrieb Wolfgang Engelmann:
> When I am sending a mail to the Lyx User group lyx-us...@lists.lyx.or
> g I am getting 
> always this message:
> Olen lomalla. Sähköpostia voi lähettää jollekin muulle
> henkilökunnastamme etunimi.sukun...@vskonetarvike.com tai
> vaihtoehtoisesti myy...@vskonetarvike.com

This is an out-of-office message of someone subscribed to the list.
Everybody posting to the lists gets this now.

> Although I definetely do not use this address nor is it in my address
> book. In addition I got today this mail 
> On 24.01.2017 18:06, mailmars...@fli.de wrote:
> > The following message was addressed to our organization using a
> > domain name that is being retired:
> >  
> >    From:  engelm...@uni-tuebingen.de
> >    To:eildert.groenev...@fli.bund.de
> >    Subject:   getting rid of white space in graphic
> > 
> > Please update your email address lists by changing any addresses
> > that refer to fli.bund.de to our new domain name of fli.de.

Similar.

Of course such automated messages should not go to mailing lists. But
these things happen.

Jürgen

signature.asc
Description: This is a digitally signed message part

strange

[Wolfgang Engelmann]

When I am sending a mail to the Lyx User group lyx-users@lists.lyx.org I 
am getting


always this message:

Olen lomalla. Sähköpostia voi lähettää jollekin muulle 
henkilökunnastammeetunimi.sukun...@vskonetarvike.com  tai 
vaihtoehtoisestimyy...@vskonetarvike.com


Although I definetely do not use this address nor is it in my address 
book. In addition I got today this mail

On 24.01.2017 18:06, mailmars...@fli.de wrote:
The following message was addressed to our organization using a 
*domain name* that is being *retired*:


*From:* engelm...@uni-tuebingen.de
*To:*eildert.groenev...@fli.bund.de
*Subject:*   getting rid of white space in graphic

Please update your email address lists by changing any addresses that 
refer to *fli.bund.de* to our new domain name of *fli.de*.


This notification is for your information only - your original message 
*has been delivered* to the intended recipient.


FLI MailMarshal
*Email Content Security*

Friedrich-Loeffler-Institut
Bundesforschungsinstitut für Tiergesundheit
Federal Research Institute for Animal Health


What could I do about it?
Wolfgang

Re: Strange xxx-lyxformat-474.lyx files

[Dr Eberhard Lisse]

Rich,

LyX has a versioning system (by default).

It uses RCS, which used to be part of the XCode command line tools on
the Mac (and can still be installed via homebrew) and an Ubuntu
package by itself.  There should be some Windoze package too,
somewhere.

There is also SVN support for document preparation but it's way more
complicated :-)-O

el

On 2016-08-02 16:37, Rich Shepard wrote:
[...]
> When I'm working on a project and prior verions need to be retained
> I create a subversion directory for them and commit changes when
> they're made.
> 
> Thanks,
> 
> Rich
> 

Re: Strange xxx-lyxformat-474.lyx files

[Dr Eberhard Lisse]

I got Time Machine running and am VERY diligent with Unison :-)-O, but
of course once can always run ... rm -v ...

But,

find ~/ -name '*.lyx' -exec  grep -h \\lyxformat {} \; | sort| uniq

shows that I have LyX files from 26 different versions lying around
:-)-O

el

On 2016-08-02 16:31, Steve Litt wrote:
> On Tue, 2 Aug 2016 15:26:42 +0100
> Dr Eberhard Lisse  wrote:
> 
>> find ~/ -name '*-lyxformat-*.lyx' -exec rm {] \;
> 
> Danger Will Robinson!
> 
> I personally would never run a one-liner that does deletions. My pencil
> has an eraser because I make mistakes. A mistake with such a one liner
> could do horrible things. I'd do something like this:
> 
> find ~/ -name '*-lyxformat-*.lyx' > danger.sh
> ### Edit danger.sh, prepend each line with "rm "
> ### Completely check danger.sh
> . ./danger.sh
> 
> My way is sort of like "What you see is what you get." The 1liner way
> is more like "You asked for it, you got it."
> 
> Did I mention that I make mistakes.
>  
> SteveT
> 
> Steve Litt 
> July 2016 featured book: Troubleshooting Techniques
>  of the Successful Technologist
> http://www.troubleshooters.com/techniques
> 

Re: Strange xxx-lyxformat-474.lyx files

[Påvel Nicklasson]

Thank you all for clarifications and suggestions! I suspected the files
were connected to the new 2.2 version, It's better to ask before deleting
files and discover doing something stupid too late.

2016-08-02 17:52 GMT+02:00 David L. Johnson :

> On 08/02/2016 10:40 AM, Rich Shepard wrote:
>
> On Tue, 2 Aug 2016, David L. Johnson wrote:
>
> These are being created since the files were edited by the new version of
> LyX you installed, which uses a newer format. LyX then auto-saves them in
> the old format so that you can edit it, if you need to, with an older
> version of LyX. This seems to be a reasonable thing to do at the start of
> a new format, and will not occur when you edit files using LyX-2.2 that
> are already in the new format.
>
>
> David,
>
>   Thanks for the clarification. I don't recall seeing these files when
> previous versions (from 1.0 on) were upgraded.
>
>
> It was certainly not the case with every change of format --- and was
> probably added because someone got caught with a file they could not edit
> after going to a new version of LyX, then backing out of the upgrade for
> some reason.  I am not sure whether this feature had been added earlier ---
> I don't have such backups around except those created by lyx 2.2.
>
>
> --
>
> David L. Johnson
> Department of Mathematics
> Lehigh University
>
>

Re: Strange xxx-lyxformat-474.lyx files

[Kornel Benko]

Am Dienstag, 2. August 2016 um 11:52:31, schrieb David L. Johnson 

> On 08/02/2016 10:40 AM, Rich Shepard wrote:
> > On Tue, 2 Aug 2016, David L. Johnson wrote:
> >
> >> These are being created since the files were edited by the new 
> >> version of
> >> LyX you installed, which uses a newer format. LyX then auto-saves 
> >> them in
> >> the old format so that you can edit it, if you need to, with an older
> >> version of LyX. This seems to be a reasonable thing to do at the 
> >> start of
> >> a new format, and will not occur when you edit files using LyX-2.2 that
> >> are already in the new format.
> >
> > David,
> >
> >   Thanks for the clarification. I don't recall seeing these files when
> > previous versions (from 1.0 on) were upgraded.
> >
> >
> It was certainly not the case with every change of format --- and was 
> probably added because someone got caught with a file they could not 
> edit after going to a new version of LyX, then backing out of the 
> upgrade for some reason.  I am not sure whether this feature had been 
> added earlier --- I don't have such backups around except those created 
> by lyx 2.2.
> 

File 'README' suggests to read 'NEWS'.
File 'NEWS' suggests to read 'RELEASE-NOTES'.

There it is described in the last paragraph.

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: Strange xxx-lyxformat-474.lyx files

[David L. Johnson]

On 08/02/2016 10:40 AM, Rich Shepard wrote:

On Tue, 2 Aug 2016, David L. Johnson wrote:

These are being created since the files were edited by the new 
version of
LyX you installed, which uses a newer format. LyX then auto-saves 
them in

the old format so that you can edit it, if you need to, with an older
version of LyX. This seems to be a reasonable thing to do at the 
start of

a new format, and will not occur when you edit files using LyX-2.2 that
are already in the new format.


David,

  Thanks for the clarification. I don't recall seeing these files when
previous versions (from 1.0 on) were upgraded.


It was certainly not the case with every change of format --- and was 
probably added because someone got caught with a file they could not 
edit after going to a new version of LyX, then backing out of the 
upgrade for some reason.  I am not sure whether this feature had been 
added earlier --- I don't have such backups around except those created 
by lyx 2.2.



--
 
David L. Johnson

Department of Mathematics
Lehigh University

Re: Strange xxx-lyxformat-474.lyx files

[Rich Shepard]

On Tue, 2 Aug 2016, Jürgen Spitzmüller wrote:


Note that if you specify a backup directory in Tools > Preferences >
Paths, these files will end up there instead of the working directory,
which might disturb you less.


Jürgen,

  I'm not disturbed, just assumed they were backup files and deleted them.
No big deal.

  When I'm working on a project and prior verions need to be retained I
create a subversion directory for them and commit changes when they're made.

Thanks,

Rich

Re: Strange xxx-lyxformat-474.lyx files

[Jürgen Spitzmüller]

Am Dienstag, den 02.08.2016, 06:47 -0700 schrieb Rich Shepard:
> On Tue, 2 Aug 2016, Påvel Nicklasson wrote:
> 
> > I work on several projects in LyX. Lately I have noticed that in
> the same
> > folders as my .lyx files there is a second file called -lyxformat-
> 474.lyx.
> > For instance, if the regular file is called xxx.lyx. The second is
> called
> > xxx-lyxformat-474.lyx. The 474.lyx files seems to be old versions
> of the
> > regular files.
> 
>    I, too, have started to find these apparent backup files left in
> the
> document directory when I exit lyx. It would be nice for them to be
> cleaned
> up when the program exits, but I do it manually.

Note that if you specify a backup directory in Tools > Preferences >
Paths, these files will end up there instead of the working directory,
which might disturb you less.

Jürgen

> 
> Rich

signature.asc
Description: This is a digitally signed message part

Re: Strange xxx-lyxformat-474.lyx files

[Steve Litt]

On Tue, 2 Aug 2016 15:26:42 +0100
Dr Eberhard Lisse  wrote:

> find ~/ -name '*-lyxformat-*.lyx' -exec rm {] \;

Danger Will Robinson!

I personally would never run a one-liner that does deletions. My pencil
has an eraser because I make mistakes. A mistake with such a one liner
could do horrible things. I'd do something like this:

find ~/ -name '*-lyxformat-*.lyx' > danger.sh
### Edit danger.sh, prepend each line with "rm "
### Completely check danger.sh
. ./danger.sh

My way is sort of like "What you see is what you get." The 1liner way
is more like "You asked for it, you got it."

Did I mention that I make mistakes.
 
SteveT

Steve Litt 
July 2016 featured book: Troubleshooting Techniques
 of the Successful Technologist
http://www.troubleshooters.com/techniques

Re: Strange xxx-lyxformat-474.lyx files

[Rich Shepard]

On Tue, 2 Aug 2016, Richard Heck wrote:


It's a new feature with 2.2. When you load files with a new major release,
it has to be converted to the new format (which encodes various new
features). We had some cases where people tried to load files with 2.1 and
the file was for some reason corrupted. Of course, they had a backup. Or
not. So now we do not over- write the original file, but just rename it.


Richard,

  Works for me. When I upgrade I don't keep the older version installed. If
I work on a file created with a previous version I save the current flavor
and continue with that.

  I understand that others work differently so I appreciate you devs
accommodating their needs.

Regards,

Rich

Re: Strange xxx-lyxformat-474.lyx files

[Richard Heck]

On 08/02/2016 10:40 AM, Rich Shepard wrote:
> On Tue, 2 Aug 2016, David L. Johnson wrote:
>
>> These are being created since the files were edited by the new
>> version of
>> LyX you installed, which uses a newer format. LyX then auto-saves
>> them in
>> the old format so that you can edit it, if you need to, with an older
>> version of LyX. This seems to be a reasonable thing to do at the
>> start of
>> a new format, and will not occur when you edit files using LyX-2.2 that
>> are already in the new format.
>
> David,
>
>   Thanks for the clarification. I don't recall seeing these files when
> previous versions (from 1.0 on) were upgraded.

It's a new feature with 2.2. When you load files with a new major
release, it has
to be converted to the new format (which encodes various new features).
We had
some cases where people tried to load files with 2.1 and the file was
for some
reason corrupted. Of course, they had a backup. Or not. So now we do not
over-
write the original file, but just rename it.

Richard

Re: Strange xxx-lyxformat-474.lyx files

[Rich Shepard]

On Tue, 2 Aug 2016, David L. Johnson wrote:


These are being created since the files were edited by the new version of
LyX you installed, which uses a newer format. LyX then auto-saves them in
the old format so that you can edit it, if you need to, with an older
version of LyX. This seems to be a reasonable thing to do at the start of
a new format, and will not occur when you edit files using LyX-2.2 that
are already in the new format.


David,

  Thanks for the clarification. I don't recall seeing these files when
previous versions (from 1.0 on) were upgraded.

Regards,

Rich

Re: Strange xxx-lyxformat-474.lyx files

[Dr Eberhard Lisse]

find ~/ -name '*-lyxformat-*.lyx' -exec rm {] \;

el

On 2016-08-02 14:58, David L. Johnson wrote:
> On 08/02/2016 09:47 AM, Rich Shepard wrote:
>> On Tue, 2 Aug 2016, Påvel Nicklasson wrote:
>>
>>> I work on several projects in LyX. Lately I have noticed that in the
>>> same
>>> folders as my .lyx files there is a second file called
>>> -lyxformat-474.lyx.
>>> For instance, if the regular file is called xxx.lyx. The second is
>>> called
>>> xxx-lyxformat-474.lyx. The 474.lyx files seems to be old versions of the
>>> regular files.
>>
>>   I, too, have started to find these apparent backup files left in the
>> document directory when I exit lyx. It would be nice for them to be
>> cleaned
>> up when the program exits, but I do it manually.
>>
> These are being created since the files were edited by the new version
> of LyX you installed, which uses a newer format.  LyX then auto-saves
> them in the old format so that you can edit it, if you need to, with an
> older version of LyX.  This seems to be a reasonable thing to do at the
> start of a new format, and will not occur when you edit files using
> LyX-2.2 that are already in the new format.
> 
> -- 
>  
> David L. Johnson
> Department of Mathematics
> Lehigh University
> 

Re: Strange xxx-lyxformat-474.lyx files

[David L. Johnson]

On 08/02/2016 09:47 AM, Rich Shepard wrote:

On Tue, 2 Aug 2016, Påvel Nicklasson wrote:

I work on several projects in LyX. Lately I have noticed that in the 
same
folders as my .lyx files there is a second file called 
-lyxformat-474.lyx.
For instance, if the regular file is called xxx.lyx. The second is 
called

xxx-lyxformat-474.lyx. The 474.lyx files seems to be old versions of the
regular files.


  I, too, have started to find these apparent backup files left in the
document directory when I exit lyx. It would be nice for them to be 
cleaned

up when the program exits, but I do it manually.

These are being created since the files were edited by the new version 
of LyX you installed, which uses a newer format.  LyX then auto-saves 
them in the old format so that you can edit it, if you need to, with an 
older version of LyX.  This seems to be a reasonable thing to do at the 
start of a new format, and will not occur when you edit files using 
LyX-2.2 that are already in the new format.


--
 
David L. Johnson

Department of Mathematics
Lehigh University

Re: Strange xxx-lyxformat-474.lyx files

[Rich Shepard]

On Tue, 2 Aug 2016, Påvel Nicklasson wrote:


I work on several projects in LyX. Lately I have noticed that in the same
folders as my .lyx files there is a second file called -lyxformat-474.lyx.
For instance, if the regular file is called xxx.lyx. The second is called
xxx-lyxformat-474.lyx. The 474.lyx files seems to be old versions of the
regular files.


  I, too, have started to find these apparent backup files left in the
document directory when I exit lyx. It would be nice for them to be cleaned
up when the program exits, but I do it manually.

Rich

Strange xxx-lyxformat-474.lyx files

[Påvel Nicklasson]

I work on several projects in LyX. Lately I have noticed that in the same
folders as my .lyx files there is a second file called -lyxformat-474.lyx.
For instance, if the regular file is called xxx.lyx. The second is called
xxx-lyxformat-474.lyx. The 474.lyx files seems to be old versions of the
regular files.
I have no idea how och when the 474 files were created, certainly not by
me. The only major tampering I have done lately is upgrading to LyX 2.2. I
am on *Buntu 16.04 with LyX stable ppa added. Does anyone know what he 474
files are, and if it is OK to delete them?

Strange font copy and paste problem

[Murat Yildizoglu]

Maybe this is not a LyX problem, I am not sure. But I only observe this
with text pasted from LyX. I use LyX Version 2.1.2.2 for OSX 10.10.1.

I am testing a new text correction (spelling/grammar/usage) software for
French: Le Robert Correcteur (*LRC*). It does not come for a module for LyX
of course, but it can check the text that is already on the clipboard when
one types a keyboard shortcut.

When I select the text in LyX and activate the copy in the clipboard and
the keyboard shortcut for text verification, the pasted text comes without
the accented characters in LRC. I have set the document for using utf8 for
font encoding (I am not sure that this is relevant for the copied text),
and I use the Latin Modern Sans Unitype font for the screen fonts for sans
serif (this is a beamer doc), and Georgia for the roman fonts.

Even stranger: when I paste the text in a GMail window in Firefox or in
Safari, it comes complete with all the accented characters...

It seems that the problem is mainly with LRC, but I do not know if there is
a way to solve it, by changing an option in Lyx. It seems specific to LyX
because if I copy an accented text from TeXMaker, for example, I do not
observe it.

Any idea how I could tell LyX to send the copied text in a format that is
compatible with LRC (the documentation of LRC does not say a word about the
format expected by it unfortunately, but it should be standard format for
Mac because I do meet this proble with text pasted from elsewhere?

Best regards,

Murat




-- 
Prof. Murat Yildizoglu

Université Montesquieu Bordeaux IV
GREThA (UMR CNRS 5113)
Avenue Léon Duguit
33608 Pessac cedex
France

Bureau : E-331

mail: yildi-at-u-bordeaux4.fr

web: yildizoglu.info

Re: Strange font copy and paste problem

[Murat Yildizoglu]

Just to complete this, I also get the same problem when I paste the text
copied from LyX in a TextEdit window, so it does not seem to be specific to
Le Robert Correcteur.

2014-12-06 13:04 GMT+01:00 Murat Yildizoglu myi...@gmail.com:

 Maybe this is not a LyX problem, I am not sure. But I only observe this
 with text pasted from LyX. I use LyX Version 2.1.2.2 for OSX 10.10.1.

 I am testing a new text correction (spelling/grammar/usage) software for
 French: Le Robert Correcteur (*LRC*). It does not come for a module for
 LyX of course, but it can check the text that is already on the clipboard
 when one types a keyboard shortcut.

 When I select the text in LyX and activate the copy in the clipboard and
 the keyboard shortcut for text verification, the pasted text comes without
 the accented characters in LRC. I have set the document for using utf8 for
 font encoding (I am not sure that this is relevant for the copied text),
 and I use the Latin Modern Sans Unitype font for the screen fonts for sans
 serif (this is a beamer doc), and Georgia for the roman fonts.

 Even stranger: when I paste the text in a GMail window in Firefox or in
 Safari, it comes complete with all the accented characters...

 It seems that the problem is mainly with LRC, but I do not know if there
 is a way to solve it, by changing an option in Lyx. It seems specific to
 LyX because if I copy an accented text from TeXMaker, for example, I do not
 observe it.

 Any idea how I could tell LyX to send the copied text in a format that is
 compatible with LRC (the documentation of LRC does not say a word about the
 format expected by it unfortunately, but it should be standard format for
 Mac because I do meet this proble with text pasted from elsewhere?

 Best regards,

 Murat




 --
 Prof. Murat Yildizoglu

 Université Montesquieu Bordeaux IV
 GREThA (UMR CNRS 5113)
 Avenue Léon Duguit
 33608 Pessac cedex
 France

 Bureau : E-331

 mail: yildi-at-u-bordeaux4.fr

 web: yildizoglu.info




-- 
Prof. Murat Yildizoglu

Université Montesquieu Bordeaux IV
GREThA (UMR CNRS 5113)
Avenue Léon Duguit
33608 Pessac cedex
France

Bureau : E-331

mail: yildi-at-u-bordeaux4.fr

web: yildizoglu.info

Strange font copy and paste problem

[Murat Yildizoglu]

Maybe this is not a LyX problem, I am not sure. But I only observe this
with text pasted from LyX. I use LyX Version 2.1.2.2 for OSX 10.10.1.

I am testing a new text correction (spelling/grammar/usage) software for
French: Le Robert Correcteur (*LRC*). It does not come for a module for LyX
of course, but it can check the text that is already on the clipboard when
one types a keyboard shortcut.

When I select the text in LyX and activate the copy in the clipboard and
the keyboard shortcut for text verification, the pasted text comes without
the accented characters in LRC. I have set the document for using utf8 for
font encoding (I am not sure that this is relevant for the copied text),
and I use the Latin Modern Sans Unitype font for the screen fonts for sans
serif (this is a beamer doc), and Georgia for the roman fonts.

Even stranger: when I paste the text in a GMail window in Firefox or in
Safari, it comes complete with all the accented characters...

It seems that the problem is mainly with LRC, but I do not know if there is
a way to solve it, by changing an option in Lyx. It seems specific to LyX
because if I copy an accented text from TeXMaker, for example, I do not
observe it.

Any idea how I could tell LyX to send the copied text in a format that is
compatible with LRC (the documentation of LRC does not say a word about the
format expected by it unfortunately, but it should be standard format for
Mac because I do meet this proble with text pasted from elsewhere?

Best regards,

Murat




-- 
Prof. Murat Yildizoglu

Université Montesquieu Bordeaux IV
GREThA (UMR CNRS 5113)
Avenue Léon Duguit
33608 Pessac cedex
France

Bureau : E-331

mail: yildi-at-u-bordeaux4.fr

web: yildizoglu.info

Re: Strange font copy and paste problem

[Murat Yildizoglu]

Just to complete this, I also get the same problem when I paste the text
copied from LyX in a TextEdit window, so it does not seem to be specific to
Le Robert Correcteur.

2014-12-06 13:04 GMT+01:00 Murat Yildizoglu myi...@gmail.com:

 Maybe this is not a LyX problem, I am not sure. But I only observe this
 with text pasted from LyX. I use LyX Version 2.1.2.2 for OSX 10.10.1.

 I am testing a new text correction (spelling/grammar/usage) software for
 French: Le Robert Correcteur (*LRC*). It does not come for a module for
 LyX of course, but it can check the text that is already on the clipboard
 when one types a keyboard shortcut.

 When I select the text in LyX and activate the copy in the clipboard and
 the keyboard shortcut for text verification, the pasted text comes without
 the accented characters in LRC. I have set the document for using utf8 for
 font encoding (I am not sure that this is relevant for the copied text),
 and I use the Latin Modern Sans Unitype font for the screen fonts for sans
 serif (this is a beamer doc), and Georgia for the roman fonts.

 Even stranger: when I paste the text in a GMail window in Firefox or in
 Safari, it comes complete with all the accented characters...

 It seems that the problem is mainly with LRC, but I do not know if there
 is a way to solve it, by changing an option in Lyx. It seems specific to
 LyX because if I copy an accented text from TeXMaker, for example, I do not
 observe it.

 Any idea how I could tell LyX to send the copied text in a format that is
 compatible with LRC (the documentation of LRC does not say a word about the
 format expected by it unfortunately, but it should be standard format for
 Mac because I do meet this proble with text pasted from elsewhere?

 Best regards,

 Murat




 --
 Prof. Murat Yildizoglu

 Université Montesquieu Bordeaux IV
 GREThA (UMR CNRS 5113)
 Avenue Léon Duguit
 33608 Pessac cedex
 France

 Bureau : E-331

 mail: yildi-at-u-bordeaux4.fr

 web: yildizoglu.info




-- 
Prof. Murat Yildizoglu

Université Montesquieu Bordeaux IV
GREThA (UMR CNRS 5113)
Avenue Léon Duguit
33608 Pessac cedex
France

Bureau : E-331

mail: yildi-at-u-bordeaux4.fr

web: yildizoglu.info

Strange font copy and paste problem

[Murat Yildizoglu]

Maybe this is not a LyX problem, I am not sure. But I only observe this
with text pasted from LyX. I use LyX Version 2.1.2.2 for OSX 10.10.1.

I am testing a new text correction (spelling/grammar/usage) software for
French: Le Robert Correcteur (*LRC*). It does not come for a module for LyX
of course, but it can check the text that is already on the clipboard when
one types a keyboard shortcut.

When I select the text in LyX and activate the copy in the clipboard and
the keyboard shortcut for text verification, the pasted text comes without
the accented characters in LRC. I have set the document for using utf8 for
font encoding (I am not sure that this is relevant for the copied text),
and I use the Latin Modern Sans Unitype font for the screen fonts for sans
serif (this is a beamer doc), and Georgia for the roman fonts.

Even stranger: when I paste the text in a GMail window in Firefox or in
Safari, it comes complete with all the accented characters...

It seems that the problem is mainly with LRC, but I do not know if there is
a way to solve it, by changing an option in Lyx. It seems specific to LyX
because if I copy an accented text from TeXMaker, for example, I do not
observe it.

Any idea how I could tell LyX to send the copied text in a format that is
compatible with LRC (the documentation of LRC does not say a word about the
format expected by it unfortunately, but it should be standard format for
Mac because I do meet this proble with text pasted from elsewhere?

Best regards,

Murat




-- 
Prof. Murat Yildizoglu

Université Montesquieu Bordeaux IV
GREThA (UMR CNRS 5113)
Avenue Léon Duguit
33608 Pessac cedex
France

Bureau : E-331

mail: yildi-at-u-bordeaux4.fr

web: yildizoglu.info

Re: Strange font copy and paste problem

[Murat Yildizoglu]

Just to complete this, I also get the same problem when I paste the text
copied from LyX in a TextEdit window, so it does not seem to be specific to
Le Robert Correcteur.

2014-12-06 13:04 GMT+01:00 Murat Yildizoglu :

> Maybe this is not a LyX problem, I am not sure. But I only observe this
> with text pasted from LyX. I use LyX Version 2.1.2.2 for OSX 10.10.1.
>
> I am testing a new text correction (spelling/grammar/usage) software for
> French: Le Robert Correcteur (*LRC*). It does not come for a module for
> LyX of course, but it can check the text that is already on the clipboard
> when one types a keyboard shortcut.
>
> When I select the text in LyX and activate the copy in the clipboard and
> the keyboard shortcut for text verification, the pasted text comes without
> the accented characters in LRC. I have set the document for using utf8 for
> font encoding (I am not sure that this is relevant for the copied text),
> and I use the Latin Modern Sans Unitype font for the screen fonts for sans
> serif (this is a beamer doc), and Georgia for the roman fonts.
>
> Even stranger: when I paste the text in a GMail window in Firefox or in
> Safari, it comes complete with all the accented characters...
>
> It seems that the problem is mainly with LRC, but I do not know if there
> is a way to solve it, by changing an option in Lyx. It seems specific to
> LyX because if I copy an accented text from TeXMaker, for example, I do not
> observe it.
>
> Any idea how I could tell LyX to send the copied text in a format that is
> compatible with LRC (the documentation of LRC does not say a word about the
> format expected by it unfortunately, but it should be standard format for
> Mac because I do meet this proble with text pasted from elsewhere?
>
> Best regards,
>
> Murat
>
>
>
>
> --
> Prof. Murat Yildizoglu
>
> Université Montesquieu Bordeaux IV
> GREThA (UMR CNRS 5113)
> Avenue Léon Duguit
> 33608 Pessac cedex
> France
>
> Bureau : E-331
>
> mail: yildi-at-u-bordeaux4.fr
>
> web: yildizoglu.info
>



-- 
Prof. Murat Yildizoglu

Université Montesquieu Bordeaux IV
GREThA (UMR CNRS 5113)
Avenue Léon Duguit
33608 Pessac cedex
France

Bureau : E-331

mail: yildi-at-u-bordeaux4.fr

web: yildizoglu.info

Document stoped compileing with strange error: LaTeX Error: Missing begin{document}.

[Bruno Morgado]

Hi all,
I was writing the introduction to my PhD thesis and since the references to
some pictures were showing up as ?? I changed the label of one of those
pictures in the hopes that it solved the problem.

Well, it didn't, in fact I can't compile my thesis anymore.

Now it fails with the error LaTeX Error: Missing begin{document}

I tried to delete that picture to no avail, I also tried to create a new
document and copy past everything but it didn't work as well.

Any ideas?

Here is the complete log:

This is pdfTeX, Version 3.14159265-2.6-1.40.15 (TeX Live 2014) (preloaded
format=pdflatex 2014.7.11)  11 JUL 2014 18:13
entering extended mode
 restricted \write18 enabled.
 %-line parsing enabled.
**Thesis_Intro.tex
(./Thesis_Intro.tex
LaTeX2e 2014/05/01
Babel 3.9k and hyphenation patterns for 78 languages loaded.

(/usr/local/texlive/2014/texmf-dist/tex/latex/base/article.cls
Document Class: article 2007/10/19 v1.4h Standard LaTeX document class
(/usr/local/texlive/2014/texmf-dist/tex/latex/base/size10.clo
File: size10.clo 2007/10/19 v1.4h Standard LaTeX file (size option)
)
\c@part=\count79
\c@section=\count80
\c@subsection=\count81
\c@subsubsection=\count82
\c@paragraph=\count83
\c@subparagraph=\count84
\c@figure=\count85
\c@table=\count86
\abovecaptionskip=\skip41
\belowcaptionskip=\skip42
\bibindent=\dimen102
) (/usr/local/texlive/2014/texmf-dist/tex/latex/base/fontenc.sty
Package: fontenc 2005/09/27 v1.99g Standard LaTeX package
(/usr/local/texlive/2014/texmf-dist/tex/latex/base/t1enc.def
File: t1enc.def 2005/09/27 v1.99g Standard LaTeX file
LaTeX Font Info:Redeclaring font encoding T1 on input line 43.
)) (/usr/local/texlive/2014/texmf-dist/tex/latex/base/inputenc.sty
Package: inputenc 2014/04/30 v1.2b Input encoding file
\inpenc@prehook=\toks14
\inpenc@posthook=\toks15
(/usr/local/texlive/2014/texmf-dist/tex/latex/base/latin9.def
File: latin9.def 2014/04/30 v1.2b Input encoding file
)) (/usr/local/texlive/2014/texmf-dist/tex/latex/tools/array.sty
Package: array 2008/09/09 v2.4c Tabular extension package (FMi)
\col@sep=\dimen103
\extrarowheight=\dimen104
\NC@list=\toks16
\extratabsurround=\skip43
\backup@length=\skip44
) (/usr/local/texlive/2014/texmf-dist/tex/latex/float/float.sty
Package: float 2001/11/08 v1.3d Float enhancements (AL)
\c@float@type=\count87
\float@exts=\toks17
\float@box=\box26
\@float@everytoks=\toks18
\@floatcapt=\box27
) (/usr/local/texlive/2014/texmf-dist/tex/latex/units/units.sty
Package: units 1998/08/04 v0.9b Typesetting units
(/usr/local/texlive/2014/texmf-dist/tex/latex/base/ifthen.sty
Package: ifthen 2001/05/26 v1.1c Standard LaTeX ifthen package (DPC)
) (/usr/local/texlive/2014/texmf-dist/tex/latex/units/nicefrac.sty
Package: nicefrac 1998/08/04 v0.9b Nice fractions
\L@UnitsRaiseDisplaystyle=\skip45
\L@UnitsRaiseTextstyle=\skip46
\L@UnitsRaiseScriptstyle=\skip47
)) (/usr/local/texlive/2014/texmf-dist/tex/latex/base/textcomp.sty
Package: textcomp 2005/09/27 v1.99g Standard LaTeX package
Package textcomp Info: Sub-encoding information:
(textcomp)   5 = only ISO-Adobe without \textcurrency
(textcomp)   4 = 5 + \texteuro
(textcomp)   3 = 4 + \textohm
(textcomp)   2 = 3 + \textestimated + \textcurrency
(textcomp)   1 = TS1 - \textcircled - \t
(textcomp)   0 = TS1 (full)
(textcomp) Font families with sub-encoding setting implement
(textcomp) only a restricted character set as indicated.
(textcomp) Family '?' is the default used for unknown fonts.
(textcomp) See the documentation for details.
Package textcomp Info: Setting ? sub-encoding to TS1/1 on input line 71.
(/usr/local/texlive/2014/texmf-dist/tex/latex/base/ts1enc.def
File: ts1enc.def 2001/06/05 v3.0e (jk/car/fm) Standard LaTeX file
)
LaTeX Info: Redefining \oldstylenums on input line 266.
Package textcomp Info: Setting cmr sub-encoding to TS1/0 on input line 281.
Package textcomp Info: Setting cmss sub-encoding to TS1/0 on input line 282.
Package textcomp Info: Setting cmtt sub-encoding to TS1/0 on input line 283.
Package textcomp Info: Setting cmvtt sub-encoding to TS1/0 on input line 284.
Package textcomp Info: Setting cmbr sub-encoding to TS1/0 on input line 285.
Package textcomp Info: Setting cmtl sub-encoding to TS1/0 on input line 286.
Package textcomp Info: Setting ccr sub-encoding to TS1/0 on input line 287.
Package textcomp Info: Setting ptm sub-encoding to TS1/4 on input line 288.
Package textcomp Info: Setting pcr sub-encoding to TS1/4 on input line 289.
Package textcomp Info: Setting phv sub-encoding to TS1/4 on input line 290.
Package textcomp Info: Setting ppl sub-encoding to TS1/3 on input line 291.
Package textcomp Info: Setting pag sub-encoding to TS1/4 on input line 292.
Package textcomp Info: Setting pbk sub-encoding to TS1/4 on input line 293.
Package textcomp Info: Setting pnc sub-encoding to TS1/4 on input line 294.
Package textcomp Info: Setting pzc sub-encoding to TS1/4 on 

Re: Document stoped compileing with strange error: LaTeX Error: Missing begin{document}.

[Eisa Ayed]

This is normal behavior. Just compile the file twice after compiling the .bib 
file. Roughly: 

Pdflatex file.tex
Bibtex file.tex
Pdflatex file.tex
Pdflatex file.tex


Sent from my iPhone

 On Jul 11, 2014, at 8:16 PM, Bruno Morgado jb.morg...@gmail.com wrote:
 
 Hi all,
 I was writing the introduction to my PhD thesis and since the references to
 some pictures were showing up as ??

Re: Document stoped compileing with strange error: LaTeX Error: Missing begin{document}.

[Bruno Morgado]

Hi,
but how do I do that from Lyx?
-- 
Bruno Morgado
Sent with Airmail

On 11 Jul 2014 at 18:43:55, Eisa Ayed (eisalen...@yahoo.com) wrote:

This is normal behavior. Just compile the file twice after compiling the .bib 
file. Roughly: 

Pdflatex file.tex
Bibtex file.tex
Pdflatex file.tex
Pdflatex file.tex


Sent from my iPhone

On Jul 11, 2014, at 8:16 PM, Bruno Morgado jb.morg...@gmail.com wrote:

Hi all,
I was writing the introduction to my PhD thesis and since the references to
some pictures were showing up as ??

Document stoped compileing with strange error: LaTeX Error: Missing begin{document}.

[Bruno Morgado]

Hi all,
I was writing the introduction to my PhD thesis and since the references to
some pictures were showing up as ?? I changed the label of one of those
pictures in the hopes that it solved the problem.

Well, it didn't, in fact I can't compile my thesis anymore.

Now it fails with the error LaTeX Error: Missing begin{document}

I tried to delete that picture to no avail, I also tried to create a new
document and copy past everything but it didn't work as well.

Any ideas?

Here is the complete log:

This is pdfTeX, Version 3.14159265-2.6-1.40.15 (TeX Live 2014) (preloaded
format=pdflatex 2014.7.11)  11 JUL 2014 18:13
entering extended mode
 restricted \write18 enabled.
 %-line parsing enabled.
**Thesis_Intro.tex
(./Thesis_Intro.tex
LaTeX2e 2014/05/01
Babel 3.9k and hyphenation patterns for 78 languages loaded.

(/usr/local/texlive/2014/texmf-dist/tex/latex/base/article.cls
Document Class: article 2007/10/19 v1.4h Standard LaTeX document class
(/usr/local/texlive/2014/texmf-dist/tex/latex/base/size10.clo
File: size10.clo 2007/10/19 v1.4h Standard LaTeX file (size option)
)
\c@part=\count79
\c@section=\count80
\c@subsection=\count81
\c@subsubsection=\count82
\c@paragraph=\count83
\c@subparagraph=\count84
\c@figure=\count85
\c@table=\count86
\abovecaptionskip=\skip41
\belowcaptionskip=\skip42
\bibindent=\dimen102
) (/usr/local/texlive/2014/texmf-dist/tex/latex/base/fontenc.sty
Package: fontenc 2005/09/27 v1.99g Standard LaTeX package
(/usr/local/texlive/2014/texmf-dist/tex/latex/base/t1enc.def
File: t1enc.def 2005/09/27 v1.99g Standard LaTeX file
LaTeX Font Info:Redeclaring font encoding T1 on input line 43.
)) (/usr/local/texlive/2014/texmf-dist/tex/latex/base/inputenc.sty
Package: inputenc 2014/04/30 v1.2b Input encoding file
\inpenc@prehook=\toks14
\inpenc@posthook=\toks15
(/usr/local/texlive/2014/texmf-dist/tex/latex/base/latin9.def
File: latin9.def 2014/04/30 v1.2b Input encoding file
)) (/usr/local/texlive/2014/texmf-dist/tex/latex/tools/array.sty
Package: array 2008/09/09 v2.4c Tabular extension package (FMi)
\col@sep=\dimen103
\extrarowheight=\dimen104
\NC@list=\toks16
\extratabsurround=\skip43
\backup@length=\skip44
) (/usr/local/texlive/2014/texmf-dist/tex/latex/float/float.sty
Package: float 2001/11/08 v1.3d Float enhancements (AL)
\c@float@type=\count87
\float@exts=\toks17
\float@box=\box26
\@float@everytoks=\toks18
\@floatcapt=\box27
) (/usr/local/texlive/2014/texmf-dist/tex/latex/units/units.sty
Package: units 1998/08/04 v0.9b Typesetting units
(/usr/local/texlive/2014/texmf-dist/tex/latex/base/ifthen.sty
Package: ifthen 2001/05/26 v1.1c Standard LaTeX ifthen package (DPC)
) (/usr/local/texlive/2014/texmf-dist/tex/latex/units/nicefrac.sty
Package: nicefrac 1998/08/04 v0.9b Nice fractions
\L@UnitsRaiseDisplaystyle=\skip45
\L@UnitsRaiseTextstyle=\skip46
\L@UnitsRaiseScriptstyle=\skip47
)) (/usr/local/texlive/2014/texmf-dist/tex/latex/base/textcomp.sty
Package: textcomp 2005/09/27 v1.99g Standard LaTeX package
Package textcomp Info: Sub-encoding information:
(textcomp)   5 = only ISO-Adobe without \textcurrency
(textcomp)   4 = 5 + \texteuro
(textcomp)   3 = 4 + \textohm
(textcomp)   2 = 3 + \textestimated + \textcurrency
(textcomp)   1 = TS1 - \textcircled - \t
(textcomp)   0 = TS1 (full)
(textcomp) Font families with sub-encoding setting implement
(textcomp) only a restricted character set as indicated.
(textcomp) Family '?' is the default used for unknown fonts.
(textcomp) See the documentation for details.
Package textcomp Info: Setting ? sub-encoding to TS1/1 on input line 71.
(/usr/local/texlive/2014/texmf-dist/tex/latex/base/ts1enc.def
File: ts1enc.def 2001/06/05 v3.0e (jk/car/fm) Standard LaTeX file
)
LaTeX Info: Redefining \oldstylenums on input line 266.
Package textcomp Info: Setting cmr sub-encoding to TS1/0 on input line 281.
Package textcomp Info: Setting cmss sub-encoding to TS1/0 on input line 282.
Package textcomp Info: Setting cmtt sub-encoding to TS1/0 on input line 283.
Package textcomp Info: Setting cmvtt sub-encoding to TS1/0 on input line 284.
Package textcomp Info: Setting cmbr sub-encoding to TS1/0 on input line 285.
Package textcomp Info: Setting cmtl sub-encoding to TS1/0 on input line 286.
Package textcomp Info: Setting ccr sub-encoding to TS1/0 on input line 287.
Package textcomp Info: Setting ptm sub-encoding to TS1/4 on input line 288.
Package textcomp Info: Setting pcr sub-encoding to TS1/4 on input line 289.
Package textcomp Info: Setting phv sub-encoding to TS1/4 on input line 290.
Package textcomp Info: Setting ppl sub-encoding to TS1/3 on input line 291.
Package textcomp Info: Setting pag sub-encoding to TS1/4 on input line 292.
Package textcomp Info: Setting pbk sub-encoding to TS1/4 on input line 293.
Package textcomp Info: Setting pnc sub-encoding to TS1/4 on input line 294.
Package textcomp Info: Setting pzc sub-encoding to TS1/4 on 

Re: Document stoped compileing with strange error: LaTeX Error: Missing begin{document}.

[Eisa Ayed]

This is normal behavior. Just compile the file twice after compiling the .bib 
file. Roughly: 

Pdflatex file.tex
Bibtex file.tex
Pdflatex file.tex
Pdflatex file.tex


Sent from my iPhone

 On Jul 11, 2014, at 8:16 PM, Bruno Morgado jb.morg...@gmail.com wrote:
 
 Hi all,
 I was writing the introduction to my PhD thesis and since the references to
 some pictures were showing up as ??

Re: Document stoped compileing with strange error: LaTeX Error: Missing begin{document}.

[Bruno Morgado]

Hi,
but how do I do that from Lyx?
-- 
Bruno Morgado
Sent with Airmail

On 11 Jul 2014 at 18:43:55, Eisa Ayed (eisalen...@yahoo.com) wrote:

This is normal behavior. Just compile the file twice after compiling the .bib 
file. Roughly: 

Pdflatex file.tex
Bibtex file.tex
Pdflatex file.tex
Pdflatex file.tex


Sent from my iPhone

On Jul 11, 2014, at 8:16 PM, Bruno Morgado jb.morg...@gmail.com wrote:

Hi all,
I was writing the introduction to my PhD thesis and since the references to
some pictures were showing up as ??

Document stoped compileing with strange error: LaTeX Error: Missing begin{document}.

[Bruno Morgado]

Hi all,
I was writing the introduction to my PhD thesis and since the references to
some pictures were showing up as ?? I changed the label of one of those
pictures in the hopes that it solved the problem.

Well, it didn't, in fact I can't compile my thesis anymore.

Now it fails with the error LaTeX Error: Missing begin{document}

I tried to delete that picture to no avail, I also tried to create a new
document and copy past everything but it didn't work as well.

Any ideas?

Here is the complete log:

This is pdfTeX, Version 3.14159265-2.6-1.40.15 (TeX Live 2014) (preloaded
format=pdflatex 2014.7.11)  11 JUL 2014 18:13
entering extended mode
 restricted \write18 enabled.
 %&-line parsing enabled.
**Thesis_Intro.tex
(./Thesis_Intro.tex
LaTeX2e <2014/05/01>
Babel <3.9k> and hyphenation patterns for 78 languages loaded.

(/usr/local/texlive/2014/texmf-dist/tex/latex/base/article.cls
Document Class: article 2007/10/19 v1.4h Standard LaTeX document class
(/usr/local/texlive/2014/texmf-dist/tex/latex/base/size10.clo
File: size10.clo 2007/10/19 v1.4h Standard LaTeX file (size option)
)
\c@part=\count79
\c@section=\count80
\c@subsection=\count81
\c@subsubsection=\count82
\c@paragraph=\count83
\c@subparagraph=\count84
\c@figure=\count85
\c@table=\count86
\abovecaptionskip=\skip41
\belowcaptionskip=\skip42
\bibindent=\dimen102
) (/usr/local/texlive/2014/texmf-dist/tex/latex/base/fontenc.sty
Package: fontenc 2005/09/27 v1.99g Standard LaTeX package
(/usr/local/texlive/2014/texmf-dist/tex/latex/base/t1enc.def
File: t1enc.def 2005/09/27 v1.99g Standard LaTeX file
LaTeX Font Info:Redeclaring font encoding T1 on input line 43.
)) (/usr/local/texlive/2014/texmf-dist/tex/latex/base/inputenc.sty
Package: inputenc 2014/04/30 v1.2b Input encoding file
\inpenc@prehook=\toks14
\inpenc@posthook=\toks15
(/usr/local/texlive/2014/texmf-dist/tex/latex/base/latin9.def
File: latin9.def 2014/04/30 v1.2b Input encoding file
)) (/usr/local/texlive/2014/texmf-dist/tex/latex/tools/array.sty
Package: array 2008/09/09 v2.4c Tabular extension package (FMi)
\col@sep=\dimen103
\extrarowheight=\dimen104
\NC@list=\toks16
\extratabsurround=\skip43
\backup@length=\skip44
) (/usr/local/texlive/2014/texmf-dist/tex/latex/float/float.sty
Package: float 2001/11/08 v1.3d Float enhancements (AL)
\c@float@type=\count87
\float@exts=\toks17
\float@box=\box26
\@float@everytoks=\toks18
\@floatcapt=\box27
) (/usr/local/texlive/2014/texmf-dist/tex/latex/units/units.sty
Package: units 1998/08/04 v0.9b Typesetting units
(/usr/local/texlive/2014/texmf-dist/tex/latex/base/ifthen.sty
Package: ifthen 2001/05/26 v1.1c Standard LaTeX ifthen package (DPC)
) (/usr/local/texlive/2014/texmf-dist/tex/latex/units/nicefrac.sty
Package: nicefrac 1998/08/04 v0.9b Nice fractions
\L@UnitsRaiseDisplaystyle=\skip45
\L@UnitsRaiseTextstyle=\skip46
\L@UnitsRaiseScriptstyle=\skip47
)) (/usr/local/texlive/2014/texmf-dist/tex/latex/base/textcomp.sty
Package: textcomp 2005/09/27 v1.99g Standard LaTeX package
Package textcomp Info: Sub-encoding information:
(textcomp)   5 = only ISO-Adobe without \textcurrency
(textcomp)   4 = 5 + \texteuro
(textcomp)   3 = 4 + \textohm
(textcomp)   2 = 3 + \textestimated + \textcurrency
(textcomp)   1 = TS1 - \textcircled - \t
(textcomp)   0 = TS1 (full)
(textcomp) Font families with sub-encoding setting implement
(textcomp) only a restricted character set as indicated.
(textcomp) Family '?' is the default used for unknown fonts.
(textcomp) See the documentation for details.
Package textcomp Info: Setting ? sub-encoding to TS1/1 on input line 71.
(/usr/local/texlive/2014/texmf-dist/tex/latex/base/ts1enc.def
File: ts1enc.def 2001/06/05 v3.0e (jk/car/fm) Standard LaTeX file
)
LaTeX Info: Redefining \oldstylenums on input line 266.
Package textcomp Info: Setting cmr sub-encoding to TS1/0 on input line 281.
Package textcomp Info: Setting cmss sub-encoding to TS1/0 on input line 282.
Package textcomp Info: Setting cmtt sub-encoding to TS1/0 on input line 283.
Package textcomp Info: Setting cmvtt sub-encoding to TS1/0 on input line 284.
Package textcomp Info: Setting cmbr sub-encoding to TS1/0 on input line 285.
Package textcomp Info: Setting cmtl sub-encoding to TS1/0 on input line 286.
Package textcomp Info: Setting ccr sub-encoding to TS1/0 on input line 287.
Package textcomp Info: Setting ptm sub-encoding to TS1/4 on input line 288.
Package textcomp Info: Setting pcr sub-encoding to TS1/4 on input line 289.
Package textcomp Info: Setting phv sub-encoding to TS1/4 on input line 290.
Package textcomp Info: Setting ppl sub-encoding to TS1/3 on input line 291.
Package textcomp Info: Setting pag sub-encoding to TS1/4 on input line 292.
Package textcomp Info: Setting pbk sub-encoding to TS1/4 on input line 293.
Package textcomp Info: Setting pnc sub-encoding to TS1/4 on input line 294.
Package textcomp Info: Setting pzc sub-encoding to 

Re: Document stoped compileing with strange error: LaTeX Error: Missing begin{document}.

[Eisa Ayed]

This is normal behavior. Just compile the file twice after compiling the .bib 
file. Roughly: 

Pdflatex file.tex
Bibtex file.tex
Pdflatex file.tex
Pdflatex file.tex


Sent from my iPhone

> On Jul 11, 2014, at 8:16 PM, Bruno Morgado  wrote:
> 
> Hi all,
> I was writing the introduction to my PhD thesis and since the references to
> some pictures were showing up as ??

Re: Document stoped compileing with strange error: LaTeX Error: Missing begin{document}.

[Bruno Morgado]

Hi,
but how do I do that from Lyx?
-- 
Bruno Morgado
Sent with Airmail

On 11 Jul 2014 at 18:43:55, Eisa Ayed (eisalen...@yahoo.com) wrote:

This is normal behavior. Just compile the file twice after compiling the .bib 
file. Roughly: 

Pdflatex file.tex
Bibtex file.tex
Pdflatex file.tex
Pdflatex file.tex


Sent from my iPhone

On Jul 11, 2014, at 8:16 PM, Bruno Morgado  wrote:

Hi all,
I was writing the introduction to my PhD thesis and since the references to
some pictures were showing up as ??

Re: very strange problem with microtype

[Jürgen Spitzmüller]

2014-06-04 3:53 GMT+02:00 Richard Heck:

  On 06/03/2014 03:48 PM, Neal Becker wrote:

 But without microtype it hyphenates correctly


 Yes, I understand. But microtype modifies all kinds of things.


Also, the use of TeX font style switches is strongly discouraged in
LaTeX2e. I recommend to read An essential guide to LaTeX2e usage. Obsolete
commands and packages (sec. 2.1 in this case):
http://mirrors.ctan.org/info/l2tabu/english/l2tabuen.pdf

Jürgen

Re: very strange problem with microtype

[Neal Becker]

Jürgen Spitzmüller wrote:

 2014-06-04 3:53 GMT+02:00 Richard Heck:
 
  On 06/03/2014 03:48 PM, Neal Becker wrote:

 But without microtype it hyphenates correctly


 Yes, I understand. But microtype modifies all kinds of things.

 
 Also, the use of TeX font style switches is strongly discouraged in
 LaTeX2e. I recommend to read An essential guide to LaTeX2e usage. Obsolete
 commands and packages (sec. 2.1 in this case):
 http://mirrors.ctan.org/info/l2tabu/english/l2tabuen.pdf
 
 Jürgen

By TeX font style switches, you mean the {\em ...}?

This was produced automatically from bibtex.  The paragraph that produced the 
problem was from the bibliography, this was the .bbl file

Re: very strange problem with microtype

[Jürgen Spitzmüller]

2014-06-04 13:06 GMT+02:00 Neal Becker:

 By TeX font style switches, you mean the {\em ...}?


Yes.


 This was produced automatically from bibtex.  The paragraph that produced
 the
 problem was from the bibliography, this was the .bbl file


OK, then the bst file is to blame.

Jürgen

Re: very strange problem with microtype

[Neal Becker]

Well that would be IEEE.bst then


On Wed, Jun 4, 2014 at 7:42 AM, Jürgen Spitzmüller sp...@lyx.org wrote:

 2014-06-04 13:06 GMT+02:00 Neal Becker:

  By TeX font style switches, you mean the {\em ...}?


 Yes.


 This was produced automatically from bibtex.  The paragraph that produced
 the
 problem was from the bibliography, this was the .bbl file


 OK, then the bst file is to blame.

 Jürgen

Re: very strange problem with microtype

[Jürgen Spitzmüller]

2014-06-04 3:53 GMT+02:00 Richard Heck:

  On 06/03/2014 03:48 PM, Neal Becker wrote:

 But without microtype it hyphenates correctly


 Yes, I understand. But microtype modifies all kinds of things.


Also, the use of TeX font style switches is strongly discouraged in
LaTeX2e. I recommend to read An essential guide to LaTeX2e usage. Obsolete
commands and packages (sec. 2.1 in this case):
http://mirrors.ctan.org/info/l2tabu/english/l2tabuen.pdf

Jürgen

Re: very strange problem with microtype

[Neal Becker]

Jürgen Spitzmüller wrote:

 2014-06-04 3:53 GMT+02:00 Richard Heck:
 
  On 06/03/2014 03:48 PM, Neal Becker wrote:

 But without microtype it hyphenates correctly


 Yes, I understand. But microtype modifies all kinds of things.

 
 Also, the use of TeX font style switches is strongly discouraged in
 LaTeX2e. I recommend to read An essential guide to LaTeX2e usage. Obsolete
 commands and packages (sec. 2.1 in this case):
 http://mirrors.ctan.org/info/l2tabu/english/l2tabuen.pdf
 
 Jürgen

By TeX font style switches, you mean the {\em ...}?

This was produced automatically from bibtex.  The paragraph that produced the 
problem was from the bibliography, this was the .bbl file

Re: very strange problem with microtype

[Jürgen Spitzmüller]

2014-06-04 13:06 GMT+02:00 Neal Becker:

 By TeX font style switches, you mean the {\em ...}?


Yes.


 This was produced automatically from bibtex.  The paragraph that produced
 the
 problem was from the bibliography, this was the .bbl file


OK, then the bst file is to blame.

Jürgen

Re: very strange problem with microtype

[Neal Becker]

Well that would be IEEE.bst then


On Wed, Jun 4, 2014 at 7:42 AM, Jürgen Spitzmüller sp...@lyx.org wrote:

 2014-06-04 13:06 GMT+02:00 Neal Becker:

  By TeX font style switches, you mean the {\em ...}?


 Yes.


 This was produced automatically from bibtex.  The paragraph that produced
 the
 problem was from the bibliography, this was the .bbl file


 OK, then the bst file is to blame.

 Jürgen

Re: very strange problem with microtype

[Jürgen Spitzmüller]

2014-06-04 3:53 GMT+02:00 Richard Heck:

>  On 06/03/2014 03:48 PM, Neal Becker wrote:
>
> But without microtype it hyphenates correctly
>
>
> Yes, I understand. But microtype modifies all kinds of things.
>

Also, the use of TeX font style switches is strongly discouraged in
LaTeX2e. I recommend to read "An essential guide to LaTeX2e usage. Obsolete
commands and packages" (sec. 2.1 in this case):
http://mirrors.ctan.org/info/l2tabu/english/l2tabuen.pdf

Jürgen

Re: very strange problem with microtype

[Neal Becker]

Jürgen Spitzmüller wrote:

> 2014-06-04 3:53 GMT+02:00 Richard Heck:
> 
>>  On 06/03/2014 03:48 PM, Neal Becker wrote:
>>
>> But without microtype it hyphenates correctly
>>
>>
>> Yes, I understand. But microtype modifies all kinds of things.
>>
> 
> Also, the use of TeX font style switches is strongly discouraged in
> LaTeX2e. I recommend to read "An essential guide to LaTeX2e usage. Obsolete
> commands and packages" (sec. 2.1 in this case):
> http://mirrors.ctan.org/info/l2tabu/english/l2tabuen.pdf
> 
> Jürgen

By TeX font style switches, you mean the {\em ...}?

This was produced automatically from bibtex.  The paragraph that produced the 
problem was from the bibliography, this was the .bbl file

Re: very strange problem with microtype

[Jürgen Spitzmüller]

2014-06-04 13:06 GMT+02:00 Neal Becker:

> By TeX font style switches, you mean the {\em ...}?
>

Yes.


> This was produced automatically from bibtex.  The paragraph that produced
> the
> problem was from the bibliography, this was the .bbl file
>

OK, then the bst file is to blame.

Jürgen

Re: very strange problem with microtype

[Neal Becker]

Well that would be IEEE.bst then


On Wed, Jun 4, 2014 at 7:42 AM, Jürgen Spitzmüller  wrote:

> 2014-06-04 13:06 GMT+02:00 Neal Becker:
>
>>  By TeX font style switches, you mean the {\em ...}?
>>
>
> Yes.
>
>
>> This was produced automatically from bibtex.  The paragraph that produced
>> the
>> problem was from the bibliography, this was the .bbl file
>>
>
> OK, then the bst file is to blame.
>
> Jürgen
>
>
>

very strange problem with microtype

[Neal Becker]

I am finalizing my IEEE conf paper.  I added
\usepackage{microtype}

When I do that, one of the references is typeset with an extremely overfull 
hbox.  But the log says nothing about any overfull hbox!

Without microtype it's fine.

The offending item comes from this:

\bibitem{dvbs2-acm}
R.~Rinaldo, M.~A. Vazquez-Castro, and A.~Morello, ``{DVB‐S2 ACM} modes for
  {IP} and {MPEG} unicast applications,'' {\em International Journal of
  Satellite Communications and Networking}, 2004.

Here, the title 'International Journal...' sticks way out into the margin.

Any ideas?

Re: very strange problem with microtype

[Richard Heck]

On 06/03/2014 01:15 PM, Neal Becker wrote:

I am finalizing my IEEE conf paper.  I added
\usepackage{microtype}

When I do that, one of the references is typeset with an extremely overfull
hbox.  But the log says nothing about any overfull hbox!

Without microtype it's fine.

The offending item comes from this:

\bibitem{dvbs2-acm}
R.~Rinaldo, M.~A. Vazquez-Castro, and A.~Morello, ``{DVB‐S2 ACM} modes for
   {IP} and {MPEG} unicast applications,'' {\em International Journal of
   Satellite Communications and Networking}, 2004.

Here, the title 'International Journal...' sticks way out into the margin.


I wonder if it is refusing to break inside the brackets. Try \emph{ ... }?

rh

Re: very strange problem with microtype

[Neal Becker]

But without microtype it hyphenates correctly
On Jun 3, 2014 3:46 PM, Richard Heck rgh...@lyx.org wrote:

 On 06/03/2014 01:15 PM, Neal Becker wrote:

 I am finalizing my IEEE conf paper.  I added
 \usepackage{microtype}

 When I do that, one of the references is typeset with an extremely
 overfull
 hbox.  But the log says nothing about any overfull hbox!

 Without microtype it's fine.

 The offending item comes from this:

 \bibitem{dvbs2-acm}
 R.~Rinaldo, M.~A. Vazquez-Castro, and A.~Morello, ``{DVB‐S2 ACM} modes for
{IP} and {MPEG} unicast applications,'' {\em International Journal of
Satellite Communications and Networking}, 2004.

 Here, the title 'International Journal...' sticks way out into the margin.


 I wonder if it is refusing to break inside the brackets. Try \emph{ ... }?

 rh

Re: very strange problem with microtype

[Richard Heck]

On 06/03/2014 03:48 PM, Neal Becker wrote:


But without microtype it hyphenates correctly



Yes, I understand. But microtype modifies all kinds of things.

rh

On Jun 3, 2014 3:46 PM, Richard Heck rgh...@lyx.org 
mailto:rgh...@lyx.org wrote:


On 06/03/2014 01:15 PM, Neal Becker wrote:

I am finalizing my IEEE conf paper.  I added
\usepackage{microtype}

When I do that, one of the references is typeset with an
extremely overfull
hbox.  But the log says nothing about any overfull hbox!

Without microtype it's fine.

The offending item comes from this:

\bibitem{dvbs2-acm}
R.~Rinaldo, M.~A. Vazquez-Castro, and A.~Morello, ``{DVB‐S2
ACM} modes for
   {IP} and {MPEG} unicast applications,'' {\em International
Journal of
   Satellite Communications and Networking}, 2004.

Here, the title 'International Journal...' sticks way out into
the margin.


I wonder if it is refusing to break inside the brackets. Try
\emph{ ... }?

rh

very strange problem with microtype

[Neal Becker]

I am finalizing my IEEE conf paper.  I added
\usepackage{microtype}

When I do that, one of the references is typeset with an extremely overfull 
hbox.  But the log says nothing about any overfull hbox!

Without microtype it's fine.

The offending item comes from this:

\bibitem{dvbs2-acm}
R.~Rinaldo, M.~A. Vazquez-Castro, and A.~Morello, ``{DVB‐S2 ACM} modes for
  {IP} and {MPEG} unicast applications,'' {\em International Journal of
  Satellite Communications and Networking}, 2004.

Here, the title 'International Journal...' sticks way out into the margin.

Any ideas?

Re: very strange problem with microtype

[Richard Heck]

On 06/03/2014 01:15 PM, Neal Becker wrote:

I am finalizing my IEEE conf paper.  I added
\usepackage{microtype}

When I do that, one of the references is typeset with an extremely overfull
hbox.  But the log says nothing about any overfull hbox!

Without microtype it's fine.

The offending item comes from this:

\bibitem{dvbs2-acm}
R.~Rinaldo, M.~A. Vazquez-Castro, and A.~Morello, ``{DVB‐S2 ACM} modes for
   {IP} and {MPEG} unicast applications,'' {\em International Journal of
   Satellite Communications and Networking}, 2004.

Here, the title 'International Journal...' sticks way out into the margin.


I wonder if it is refusing to break inside the brackets. Try \emph{ ... }?

rh

Re: very strange problem with microtype

[Neal Becker]

But without microtype it hyphenates correctly
On Jun 3, 2014 3:46 PM, Richard Heck rgh...@lyx.org wrote:

 On 06/03/2014 01:15 PM, Neal Becker wrote:

 I am finalizing my IEEE conf paper.  I added
 \usepackage{microtype}

 When I do that, one of the references is typeset with an extremely
 overfull
 hbox.  But the log says nothing about any overfull hbox!

 Without microtype it's fine.

 The offending item comes from this:

 \bibitem{dvbs2-acm}
 R.~Rinaldo, M.~A. Vazquez-Castro, and A.~Morello, ``{DVB‐S2 ACM} modes for
{IP} and {MPEG} unicast applications,'' {\em International Journal of
Satellite Communications and Networking}, 2004.

 Here, the title 'International Journal...' sticks way out into the margin.


 I wonder if it is refusing to break inside the brackets. Try \emph{ ... }?

 rh

Re: very strange problem with microtype

[Richard Heck]

On 06/03/2014 03:48 PM, Neal Becker wrote:


But without microtype it hyphenates correctly



Yes, I understand. But microtype modifies all kinds of things.

rh

On Jun 3, 2014 3:46 PM, Richard Heck rgh...@lyx.org 
mailto:rgh...@lyx.org wrote:


On 06/03/2014 01:15 PM, Neal Becker wrote:

I am finalizing my IEEE conf paper.  I added
\usepackage{microtype}

When I do that, one of the references is typeset with an
extremely overfull
hbox.  But the log says nothing about any overfull hbox!

Without microtype it's fine.

The offending item comes from this:

\bibitem{dvbs2-acm}
R.~Rinaldo, M.~A. Vazquez-Castro, and A.~Morello, ``{DVB‐S2
ACM} modes for
   {IP} and {MPEG} unicast applications,'' {\em International
Journal of
   Satellite Communications and Networking}, 2004.

Here, the title 'International Journal...' sticks way out into
the margin.


I wonder if it is refusing to break inside the brackets. Try
\emph{ ... }?

rh

very strange problem with microtype

[Neal Becker]

I am finalizing my IEEE conf paper.  I added
\usepackage{microtype}

When I do that, one of the references is typeset with an extremely overfull 
hbox.  But the log says nothing about any overfull hbox!

Without microtype it's fine.

The offending item comes from this:

\bibitem{dvbs2-acm}
R.~Rinaldo, M.~A. Vazquez-Castro, and A.~Morello, ``{DVB‐S2 ACM} modes for
  {IP} and {MPEG} unicast applications,'' {\em International Journal of
  Satellite Communications and Networking}, 2004.

Here, the title 'International Journal...' sticks way out into the margin.

Any ideas?

Re: very strange problem with microtype

[Richard Heck]

On 06/03/2014 01:15 PM, Neal Becker wrote:

I am finalizing my IEEE conf paper.  I added
\usepackage{microtype}

When I do that, one of the references is typeset with an extremely overfull
hbox.  But the log says nothing about any overfull hbox!

Without microtype it's fine.

The offending item comes from this:

\bibitem{dvbs2-acm}
R.~Rinaldo, M.~A. Vazquez-Castro, and A.~Morello, ``{DVB‐S2 ACM} modes for
   {IP} and {MPEG} unicast applications,'' {\em International Journal of
   Satellite Communications and Networking}, 2004.

Here, the title 'International Journal...' sticks way out into the margin.


I wonder if it is refusing to break inside the brackets. Try \emph{ ... }?

rh

Re: very strange problem with microtype

[Neal Becker]

But without microtype it hyphenates correctly
On Jun 3, 2014 3:46 PM, "Richard Heck"  wrote:

> On 06/03/2014 01:15 PM, Neal Becker wrote:
>
>> I am finalizing my IEEE conf paper.  I added
>> \usepackage{microtype}
>>
>> When I do that, one of the references is typeset with an extremely
>> overfull
>> hbox.  But the log says nothing about any overfull hbox!
>>
>> Without microtype it's fine.
>>
>> The offending item comes from this:
>>
>> \bibitem{dvbs2-acm}
>> R.~Rinaldo, M.~A. Vazquez-Castro, and A.~Morello, ``{DVB‐S2 ACM} modes for
>>{IP} and {MPEG} unicast applications,'' {\em International Journal of
>>Satellite Communications and Networking}, 2004.
>>
>> Here, the title 'International Journal...' sticks way out into the margin.
>>
>
> I wonder if it is refusing to break inside the brackets. Try \emph{ ... }?
>
> rh
>
>

Re: very strange problem with microtype

[Richard Heck]

On 06/03/2014 03:48 PM, Neal Becker wrote:


But without microtype it hyphenates correctly



Yes, I understand. But microtype modifies all kinds of things.

rh

On Jun 3, 2014 3:46 PM, "Richard Heck" > wrote:


On 06/03/2014 01:15 PM, Neal Becker wrote:

I am finalizing my IEEE conf paper.  I added
\usepackage{microtype}

When I do that, one of the references is typeset with an
extremely overfull
hbox.  But the log says nothing about any overfull hbox!

Without microtype it's fine.

The offending item comes from this:

\bibitem{dvbs2-acm}
R.~Rinaldo, M.~A. Vazquez-Castro, and A.~Morello, ``{DVB‐S2
ACM} modes for
   {IP} and {MPEG} unicast applications,'' {\em International
Journal of
   Satellite Communications and Networking}, 2004.

Here, the title 'International Journal...' sticks way out into
the margin.


I wonder if it is refusing to break inside the brackets. Try
\emph{ ... }?

rh

strange centering behavior in float

[Liviu Andronic]

Dear all,
I'm seeing this strange behavior when centering a paragraph within a
table float. I see this  in both 2.0.6 and 2.1beta1.

In the attached document, each table float contains an ERT inset (for
subsequent use with Sweave) within a centered paragraph. If the ERT
inset is above the caption, then the following construct is used:
\begin{centering}
=
2+2
@
\par\end{centering}

The same construct is used if the ERT inset is below the caption _and_
there is an empty line below it (say, kept with a protected space).
But if I remove this line below, then this construct is used:
\centering{}=
2+2
@

The problem with this construct is that since it's on the same line as
the beginning of the chunk, it breaks Sweave compilation.

So is this inconsistency expected? And can it be avoided?

Regards,
Liviu



-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail


lyx_float_centering.20.lyx
Description: Binary data


lyx_float_centering.lyx
Description: Binary data

Re: strange centering behavior in float

[Csikos Bela]

Liviu Andronic landronim...@gmail.com írta:
Dear all,
I'm seeing this strange behavior when centering a paragraph within a
table float. I see this  in both 2.0.6 and 2.1beta1.

In the attached document, each table float contains an ERT inset (for
subsequent use with Sweave) within a centered paragraph. If the ERT
inset is above the caption, then the following construct is used:
\begin{centering}
=
2+2
@
\par\end{centering}

Liviu,

What is begin{centering}?

I know of \centering command and center environment as
\begin{center}, \end{center}.

Can you give a definition of centering environment or a link
where it is described?

Thanks,

bcsikos

Re: strange centering behavior in float

[Jürgen Spitzmüller]

Am Freitag 11 Oktober 2013, 14:56:19 schrieb Csikos Bela:
 What is begin{centering}?
 
 I know of \centering command and center environment as
 \begin{center}, \end{center}.
 
 Can you give a definition of centering environment or a link
 where it is described?

The centering environment internally just calls \centering ... 
\endcentering, with an empty \endcentering. You can do this with any switch, 
although it is rather the consequence of LaTeX's questionable environment 
implementation. LyX (mis)uses this, since it's easier than tracking switches.

Jürgen

Re: strange centering behavior in float

[Csikos Bela]

Jürgen Spitzmüller juer...@spitzmueller.org írta:
Am Freitag 11 Oktober 2013, 14:56:19 schrieb Csikos Bela:
 What is begin{centering}?
 
 I know of \centering command and center environment as
 \begin{center}, \end{center}.
 
 Can you give a definition of centering environment or a link
 where it is described?

The centering environment internally just calls \centering ... 
\endcentering, with an empty \endcentering. You can do this with any switch, 
although it is rather the consequence of LaTeX's questionable environment 
implementation. LyX (mis)uses this, since it's easier than tracking switches.

Thanks.

If I understand correctly in latex you can write

\begin{centering}, which becomes/equals \centering,

and 

\end{centering},  which becomes/equals \endcentering.

What do you mean by empty \endcentering ?
empty \endcentering.

I have a question as well related to centering but as I don't want
to hijack the thread I will ask it separately.

Thanks,

bcsikos

Re: strange centering behavior in float

[Jürgen Spitzmüller]

Csikos Bela wrote:
 What do you mean by empty \endcentering ?
 empty \endcentering.

It means that \end{centering} calls \endcentering only if this command exists. 
This is due to the way LaTeX environments are defined (the environment end 
does not call \endcentering directly, but \csname endcentering\endcsname, 
which sets \endcentering to \relax if it is not defined. Hence, LaTeX does not 
complain about an undefined \endcentering, but just treat it as if th command 
was empty.

Try
\newcommand\myname{Csikos Bela}

[...]

\begin{myname}
\end{myname}

Jürgen

strange centering behavior in float

[Liviu Andronic]

Dear all,
I'm seeing this strange behavior when centering a paragraph within a
table float. I see this  in both 2.0.6 and 2.1beta1.

In the attached document, each table float contains an ERT inset (for
subsequent use with Sweave) within a centered paragraph. If the ERT
inset is above the caption, then the following construct is used:
\begin{centering}
=
2+2
@
\par\end{centering}

The same construct is used if the ERT inset is below the caption _and_
there is an empty line below it (say, kept with a protected space).
But if I remove this line below, then this construct is used:
\centering{}=
2+2
@

The problem with this construct is that since it's on the same line as
the beginning of the chunk, it breaks Sweave compilation.

So is this inconsistency expected? And can it be avoided?

Regards,
Liviu



-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail


lyx_float_centering.20.lyx
Description: Binary data


lyx_float_centering.lyx
Description: Binary data

Re: strange centering behavior in float

[Csikos Bela]

Liviu Andronic landronim...@gmail.com írta:
Dear all,
I'm seeing this strange behavior when centering a paragraph within a
table float. I see this  in both 2.0.6 and 2.1beta1.

In the attached document, each table float contains an ERT inset (for
subsequent use with Sweave) within a centered paragraph. If the ERT
inset is above the caption, then the following construct is used:
\begin{centering}
=
2+2
@
\par\end{centering}

Liviu,

What is begin{centering}?

I know of \centering command and center environment as
\begin{center}, \end{center}.

Can you give a definition of centering environment or a link
where it is described?

Thanks,

bcsikos

Re: strange centering behavior in float

[Jürgen Spitzmüller]

Am Freitag 11 Oktober 2013, 14:56:19 schrieb Csikos Bela:
 What is begin{centering}?
 
 I know of \centering command and center environment as
 \begin{center}, \end{center}.
 
 Can you give a definition of centering environment or a link
 where it is described?

The centering environment internally just calls \centering ... 
\endcentering, with an empty \endcentering. You can do this with any switch, 
although it is rather the consequence of LaTeX's questionable environment 
implementation. LyX (mis)uses this, since it's easier than tracking switches.

Jürgen

Re: strange centering behavior in float

[Csikos Bela]

Jürgen Spitzmüller juer...@spitzmueller.org írta:
Am Freitag 11 Oktober 2013, 14:56:19 schrieb Csikos Bela:
 What is begin{centering}?
 
 I know of \centering command and center environment as
 \begin{center}, \end{center}.
 
 Can you give a definition of centering environment or a link
 where it is described?

The centering environment internally just calls \centering ... 
\endcentering, with an empty \endcentering. You can do this with any switch, 
although it is rather the consequence of LaTeX's questionable environment 
implementation. LyX (mis)uses this, since it's easier than tracking switches.

Thanks.

If I understand correctly in latex you can write

\begin{centering}, which becomes/equals \centering,

and 

\end{centering},  which becomes/equals \endcentering.

What do you mean by empty \endcentering ?
empty \endcentering.

I have a question as well related to centering but as I don't want
to hijack the thread I will ask it separately.

Thanks,

bcsikos