lyx graphical tour: bad images

Hi, Just looking at http://www.lyx.org/LGT/, I get bad images for a lot of the screenshots. I tried Firefox 1.5 and IE6 on Win2k. Cheers JP -- John Pye School of Mechanical and Manufacturing Engineering The University of New South Wales Sydney NSW 2052 Australia t +61 2 9385 5127 f +61 2

Re: degree symbol in LyX on Linux with Compose key

not get through. I am writing a thesis on heat transfer. I want my degree symbol! (and there's a higher degree I'm hoping for too :-P) Cheers JP Helge Hafting wrote: > John Pye wrote: >> Hi all >> >> Over on the user's list we've run out of ideas on this o

Re: degree symbol in LyX on Linux with Compose key

Hi Georg, Georg Baum wrote: > John Pye wrote: > > >> Hi Helge >> >> The issue here, as far as I can tell, is: why doesn't LyX accept these >> characters if they work fine in other X-windows applications on my >> machine? >> > > It is

Re: degree symbol in LyX on Linux with Compose key

It seems that part of the issue could be that Ubuntu has a local that uses unicode. Not sure what that means in detail, but perhaps it's a difference from Solaris? Whether there is a native compose key or not is not really the issue, AFAICT. The issue is: why would characters fail to appear in LyX

Re: degree symbol in LyX on Linux with Compose key

Andreas Vox wrote: > John Pye <[EMAIL PROTECTED]> writes: > > >> Hi all >> >> Over on the user's list we've run out of ideas on this one. Can anyone >> here offer any suggestions? >> >> http://article.gmane.org/gmane.editors.lyx

Re: degree symbol in LyX on Linux with Compose key

Jean-Pierre Chrétien wrote: > John Pye <[EMAIL PROTECTED]> writes: > > >> It seems that part of the issue could be that Ubuntu has a local that >> uses unicode. Not sure what that means in detail, but perhaps it's a >> difference from Solaris? >>

Usability and the "insert graphics" dialog

Hi all The following are some usability comments from my use of the LyX Graphics dialog. It's not user-support stuff, so I'm hoping it's appropriate to send it here. If these have been reported already, or have even been fixed (I am using 1.4.3 in Ubuntu 6.10) please disregard. I realise that this

Re: degree symbol in LyX on Linux with Compose key

ogram. So it looks like Qt and GTK perhaps maintain their own separate key-binding settings? Cheers JP John Pye wrote: > Andreas Vox wrote: > >> John Pye <[EMAIL PROTECTED]> writes: >> >> >> >>> Hi all >>> >>> Over on the

a *very* small thing re the homepage

Hi all I noticed that there is an example image with a platypus on the homepage. But the image showing the printed output appears to have the wrong aspect ratio (at least for me, with Firefox 2.0.0.2 on Ubuntu) Cheers JP

Problems with multi-file documents & pdflatex

Hi all Two problems with multi-file LyX documents. I think they are bugs/missing features, rather than me being a stoopid user so I'll take a gamble on that and post them here! First, when I use the 'view pdf (pdflatex)' command in LyX 1.4.3 (on Ubuntu 6.10) it doesn't always show the correct up-

Re: downsampling in pdflatex output?

Helge Hafting wrote: > John Pye wrote: >> Hi all >> >> I would like to know if there's a way I can easily downsample (or >> 'degrade') images in my LyX document when creating output using >> pdflatex. I have a mix of PNGs, PDFs, EPS and JPG in my do

DIA diagram file with embedded (linked?) bitmap fails to convert

Hi all I have set up a file type and converter for DIA diagram files in LyX. The first problem was that if the DIA file is compressed (settings in the DIA File..Save As window) then LyX recognises it as a 'gzip' type file, even though it has .dia file extension and is a value DIA file. The next

LyX document-build process (was Re: DIA diagram file with embedded (linked?) bitmap fails to convert)

Out of curiosity, has anyone ever considered embedding something like SCons into LyX? A python-based system for building 'targets' from disparate 'sources' -- in this case LyX documents, bitmaps, diagrams, SVGs, EPSs etc? The current system seems (from my rather superficial inspection) to revolve

