euro-symbol in math-mode
Hello, is there any way of using an euro-symbol in mathmode? (I want to create some exercises with the rule of three (Dreisatz)). I use the eurosym-package, but this works only in textmode. Thanks Robert
Re: Single Author, Single Year, Multiple Articles
As far as I know, the addition of a letter to the year, which is useful in the case you cite in the same paper 2 or more publications by the same author with different titles but published in the same year, depends from the specific citation style used and selected once and for all in the selection window in LyX where you also select the bib file. For example, econometrica, which is one of the citation styles proposed by LyX, manages the addition of a letter to the publication year in the needed cases. Pierfranco 2008/11/23 npierre [EMAIL PROTECTED] Hi All, I have an author, Wei, who wrote two articles in 2000. In the citation dialog, the bibtex keys show up as Wei2000a and Wei2000b. When I insert one or the other into the text, it prints as Wei (2000). How can I get Lyx to add an a or b to distinguish between the articles, e.g. Wei (2000b)? Thanks. Norbert Pierre
Re: euro-symbol in math-mode
Robert Neumann [EMAIL PROTECTED] schrieb: is there any way of using an euro-symbol in mathmode? If works out of the box with the unicode Euro symbol € in LyX 1.6. I use the eurosym-package, but this works only in textmode. You could try with text-in-math (pressing Ctrl-m in math mode). Günter
Re: Key bindings
Dov Feldstern [EMAIL PROTECTED] schrieb: Peleg Michaeli wrote: On Sat, 2008-11-22 at 20:28 +0200, Dov Feldstern wrote: They shouldn't all be bothering you, only the ones you include are activated. Probably it's cua -- that's the default. what exactly does your bind file look like? I'm attaching cua and hebrew here. The cua.bind is in usr/share/... and the hebrew.bind is in ~/.lyx1.5.1/bind/ The first line of hebrew.bind (\bind_file cua) is including cua.bind. I don't remember the rules in terms of whether you can override bindings, and they may also have changes since 1.5. Generally, you can overwrite bindings. However in this case it is more complicated: ./bind/cua.bind:\bind C-g error-next binds ^G, so LyX will not wait for ^G y. @ the LyX experts: Is there a way to unbind a key so that it can be used at basis for a set of multi-key bindings? The easiest thing to do may be to just copy cua.bind from /usr to your local lyx bind directory, rename it to mycua or something, Actually, there is no need to rename (other than clarity), as LyX will try the version in your personal LyXDir first. get rid of the C-g y in there, and include that in hebrew instead of cua. It will not matter where the new bindings are included as long as the original binding is commented out: - \bind C-g error-next + # \bind C-g error-next Günter
Helper function/shortcut
Hi, I'm looking for a way to insert (pre-formatted) text into a LyX document using a keyboard shortcut. For example, I'd like to insert i.e. when pressing a certain key combination. I tried to use the LyX function self-insert with the argument i.e., but with LyX 1.6 I only got the error message: Can not insert shortcut to the list. Is there any way to add pre-formatted text to a LyX document? For example, when inserting i.e. with the shortcut described above, I'd like to set i.e. in an italic style and with a thin space between the two characters. Is this possible with LyX 1.6? Thanks, Frank
Re: Key bindings
Guenter Milde wrote: Is there a way to unbind a key so that it can be used at basis for a set of multi-key bindings? In 1.6, \unbind ? /Konrad
Subfig(ure) in class Memoir
How to get subfigure captions in memoir without resorting to ERT? I am merging some documents into my thesis, and some of them contain subfigures. Now, the thesis class (kthesis.cls) is based upon memoir, which seem to have an issue with subfigure. (LatTeX Error: Command [EMAIL PROTECTED] already defined.). One of the suggested solution is using the subfig package instead. However, LyX automatically adds \usepackage{subfig} to the latex preamble when a subfigure caption is added to a figure via the GUI. This result in the above error. Can adding subfigure be avoided? Can I force LyX to use subfig instead? Or is there perhaps any other solution to this dilemma without resorting to ERT? LyX 1.5.3 under Linux. Thanks, Johan
Equation numbering
Hi: How can make the equation numbers to appear to the right of the equations in LyX 1.6? Thanks! * Fernando Díaz H, Ph.D. * Profesor de Economía y Finanzas Facultad de Ciencias Económicas y Empresariales Universidad de los Andes (56 2) 412-9650 [EMAIL PROTECTED] [EMAIL PROTECTED] Avda. San Carlos de Apoquindo 2200, Las Condes, Santiago Chile
DVI chokes on PNG Logo in fancy header
Hello, This must be a stupid question but I can't find a proper answer on the web. Does anyone know how to make this work? I get Latex errors like those: LaTeX Error: Cannot determine size of graphic in /home/younes/Documents/ Some links suggested that image magic should be installed; but it is: convert my_logo.png my_logo.eps just works. 'pdflatex' works fine but 'dvi' don't. I have this in my preamble: \rhead{} \rhead{\includegraphics[clip=,scale=.3] {graphics/my_logo.png}} Idea someone? Abdel.
Re: DVI chokes on PNG Logo in fancy header
Abdelrazak Younes [EMAIL PROTECTED] writes: 'pdflatex' works fine but 'dvi' don't. I have this in my preamble: \rhead{} \rhead{\includegraphics[clip=,scale=.3] {graphics/my_logo.png}} Idea someone? Err, ERT is not handled by LyX and including a png via includegraphics is not possible. Create the eps by hand or maybe use the following in your document instead: ert\rhead{/ert[your nice graphics]ert}/ert JMarc
Re: DVI chokes on PNG Logo in fancy header
Jean-Marc Lasgouttes wrote: Abdelrazak Younes [EMAIL PROTECTED] writes: 'pdflatex' works fine but 'dvi' don't. I have this in my preamble: \rhead{} \rhead{\includegraphics[clip=,scale=.3] {graphics/my_logo.png}} Idea someone? Err, ERT is not handled by LyX and including a png via includegraphics is not possible. I knew there was something obvious but couldn't find it :-) Create the eps by hand or maybe use the following in your document instead: ert\rhead{/ert[your nice graphics]ert}/ert I can't do that as this is in the preamble. Or can I just use the \rhead command in the document? If not, is there something like conditional include with LateX? Something like that (in pseudo C-like code): \includegraphics{ \engine == 'dvi' ? graphics/my_logo.eps : graphics/my_logo.png} } Thanks, Abdel.
Re: Equation numbering
Right click and choose Toggle Labeling/Numbering On Nov 24, 2008, at 7:35 AM, FERNANDO DIAZ wrote: Hi: How can make the equation numbers to appear to the right of the equations in LyX 1.6? Thanks! * Fernando Díaz H, Ph.D. * Profesor de Economía y Finanzas Facultad de Ciencias Económicas y Empresariales Universidad de los Andes (56 2) 412-9650 [EMAIL PROTECTED] [EMAIL PROTECTED] Avda. San Carlos de Apoquindo 2200, Las Condes, Santiago Chile
Re: Equation numbering
How can make the equation numbers to appear to the right of the equations in LyX 1.6? Normally (Insert Math numberedformula) gives the equation number, right justified, applicable in many journals and books. Maybe this is not what you want ? WAS
Re: DVI chokes on PNG Logo in fancy header
Abdelrazak Younes [EMAIL PROTECTED] writes: I can't do that as this is in the preamble. Or can I just use the \rhead command in the document? I think so, try it. If not, is there something like conditional include with LateX? Something like that (in pseudo C-like code): \includegraphics{ \engine == 'dvi' ? graphics/my_logo.eps : graphics/my_logo.png} } It is possible (latex is a full-fledge language, after all), but not needed here. Make a png file and an eps one, and use \includegraphics{graphics/my_logo} the right extension will be picked automatically. JMarc
Re: Helper function/shortcut
Frank Grimm wrote: Hi, I'm looking for a way to insert (pre-formatted) text into a LyX document using a keyboard shortcut. For example, I'd like to insert i.e. when pressing a certain key combination. I tried to use the LyX function self-insert with the argument i.e., but with LyX 1.6 I only got the error message: Can not insert shortcut to the list. That's a bug. I'm getting that message pretty much no matter what I try to do. Is there any way to add pre-formatted text to a LyX document? For example, when inserting i.e. with the shortcut described above, I'd like to set i.e. in an italic style and with a thin space between the two characters. Is this possible with LyX 1.6? Yes, it should be. You can do it inside your bind file for now. You'll need to use something like: command-sequence font-emph; self-insert i.e.; font-emph; space-insert normal Modify as required. rh
Re: Subfig(ure) in class Memoir
On Monday 24 November 2008, Johan Tegin wrote: How to get subfigure captions in memoir without resorting to ERT? I am merging some documents into my thesis, and some of them contain subfigures. Now, the thesis class (kthesis.cls) is based upon memoir, which seem to have an issue with subfigure. (LatTeX Error: Command [EMAIL PROTECTED] already defined.). One of the suggested solution is using the subfig package instead. However, LyX automatically adds \usepackage{subfig} to the latex preamble when a subfigure caption is added to a figure via the GUI. This result in the above error. Can adding subfigure be avoided? Can I force LyX to use subfig instead? Or is there perhaps any other solution to this dilemma without resorting to ERT? LyX 1.5.3 under Linux. Thanks, Johan Johan, I ran into exactly this problem a few months ago when I decided to convert a rather large document from book(KOMA-script) to memoir, to take advantage of some of the neat features in memoir. My solution (after trying various mechanisms to get subfigures to work) was to replace the figures containing subfigures with a single figure float, putting more than one image in one float. The only disadvantage I found is the lack of separate captions, which I overcame by using phrases such as on the left in the single caption referring to multiple images. -- Les ~~ Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html
Re: DVI chokes on PNG Logo in fancy header
Jean-Marc Lasgouttes wrote: Abdelrazak Younes [EMAIL PROTECTED] writes: I can't do that as this is in the preamble. Or can I just use the \rhead command in the document? I think so, try it. I confirm. If not, is there something like conditional include with LateX? Something like that (in pseudo C-like code): \includegraphics{ \engine == 'dvi' ? graphics/my_logo.eps : graphics/my_logo.png} } It is possible (latex is a full-fledge language, after all), but not needed here. Make a png file and an eps one, and use \includegraphics{graphics/my_logo} the right extension will be picked automatically. Even better, thanks! Abdel.
Going from custom charstyles to module
Hello I'm starting to move my real work to LyX 1.6 and I have problem with the new modules. I had in LyX 1.5 some semantic custom markup for citations in Latin and Old French in a mycharstyles.inc file # Personal character styles definition Format 2 CharStyle Latin LatexType Command LatexName latin Font Family Sans EndFont LabelFont Family Roman Color blue EndFont Preamble \newcommand{\latin}[1]{\og~#1~\fg} EndPreamble End CharStyle Ancien LatexType Command LatexName ancien Font Family Sans EndFont LabelFont Family Roman Color blue EndFont Preamble \newcommand{\ancien}[1]{\og~#1~\fg} EndPreamble End I have created a module in LyX 1.6 (I could not find any documentation about the syntax of modules and the new flexible insets) Latin.module #\DeclareLyXModule{Latin} #DescriptionBegin #Définit des styles spécifiques pour les textes en latin et en ancien français #DescriptionEnd #Charles de Miramon 24/11/08 Format 11 InsetLayout Latin LyxType charstyle LabelString Latin LatexType Command LatexName latin Font Family Sans EndFont LabelFont Family Roman Color blue EndFont Preamble \newcommand{\latin}[1]{\og~#1~\fg} EndPreamble End InsetLayout Ancien LyxType charstyle LabelString Ancien LatexType Command LatexName ancien Font Family Sans EndFont LabelFont Family Roman Color blue EndFont Preamble \newcommand{\ancien}[1]{\og~#1~\fg} EndPreamble End It works for new files but does not translate the old files. The old LyX code was : \begin_inset CharStyle Latin status inlined and the new one seems to be : \begin_inset Flex Latin status collapsed Questions : 1) Is there a way to automatically transform the old custom charstyle formatting to the module ? 2) Why do we have in the new syntax a 'status collapsed' ? Charstyles are not insets that can be closed or opened 3) I'm a bit mixed up between the old custom charstyles, flexible insets, modules. What is going to be deprecated ? Cheers, Charles -- http://www.kde-france.org
Re: Helper function/shortcut
Richard Heck wrote: Frank Grimm wrote: Hi, I'm looking for a way to insert (pre-formatted) text into a LyX document using a keyboard shortcut. For example, I'd like to insert i.e. when pressing a certain key combination. I tried to use the LyX function self-insert with the argument i.e., but with LyX 1.6 I only got the error message: Can not insert shortcut to the list. That's a bug. I'm getting that message pretty much no matter what I try to do. OK, the problem is that self-insert cannot be added to the list as a function. There's a reason for this, namely, that you don't really want to see the bindings for normal keys in that list, e.g.: \bind 2 self-insert The solution is to use this instead: command-sequence self-insert i.e. for the simple case. rh
Re: Subfig(ure) in class Memoir
Johan Tegin [EMAIL PROTECTED] writes: One of the suggested solution is using the subfig package instead. However, LyX automatically adds \usepackage{subfig} to the latex preamble when a subfigure caption is added to a figure via the GUI. This result in the above error. Can adding subfigure be avoided? Can I force LyX to use subfig instead? Or is there perhaps any other solution to this dilemma without resorting to ERT? LyX 1.6.0 has switched to using subfig instead of subfigure. Maybe an incentive to upgrade ? JMarc
Problems with installing GNU Aspell 0.60.6 on OSX 10.5.5
Hello, I have tried to install the Aspell-dictionary using the instructions from this site: http://wiki.lyx.org/Mac/MacSpelling#toc2 It worked so far, I downloaded Aspell and followed the above mentioned instructions, until I entered »make«. Then I have got the following message out of the terminal: »make: *** No targets specified and no makefile found. Stop. jzs-ibook-g4:aspell-0.60.6 stefan$« What did I do wrong? I entered everything exactly as mentioned. Would I have to install the dictionaries first?
Symbol in manual
Hi. I am curious about the symbol in the help documents. There is the sideways triangle used when referring to menu item, for example, Insert-Box. The - actually looks like a triangle in LyX. How do I insert a symbol like that? Thanks. Max
Re: Building LyX layout for Copernicus Journals, class definition and estimate of time span?
Maarten Smoorenburg wrote: Now I've added your suggestion; ClassOptions Other hess,ms End But, still it doesnot work, I get the error message when trying to define in Document Settings: /The layout file... is not usable. This is probably because a LaTeX class or style file required by it is not available./ Did you ToolsReconfigure? Richard
Re: Problems with installing GNU Aspell 0.60.6 on OSX 10.5.5
Do you have the mac developer tools installed? They are available for download (large requiring registration) on the Mac site. jezZiFeR wrote: »make: *** No targets specified and no makefile found. Stop. jzs-ibook-g4:aspell-0.60.6 stefan$« z
Re: Equation numbering
FERNANDO DIAZ wrote: Hi: How can make the equation numbers to appear to the right of the equations in LyX 1.6? If you're getting equation numbers on the left side, try adding 'reqno' as a class option in Document - Settings... - Document Class. /Paul
Re: Building LyX layout for Copernicus Journals, class definition and estimate of time span?
Yes sure... And now it is in the 'unavailable' part of the document class list of LyX... so what you suggest? On Mon, Nov 24, 2008 at 5:18 PM, Richard Heck [EMAIL PROTECTED] wrote: Maarten Smoorenburg wrote: Now I've added your suggestion; ClassOptions Other hess,ms End But, still it doesnot work, I get the error message when trying to define in Document Settings: /The layout file... is not usable. This is probably because a LaTeX class or style file required by it is not available./ Did you ToolsReconfigure? Richard
RE: Symbol in manual
I am curious about the symbol in the help documents. There is the sideways triangle used when referring to menu item, for example, Insert-Box. The - actually looks like a triangle in LyX. How do I insert a symbol like that? Insert-Special Character-Menu Separator. Thanks. Max Vincent
Re: Building LyX layout for Copernicus Journals, class definition and estimate of time span?
Maarten Smoorenburg wrote: Yes sure... And now it is in the 'unavailable' part of the document class list of LyX... so what you suggest? Then LyX for some reason isn't finding the LaTeX class file. That's when it lists things as unavailable. What is your layout file named? What is the class file named? Maybe you should post the layout. And also the configure.log file that's dumped in your user directory when you reconfigure. rh
Re: Symbol in manual
Max Bian wrote: Hi. I am curious about the symbol in the help documents. There is the sideways triangle used when referring to menu item, for example, Insert-Box. The - actually looks like a triangle in LyX. How do I insert a symbol like that? That particular symbol is under InsertSpecial Characters. rh
Lyx and BibDesk connection
I am new user to Lyx and I have been working on a Mac (10.5) with TeXShop and BibDesk successfully so far. I just updated to the latest Mac install for TeX and gave Lyx another try in v1.6 and want to do the switch. Here's my problem - whenever I try to send something from BibDesk to Lyx, I get the following error msg: Unable to open the LyX pipe at /Users/jrennstich/Library/ Application Support/LyX-1.6/.lyxpipe.in for writing. You should quit LyX and possibly remove the pipe manually if this error persists. The underlying system error code was 6 (Device not configured). I saw the post here http://wiki.lyx.org/Mac/Environment about changing the .MacOSX/environment.plist but I am simply not able to find the relevant files: neither the .lyxpipe.in, nor ~/.MacOSX/ environment.plist. Any help how to link Lyx and BibDesk successfully and help Lyx and BibDesk identify my .bib libraries would be greatly appreciated. I couldn't find that information in a search on here, my apologies, if this has been covered before :-( Needless to say, since I cannot find the lyxpipe.in nor the environment.plist, I am one of those sad Mac- users, who need a GUI and some guidance if that won't let me do the stuff I need to do... ;-) Thx, -Joachim
Re: Going from custom charstyles to module
Charles de Miramon wrote: Hello I'm starting to move my real work to LyX 1.6 and I have problem with the new modules. This seems mostly to be a problem with the new Flex insets. It doesn't matter whether you put the code into a module or into an inc file as far as this problem is concerned. I had in LyX 1.5 some semantic custom markup for citations in Latin and Old French in a mycharstyles.inc file # Personal character styles definition Format 2 CharStyle Latin LatexType Command LatexName latin Font Family Sans EndFont LabelFont Family Roman Color blue EndFont Preamble \newcommand{\latin}[1]{\og~#1~\fg} EndPreamble End CharStyle Ancien LatexType Command LatexName ancien Font Family Sans EndFont LabelFont Family Roman Color blue EndFont Preamble \newcommand{\ancien}[1]{\og~#1~\fg} EndPreamble End I have created a module in LyX 1.6 (I could not find any documentation about the syntax of modules and the new flexible insets) See the Customization manual, chapter 5, especially sections 5.2.1 and 5.3.6. Latin.module #\DeclareLyXModule{Latin} #DescriptionBegin #Définit des styles spécifiques pour les textes en latin et en ancien français #DescriptionEnd #Charles de Miramon 24/11/08 Format 11 InsetLayout Latin LyxType charstyle LabelString Latin LatexType Command LatexName latin Font Family Sans EndFont LabelFont Family Roman Color blue EndFont Preamble \newcommand{\latin}[1]{\og~#1~\fg} EndPreamble End InsetLayout Ancien LyxType charstyle LabelString Ancien LatexType Command LatexName ancien Font Family Sans EndFont LabelFont Family Roman Color blue EndFont Preamble \newcommand{\ancien}[1]{\og~#1~\fg} EndPreamble End It works for new files but does not translate the old files. The old LyX code was : \begin_inset CharStyle Latin status inlined and the new one seems to be : \begin_inset Flex Latin status collapsed Questions : 1) Is there a way to automatically transform the old custom charstyle formatting to the module ? This SHOULD work. As you see, LyX does update the file to the new format. What does the LyX code look like if you use your new InsetLayout definition? It's the disagreement between these that is causing the problem, I think. What you might want to do is just to put your old Format 2 code into a module and let LyX do the conversion to Format 11 for you. You can also run: python $LYXDIR/layout2layout.py oldlayout.module newlayout.module and see how LyX converts it, then just use newlayout.module instead of oldlayout.module. 2) Why do we have in the new syntax a 'status collapsed' ? Charstyles are not insets that can be closed or opened No, but they can have the sublabel, showing which charstyle they are. That's what this reflects. And in fact, they can be collapsable if you want them to be. The Decoration tag controls this. 3) I'm a bit mixed up between the old custom charstyles, flexible insets, modules. What is going to be deprecated ? There are no charstyles any more, only Flex insets. Modules are an entirely different matter. They are a more flexible alternative to include files. rh
Re: Going from custom charstyles to module
Richard Heck wrote: See the Customization manual, chapter 5, especially sections 5.2.1 and 5.3.6. OK. I missed that because it is not translated yet in French. This SHOULD work. As you see, LyX does update the file to the new format. What does the LyX code look like if you use your new InsetLayout definition? It's the disagreement between these that is causing the problem, I think. What you might want to do is just to put your old Format 2 code into a module and let LyX do the conversion to Format 11 for you. You can also run: python $LYXDIR/layout2layout.py oldlayout.module newlayout.module and see how LyX converts it, then just use newlayout.module instead of oldlayout.module. It worked. The main difference is that the script gives : InsetLayout CharStyle:Latin where my handcrafted version had InsetLayout Latin The 'Charstyle:' is not very elegant but seems to be necessary. And in fact, they can be collapsable if you want them to be. The Decoration tag controls this. What is the difference between Minimalistic and Conglomerate ? I do not see on the screen any difference. Would it be possible when your cursor is in a zone formatted with a custom charstyle to print in the status bar after the font formatting information something like 'Custom character style : Foo' ? Cheers, Charles -- http://www.kde-france.org
Re: lyx2lyx script broken (1.6.0 on Vista)
Jean-Marc Lasgouttes wrote: Completely infeasible on Windows. The loss of shared text would make the working set of the typical application mix grossly exceed even the absurd amounts of RAM available in typical machines today. The disk space problem would be even worse. I meant just for application which feel that they have to distribute their own version-of-the-day of whatever.dll. There is no reason to do it everywhere of course. Still not feasible, unfortunately, because that includes everything linked with any of the Microsoft C/C++ runtime DLLs. This is the central problem: if you build an application that uses anything in the MS C/C++ library (Microsoft combines the C and C++ standard libraries into a single DLL), which means pretty much anything built with a Microsoft C or C++ compiler, or with the Microsoft Platform SDK, you'll link against some specific version of one or more of the MSVC DLLs. You don't have much choice about which version you get - it depends on what version of the compiler or SDK you have installed, and what updates have been applied to it. For someone else to run that binary, they need that exact same version of the MSVC DLLs. In older versions of the Microsoft toolchain, you could just drop the MSVC DLLs into the same directory as your executable. That's no longer allowed (I think as of Visual Studio 2005 and Platform SDK 6.0). Now they have to be installed into the SxS tree. Microsoft's solution is for every application linked against any MSVC DLL to include the redistributable DLL package for that specific MSVC version as part of their installer package. So it's not the application developers who want you to install a dozen versions of the MSVC runtime. They don't know what versions you already have installed. There's no way to coordinate versions among unrelated applications. People build and distribute binaries, and they carry with them MSVC version requirements. -- Michael Wojcik Micro Focus Rhetoric Writing, Michigan State University
Re: lyx2lyx script broken (1.6.0 on Vista)
Andre Poenitz wrote: On Tue, Nov 18, 2008 at 03:47:45PM -0500, Michael Wojcik wrote: Jean-Marc Lasgouttes wrote: What's wrong with static linking? At least it goes away when the application goes away. Completely infeasible on Windows. ... Many people have done back-of-the-envelope calculations to demonstrate this; I think I did some myself, in a post to alt.folklore.computers some time back. Some time back I was disputing the sheer possibility to catch a virus using email. Still ... environments ... came up that made _not catching one_ an art... So things done a while back do not count in IT. That's one of the silliest generalizations I've seen in some time. People who ignore the history of IT are doomed to repeat it. Usually poorly. In this specific case, the situation has only gotten worse. However, I have no particular interest in demonstrating it. If you think static linking is feasible on Windows, go ahead and build LyX that way. Mac OS X pretty much shows that _not_ sharing shared libraries on an application level is a feasible approach to DLL hell. I wouldn't take anything Apple does as a model. I've used too many Apple products. And avoiding shared code in applications is a solution to DLL hell (which is a system administration problem, not an application architecture one) in the same way that walking is a solution to airplane safety. It's a lousy idea in any case, as anyone who remembers compiling all of BSD 4.2 to switch from local-files resolution to DNS remembers. Dynamic linking lets you fix the bug or add the feature in one place. So why go from libstdc++.so.5 to libstdc++.so.6 at all, if incompatible changes can be, as you seem to say, avoided? Because there are many changes that *are* compatible? I'm not a libstdc++ maintainer, so I don't know offhand what the differences in those two releases are; and I'm not going to trawl through the release notes to find out. But it's very rare that a bug fix, or even a new feature, needs to alter an existing API, so there's no reason for it to introduce incompatibility. (Maintaining undefined behavior isn't a compatibility issue. Applications that rely on undefined behavior are broken.) Dynamic linking is a good thing. It's worked very well on a number of OSes. Examples? Most mainframe OSes - all of the MVS and VM family, for example. Also IBM's midrange OSes from S/38 through AS/400 to iOS. Many Unix variants, such as SVR4 and AIX. I believe dynamic linking in VMS wasn't bad, though I only ever looked at it briefly. Worked pretty well on OS/2. For that matter, it often works well on Windows, when DLL management is done properly. It would work on Windows if Microsoft could figure out 1) how to version properly, and 2) how to maintain backward compatibility. And it's not like those are unsolved problems. I am happy to have learned now that these problems are solved. They were solved decades ago. -- Michael Wojcik Micro Focus Rhetoric Writing, Michigan State University
Re: lyx2lyx script broken (1.6.0 on Vista)
Andre Poenitz wrote: On Tue, Nov 18, 2008 at 03:42:52PM -0500, Michael Wojcik wrote: Andre Poenitz wrote: On Mon, Nov 17, 2008 at 11:07:05AM -0500, Paul A. Rubin wrote: I've worked on many projects that maintained backward compatibility with new releases of the API, and seen a great many more. Just for my curiosity: Which projects, which scope? Hmm. Off the top of my head, in roughly chronological order: - Various IBM internal-only projects, such as the E editor. - Early versions of Windows. The Windows 1.x to Windows 2.0 and Windows/286 transition maintained compatibility in the Windows API; Windows 1.x applications ran unchanged in the 2.0 family. - X11R3. The X11 API was layered correctly: as long as the server follows the protocol spec, it doesn't matter what it does under the covers. I added support for new hardware to the ddx layer; wrote new window managers with completely different look-and-feel from the standard ones; added extensions to X11 itself. None of that interfered with existing clients one bit. - The 4.3 BSD kernel. Extended multihead support in the console driver and wrote some drivers for new hardware. Enhanced the shared memory kernel option. Nothing that didn't want to use the new features needed to be recompiled. - A number of Micro Focus commercial products and components thereof: AAI, CSB, CCI, MFCC ... These are commercial APIs used by paying customers to build in-house and ISV commercial applications. Changing them and breaking existing mission-critical applications isn't good for business. But we release updates a few times a year for most of them. Take AAI, for example. AAI 1.0 came out in 1988, and had major new releases for the next 10 years. Typical AAI purchases were in the $10K to $300K range, with yearly maintenance fees. The 1998 release had a feature set probably five times as large as in the 1988 release and ran on a dozen more platforms (from 16-bit Windows to big iron). We still shipped, as one of the demos, the original 1988 demo source - unchanged. The *binaries* from 1988 still ran, unchanged. The 1988 AAI clients and servers interoperated with the 1998 ones, with no user intervention (just a bit of automatic protocol negotiation). Maintaining backward compatibility simply is not that hard. I am still pretty convinced that compatibility and progress are fairly incompatible notions when it comes to the development of _usable_ libraries. And I'll say that my experience as a professional software developer for 20 years, and as a hobbyist for a number of years prior to that, shows me otherwise. you try to provide everything and the kitchen sink, and end up with design and implementation decisions that need to be re-evaluated from time to time in the presence of new environments. Java and Python, or anything including a GUI comes to mind. I'll offer X11 as a counterexample. And in this case, we're talking C and C++ runtimes, which should conform to the ISO standard anyway. Ah... should they conform to the Standard or should they be compatible to older versions? To the standard. What is supposed to happen if an existing version does _not_ conform to the Standard? Since the standards attempt to codify existing practice, that rarely happens. The only case that comes to mind of an incompatible change in the C standard, between C90 (ISO 9899-1990) and C99, is the choice of return code semantics for snprintf when it was added to the standard. There were two implementations with different semantics; the committee chose the sensible one. The only significant broken implementations by that point were HP's and Microsoft's, and Microsoft's doesn't really count because 1) the canonical name of the function in the Microsoft libraries was _sprintf, an identifier reserved to the implementation, and 2) Microsoft wasn't inclined to follow the standard anyway. Also: What am I supposed to do in case there is no obvious standard to adhere to? I have e.g. a few hundred kLOC of pre-1998 C++ code (done well before 1998...) around that's uncompilable with todays compilers. Who is to blame here? Should g++ have sticked to 2.95's view of the world? That's not a dynamic-runtime issue, which is what we were discussing. It's another problem entirely - the overly large and loose definition of the C++ language. In particular that would mean not only source and binary but also behavioural compatibility including keeping buggy behaviour. No it doesn't. Undefined behavior is undefined; an application that relies on it is broken. What is an application supposed to do when it lives in an environment where only buggy libraries are available? Suck it up? Might as well ask what a car is supposed to do in an environment with no roads. That's not a design failure in the car, nor a mistake on the part of the car's engineers; and neither does it mean that cars are a bad idea. And for the rare application that does, there are other Windows mechanisms
Re: Problems with installing GNU Aspell 0.60.6 on OSX 10.5.5
jezZiFeR wrote: No, but I´ve downloaded it now. Which components would I have to install? Sytem Tools and UNIX Development Support? Could I uninstall this tools after having installed Aspell? Thanks! I am not sure exactly which portion provides the compiling code, I installed the whole package. 2GB total installed size, and you may do what you like with it afterwards. 2008/11/24 Zan [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Do you have the mac developer tools installed? They are available for download (large requiring registration) on the Mac site. jezZiFeR wrote: »make: *** No targets specified and no makefile found. Stop. jzs-ibook-g4:aspell-0.60.6 stefan$« z
Re: lyx2lyx script broken (1.6.0 on Vista)
On Sun, Nov 23, 2008 at 10:26:30AM -0500, Michael Wojcik wrote: Jean-Marc Lasgouttes wrote: Completely infeasible on Windows. The loss of shared text would make the working set of the typical application mix grossly exceed even the absurd amounts of RAM available in typical machines today. The disk space problem would be even worse. I meant just for application which feel that they have to distribute their own version-of-the-day of whatever.dll. There is no reason to do it everywhere of course. Still not feasible, unfortunately, because that includes everything linked with any of the Microsoft C/C++ runtime DLLs. *cough* We were _not_ talking about statically linking _everything_. We were talking about things like Qt which are not a typical part of a Windows system. This is the central problem: if you build an application that uses anything in the MS C/C++ library (Microsoft combines the C and C++ standard libraries into a single DLL), which means pretty much anything built with a Microsoft C or C++ compiler, or with the Microsoft Platform SDK, you'll link against some specific version of one or more of the MSVC DLLs. You don't have much choice about which version you get - it depends on what version of the compiler or SDK you have installed, and what updates have been applied to it. [...] [...] [...] You are fighting windmills. Andre'
Re: lyx2lyx script broken (1.6.0 on Vista)
On Sun, Nov 23, 2008 at 11:21:27AM -0500, Michael Wojcik wrote: Andre Poenitz wrote: On Tue, Nov 18, 2008 at 03:42:52PM -0500, Michael Wojcik wrote: Andre Poenitz wrote: On Mon, Nov 17, 2008 at 11:07:05AM -0500, Paul A. Rubin wrote: I've worked on many projects that maintained backward compatibility with new releases of the API, and seen a great many more. Just for my curiosity: Which projects, which scope? Hmm. Off the top of my head, in roughly chronological order: - Various IBM internal-only projects, such as the E editor. - Early versions of Windows. The Windows 1.x to Windows 2.0 and Windows/286 transition maintained compatibility in the Windows API; Windows 1.x applications ran unchanged in the 2.0 family. Windows 2.0 was released pretty exactly two years after 1.0, Windows 3.0 completely broke the API 2 1/2 years later. So, at best, that's a period of 4.5 years of API stability. That's close to a joke, especially when taking into account that 3.11 was not usable for any reasonable practical purpose... - X11R3. The X11 API was layered correctly: as long as the server follows the protocol spec, it doesn't matter what it does under the covers. I added support for new hardware to the ddx layer; wrote new window managers with completely different look-and-feel from the standard ones; added extensions to X11 itself. None of that interfered with existing clients one bit. X11R3: End of 88, X11R4: End of 89. In any case, this is a nice example for something that is finished at some point of time. Nobody changed 7 bit ASCII for a while for that matter. If a feature set is closed at some point of time it is easy to outsource the problems to extensions and toolkits. Pretty much around 1990 supposedly the last person died that used plain X. [No, that was not me *cough*] SCNR ;-) - The 4.3 BSD kernel. Extended multihead support in the console driver and wrote some drivers for new hardware. Enhanced the shared memory kernel option. Nothing that didn't want to use the new features needed to be recompiled. Spring (?) 2001 - January 2002. I can't/won't comment on the others. Maintaining backward compatibility simply is not that hard. We are _not_ talking about _two_ years here. I can maintain compatibility over two years by simply ignoring advancements in the outside world for that long and release incompatible version x+1 after that. I am still pretty convinced that compatibility and progress are fairly incompatible notions when it comes to the development of _usable_ libraries. And I'll say that my experience as a professional software developer for 20 years, and as a hobbyist for a number of years prior to that, shows me otherwise. Fine. My experience so far shows that one has a choice between stagnation and breaking compatibility. And making that choice is neither obvious nor easy. you try to provide everything and the kitchen sink, and end up with design and implementation decisions that need to be re-evaluated from time to time in the presence of new environments. Java and Python, or anything including a GUI comes to mind. I'll offer X11 as a counterexample. X11 has certainly its merits and is time proven. Still it puts a lot of burden on the application developer, or, at the very least, on the toolkit developer. Lots of the initial design decisions that do not scale well into the 21st century are only bearable because of the outsourcing mentioned above. Plain X11 does _not_ come with kitchen sinks. And in this case, we're talking C and C++ runtimes, which should conform to the ISO standard anyway. Ah... should they conform to the Standard or should they be compatible to older versions? To the standard. That rules out fixing bugs, and it also breaks compatibility. I do not say that's a bad choice - in fact that's what I'd do in most cases - but it is incompatible with your statement that maintaining compatibility is possible _and easy_. What is supposed to happen if an existing version does _not_ conform to the Standard? Since the standards attempt to codify existing practice, that rarely happens. Hear, hear. How come ISO 14882 codifies export for templates when not a single compiler was able to handle that in 1998 (and for a few years after that)? Apart from that the point is not how often it happens but that it happens at all. You just admit that it happens. The only case that comes to mind of an incompatible change in the C standard, between C90 (ISO 9899-1990) and C99, is the choice of return code semantics for snprintf when it was added to the standard. There were two implementations with different semantics; the committee chose the sensible one. The only significant broken implementations by that point were HP's and Microsoft's, and Microsoft's doesn't really count because 1) the canonical name of the function in the Microsoft libraries was _sprintf, an identifier reserved to the
Lyx 1.6.0: Question about Document Class Memoir Installation
Hi there, I'm a newbie, having installed Lyx 1.6.0 today. Very good program. Thanks for the great work. I have heard a lot about the Memoir class and wanted to try it out. Can you tell if it is correct that I see about 37 options under the primary drop-down bar (the one that says Standard, Chapter, etc)? I was hoping I'd see more, items like publisher, etc. For instance the AMS book class has this and since I expected the Memoir class to be more refined and hence have more defined styles (if this is the right word), I expected to see more options here. Thus I am now wondering if somehow my installation did not work as expected or if I need to do something else? Thanks, Shane Forbes.
Flex insets
In layout directory stdinsets.inc, there are definitions of Info:menu, Info:shortcut, and Info:shortcuts. It appears that these are the ones to define the menu/shortcut styles in the help files. However, I don't see there is anyway to use these from LyX menu. Actually, the definitions in Logical Markup module is listed in Edit-Text Style. I am a little confused. Shouldn't these Info:??? styles be available from the LyX Menu, like Algorithm, Box, ERT, etc? Or am I only supposed to copy them and make my own in a layout or module file? I am using lyx 1.6 on Windows. Thanks. Max
Re: lyx2lyx script broken (1.6.0 on Vista)
On 23/11/2008 16:26, Michael Wojcik wrote: In older versions of the Microsoft toolchain, you could just drop the MSVC DLLs into the same directory as your executable. That's no longer allowed (I think as of Visual Studio 2005 and Platform SDK 6.0). Now they have to be installed into the SxS tree. FYI, unless I'm misunderstanding you, that's not really true, many open source (or not) programs distribute the C and C++ runtime along the executable and the manifest file. We do that for LyX for example. So the old method still stands. Abdel.
PDF Update fails, LyX 1.5.7 (WinXP)
I upgraded to LyX 1.5.7 on WinXP with MikTeX 2.7 (updated). Everything is fine except that update PDF does not work. When I try to update an open PDF, which always worked fine before, I get an error from LaTeX: --- I can't write on file `test.pdf' --- The snippet of the Log file is here: LaTeX Info: Redefining \ref on input line 49. LaTeX Info: Redefining \pageref on input line 49. (test.out) (test.out ! I can't write on file `test.pdf'. Please type another file name for output ! Emergency stop. [EMAIL PROTECTED] ...utline goto name{#2}count#3{#4} l.1 \BOOKMARK [1][-]{section.1}{Introduction}{} Any help is appreciated. For the record, I updated MikTeX, refreshed it, and re-created the format files, and also ran Reconfigure in LyX. Dave Hewitt
InsetLayout CharStyle:MenuItem
If I have InsetLayout CharStyle:MenuItem, it works. If I have InsetLayout CharStyle:Menu_Item in a layout module, LyX displays it as a red box. I like the latter since it displays a space in the Edit-Text Style menu. Not sure why it would be red though. Any idea? I am using LyX 1.6 on Windows. Thanks. Max
Re: euro-symbol in math-mode
Guenter Milde [EMAIL PROTECTED] writes: Robert Neumann [EMAIL PROTECTED] schrieb: is there any way of using an euro-symbol in mathmode? If works out of the box with the unicode Euro symbol € in LyX 1.6. unfortunately I still use 1.37... I use the eurosym-package, but this works only in textmode. You could try with text-in-math (pressing Ctrl-m in math mode). works! thanks!
Re: lyx2lyx script broken (1.6.0 on Vista)
- The 4.3 BSD kernel. Extended multihead support in the console driver and wrote some drivers for new hardware. Enhanced the shared memory kernel option. Nothing that didn't want to use the new features needed to be recompiled. Spring (?) 2001 - January 2002. Sorry to jump into your thread. But the dates are many years off. 4.3BSD kernel was released by CSRG in 1986.
Re: Going from custom charstyles to module
Charles de Miramon wrote: Richard Heck wrote: This SHOULD work. As you see, LyX does update the file to the new format. What does the LyX code look like if you use your new InsetLayout definition? It's the disagreement between these that is causing the problem, I think. What you might want to do is just to put your old Format 2 code into a module and let LyX do the conversion to Format 11 for you. You can also run: python $LYXDIR/layout2layout.py oldlayout.module newlayout.module and see how LyX converts it, then just use newlayout.module instead of oldlayout.module. It worked. The main difference is that the script gives : InsetLayout CharStyle:Latin where my handcrafted version had InsetLayout Latin The 'Charstyle:' is not very elegant but seems to be necessary. It's necessary only because that's how lyx2lyx does the translation. And, well, it used to be necessary, but then it wasn't. So you do NOT have to put that in your own layouts, though if you want to translate an old one then, as you see, you should. We only discovered this issue very late And in fact, they can be collapsable if you want them to be. The Decoration tag controls this. What is the difference between Minimalistic and Conglomerate ? I do not see on the screen any difference. I think they collapse or expand differently. Would it be possible when your cursor is in a zone formatted with a custom charstyle to print in the status bar after the font formatting information something like 'Custom character style : Foo' ? I assume. Though was meant to be what Ctrl-E was for: so that you can see what charstyle it is. rh
Re: Flex insets
Max Bian wrote: In layout directory stdinsets.inc, there are definitions of Info:menu, Info:shortcut, and Info:shortcuts. It appears that these are the ones to define the menu/shortcut styles in the help files. However, I don't see there is anyway to use these from LyX menu. Actually, the definitions in Logical Markup module is listed in Edit-Text Style. I am a little confused. Shouldn't these Info:??? styles be available from the LyX Menu, like Algorithm, Box, ERT, etc? Or am I only supposed to copy them and make my own in a layout or module file? I am using lyx 1.6 on Windows. You can define shortcuts for them if you like, or even arrange for it to be on your menu. What it would do is insert an InsetInfo object into your file, which is used e.g. to show which shortcut is associated with font-emph. InsetInfo isn't on the menu because it was never intended for ordinary users. I'm not sure why you'd want to use it, unless you're writing docs for LyX. rh
Re: InsetLayout CharStyle:MenuItem
Max Bian wrote: If I have InsetLayout CharStyle:MenuItem, it works. If I have InsetLayout CharStyle:Menu_Item in a layout module, LyX displays it as a red box. I like the latter since it displays a space in the Edit-Text Style menu. Not sure why it would be red though. Any idea? I am using LyX 1.6 on Windows. That'd be a bug. I've just fixed it in trunk. It should make it into 1.6.1. rh
Re: Building LyX layout for Copernicus Journals, class definition and estimate of time span?
Maarten Smoorenburg wrote: Allright, here's a zip of all my layouts (I modified a few article layouts). Some area recognised by LyX as unavailable and give the mentioned error message, others (i.e., copernicus and hess layouts) give the message 'The document class copernicus (or hess) could not be loaded. I also added the configure.log file and some of the copernicus LaTeX class and style files + documentation. My aim is to build one copernicus layout, for which the user must specify the journal abbreviation in the LyX custon class options field of the document settings. Hope you can see anything more than I in the logfile? Ciao Hmm. Works for me! Both your copernicus.layout and hess.layout load just fine---except that the ClassOptions thing doesn't seem to like commas. So you need to do this: ClassOptions Other hess,ms End with the quotes. Your configure file doesn't contain any check for copernicus, which is strange. Can you reconfigure again, and then post both the configure log and the file textclass.lst? You can also try deleting your textclass.lst and forcing configure to regenerate it. Richard
includegraphics - a newbie question
Hello there, I am new to this list. I used plain LaTeX in older days but in the last few years I deteriorated into using the PowerPoint. Recently I co-authored a presentation with a guy who uses LeTeX all the time. We did it using Beamer and it looked beautiful. For that we used the TexXnic Center which works fine except it still takes a lot of raw LaTeX typing to get things right. In any case, I have started to experiment with LyX. I have version 1.6.0.1 installed on WinXP Pro machine together with the latest MiKTeX distribution and whatever else is needed. I have been going through the LyX tutorial and decided to do my variations to the example-raw.lyx file. I tried some tables and they seemed to work just fine. Then I tried the Insert Graphics button. This gives me a problem. I typed a name of my *.png test file there and tied to preview the PDF but got an error message about not being able to determine the bounding box. I put my own width and height into the dialog box but got the same error message. I started to investigate the matter further by exporting pdflatex code from the document. I noticed that I get the following code for the graphics part \begin{center} \includegraphics[width=4in,height=4in]{test.png} \par\end{center} which looks OK to me (except I do not understand the \par bit). Then I noticed that in the preamble of the document I have a line \usepackage[dvips]{graphicx} When I remove the [dvips] than I can run pdflatex on the *.tex file any everything is OK. After looking a little further I found a workaround (sort of). I can use the Insert Float Graphics button and then use the TeX box to enter the includegraphics command. Since using the Insert Float Graphics seems to generate the \begin{graphics} ... \end{graphics} environment it does not add anything to the preamble. Then I can add the \usepackage{graphicx} into the preamble myself in the Document Settings Preamble. My question is this - is there a more straightforward way of doing this? I like the Insert Graphics way. Is there any way to stop LyX from sticking the [dvips] option into the preamble? Thanks for your time, Andy __ Andy Jaworski 518-1-01 Process Laboratory 3M Corporate Research Laboratory - E-mail: [EMAIL PROTECTED] Tel: (651) 733-6092 Fax: (651) 736-3122
Re: Problems with installing GNU Aspell 0.60.6 on OSX 10.5.5
On Mon, Nov 24, 2008 at 1:16 PM, Zan [EMAIL PROTECTED] wrote: jezZiFeR wrote: No, but I´ve downloaded it now. Which components would I have to install? Sytem Tools and UNIX Development Support? Could I uninstall this tools after having installed Aspell? Thanks! I am not sure exactly which portion provides the compiling code, I installed the whole package. 2GB total installed size, and you may do what you like with it afterwards. If you're uncertain what to do, the easiest thing is to use CocoAspell. The instructions for getting LyX to work with that can be found here: http://wiki.lyx.org/Mac/MacSpelling#toc2 Bennett
Re: Koma-script not fully compatible with hyperref package
Pavel Sanda [EMAIL PROTECTED] writes: P.S. Should I also report this bug somewhere on CTAN where the packages reside? I can't figure out for the love of God where I can sign up for a user account on the Koma Script website, though my German is good enough. It only lets _existing_ users log in or renew passwords though! http://www.komascript.de/forum/ at least put it into our bugzilla. pavel Well, I finally heard back from the guy who maintains the Koma-script package. I was amazed of the level of detail he offered in his answer, but basically the issues are within the hyperref package and how koma-script is able to work with hyperref. So, I didn't want to bother the LyX developers with this... Latex 2e needs fixes! :) Alex
Re: Lyx and BibDesk connection
On Mon, Nov 24, 2008 at 11:02 AM, Dr. Joachim K. Rennstich [EMAIL PROTECTED] wrote: I am new user to Lyx and I have been working on a Mac (10.5) with TeXShop and BibDesk successfully so far. I just updated to the latest Mac install for TeX and gave Lyx another try in v1.6 and want to do the switch. Here's my problem - whenever I try to send something from BibDesk to Lyx, I get the following error msg: Unable to open the LyX pipe at /Users/jrennstich/Library/Application Support/LyX-1.6/.lyxpipe.in for writing. You should quit LyX and possibly remove the pipe manually if this error persists. The underlying system error code was 6 (Device not configured). I saw the post here http://wiki.lyx.org/Mac/Environment about changing the .MacOSX/environment.plist but I am simply not able to find the relevant files: neither the .lyxpipe.in, nor ~/.MacOSX/environment.plist. That webpage is for earlier versions of LyX and Mac OS X. You should ignore it. You will need to delete /Users/jrennstich/Library/Application Support/LyX-1.6/.lyxpipe.in manually, though you won't find them in the GUI (since the Finder does not display any file whose name begins with .. So you need to do it using the Terminal: rm /Users/jrennstich/Library/Application\ Support/LyX-1.6/.lyxpipe.in (Notice the \ between Application and Support.) Any help how to link Lyx and BibDesk successfully and help Lyx and BibDesk identify my .bib libraries would be greatly appreciated. Just make sure you put your .bib libraries in the usual place: ~/Library/texmf/tex/bib. Then LaTeX (and LyX) can find them. Bennett
use of xcolor in LyX
Dear LyX-users, I need some help to use the xcolor package. I want to set a blue-marine (or dark blue) color for url's. I use the following in the preamble: \usepackage{hyperref} \hypersetup{colorlinks=true,urlcolor=blue} How can I define the urcolor= to be lets say Red 0, Green 47, Blue 76? Thank you in advance, Nikos P.S. This list is one of the most active I've been following. It's amazing :-)
Re: use of xcolor in LyX
On Tue, 2008-11-25 at 02:52 +0100, Nikos Alexandris wrote: Dear LyX-users, I need some help to use the xcolor package. I want to set a blue-marine (or dark blue) color for url's. I use the following in the preamble: \usepackage{xcolor} \usepackage{hyperref} \hypersetup{colorlinks=true,urlcolor=blue} How can I define the urcolor= to be lets say Red 0, Green 47, Blue 76? Thank you in advance, Nikos P.S. This list is one of the most active I've been following. It's amazing :-)
Toolbar bug?
I am using LyX 1.6 on Windows Vista. If I have the three toolbar panels on three separate rows, it works fine. If I put two of them on one line, LyX will not be able to restore them correctly when I start it next time: the second one on the row will go all the way to the right and I cannot see any icons. Anyone else seeing this? Max
Re: Toolbar bug?
On Nov 24, 2008, at 8:19 PM, Max Bian wrote: I am using LyX 1.6 on Windows Vista. If I have the three toolbar panels on three separate rows, it works fine. If I put two of them on one line, LyX will not be able to restore them correctly when I start it next time: the second one on the row will go all the way to the right and I cannot see any icons. Anyone else seeing this? No problem on Mac.
Re: PDF Update fails, LyX 1.5.7 (WinXP)
David Hewitt wrote: I upgraded to LyX 1.5.7 on WinXP with MikTeX 2.7 (updated). Everything is fine except that update PDF does not work. When I try to update an open PDF, which always worked fine before, I get an error from LaTeX: --- I can't write on file `test.pdf' --- The snippet of the Log file is here: LaTeX Info: Redefining \ref on input line 49. LaTeX Info: Redefining \pageref on input line 49. (test.out) (test.out ! I can't write on file `test.pdf'. Please type another file name for output ! Emergency stop. [EMAIL PROTECTED] ...utline goto name{#2}count#3{#4} l.1 \BOOKMARK [1][-]{section.1}{Introduction}{} Any help is appreciated. For the record, I updated MikTeX, refreshed it, and re-created the format files, and also ran Reconfigure in LyX. Dave Hewitt Dave, I suspect you're using Acrobat Reader, which locks the file while it's open. Check in the LyX bin directory and see if you have pdfview.exe installed. If yes, go to Tools - Preferences... - File formats, highlight in turn each PDF format you use, such as PDF (pdflatex), change the Viewer from 'auto' to 'pdfview' and click Modify and then Save. Then I think you'll need to restart LyX (but not reconfigure). /Paul
Re: Lyx and BibDesk connection
On Mon, Nov 24, 2008 at 10:54 PM, Dr. Joachim K. Rennstich [EMAIL PROTECTED] wrote: Thanks so much for your help! I now successfully deleted the / .lyxpipe.in file. The new problem is that now the option of sending an entry from BibDesk to Lyx is greyed out. So I don't even have a chance to get an error message. How can I recreate a new pipe? Or tell BibDesk that Lyx is available? I restarted the Mac and thus all the apps, to no avail. The problem is that the SendToLyx script has not been updated for LyX-1.6, and so it's not finding your .lyxpipe. I've send a note to Mark Reid, author of the script, to see if he'll post an updated version on his website. In the meantime, I'll see if I can have the LyX wiki updated with the new file as well. Bennett
Lyx users mailing list administrator
Could the person responsible for configuring the lyx users mailing list be kind enough to contact me off-list please? Kind Regards, Keith Roberts - Websites: http://www.php-debuggers.net http://www.karsites.net http://www.raised-from-the-dead.org.uk All email addresses are challenge-response protected with TMDA [http://tmda.net] -
Re: Flex insets
I am a little confused. Shouldn't these Info:??? styles be available from the LyX Menu, like Algorithm, Box, ERT, etc? Or am I only supposed to copy them and make my own in a layout or module file? You can define shortcuts for them if you like, or even arrange for it to be on your menu. FWIW the shortcut is already Ctrl-Shift-I. JMarc
Re: Helper function/shortcut
Richard, thanks for your reply! On 24/11/2008 16:20, Richard Heck wrote: Frank Grimm wrote: Is there any way to add pre-formatted text to a LyX document? For example, when inserting i.e. with the shortcut described above, I'd like to set i.e. in an italic style and with a thin space between the two characters. Is this possible with LyX 1.6? Yes, it should be. You can do it inside your bind file for now. You'll need to use something like: command-sequence font-emph; self-insert i.e.; font-emph; space-insert normal Modify as required. I tried the following command sequence command-sequence font-ital; self-insert i.e.; font-ital where I replaced font-emph in your suggestion with font-ital since I don't want the i.e. the be emphasized, but just in italic shape. But when I use the shortcut for this command LyX tells me that the command is disabled. Are there any restrictions for the font-ital command that the font-emph command doesn't have? Thanks, Frank
euro-symbol in math-mode
Hello, is there any way of using an euro-symbol in mathmode? (I want to create some exercises with the rule of three (Dreisatz)). I use the eurosym-package, but this works only in textmode. Thanks Robert
Re: Single Author, Single Year, Multiple Articles
As far as I know, the addition of a letter to the year, which is useful in the case you cite in the same paper 2 or more publications by the same author with different titles but published in the same year, depends from the specific citation style used and selected once and for all in the selection window in LyX where you also select the bib file. For example, econometrica, which is one of the citation styles proposed by LyX, manages the addition of a letter to the publication year in the needed cases. Pierfranco 2008/11/23 npierre [EMAIL PROTECTED] Hi All, I have an author, Wei, who wrote two articles in 2000. In the citation dialog, the bibtex keys show up as Wei2000a and Wei2000b. When I insert one or the other into the text, it prints as Wei (2000). How can I get Lyx to add an a or b to distinguish between the articles, e.g. Wei (2000b)? Thanks. Norbert Pierre
Re: euro-symbol in math-mode
Robert Neumann [EMAIL PROTECTED] schrieb: is there any way of using an euro-symbol in mathmode? If works out of the box with the unicode Euro symbol € in LyX 1.6. I use the eurosym-package, but this works only in textmode. You could try with text-in-math (pressing Ctrl-m in math mode). Günter
Re: Key bindings
Dov Feldstern [EMAIL PROTECTED] schrieb: Peleg Michaeli wrote: On Sat, 2008-11-22 at 20:28 +0200, Dov Feldstern wrote: They shouldn't all be bothering you, only the ones you include are activated. Probably it's cua -- that's the default. what exactly does your bind file look like? I'm attaching cua and hebrew here. The cua.bind is in usr/share/... and the hebrew.bind is in ~/.lyx1.5.1/bind/ The first line of hebrew.bind (\bind_file cua) is including cua.bind. I don't remember the rules in terms of whether you can override bindings, and they may also have changes since 1.5. Generally, you can overwrite bindings. However in this case it is more complicated: ./bind/cua.bind:\bind C-g error-next binds ^G, so LyX will not wait for ^G y. @ the LyX experts: Is there a way to unbind a key so that it can be used at basis for a set of multi-key bindings? The easiest thing to do may be to just copy cua.bind from /usr to your local lyx bind directory, rename it to mycua or something, Actually, there is no need to rename (other than clarity), as LyX will try the version in your personal LyXDir first. get rid of the C-g y in there, and include that in hebrew instead of cua. It will not matter where the new bindings are included as long as the original binding is commented out: - \bind C-g error-next + # \bind C-g error-next Günter
Helper function/shortcut
Hi, I'm looking for a way to insert (pre-formatted) text into a LyX document using a keyboard shortcut. For example, I'd like to insert i.e. when pressing a certain key combination. I tried to use the LyX function self-insert with the argument i.e., but with LyX 1.6 I only got the error message: Can not insert shortcut to the list. Is there any way to add pre-formatted text to a LyX document? For example, when inserting i.e. with the shortcut described above, I'd like to set i.e. in an italic style and with a thin space between the two characters. Is this possible with LyX 1.6? Thanks, Frank
Re: Key bindings
Guenter Milde wrote: Is there a way to unbind a key so that it can be used at basis for a set of multi-key bindings? In 1.6, \unbind ? /Konrad
Subfig(ure) in class Memoir
How to get subfigure captions in memoir without resorting to ERT? I am merging some documents into my thesis, and some of them contain subfigures. Now, the thesis class (kthesis.cls) is based upon memoir, which seem to have an issue with subfigure. (LatTeX Error: Command [EMAIL PROTECTED] already defined.). One of the suggested solution is using the subfig package instead. However, LyX automatically adds \usepackage{subfig} to the latex preamble when a subfigure caption is added to a figure via the GUI. This result in the above error. Can adding subfigure be avoided? Can I force LyX to use subfig instead? Or is there perhaps any other solution to this dilemma without resorting to ERT? LyX 1.5.3 under Linux. Thanks, Johan
Equation numbering
Hi: How can make the equation numbers to appear to the right of the equations in LyX 1.6? Thanks! * Fernando Díaz H, Ph.D. * Profesor de Economía y Finanzas Facultad de Ciencias Económicas y Empresariales Universidad de los Andes (56 2) 412-9650 [EMAIL PROTECTED] [EMAIL PROTECTED] Avda. San Carlos de Apoquindo 2200, Las Condes, Santiago Chile
DVI chokes on PNG Logo in fancy header
Hello, This must be a stupid question but I can't find a proper answer on the web. Does anyone know how to make this work? I get Latex errors like those: LaTeX Error: Cannot determine size of graphic in /home/younes/Documents/ Some links suggested that image magic should be installed; but it is: convert my_logo.png my_logo.eps just works. 'pdflatex' works fine but 'dvi' don't. I have this in my preamble: \rhead{} \rhead{\includegraphics[clip=,scale=.3] {graphics/my_logo.png}} Idea someone? Abdel.
Re: DVI chokes on PNG Logo in fancy header
Abdelrazak Younes [EMAIL PROTECTED] writes: 'pdflatex' works fine but 'dvi' don't. I have this in my preamble: \rhead{} \rhead{\includegraphics[clip=,scale=.3] {graphics/my_logo.png}} Idea someone? Err, ERT is not handled by LyX and including a png via includegraphics is not possible. Create the eps by hand or maybe use the following in your document instead: ert\rhead{/ert[your nice graphics]ert}/ert JMarc
Re: DVI chokes on PNG Logo in fancy header
Jean-Marc Lasgouttes wrote: Abdelrazak Younes [EMAIL PROTECTED] writes: 'pdflatex' works fine but 'dvi' don't. I have this in my preamble: \rhead{} \rhead{\includegraphics[clip=,scale=.3] {graphics/my_logo.png}} Idea someone? Err, ERT is not handled by LyX and including a png via includegraphics is not possible. I knew there was something obvious but couldn't find it :-) Create the eps by hand or maybe use the following in your document instead: ert\rhead{/ert[your nice graphics]ert}/ert I can't do that as this is in the preamble. Or can I just use the \rhead command in the document? If not, is there something like conditional include with LateX? Something like that (in pseudo C-like code): \includegraphics{ \engine == 'dvi' ? graphics/my_logo.eps : graphics/my_logo.png} } Thanks, Abdel.
Re: Equation numbering
Right click and choose Toggle Labeling/Numbering On Nov 24, 2008, at 7:35 AM, FERNANDO DIAZ wrote: Hi: How can make the equation numbers to appear to the right of the equations in LyX 1.6? Thanks! * Fernando Díaz H, Ph.D. * Profesor de Economía y Finanzas Facultad de Ciencias Económicas y Empresariales Universidad de los Andes (56 2) 412-9650 [EMAIL PROTECTED] [EMAIL PROTECTED] Avda. San Carlos de Apoquindo 2200, Las Condes, Santiago Chile
Re: Equation numbering
How can make the equation numbers to appear to the right of the equations in LyX 1.6? Normally (Insert Math numberedformula) gives the equation number, right justified, applicable in many journals and books. Maybe this is not what you want ? WAS
Re: DVI chokes on PNG Logo in fancy header
Abdelrazak Younes [EMAIL PROTECTED] writes: I can't do that as this is in the preamble. Or can I just use the \rhead command in the document? I think so, try it. If not, is there something like conditional include with LateX? Something like that (in pseudo C-like code): \includegraphics{ \engine == 'dvi' ? graphics/my_logo.eps : graphics/my_logo.png} } It is possible (latex is a full-fledge language, after all), but not needed here. Make a png file and an eps one, and use \includegraphics{graphics/my_logo} the right extension will be picked automatically. JMarc
Re: Helper function/shortcut
Frank Grimm wrote: Hi, I'm looking for a way to insert (pre-formatted) text into a LyX document using a keyboard shortcut. For example, I'd like to insert i.e. when pressing a certain key combination. I tried to use the LyX function self-insert with the argument i.e., but with LyX 1.6 I only got the error message: Can not insert shortcut to the list. That's a bug. I'm getting that message pretty much no matter what I try to do. Is there any way to add pre-formatted text to a LyX document? For example, when inserting i.e. with the shortcut described above, I'd like to set i.e. in an italic style and with a thin space between the two characters. Is this possible with LyX 1.6? Yes, it should be. You can do it inside your bind file for now. You'll need to use something like: command-sequence font-emph; self-insert i.e.; font-emph; space-insert normal Modify as required. rh
Re: Subfig(ure) in class Memoir
On Monday 24 November 2008, Johan Tegin wrote: How to get subfigure captions in memoir without resorting to ERT? I am merging some documents into my thesis, and some of them contain subfigures. Now, the thesis class (kthesis.cls) is based upon memoir, which seem to have an issue with subfigure. (LatTeX Error: Command [EMAIL PROTECTED] already defined.). One of the suggested solution is using the subfig package instead. However, LyX automatically adds \usepackage{subfig} to the latex preamble when a subfigure caption is added to a figure via the GUI. This result in the above error. Can adding subfigure be avoided? Can I force LyX to use subfig instead? Or is there perhaps any other solution to this dilemma without resorting to ERT? LyX 1.5.3 under Linux. Thanks, Johan Johan, I ran into exactly this problem a few months ago when I decided to convert a rather large document from book(KOMA-script) to memoir, to take advantage of some of the neat features in memoir. My solution (after trying various mechanisms to get subfigures to work) was to replace the figures containing subfigures with a single figure float, putting more than one image in one float. The only disadvantage I found is the lack of separate captions, which I overcame by using phrases such as on the left in the single caption referring to multiple images. -- Les ~~ Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html
Re: DVI chokes on PNG Logo in fancy header
Jean-Marc Lasgouttes wrote: Abdelrazak Younes [EMAIL PROTECTED] writes: I can't do that as this is in the preamble. Or can I just use the \rhead command in the document? I think so, try it. I confirm. If not, is there something like conditional include with LateX? Something like that (in pseudo C-like code): \includegraphics{ \engine == 'dvi' ? graphics/my_logo.eps : graphics/my_logo.png} } It is possible (latex is a full-fledge language, after all), but not needed here. Make a png file and an eps one, and use \includegraphics{graphics/my_logo} the right extension will be picked automatically. Even better, thanks! Abdel.
Going from custom charstyles to module
Hello I'm starting to move my real work to LyX 1.6 and I have problem with the new modules. I had in LyX 1.5 some semantic custom markup for citations in Latin and Old French in a mycharstyles.inc file # Personal character styles definition Format 2 CharStyle Latin LatexType Command LatexName latin Font Family Sans EndFont LabelFont Family Roman Color blue EndFont Preamble \newcommand{\latin}[1]{\og~#1~\fg} EndPreamble End CharStyle Ancien LatexType Command LatexName ancien Font Family Sans EndFont LabelFont Family Roman Color blue EndFont Preamble \newcommand{\ancien}[1]{\og~#1~\fg} EndPreamble End I have created a module in LyX 1.6 (I could not find any documentation about the syntax of modules and the new flexible insets) Latin.module #\DeclareLyXModule{Latin} #DescriptionBegin #Définit des styles spécifiques pour les textes en latin et en ancien français #DescriptionEnd #Charles de Miramon 24/11/08 Format 11 InsetLayout Latin LyxType charstyle LabelString Latin LatexType Command LatexName latin Font Family Sans EndFont LabelFont Family Roman Color blue EndFont Preamble \newcommand{\latin}[1]{\og~#1~\fg} EndPreamble End InsetLayout Ancien LyxType charstyle LabelString Ancien LatexType Command LatexName ancien Font Family Sans EndFont LabelFont Family Roman Color blue EndFont Preamble \newcommand{\ancien}[1]{\og~#1~\fg} EndPreamble End It works for new files but does not translate the old files. The old LyX code was : \begin_inset CharStyle Latin status inlined and the new one seems to be : \begin_inset Flex Latin status collapsed Questions : 1) Is there a way to automatically transform the old custom charstyle formatting to the module ? 2) Why do we have in the new syntax a 'status collapsed' ? Charstyles are not insets that can be closed or opened 3) I'm a bit mixed up between the old custom charstyles, flexible insets, modules. What is going to be deprecated ? Cheers, Charles -- http://www.kde-france.org
Re: Helper function/shortcut
Richard Heck wrote: Frank Grimm wrote: Hi, I'm looking for a way to insert (pre-formatted) text into a LyX document using a keyboard shortcut. For example, I'd like to insert i.e. when pressing a certain key combination. I tried to use the LyX function self-insert with the argument i.e., but with LyX 1.6 I only got the error message: Can not insert shortcut to the list. That's a bug. I'm getting that message pretty much no matter what I try to do. OK, the problem is that self-insert cannot be added to the list as a function. There's a reason for this, namely, that you don't really want to see the bindings for normal keys in that list, e.g.: \bind 2 self-insert The solution is to use this instead: command-sequence self-insert i.e. for the simple case. rh
Re: Subfig(ure) in class Memoir
Johan Tegin [EMAIL PROTECTED] writes: One of the suggested solution is using the subfig package instead. However, LyX automatically adds \usepackage{subfig} to the latex preamble when a subfigure caption is added to a figure via the GUI. This result in the above error. Can adding subfigure be avoided? Can I force LyX to use subfig instead? Or is there perhaps any other solution to this dilemma without resorting to ERT? LyX 1.6.0 has switched to using subfig instead of subfigure. Maybe an incentive to upgrade ? JMarc
Problems with installing GNU Aspell 0.60.6 on OSX 10.5.5
Hello, I have tried to install the Aspell-dictionary using the instructions from this site: http://wiki.lyx.org/Mac/MacSpelling#toc2 It worked so far, I downloaded Aspell and followed the above mentioned instructions, until I entered »make«. Then I have got the following message out of the terminal: »make: *** No targets specified and no makefile found. Stop. jzs-ibook-g4:aspell-0.60.6 stefan$« What did I do wrong? I entered everything exactly as mentioned. Would I have to install the dictionaries first?
Symbol in manual
Hi. I am curious about the symbol in the help documents. There is the sideways triangle used when referring to menu item, for example, Insert-Box. The - actually looks like a triangle in LyX. How do I insert a symbol like that? Thanks. Max
Re: Building LyX layout for Copernicus Journals, class definition and estimate of time span?
Maarten Smoorenburg wrote: Now I've added your suggestion; ClassOptions Other hess,ms End But, still it doesnot work, I get the error message when trying to define in Document Settings: /The layout file... is not usable. This is probably because a LaTeX class or style file required by it is not available./ Did you ToolsReconfigure? Richard
Re: Problems with installing GNU Aspell 0.60.6 on OSX 10.5.5
Do you have the mac developer tools installed? They are available for download (large requiring registration) on the Mac site. jezZiFeR wrote: »make: *** No targets specified and no makefile found. Stop. jzs-ibook-g4:aspell-0.60.6 stefan$« z
Re: Equation numbering
FERNANDO DIAZ wrote: Hi: How can make the equation numbers to appear to the right of the equations in LyX 1.6? If you're getting equation numbers on the left side, try adding 'reqno' as a class option in Document - Settings... - Document Class. /Paul
Re: Building LyX layout for Copernicus Journals, class definition and estimate of time span?
Yes sure... And now it is in the 'unavailable' part of the document class list of LyX... so what you suggest? On Mon, Nov 24, 2008 at 5:18 PM, Richard Heck [EMAIL PROTECTED] wrote: Maarten Smoorenburg wrote: Now I've added your suggestion; ClassOptions Other hess,ms End But, still it doesnot work, I get the error message when trying to define in Document Settings: /The layout file... is not usable. This is probably because a LaTeX class or style file required by it is not available./ Did you ToolsReconfigure? Richard
RE: Symbol in manual
I am curious about the symbol in the help documents. There is the sideways triangle used when referring to menu item, for example, Insert-Box. The - actually looks like a triangle in LyX. How do I insert a symbol like that? Insert-Special Character-Menu Separator. Thanks. Max Vincent
Re: Building LyX layout for Copernicus Journals, class definition and estimate of time span?
Maarten Smoorenburg wrote: Yes sure... And now it is in the 'unavailable' part of the document class list of LyX... so what you suggest? Then LyX for some reason isn't finding the LaTeX class file. That's when it lists things as unavailable. What is your layout file named? What is the class file named? Maybe you should post the layout. And also the configure.log file that's dumped in your user directory when you reconfigure. rh
Re: Symbol in manual
Max Bian wrote: Hi. I am curious about the symbol in the help documents. There is the sideways triangle used when referring to menu item, for example, Insert-Box. The - actually looks like a triangle in LyX. How do I insert a symbol like that? That particular symbol is under InsertSpecial Characters. rh
Lyx and BibDesk connection
I am new user to Lyx and I have been working on a Mac (10.5) with TeXShop and BibDesk successfully so far. I just updated to the latest Mac install for TeX and gave Lyx another try in v1.6 and want to do the switch. Here's my problem - whenever I try to send something from BibDesk to Lyx, I get the following error msg: Unable to open the LyX pipe at /Users/jrennstich/Library/ Application Support/LyX-1.6/.lyxpipe.in for writing. You should quit LyX and possibly remove the pipe manually if this error persists. The underlying system error code was 6 (Device not configured). I saw the post here http://wiki.lyx.org/Mac/Environment about changing the .MacOSX/environment.plist but I am simply not able to find the relevant files: neither the .lyxpipe.in, nor ~/.MacOSX/ environment.plist. Any help how to link Lyx and BibDesk successfully and help Lyx and BibDesk identify my .bib libraries would be greatly appreciated. I couldn't find that information in a search on here, my apologies, if this has been covered before :-( Needless to say, since I cannot find the lyxpipe.in nor the environment.plist, I am one of those sad Mac- users, who need a GUI and some guidance if that won't let me do the stuff I need to do... ;-) Thx, -Joachim
Re: Going from custom charstyles to module
Charles de Miramon wrote: Hello I'm starting to move my real work to LyX 1.6 and I have problem with the new modules. This seems mostly to be a problem with the new Flex insets. It doesn't matter whether you put the code into a module or into an inc file as far as this problem is concerned. I had in LyX 1.5 some semantic custom markup for citations in Latin and Old French in a mycharstyles.inc file # Personal character styles definition Format 2 CharStyle Latin LatexType Command LatexName latin Font Family Sans EndFont LabelFont Family Roman Color blue EndFont Preamble \newcommand{\latin}[1]{\og~#1~\fg} EndPreamble End CharStyle Ancien LatexType Command LatexName ancien Font Family Sans EndFont LabelFont Family Roman Color blue EndFont Preamble \newcommand{\ancien}[1]{\og~#1~\fg} EndPreamble End I have created a module in LyX 1.6 (I could not find any documentation about the syntax of modules and the new flexible insets) See the Customization manual, chapter 5, especially sections 5.2.1 and 5.3.6. Latin.module #\DeclareLyXModule{Latin} #DescriptionBegin #Définit des styles spécifiques pour les textes en latin et en ancien français #DescriptionEnd #Charles de Miramon 24/11/08 Format 11 InsetLayout Latin LyxType charstyle LabelString Latin LatexType Command LatexName latin Font Family Sans EndFont LabelFont Family Roman Color blue EndFont Preamble \newcommand{\latin}[1]{\og~#1~\fg} EndPreamble End InsetLayout Ancien LyxType charstyle LabelString Ancien LatexType Command LatexName ancien Font Family Sans EndFont LabelFont Family Roman Color blue EndFont Preamble \newcommand{\ancien}[1]{\og~#1~\fg} EndPreamble End It works for new files but does not translate the old files. The old LyX code was : \begin_inset CharStyle Latin status inlined and the new one seems to be : \begin_inset Flex Latin status collapsed Questions : 1) Is there a way to automatically transform the old custom charstyle formatting to the module ? This SHOULD work. As you see, LyX does update the file to the new format. What does the LyX code look like if you use your new InsetLayout definition? It's the disagreement between these that is causing the problem, I think. What you might want to do is just to put your old Format 2 code into a module and let LyX do the conversion to Format 11 for you. You can also run: python $LYXDIR/layout2layout.py oldlayout.module newlayout.module and see how LyX converts it, then just use newlayout.module instead of oldlayout.module. 2) Why do we have in the new syntax a 'status collapsed' ? Charstyles are not insets that can be closed or opened No, but they can have the sublabel, showing which charstyle they are. That's what this reflects. And in fact, they can be collapsable if you want them to be. The Decoration tag controls this. 3) I'm a bit mixed up between the old custom charstyles, flexible insets, modules. What is going to be deprecated ? There are no charstyles any more, only Flex insets. Modules are an entirely different matter. They are a more flexible alternative to include files. rh
Re: Going from custom charstyles to module
Richard Heck wrote: See the Customization manual, chapter 5, especially sections 5.2.1 and 5.3.6. OK. I missed that because it is not translated yet in French. This SHOULD work. As you see, LyX does update the file to the new format. What does the LyX code look like if you use your new InsetLayout definition? It's the disagreement between these that is causing the problem, I think. What you might want to do is just to put your old Format 2 code into a module and let LyX do the conversion to Format 11 for you. You can also run: python $LYXDIR/layout2layout.py oldlayout.module newlayout.module and see how LyX converts it, then just use newlayout.module instead of oldlayout.module. It worked. The main difference is that the script gives : InsetLayout CharStyle:Latin where my handcrafted version had InsetLayout Latin The 'Charstyle:' is not very elegant but seems to be necessary. And in fact, they can be collapsable if you want them to be. The Decoration tag controls this. What is the difference between Minimalistic and Conglomerate ? I do not see on the screen any difference. Would it be possible when your cursor is in a zone formatted with a custom charstyle to print in the status bar after the font formatting information something like 'Custom character style : Foo' ? Cheers, Charles -- http://www.kde-france.org
Re: lyx2lyx script broken (1.6.0 on Vista)
Jean-Marc Lasgouttes wrote: Completely infeasible on Windows. The loss of shared text would make the working set of the typical application mix grossly exceed even the absurd amounts of RAM available in typical machines today. The disk space problem would be even worse. I meant just for application which feel that they have to distribute their own version-of-the-day of whatever.dll. There is no reason to do it everywhere of course. Still not feasible, unfortunately, because that includes everything linked with any of the Microsoft C/C++ runtime DLLs. This is the central problem: if you build an application that uses anything in the MS C/C++ library (Microsoft combines the C and C++ standard libraries into a single DLL), which means pretty much anything built with a Microsoft C or C++ compiler, or with the Microsoft Platform SDK, you'll link against some specific version of one or more of the MSVC DLLs. You don't have much choice about which version you get - it depends on what version of the compiler or SDK you have installed, and what updates have been applied to it. For someone else to run that binary, they need that exact same version of the MSVC DLLs. In older versions of the Microsoft toolchain, you could just drop the MSVC DLLs into the same directory as your executable. That's no longer allowed (I think as of Visual Studio 2005 and Platform SDK 6.0). Now they have to be installed into the SxS tree. Microsoft's solution is for every application linked against any MSVC DLL to include the redistributable DLL package for that specific MSVC version as part of their installer package. So it's not the application developers who want you to install a dozen versions of the MSVC runtime. They don't know what versions you already have installed. There's no way to coordinate versions among unrelated applications. People build and distribute binaries, and they carry with them MSVC version requirements. -- Michael Wojcik Micro Focus Rhetoric Writing, Michigan State University
Re: lyx2lyx script broken (1.6.0 on Vista)
Andre Poenitz wrote: On Tue, Nov 18, 2008 at 03:47:45PM -0500, Michael Wojcik wrote: Jean-Marc Lasgouttes wrote: What's wrong with static linking? At least it goes away when the application goes away. Completely infeasible on Windows. ... Many people have done back-of-the-envelope calculations to demonstrate this; I think I did some myself, in a post to alt.folklore.computers some time back. Some time back I was disputing the sheer possibility to catch a virus using email. Still ... environments ... came up that made _not catching one_ an art... So things done a while back do not count in IT. That's one of the silliest generalizations I've seen in some time. People who ignore the history of IT are doomed to repeat it. Usually poorly. In this specific case, the situation has only gotten worse. However, I have no particular interest in demonstrating it. If you think static linking is feasible on Windows, go ahead and build LyX that way. Mac OS X pretty much shows that _not_ sharing shared libraries on an application level is a feasible approach to DLL hell. I wouldn't take anything Apple does as a model. I've used too many Apple products. And avoiding shared code in applications is a solution to DLL hell (which is a system administration problem, not an application architecture one) in the same way that walking is a solution to airplane safety. It's a lousy idea in any case, as anyone who remembers compiling all of BSD 4.2 to switch from local-files resolution to DNS remembers. Dynamic linking lets you fix the bug or add the feature in one place. So why go from libstdc++.so.5 to libstdc++.so.6 at all, if incompatible changes can be, as you seem to say, avoided? Because there are many changes that *are* compatible? I'm not a libstdc++ maintainer, so I don't know offhand what the differences in those two releases are; and I'm not going to trawl through the release notes to find out. But it's very rare that a bug fix, or even a new feature, needs to alter an existing API, so there's no reason for it to introduce incompatibility. (Maintaining undefined behavior isn't a compatibility issue. Applications that rely on undefined behavior are broken.) Dynamic linking is a good thing. It's worked very well on a number of OSes. Examples? Most mainframe OSes - all of the MVS and VM family, for example. Also IBM's midrange OSes from S/38 through AS/400 to iOS. Many Unix variants, such as SVR4 and AIX. I believe dynamic linking in VMS wasn't bad, though I only ever looked at it briefly. Worked pretty well on OS/2. For that matter, it often works well on Windows, when DLL management is done properly. It would work on Windows if Microsoft could figure out 1) how to version properly, and 2) how to maintain backward compatibility. And it's not like those are unsolved problems. I am happy to have learned now that these problems are solved. They were solved decades ago. -- Michael Wojcik Micro Focus Rhetoric Writing, Michigan State University
Re: lyx2lyx script broken (1.6.0 on Vista)
Andre Poenitz wrote: On Tue, Nov 18, 2008 at 03:42:52PM -0500, Michael Wojcik wrote: Andre Poenitz wrote: On Mon, Nov 17, 2008 at 11:07:05AM -0500, Paul A. Rubin wrote: I've worked on many projects that maintained backward compatibility with new releases of the API, and seen a great many more. Just for my curiosity: Which projects, which scope? Hmm. Off the top of my head, in roughly chronological order: - Various IBM internal-only projects, such as the E editor. - Early versions of Windows. The Windows 1.x to Windows 2.0 and Windows/286 transition maintained compatibility in the Windows API; Windows 1.x applications ran unchanged in the 2.0 family. - X11R3. The X11 API was layered correctly: as long as the server follows the protocol spec, it doesn't matter what it does under the covers. I added support for new hardware to the ddx layer; wrote new window managers with completely different look-and-feel from the standard ones; added extensions to X11 itself. None of that interfered with existing clients one bit. - The 4.3 BSD kernel. Extended multihead support in the console driver and wrote some drivers for new hardware. Enhanced the shared memory kernel option. Nothing that didn't want to use the new features needed to be recompiled. - A number of Micro Focus commercial products and components thereof: AAI, CSB, CCI, MFCC ... These are commercial APIs used by paying customers to build in-house and ISV commercial applications. Changing them and breaking existing mission-critical applications isn't good for business. But we release updates a few times a year for most of them. Take AAI, for example. AAI 1.0 came out in 1988, and had major new releases for the next 10 years. Typical AAI purchases were in the $10K to $300K range, with yearly maintenance fees. The 1998 release had a feature set probably five times as large as in the 1988 release and ran on a dozen more platforms (from 16-bit Windows to big iron). We still shipped, as one of the demos, the original 1988 demo source - unchanged. The *binaries* from 1988 still ran, unchanged. The 1988 AAI clients and servers interoperated with the 1998 ones, with no user intervention (just a bit of automatic protocol negotiation). Maintaining backward compatibility simply is not that hard. I am still pretty convinced that compatibility and progress are fairly incompatible notions when it comes to the development of _usable_ libraries. And I'll say that my experience as a professional software developer for 20 years, and as a hobbyist for a number of years prior to that, shows me otherwise. you try to provide everything and the kitchen sink, and end up with design and implementation decisions that need to be re-evaluated from time to time in the presence of new environments. Java and Python, or anything including a GUI comes to mind. I'll offer X11 as a counterexample. And in this case, we're talking C and C++ runtimes, which should conform to the ISO standard anyway. Ah... should they conform to the Standard or should they be compatible to older versions? To the standard. What is supposed to happen if an existing version does _not_ conform to the Standard? Since the standards attempt to codify existing practice, that rarely happens. The only case that comes to mind of an incompatible change in the C standard, between C90 (ISO 9899-1990) and C99, is the choice of return code semantics for snprintf when it was added to the standard. There were two implementations with different semantics; the committee chose the sensible one. The only significant broken implementations by that point were HP's and Microsoft's, and Microsoft's doesn't really count because 1) the canonical name of the function in the Microsoft libraries was _sprintf, an identifier reserved to the implementation, and 2) Microsoft wasn't inclined to follow the standard anyway. Also: What am I supposed to do in case there is no obvious standard to adhere to? I have e.g. a few hundred kLOC of pre-1998 C++ code (done well before 1998...) around that's uncompilable with todays compilers. Who is to blame here? Should g++ have sticked to 2.95's view of the world? That's not a dynamic-runtime issue, which is what we were discussing. It's another problem entirely - the overly large and loose definition of the C++ language. In particular that would mean not only source and binary but also behavioural compatibility including keeping buggy behaviour. No it doesn't. Undefined behavior is undefined; an application that relies on it is broken. What is an application supposed to do when it lives in an environment where only buggy libraries are available? Suck it up? Might as well ask what a car is supposed to do in an environment with no roads. That's not a design failure in the car, nor a mistake on the part of the car's engineers; and neither does it mean that cars are a bad idea. And for the rare application that does, there are other Windows mechanisms
Re: Problems with installing GNU Aspell 0.60.6 on OSX 10.5.5
jezZiFeR wrote: No, but I´ve downloaded it now. Which components would I have to install? Sytem Tools and UNIX Development Support? Could I uninstall this tools after having installed Aspell? Thanks! I am not sure exactly which portion provides the compiling code, I installed the whole package. 2GB total installed size, and you may do what you like with it afterwards. 2008/11/24 Zan [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Do you have the mac developer tools installed? They are available for download (large requiring registration) on the Mac site. jezZiFeR wrote: »make: *** No targets specified and no makefile found. Stop. jzs-ibook-g4:aspell-0.60.6 stefan$« z
Re: lyx2lyx script broken (1.6.0 on Vista)
On Sun, Nov 23, 2008 at 10:26:30AM -0500, Michael Wojcik wrote: Jean-Marc Lasgouttes wrote: Completely infeasible on Windows. The loss of shared text would make the working set of the typical application mix grossly exceed even the absurd amounts of RAM available in typical machines today. The disk space problem would be even worse. I meant just for application which feel that they have to distribute their own version-of-the-day of whatever.dll. There is no reason to do it everywhere of course. Still not feasible, unfortunately, because that includes everything linked with any of the Microsoft C/C++ runtime DLLs. *cough* We were _not_ talking about statically linking _everything_. We were talking about things like Qt which are not a typical part of a Windows system. This is the central problem: if you build an application that uses anything in the MS C/C++ library (Microsoft combines the C and C++ standard libraries into a single DLL), which means pretty much anything built with a Microsoft C or C++ compiler, or with the Microsoft Platform SDK, you'll link against some specific version of one or more of the MSVC DLLs. You don't have much choice about which version you get - it depends on what version of the compiler or SDK you have installed, and what updates have been applied to it. [...] [...] [...] You are fighting windmills. Andre'
Re: lyx2lyx script broken (1.6.0 on Vista)
On Sun, Nov 23, 2008 at 11:21:27AM -0500, Michael Wojcik wrote: Andre Poenitz wrote: On Tue, Nov 18, 2008 at 03:42:52PM -0500, Michael Wojcik wrote: Andre Poenitz wrote: On Mon, Nov 17, 2008 at 11:07:05AM -0500, Paul A. Rubin wrote: I've worked on many projects that maintained backward compatibility with new releases of the API, and seen a great many more. Just for my curiosity: Which projects, which scope? Hmm. Off the top of my head, in roughly chronological order: - Various IBM internal-only projects, such as the E editor. - Early versions of Windows. The Windows 1.x to Windows 2.0 and Windows/286 transition maintained compatibility in the Windows API; Windows 1.x applications ran unchanged in the 2.0 family. Windows 2.0 was released pretty exactly two years after 1.0, Windows 3.0 completely broke the API 2 1/2 years later. So, at best, that's a period of 4.5 years of API stability. That's close to a joke, especially when taking into account that 3.11 was not usable for any reasonable practical purpose... - X11R3. The X11 API was layered correctly: as long as the server follows the protocol spec, it doesn't matter what it does under the covers. I added support for new hardware to the ddx layer; wrote new window managers with completely different look-and-feel from the standard ones; added extensions to X11 itself. None of that interfered with existing clients one bit. X11R3: End of 88, X11R4: End of 89. In any case, this is a nice example for something that is finished at some point of time. Nobody changed 7 bit ASCII for a while for that matter. If a feature set is closed at some point of time it is easy to outsource the problems to extensions and toolkits. Pretty much around 1990 supposedly the last person died that used plain X. [No, that was not me *cough*] SCNR ;-) - The 4.3 BSD kernel. Extended multihead support in the console driver and wrote some drivers for new hardware. Enhanced the shared memory kernel option. Nothing that didn't want to use the new features needed to be recompiled. Spring (?) 2001 - January 2002. I can't/won't comment on the others. Maintaining backward compatibility simply is not that hard. We are _not_ talking about _two_ years here. I can maintain compatibility over two years by simply ignoring advancements in the outside world for that long and release incompatible version x+1 after that. I am still pretty convinced that compatibility and progress are fairly incompatible notions when it comes to the development of _usable_ libraries. And I'll say that my experience as a professional software developer for 20 years, and as a hobbyist for a number of years prior to that, shows me otherwise. Fine. My experience so far shows that one has a choice between stagnation and breaking compatibility. And making that choice is neither obvious nor easy. you try to provide everything and the kitchen sink, and end up with design and implementation decisions that need to be re-evaluated from time to time in the presence of new environments. Java and Python, or anything including a GUI comes to mind. I'll offer X11 as a counterexample. X11 has certainly its merits and is time proven. Still it puts a lot of burden on the application developer, or, at the very least, on the toolkit developer. Lots of the initial design decisions that do not scale well into the 21st century are only bearable because of the outsourcing mentioned above. Plain X11 does _not_ come with kitchen sinks. And in this case, we're talking C and C++ runtimes, which should conform to the ISO standard anyway. Ah... should they conform to the Standard or should they be compatible to older versions? To the standard. That rules out fixing bugs, and it also breaks compatibility. I do not say that's a bad choice - in fact that's what I'd do in most cases - but it is incompatible with your statement that maintaining compatibility is possible _and easy_. What is supposed to happen if an existing version does _not_ conform to the Standard? Since the standards attempt to codify existing practice, that rarely happens. Hear, hear. How come ISO 14882 codifies export for templates when not a single compiler was able to handle that in 1998 (and for a few years after that)? Apart from that the point is not how often it happens but that it happens at all. You just admit that it happens. The only case that comes to mind of an incompatible change in the C standard, between C90 (ISO 9899-1990) and C99, is the choice of return code semantics for snprintf when it was added to the standard. There were two implementations with different semantics; the committee chose the sensible one. The only significant broken implementations by that point were HP's and Microsoft's, and Microsoft's doesn't really count because 1) the canonical name of the function in the Microsoft libraries was _sprintf, an identifier reserved to the