Full XeTeX support
Now that Unicode is supported and everyone is looking towards version 1.6, I would like to suggest full support for XeTeX. It is currently the most comprehensive way to put Unicode characters in a TeX document. Another great feature is direct access to TrueType and OpenType fonts. LyX would have to check if XeTeX is available, and if it is, modify the font selection dialog to allow access to additional fonts. The appropriate commands would then be included in the preamble. It would also be nice to have XeTeX font selection commands (throught the fontspec package) available from the paragraph or character style dialogs. The major limitation of XeTeX right now is poor math support, but it is possible (with the "nomath" option) to have equations passed to plain TeX/LaTeX with the standard fonts, while having the XeTeX features available in text mode. You can see some of the capabilities of the program here: http://www.ctan.org/tex-archive/macros/xetex/latex/fontspec/fontspec.pdf
Re: Full-screen editing
> So my question is if full-screen editing is a feature that is > possible, interesting and desired in LyX? In my opinion it is well in- > line with the LyX-philosophy of focusing on the writing. I think this is a great idea. In addition, for this to work well, all actions should be available from the keyboard without going through menus. By the way, it is possible to get a true full screen in Word, but it takes quite a bit of fiddling.
Re: Windows binaries for 1.5.0svn
> 1.5.0 is going to be release soon but I have compiled today's > snapshot and put it at http://www.lyx.org/~bpeng/ (windows binary > using the official windows installer, dictionary installation does not > work). Thanks. By the way, I do prefer the official installer. Unfortunately I found two bugs within the first minute or so: 1. Chapter numbering bug (minor). I have a chapter that is in a separate file and included in the main document. The chapter is in a different (but compatible) style than the main document (the chapter uses report.cls and the main document uses a style that is derived from report.cls). I have it this way because I want to be able to print the chapter separately with different formatting. In rc2 this worked fine but in the svn version the chapter is numbered as 0 instead of the correct number (5). When I export or print the document, everything looks fine, so it's just a problem with how LyX displays things. 2. Subdocument bug (major). LyX occasionally crashes while switching between subdocuments. I can't reproduce it reliably. Here is the debug log: lyx: Disabling LyX socket. OkApplyCancelReadOnlyPolicy: No transition for input SMI_OKAY from state INITIAL OkApplyCancelReadOnlyPolicy: No transition for input SMI_OKAY from state INITIAL OkApplyCancelReadOnlyPolicy: No transition for input SMI_OKAY from state INITIAL Completed
Windows binaries for 1.5.0svn
It's approaching a month since the last release candidate. Could anyone please upload a more recent Windows binary? I using rc2 and the frequent crashes are very annoying. It looks like most of the bugs I'm experiencing have been fixed in the trunk. Like most Windows users, I don't have a compiler set up here, but surely somebody has a recent version compiled that he can share. I don't even need an installer; an archive of the files would be fine. I would appreciate it very much. Thank you.
Unicode characters don't display properly in citations
I have a citation where the author has the first name Angélique. The citation key in the text shows (Angélique M Lastname et al., 2001). It shows up properly in the PDF output. I also have a bibliography item with a Unicode character in the title. When I view it within the citation dialog, it shows up as multiple incorrect characters. Again, it shows up properly in the PDF output. The display font in LyX is one that has a full set of Unicode characters. I am using 1.5.0rc1 under Windows XP. The bibliography is set to Natbib mode.
Compose key does not work properly with LyX in Windows.
I am using Allchars (http://allchars.zwolnet.com/) to duplicate a Unix-style Compose key in Windows XP. The first time I compose a character in LyX it works fine. However, if I try any more characters, the wrong characters show up. I can work around this bug by switching to another window and switching back everytime I want to compose a character. I have not had this problem in any other application. The error happens in LyX 1.4.4 and 1.5.0beta2. Steps to reproduce in 1.5.0beta2: 1. Open a new LyX document. 2. Change the document encoding to UTF8. 3. Type Compose-a-" (for example). The character ä (a-umlaut) shows up (correct). 4. Type Compose-1-2. The character ä shows up again (incorrect). 5. Type Compose-o-c. The character ä shows up once again (incorrect). 6. Switch to another application window. 7. Switch back to the LyX window. 8. Type Compose-1-2. The character ½ (one-half) shows up (correct). 9. Type Compose-o-c. The character ½ shows up again (incorrect). Correct behavior: Should get 佩 on the first try. By the way, I also see another issue that only shows up in version 1.5.0beta2. I cannot create accented characters like ä, é, etc with the encoding set to the default. This was not the case in the older versions (pre-1.5).
Citations bug in Lyx 1.5.0 beta 2
There is a bug with the loading of bibliography from a Bibtex file. Lyx 1.5.0beta2 shows bibliography keys that start with capital letters in all lowercase. By default, JabRef sets the keys like Smith1998, but Lyx shows them like smith1998. As long as Lyx is internally consistent, this doesn't matter. However, when I open a file saved with Lyx 1.4.4, none of the citations work--they show up as question marks in the output. If I click on a citation, in the dialog the list on the left is in lowercase (smith1998, thomas1999, ...) but on the selected citations list on the right it is in uppercase (Smith1998). I can make the citation work by deleting Smith1998 and adding smith1998. However I have to do this for every citation in the file. The solution would be ensure that the case of bibliography keys is maintained when they are loaded into Lyx. In addition I suggest that Lyx treats bibliography keys in a case-insensitive manner, at least as an option. I am running under Windows XP and using Natbib mode.
