Re: Can't enter extra whitespace when editing.

2007-06-21 Thread Nick Hopton
In a recent message <[EMAIL PROTECTED]>, 
Typhoon <[EMAIL PROTECTED]> wrote.


[...]

Fair enough, but I wouldn't like to see this pass without putting in my
strongest possible support for the existing policy of forbidding extra
white spaces.



Allowing extra white space, knowing that it will be wiped out by LaTeX,
is at best useless, at worst misleading.

[...]

In fact you can insert white space that won't be ignored by LaTeX by 
inserting the sort of space you get by pressing the Alt-255 key 
combination. This can sometimes be useful for fine formatting of tables, 
for example.


Regards,
Nick.

--
Nick Hopton and Anne Hopton
Caversham, Reading, England
<[EMAIL PROTECTED]>



Re: Can't enter extra whitespace when editing.

2007-06-21 Thread Juergen Spitzmueller
Nick Hopton wrote:

> In fact you can insert white space that won't be ignored by LaTeX by
> inserting the sort of space you get by pressing the Alt-255 key
> combination. This can sometimes be useful for fine formatting of tables,
> for example.

For this, you can use "normal space" (C-M-) or protected space
(C-).

Jürgen



Re: LyX 1.44: Questionmarks instead of citations

2007-06-21 Thread Rainer M. Krug

Paul A. Rubin wrote:

Rainer M. Krug wrote:
I just managed to reproduce it with a default new file and two 
references. I attache the bibtex file, the lyx file, the resulting pdf 
and the latex log


When BibTeX citations mysteriously fail, usually the first thing I look 
for is an indigestible .bib file, which seems to be the problem here.  I 
compiled you doc using both LyX and export to LaTeX/manual compile, and 
both failed as they did for you.  Then I poked around the .bib file.


I remember - I had the same problems earlier.






This file was created with JabRef 2.2.
Encoding: ISO8859_1