Re: Rarely used keybindings?

Along these lines of standard key-bindings, I vote for ctrl-I to be used for creating italics, rather than ctrl-E, which I always slip off and press ctrl-R, with dangerous consequences if I have my hand poised over the 'enter' key! Does anyone else find this? JP Michael Gerz wrote: > Darren Free

Re: LyX document-build process

Sorry for a bit of a delay on this one. I thought I would follow up with some comments though. Firstly, Jean-Marc Lasgouttes wrote: > John> The current system seems (from my rather superficial inspection) > John> to revolve around lots of little script files written in Python; > > It produces the

Re: LyX document-build process

Hi Andre, Thanks for these comments. More follows: Andre Poenitz wrote: > On Tue, Jun 05, 2007 at 09:52:49PM +1000, John Pye wrote: > >> Sorry for a bit of a delay on this one. I thought I would follow up with >> some comments though. >> >> Firstly, &g

A few issues with LyX 1.5.3

Hi all I have a few issues/bugs with LyX 1.5.3 that I'd like to comment on. Firstly, the 'compressed' feature for LyX documents seems like a problem when using LyX files in a CVS/SVN repository, because one can easily change a file's type from binary to text and back again. This causes havoc with

Re: A few issues with LyX 1.5.3

Andre Poenitz wrote: > On Sat, Jan 12, 2008 at 10:12:31PM -0500, rgheck wrote: > >> John Pye wrote: >> >>> Firstly, the 'compressed' feature for LyX documents seems like a problem >>> when using LyX files in a CVS/SVN repository, because one c

Change tracking creates syntax errors in pdflatex

Hi all, I'm afraid I got ahead of myself a bit when I wrote the following :-( > ... the track-changes stage of my [...] on the whole works very nicely. An afternoon's worth of editing with track-changes turned on has resulted in a compound document, one file per chapter, that will no longer allow

Re: Change tracking creates syntax errors in pdflatex

Attached is a screenshot with the error from LyX, and the first one highlighted. It says "argument of \let has an extra }". Cheers JP Jürgen Spitzmüller wrote: > John Pye wrote: > >> what can I do to fix my document? >> > > For a start, post the er

Re: Change tracking creates syntax errors in pdflatex

John Pye wrote: > Hi all, > > I'm afraid I got ahead of myself a bit when I wrote the following :-( > >> ... the track-changes stage of my [...] on the whole works very nicely. >> > > An afternoon's worth of editing with track-changes turned on ha

Re: Change tracking creates syntax errors in pdflatex

ience :-( Cheers JP Jürgen Spitzmüller wrote: > John Pye wrote: > >> Log file is attached. >> > > Really just a shot in the dark, but does either of the following in preamble > change anything? > > a.) > > \renewcommand{\lyxadded}[3]{\bgroup \color{lyxadd

strange pdflatex output with view change tracking in footnotes

Hi all I spotted some strangeness with the visible 'change tracking' in pdflatex output. For example, when a newly-added (hence coloured blue) footnote rolls over onto the next page, it doesn't get its colouring on the next page. (see attached .lyx file and output screenshot) Also see the attache

Re: strange pdflatex output with view change tracking in footnotes

Hi Jürgen Jürgen Spitzmüller wrote: > John Pye wrote: > >> Looks like a bug, right? >> > > A bug in pdflatex. Should be fixed in recent releases of pdflatex. > Thanks for that. Your comment sent me off to check what version of pdflatex is provided by

Re: strange pdflatex output with view change tracking in footnotes

Jürgen Spitzmüller wrote: > Herbert Voss wrote: > >> \usepackage{pdfcolmk} >> > > which we automatically load in pdflatex-ct-mode (however, until 1.5.4svn, we > loaded it too early, i.e. before color). > I tried adding \usepackage{pdfcolmk} to my latex preamble in LyX (using version 1.

Re: #4832: missing converter dialog gives no information about originating format

LyX Ticket Tracker wrote: > #4832: missing converter dialog gives no information about originating format > > Comment: > > this does not look like the cause. can you give us some recipe how to > reproduce your problem? > I think perhaps the case where this arose could have been be from documen