@INPROCEEDINGS{Baard1997,
  author = {Baard, E.H.W.},
  title = {A conservation strategy for the geometric tortoise, 
Psammobates


I think that the character immediately after "tortoise," is causing 
BibTeX digestion problems.  I deleted it, save the .bib file, then 
deleted and reapplied the references in the LyX document, and it then 
compiled correctly.


Strange - I tried the same and it didn't. Could you please post or 
emailme the working example, then I can try it out?




I'm no expert on encodings, but if that character is a legitimate 
character in ISO8859_1, there's still the question of whether that's 
what BibTeX is using.  The LyX document seems to be set for "default" 
encoding (for British).  I don't know enough about BibTeX to know if it 
reads the encoding from the .bib file, from the .aux file (which 
presumably matches the source document), or whether it just uses 
'latin1' regardless.


Thanks for this info - with the encoding issues I am still quite confused.

Thanks
Rainer



/Paul






Understanding "Encoding" problems

2007-06-21 Thread Rainer M. Krug

Hi

I am sruggling understanding the encoding and if LaTeX / LyX use the 
same as BibTeX and which one I should use when and in a BibTex file, 
where I have different names from different countries with strange 
symbols, which would be the best encoding to choose?


Can somebody shed some light on this issue or refer me to a website 
which clarifies these issues?


Thanks

Rainer



Re: Understanding "Encoding" problems

2007-06-21 Thread Dominik Waßenhoven

Rainer M. Krug schrieb am 21.06.2007:

I am sruggling understanding the encoding and if LaTeX / LyX use the 
same as BibTeX and which one I should use when and in a BibTex file, 
where I have different names from different countries with strange 
symbols, which would be the best encoding to choose?


Can somebody shed some light on this issue or refer me to a website 
which clarifies these issues?


BibTeX does not support UTF-8 encoding at all, see e.g.
http://groups.google.com/group/comp.text.tex/msg/8aefd925c735c842
http://groups.google.com/group/comp.text.tex/msg/dadb7d2a89166e42
http://groups.google.com/group/de.comp.text.tex/msg/1293749bb77ae20d

(the last one is in German)

Regards,
Dominik.-




SOLVED: LyX 1.44: Questionmarks instead of citations

2007-06-21 Thread Rainer M. Krug

Hi

I solved the problem.

I used to use bibtexall, a script to run bibtex, which I did not copy 
over to my new machine.

I simply changed it back to the default.

Thanks everybody for your help,

Rainer

Paul A. Rubin wrote:

Rainer M. Krug wrote:
I just managed to reproduce it with a default new file and two 
references. I attache the bibtex file, the lyx file, the resulting pdf 
and the latex log


This is very strange and I don't have any ideas what could be the 
problem.




When BibTeX citations mysteriously fail, usually the first thing I look 
for is an indigestible .bib file, which seems to be the problem here.  I 
compiled you doc using both LyX and export to LaTeX/manual compile, and 
both failed as they did for you.  Then I poked around the .bib file.





This file was created with JabRef 2.2.
Encoding: ISO8859_1

@INPROCEEDINGS{Baard1997,
  author = {Baard, E.H.W.},
  title = {A conservation strategy for the geometric tortoise, 
Psammobates


I think that the character immediately after "tortoise," is causing 
BibTeX digestion problems.  I deleted it, save the .bib file, then 
deleted and reapplied the references in the LyX document, and it then 
compiled correctly.


I'm no expert on encodings, but if that character is a legitimate 
character in ISO8859_1, there's still the question of whether that's 
what BibTeX is using.  The LyX document seems to be set for "default" 
encoding (for British).  I don't know enough about BibTeX to know if it 
reads the encoding from the .bib file, from the .aux file (which 
presumably matches the source document), or whether it just uses 
'latin1' regardless.


/Paul






Re: Understanding "Encoding" problems

2007-06-21 Thread Rainer M. Krug

Dominik Waßenhoven wrote:

Rainer M. Krug schrieb am 21.06.2007:

I am sruggling understanding the encoding and if LaTeX / LyX use the 
same as BibTeX and which one I should use when and in a BibTex file, 
where I have different names from different countries with strange 
symbols, which would be the best encoding to choose?


Can somebody shed some light on this issue or refer me to a website 
which clarifies these issues?


BibTeX does not support UTF-8 encoding at all, see e.g.
http://groups.google.com/group/comp.text.tex/msg/8aefd925c735c842
http://groups.google.com/group/comp.text.tex/msg/dadb7d2a89166e42
http://groups.google.com/group/de.comp.text.tex/msg/1293749bb77ae20d


Thanks for the links - so in BibTex, I have to use \"{u} which I 
actually prefer as it makes it universal.


But what is the encoding issue in LaTeX? Is it the same issue?

Also - is there an easy way to identify these "characters" in a bibtex 
file? When I import from into JabRef, I sometimes get these strange 
characters which "corrupt" the BibTeX file for usage with LaTeX and my 
databases are quite large...


Rainer



(the last one is in German)

Regards,
Dominik.-







using different dictionaries in the same document

2007-06-21 Thread Giuseppe Vitalone

Hi, I'm working with Lyx 1.5rc1 for Windows.
The main language of my document is Italian, but I'm using many English
words, so I'd like to use both dictionaries for spell checking... how can I
do that? Thanks


Disabling lyx socket

2007-06-21 Thread Paniez Paykari

Dear Sir/Madam,
 
When I want to do 'save' or 'accept all changes'
lyx does not respond anymore and the error message   'Disabling lyx socket'   
comes up.
How can I fix this?
 
Cheers
P. Paykari
_
The next generation of MSN Hotmail has arrived - Windows Live Hotmail
http://www.newhotmail.co.uk

Re: using different dictionaries in the same document

2007-06-21 Thread Helge Hafting

Giuseppe Vitalone wrote:

Hi, I'm working with Lyx 1.5rc1 for Windows.
The main language of my document is Italian, but I'm using many English
words, so I'd like to use both dictionaries for spell checking... how 
can I

do that? Thanks


LyX support this, as long as the spellchecker in use supports it.
I use it for mixed English/Norwegian.

Set the main language to the most-used language in the document.
You already do this.

For each english region in your document, do this:
1. Mark it
2. edit->Text style->customized...
3. Change the language to english, press apply

Save work by leaving the dialog open. You can then mark the
next english region and just hit apply again without
going through menus. (Don't maximise the LyX window,
leave some room for that dialog on your screen.)

You will notice that all your english stuff gets a "blue underline".
It will not be underlined in print of course, this is simply how
LyX marks it as "foreign language". Note that "foreign language"
does not work with hyperref. If you use hyperref, don't mark
anything as english if it has hypertext references. (I.e.
words in headings, and possibly some other cases.)

When I spellcheck such documents, the correct wordlists are
used for each language. Of course you must have the english
wordlists for your spellchecker installed. This works well
with aspell, and it does not work with ispell. I don't know about
other spellceckers.

Note that LyX supports several versions of the english
language: "british", "english", and "american". These will
invoke different wordlists - experiment to find out
what works for you. I have to use "british".

Helge Hafting



Re: Can't enter extra whitespace when editing.

2007-06-21 Thread Helge Hafting

Nick Hopton wrote:
[...]
In fact you can insert white space that won't be ignored by LaTeX by 
inserting the sort of space you get by pressing the Alt-255 key 
combination. This can sometimes be useful for fine formatting of 
tables, for example.
Perhaps that works on some machines (windows?), mine just adds the text 
"255" just as if "alt" wasn't in use.

For fine adjustments that works in all cases, consider
ctrl+space (protected space) or ctrl+shift+space (protected thin space).
The latter is useful in other cases where
you want a small separator too, such as phone numbers
or as a thousands separator.

Helge Hafting







LyX 1.44: Questionmarks instead of citations

2007-06-21 Thread Rainer M. Krug

Hi

I know that it has been asked before, but I can't find it. So there it 
is again:


I am having problems with bibtex. I can insert the citations in lyx 
without problems, but when I run pdflatex, I get questionmarks insted of 
the references in the text and no bibliography. In addition, the LaTeX 
log says:



Package natbib Warning: Citation `Myers2000a' on page 5 undefined on 
input line

 82.


Package natbib Warning: Citation `Harper1977' on page 5 undefined on 
input line

 84.


for each reference.

Any ideas welcome,

Rainer

--
NEW EMAIL ADDRESS AND ADDRESS:

[EMAIL PROTECTED]

[EMAIL PROTECTED] WILL BE DISCONTINUED END OF MARCH

Rainer M. Krug, Dipl. Phys. (Germany), MSc Conservation
Biology (UCT)

Leslie Hill Institute for Plant Conservation
University of Cape Town
Rondebosch 7701
South Africa

Fax:+27 - (0)86 516 2782
Fax:+27 - (0)21 650 2440 (w)
Cell:   +27 - (0)83 9479 042

Skype:  RMkrug

email:  [EMAIL PROTECTED]
[EMAIL PROTECTED]


Cross-reference dialog

2007-06-21 Thread Nicolás

Hi!

I am experimenting some behaviour with the cross-reference dialog that, I think, is not the most appropriate or desirable one. I am 
using LyX 1.4.4, so I would like to know if this also happens in Lyx 1.5 before opening a bug report.


I have some labels created with help of ERT insets. To create references to these labels, I have to open the cross-reference dialog and 
write the name of the label in the "Label" field. Here I experience the first awkward behaviour. When the cross-reference dialog is 
opened LyX seems to initially place the cursor in the Label field (this is what I would like), but it removes it immediately after. As 
a result, I have to click with the mouse in the field in order to write the label name. Once I have done this, I use to press the 
"return" key. I would expect this to behave as clicking on the "OK" button. However, the result is equivalent to clicking on the 
"Apply" button, and the dialog remains open instead of being closed.


Cheers,
Nicolás


Re: Cross-reference dialog

2007-06-21 Thread Helge Hafting

Nicolás wrote:

Hi!

I am experimenting some behaviour with the cross-reference dialog 
that, I think, is not the most appropriate or desirable one. I am 
using LyX 1.4.4, so I would like to know if this also happens in Lyx 
1.5 before opening a bug report.


I have some labels created with help of ERT insets.


I always had the impression that if the label is created with ERT,
then the reference must be done using ERT and the \ref command
as well.  At least it works, and those capable of creating a label
in ERT can usually do a \ref in ERT too. 


I didn't know you could insert a LyX cross ref to an ERT label.

I have also found that I rarely need to insert a label via ERT.
When I need a label in the middle of some latex code, I
use two ERT boxes. The first contains latex code up to where
I need that label. Then I insert a normal LyX label immediately
after the ERT box. Finally, the last ERT box with the rest of the
latex code. 


Splitting up the ERT like this lets me use a normal LyX label,
which will show up in the cross reference dialog as usual.

Helge Hafting



Re: Disabling lyx socket

2007-06-21 Thread Richard Heck

Paniez Paykari wrote:

When I want to do 'save' or 'accept all changes'
lyx does not respond anymore and the error message   'Disabling lyx socket'   
comes up.
How can I fix this?
  
You'll need to give more information: What OS you are using, exactly 
when this happens (every time? or only sometimes?), what version of LyX 
you are using, etc.


Richard


--
==
Richard G Heck, Jr
Professor of Philosophy
Brown University
http://frege.brown.edu/heck/
==
Get my public key from http://sks.keyserver.penguin.de
Hash: 0x1DE91F1E66FFBDEC
Learn how to sign your email using Thunderbird and GnuPG at:
http://dudu.dyn.2-h.org/nist/gpg-enigmail-howto



Re: Understanding "Encoding" problems

2007-06-21 Thread Richard Heck

Rainer M. Krug wrote:
Thanks for the links - so in BibTex, I have to use \"{u} which I 
actually prefer as it makes it universal.

Yes, you should use in BibTeX whatever you would use in LaTeX.
Also - is there an easy way to identify these "characters" in a bibtex 
file? When I import from into JabRef, I sometimes get these strange 
characters which "corrupt" the BibTeX file for usage with LaTeX and my 
databases are quite large...
Check your encoding settings in JabRef. These are under the General tab 
of the Preferences dialog.


Richard

--
==
Richard G Heck, Jr
Professor of Philosophy
Brown University
http://frege.brown.edu/heck/
==
Get my public key from http://sks.keyserver.penguin.de
Hash: 0x1DE91F1E66FFBDEC
Learn how to sign your email using Thunderbird and GnuPG at:
http://dudu.dyn.2-h.org/nist/gpg-enigmail-howto



Re: help on keyboard shortcut

2007-06-21 Thread Richard Heck

Dominik Waßenhoven wrote:

Richard Heck schrieb am 20.06.2007:


Bob Alvarez wrote:

2. insert a space in the text after the ERT.
This seems tricky, as I can't see how just to insert a space. 

space-insert normal
That's not a normal space. I get an "inter-word" space by inserting 
that, and it shows up at the start of the line.


Richard


--
==
Richard G Heck, Jr
Professor of Philosophy
Brown University
http://frege.brown.edu/heck/
==
Get my public key from http://sks.keyserver.penguin.de
Hash: 0x1DE91F1E66FFBDEC
Learn how to sign your email using Thunderbird and GnuPG at:
http://dudu.dyn.2-h.org/nist/gpg-enigmail-howto



Re: Cross-reference dialog

2007-06-21 Thread Nicolás

I have also found that I rarely need to insert a label via ERT.
When I need a label in the middle of some latex code, I
use two ERT boxes. The first contains latex code up to where
I need that label. Then I insert a normal LyX label immediately
after the ERT box. Finally, the last ERT box with the rest of the
latex code.
Splitting up the ERT like this lets me use a normal LyX label,
which will show up in the cross reference dialog as usual.

Helge Hafting



In may case it is not a normal label, but one used to refer to a line number in an algorithm. I need to use the command \lnl, so I 
really need to use an ERT box.


Nicolás


pyxplot-produced eps-file insert in lyx-document

2007-06-21 Thread Wolfgang Engelmann
I produce diagrams with PyXPlot and export them as .eps files via Lyx into my 
document. 
Since Pyxplot uses Latex for text, I can set the same fontsize in the diagram 
as in my document. However, I have to make sure the figure is put into the 
float correctly. I am using twocolumn style and have figures which either fit 
in one of the columns or span both columns.

There are various ways of setting the size of the diagram for the export from 
Lyx. 
e.g.
size%
pt
mm,cm...
text%
col%
page%
theight% , pheight%

Which setting is suited? If I set the width of my diagram to e.g. 6cm, I could 
use 6cm width in the setting. However, the 6cm refer to the x-axis length, 
not including the y-axis text. Any setting takes care of this?

Wolfgang



Re: Can't enter extra whitespace when editing.

2007-06-21 Thread Typhoon
On Thu, 21 Jun 2007 08:31:28 +0100
Nick Hopton <[EMAIL PROTECTED]> wrote:

> In a recent message <[EMAIL PROTECTED]>, 
> Typhoon <[EMAIL PROTECTED]> wrote.
> 
> [...]
> >Fair enough, but I wouldn't like to see this pass without putting in
> >my strongest possible support for the existing policy of forbidding
> >extra white spaces.
> 
> >Allowing extra white space, knowing that it will be wiped out by
> >LaTeX, is at best useless, at worst misleading.
> [...]
> 
> In fact you can insert white space that won't be ignored by LaTeX by 
> inserting the sort of space you get by pressing the Alt-255 key 
> combination. This can sometimes be useful for fine formatting of
> tables, for example.

Of course - and you can get protected white spaces in any number of
other ways by using other Latex constructs. But that is neither useless
nor misleading. In my view, allowing "normal" spaces is both.

Cheers,
Alan

> 
> Regards,
> Nick.
> 
> -- 
> Nick Hopton and Anne Hopton
> Caversham, Reading, England
> <[EMAIL PROTECTED]>
> 
> 


Re: Can't enter extra whitespace when editing.

2007-06-21 Thread Paul A. Rubin

Typhoon wrote:

On Wed, 20 Jun 2007 19:47:20 +1000
Darren Freeman <[EMAIL PROTECTED]> wrote:


(thread continues on lyx-devel to save confusion!)


Fair enough, but I wouldn't like to see this pass without putting in my
strongest possible support for the existing policy of forbidding extra
white spaces.

Allowing extra white space, knowing that it will be wiped out by LaTeX,
is at best useless, at worst misleading.

Furthermore, this behaviour of Lyx is one of the things that I point
out to beginners to distinguish Lyx from their old word processor. It
is a simple, yet powerful, way to show them the advantages of leaving
formatting to the latex engine.

Cheers,
Alan



I second this.  My only complaint was that earlier versions nagged me in 
the status line whenever I hit the space bar twice in a row (which is a 
combination of old habits and bad typing, not a lack of understanding of 
why consecutive spaces won't work).  The current version only nags the 
first time, which I think is ideal.


/Paul



Re: help on keyboard shortcut

2007-06-21 Thread Paul A. Rubin

Richard Heck wrote:


2. insert a space in the text after the ERT.

This seems tricky, as I can't see how just to insert a space.


Indeed.  I crabbed once about the fact that trailing spaces are 
eliminated when an LFUN is processed.  Don't know if anyone entered an 
enhancement request for a way to insert an ordinary space.


But this 
will do:
   self-insert a b; delete-backward; char-backward; delete-backward; 
char-forward

So the whole thing would be:
\bind "C-y""command-sequence ert-insert;  self-insert 
\noindent; char-forward; self-insert a b; delete-backward; 
char-backward; delete-backward; char-forward"

Or perhaps better yet:
   "command-sequence ert-insert; self-insert \noindent a; 
delete-backward; next-inset-toggle"

Then you get the space inside ERT, and the inset is collapsed for you.



If, as I suspect, Bob wants the space just to keep \noindent from 
running into the text, a somewhat simpler solution is


"command-sequence ert-insert; self-insert \noindent{}; char-forward;"

/Paul



Question about preview converters

2007-06-21 Thread killermike
I am still having problems with the use of .svg files on 1.5.0beta on my new 
Linux install (scroll down to previous message if interested).

It would seem that LyX is ignoring my settings for SVG>png (the preview 
format, I presume?) conversion and what I would like to know is: where are 
the default converter settings held? Knowing the name of this script or 
config file would be a great help.

Thanks for any help.

-- 
http://www.unmusic.co.uk - about me, music, geek sitcom etc.
http://www.unmusic.co.uk/amhs/ - alt.music.home-studio 



Re: Can't enter extra whitespace when editing.

2007-06-21 Thread Darren Freeman
On Thu, 2007-06-21 at 08:27 +1000, Typhoon wrote:
> On Wed, 20 Jun 2007 19:47:20 +1000
> Darren Freeman <[EMAIL PROTECTED]> wrote:
> 
> > (thread continues on lyx-devel to save confusion!)
> 
> Fair enough, but I wouldn't like to see this pass without putting in my
> strongest possible support for the existing policy of forbidding extra
> white spaces.
> 
> Allowing extra white space, knowing that it will be wiped out by LaTeX,
> is at best useless, at worst misleading.

Clearly you haven't read my original post because it was to the
lyx-devel list and the thread crossed over by mistake. Please let me set
the record straight before I find myself hearing about this for the next
month.

8<8<8<8<8<

Hi all,

once upon a time, I could type extra whitespace between words and then
it would magically go away when I left that region of text.

Now, extra space keypresses have no effect and I feel like I'm in a
straight-jacket. I can still insert a space *before* an existing space,
because I might be about to type a word between them, just not after
one. Anybody else get that feeling or prefer the old behaviour?

Also I point out that LyX still allows a permanent dangling space at the
end of a paragraph which is even less consistent with the current
... behaviour.

Have fun,
Darren