Re: The tortured release of 2.3.0 Windows binaries
On 2018-05-14 19:22, Richard Kimberly Heck wrote: refused, and has refused again in the last couple days. His view is that this kind of warning will confuse some users and that those same users are at risk of having broken installations if we do not do the upgrade for them. So his view is that we should do the upgrade silently. I find Silent updates of software that is not maintained/released by the LyX team would be a betrayal of user trust. I think you made the right call. Regards, Walter
Re: Google Analytics (or other)
On 2017-06-20 12:54, Trevor Jenkins wrote: Link to Google Analytics and this user will delete all traces of LyX from their systems never to re-install. Same here. Massive violation of user trust. Just put up a Piwik install on a VPS someplace and you can achieve the same. Besides, you'll be in violation of EU legislation. Regards, Walter
Re: Koma-script letter error
On 29/05/2016 15:25, Michael Berger wrote: > Ron, the information you provide is too general; that Latex Error may > also be generated in hundreds of other cases. > Please, be more specific. The name is Walter. Anyway, as a user this is the error that gets presented to you. If that is not specific enough, it might be worthwhile to have more specific error message. Either way, it was a PEBCAK, I had been using the Adress field twice and omitted to use "end of letter" (which I do not remember being part of KOMA-Script Letter v2 earlier). Regards, Walter
Koma-script letter error
Hi all, When trying to use the Koma-script Letter template I get this error:\ ! LaTeX Error: \begin{letter} on input line 27 ended by \end{document}. \end{document} Your command was ignored. Type Ito replace it with another command, orto continue without it. Suggestions on how to deal with this would be most welcome. Regards, Walter
Re: why people give up on open source software
On 24/10/2013 07:32, Richard Talley wrote: I've read good things about Scrivener. It's more a 'book project management' program than a word processor. I know some people use it for everything until it's time to print, then they export to LaTeX. Good luck with it. A somewhat close analog to Scrivener is CeltX. I prefer Scrivener over CeltX, but if FOSS is a principle, I'd recommend looking into CeltX. Regards, Walter
Re: why people give up on open source software
On 24/10/2013 07:32, Richard Talley wrote: I've read good things about Scrivener. It's more a 'book project management' program than a word processor. I know some people use it for everything until it's time to print, then they export to LaTeX. Good luck with it. A somewhat close analog to Scrivener is CeltX. I prefer Scrivener over CeltX, but if FOSS is a principle, I'd recommend looking into CeltX. Regards, Walter
Re: why people give up on open source software
On 24/10/2013 07:32, Richard Talley wrote: > I've read good things about Scrivener. It's more a 'book project > management' program than a word processor. I know some people use it for > everything until it's time to print, then they export to LaTeX. Good > luck with it. A somewhat close analog to Scrivener is CeltX. I prefer Scrivener over CeltX, but if FOSS is a principle, I'd recommend looking into CeltX. Regards, Walter
Re: Disable copy and paste
On 8 aug. 2013, at 10:17, Rilke Rainer Michael ri...@wiso.uni-koeln.de wrote: Hi List, I want to export a lyx document to a pdf. However, I want also that once reading the document it is impossible to copy and paste text from this pdf. Do you have any idea, whether there is a workaround for lyx? Basically you want DRM. Which is silly at best.
Re: Disable copy and paste
On 8 aug. 2013, at 10:17, Rilke Rainer Michael ri...@wiso.uni-koeln.de wrote: Hi List, I want to export a lyx document to a pdf. However, I want also that once reading the document it is impossible to copy and paste text from this pdf. Do you have any idea, whether there is a workaround for lyx? Basically you want DRM. Which is silly at best.
Re: Disable copy and paste
On 8 aug. 2013, at 10:17, Rilke Rainer Michaelwrote: > Hi List, > > I want to export a lyx document to a pdf. However, I want also that once > reading the document it is impossible to copy and paste text from this pdf. > Do you have any idea, whether there is a workaround for lyx? > Basically you want DRM. Which is silly at best.
Re: feature request: ribbon menus
On 2013-04-05 16:49, Alex Vergara Gil wrote: As I said this is my personal opinion so I migth be wrong, but I haven´t received any useful opinion (besides M$ patent) of why not doing such a thing just a few user complaining they will affect some how what they feel is comfortable. Regarding the patent believe me that if they patent 0s and 1s then we are definitively lost.:) Several people have responded that ribbon menus have limited use to them, to say the least. I don't think that is a useless opinion. As someone who spends most of his working hours in Microsoft's ribbon menus, allow me to add to the chorus that ribbon menus tend to be spiteful and useless. And no, they don't really grow on you. I have no idea what flavour of LSD Microsoft's usability experts have been consuming, but I hope it is widely available so that if I ever contract a terminal disease I'd like to spend my final hours tripping on that stuff. I'd much rather have people spend time on a concurrent user web front-end. Or a curses front-end to LyX. Either of these two are more likely to serve users well than the bloody ribbon menus. Regards, Walter
Re: feature request: ribbon menus
On 2013-04-05 16:49, Alex Vergara Gil wrote: As I said this is my personal opinion so I migth be wrong, but I haven´t received any useful opinion (besides M$ patent) of why not doing such a thing just a few user complaining they will affect some how what they feel is comfortable. Regarding the patent believe me that if they patent 0s and 1s then we are definitively lost.:) Several people have responded that ribbon menus have limited use to them, to say the least. I don't think that is a useless opinion. As someone who spends most of his working hours in Microsoft's ribbon menus, allow me to add to the chorus that ribbon menus tend to be spiteful and useless. And no, they don't really grow on you. I have no idea what flavour of LSD Microsoft's usability experts have been consuming, but I hope it is widely available so that if I ever contract a terminal disease I'd like to spend my final hours tripping on that stuff. I'd much rather have people spend time on a concurrent user web front-end. Or a curses front-end to LyX. Either of these two are more likely to serve users well than the bloody ribbon menus. Regards, Walter
Re: feature request: ribbon menus
On 2013-04-05 16:49, Alex Vergara Gil wrote: As I said this is my personal opinion so I migth be wrong, but I haven´t received any useful opinion (besides M$ patent) of why not doing such a thing just a few user complaining they will affect some how what they feel is comfortable. Regarding the patent believe me that if they patent 0s and 1s then we are definitively lost.:) Several people have responded that ribbon menus have limited use to them, to say the least. I don't think that is a useless opinion. As someone who spends most of his working hours in Microsoft's ribbon menus, allow me to add to the chorus that ribbon menus tend to be spiteful and useless. And no, they don't really grow on you. I have no idea what flavour of LSD Microsoft's usability experts have been consuming, but I hope it is widely available so that if I ever contract a terminal disease I'd like to spend my final hours tripping on that stuff. I'd much rather have people spend time on a concurrent user web front-end. Or a curses front-end to LyX. Either of these two are more likely to serve users well than the bloody ribbon menus. Regards, Walter
Re: Non-Latin font in document
I have found XeTeX the best for foreign font output. I use the following under Document|Settings|LaTeX preamble: % required for xelatex \usepackage{doc} % defines \bibtex macro \usepackage{fontspec} \usepackage{xunicode} \usepackage{xltxtra} % apparently for fontspec, not sure if actually needed \defaultfontfeatures{Mapping=tex-text} %: --- set up commands for different fonts for each language. %: - thai font \newfontfamily{\TH}[Scale=1.2]{Norasi} \newcommand{\thai}[1]{{\TH #1}} %: - chinese %\newfontfamily{\CH}[Scale=1]{LiSong Pro} \newfontfamily{\CH}[Scale=1]{AR PL UMing CN} ... once you have that, under 'Edit|Language' you can select Thai and it should come out, assuming you have the Norasi font. - Walter
Re: Non-Latin font in document
I have found XeTeX the best for foreign font output. I use the following under Document|Settings|LaTeX preamble: % required for xelatex \usepackage{doc} % defines \bibtex macro \usepackage{fontspec} \usepackage{xunicode} \usepackage{xltxtra} % apparently for fontspec, not sure if actually needed \defaultfontfeatures{Mapping=tex-text} %: --- set up commands for different fonts for each language. %: - thai font \newfontfamily{\TH}[Scale=1.2]{Norasi} \newcommand{\thai}[1]{{\TH #1}} %: - chinese %\newfontfamily{\CH}[Scale=1]{LiSong Pro} \newfontfamily{\CH}[Scale=1]{AR PL UMing CN} ... once you have that, under 'Edit|Language' you can select Thai and it should come out, assuming you have the Norasi font. - Walter
Re: Non-Latin font in document
I have found XeTeX the best for foreign font output. I use the following under Document|Settings|LaTeX preamble: % required for xelatex \usepackage{doc} % defines \bibtex macro \usepackage{fontspec} \usepackage{xunicode} \usepackage{xltxtra} % apparently for fontspec, not sure if actually needed \defaultfontfeatures{Mapping=tex-text} %: --- set up commands for different fonts for each language. %: - thai font \newfontfamily{\TH}[Scale=1.2]{Norasi} \newcommand{\thai}[1]{{\TH #1}} %: - chinese %\newfontfamily{\CH}[Scale=1]{LiSong Pro} \newfontfamily{\CH}[Scale=1]{AR PL UMing CN} ... once you have that, under 'Edit|Language' you can select Thai and it should come out, assuming you have the Norasi font. - Walter
Newlines or vertical spaces in table cells
Hi there, Apologies if there is some documentation for this - I couldn't find it. Is there some way to force a newline or vertical space within a table cell's contents? At the moment many of my larger tables exceed a page width and I would prefer to (automatically, if posible - otherwise manually) enforce line breaks within wider table cells. Thanks, Walter
Newlines or vertical spaces in table cells
Hi there, Apologies if there is some documentation for this - I couldn't find it. Is there some way to force a newline or vertical space within a table cell's contents? At the moment many of my larger tables exceed a page width and I would prefer to (automatically, if posible - otherwise manually) enforce line breaks within wider table cells. Thanks, Walter
Newlines or vertical spaces in table cells
Hi there, Apologies if there is some documentation for this - I couldn't find it. Is there some way to force a newline or vertical space within a table cell's contents? At the moment many of my larger tables exceed a page width and I would prefer to (automatically, if posible - otherwise manually) enforce line breaks within wider table cells. Thanks, Walter
Re: Lion
On 7/20/11 6:24 PM, Anders Host-Madsen wrote: Has anyone tried LyX (2.0) under Mac OSX Lion? Has anyone encountered any problems? I will wait with upgrading until I know LyX can run under Lion. Lyx 2.0.0 beta 2 runs fine on Lion. However, lots of other applications behave wonky on Lion, so I would not necessarily recommend upgrading now. Regards, Walter
Re: Lion
On 7/20/11 6:24 PM, Anders Host-Madsen wrote: Has anyone tried LyX (2.0) under Mac OSX Lion? Has anyone encountered any problems? I will wait with upgrading until I know LyX can run under Lion. Lyx 2.0.0 beta 2 runs fine on Lion. However, lots of other applications behave wonky on Lion, so I would not necessarily recommend upgrading now. Regards, Walter
Re: Lion
On 7/20/11 6:24 PM, Anders Host-Madsen wrote: Has anyone tried LyX (2.0) under Mac OSX Lion? Has anyone encountered any problems? I will wait with upgrading until I know LyX can run under Lion. Lyx 2.0.0 beta 2 runs fine on Lion. However, lots of other applications behave wonky on Lion, so I would not necessarily recommend upgrading now. Regards, Walter
Linux 2.0.0RC2 - Mac 2.0.0RC3 = Issues
Due to a recent change in hardware, I have just tried to load my book on to LyX for Mac. Upon opening the file I get two errors about missing elements: - document.cls - languages module Is this expected, and how do I remedy? I'm pretty inexperienced with macs, but believe I should have copied all of the resources that went along with the original document to the new machine's filesystem, at the same relative locations (ie: parent directory and all within). Right now I am able to edit, but not generate PDF output. In addition to the above errors on opening the file, an attempt to render gives me: No information on how to convert SVG files to PNG. The imagmagick installation seems to require MacPorts which seems to require XCode which is opening a whole can of worms. Thanks for any pointers! - Walter
Lyx2.0.0RC3: OSX Keyboard Shortcuts Missing
This may be my own stupid lack of OSX knowledge, but none of: - fn+i - ctrl+i - alt/option+i - command/applesquigglything+i ... seem to actually trigger the 'insert' menu, one of the most common shortcuts I would use on the Linux platform, usually to insert notes or citations mid-text. Is this a real/known bug? If unknown I am hereby reporting it! If not the case then please advise how I can get my non-mousing input back. Cheers, Walter
Re: Linux 2.0.0RC2 - Mac 2.0.0RC3 = Issues
Due to a recent change in hardware, I have just tried to load my book on to LyX for Mac. Upon opening the file I get two errors about missing elements: - document.cls This suggests to me that you haven't installed LaTeX. The easiest way on Mac is to install MacTeX (http://www.tug.org/mactex/). Then reconfigure LyX, restart, and it should recognize document.cls and allow you to generate .pdfs. Thanks. Downloading now. - languages module This may be in your user's directory on your Linux machine (~/.lyx) and if so should be moved to the appropriate location on Mac (~/Library/Application Support/LyX-2.0). This was indeed missing and has now been copied in. Fingers crossed for success post download! Thanks a lot for your quick and accurate assistance: much appreciated. - Walter
Linux 2.0.0RC2 - Mac 2.0.0RC3 = Issues
Due to a recent change in hardware, I have just tried to load my book on to LyX for Mac. Upon opening the file I get two errors about missing elements: - document.cls - languages module Is this expected, and how do I remedy? I'm pretty inexperienced with macs, but believe I should have copied all of the resources that went along with the original document to the new machine's filesystem, at the same relative locations (ie: parent directory and all within). Right now I am able to edit, but not generate PDF output. In addition to the above errors on opening the file, an attempt to render gives me: No information on how to convert SVG files to PNG. The imagmagick installation seems to require MacPorts which seems to require XCode which is opening a whole can of worms. Thanks for any pointers! - Walter
Lyx2.0.0RC3: OSX Keyboard Shortcuts Missing
This may be my own stupid lack of OSX knowledge, but none of: - fn+i - ctrl+i - alt/option+i - command/applesquigglything+i ... seem to actually trigger the 'insert' menu, one of the most common shortcuts I would use on the Linux platform, usually to insert notes or citations mid-text. Is this a real/known bug? If unknown I am hereby reporting it! If not the case then please advise how I can get my non-mousing input back. Cheers, Walter
Re: Linux 2.0.0RC2 - Mac 2.0.0RC3 = Issues
Due to a recent change in hardware, I have just tried to load my book on to LyX for Mac. Upon opening the file I get two errors about missing elements: - document.cls This suggests to me that you haven't installed LaTeX. The easiest way on Mac is to install MacTeX (http://www.tug.org/mactex/). Then reconfigure LyX, restart, and it should recognize document.cls and allow you to generate .pdfs. Thanks. Downloading now. - languages module This may be in your user's directory on your Linux machine (~/.lyx) and if so should be moved to the appropriate location on Mac (~/Library/Application Support/LyX-2.0). This was indeed missing and has now been copied in. Fingers crossed for success post download! Thanks a lot for your quick and accurate assistance: much appreciated. - Walter
Linux 2.0.0RC2 -> Mac 2.0.0RC3 = Issues
Due to a recent change in hardware, I have just tried to load my book on to LyX for Mac. Upon opening the file I get two errors about missing elements: - document.cls - languages module Is this expected, and how do I remedy? I'm pretty inexperienced with macs, but believe I should have copied all of the resources that went along with the original document to the new machine's filesystem, at the same relative locations (ie: parent directory and all within). Right now I am able to edit, but not generate PDF output. In addition to the above errors on opening the file, an attempt to render gives me: "No information on how to convert SVG files to PNG". The imagmagick installation seems to require MacPorts which seems to require XCode which is opening a whole can of worms. Thanks for any pointers! - Walter
Lyx2.0.0RC3: OSX Keyboard Shortcuts Missing
This may be my own stupid lack of OSX knowledge, but none of: - +i - +i - +i - +i ... seem to actually trigger the 'insert' menu, one of the most common shortcuts I would use on the Linux platform, usually to insert notes or citations mid-text. Is this a real/known bug? If unknown I am hereby reporting it! If not the case then please advise how I can get my non-mousing input back. Cheers, Walter
Re: Linux 2.0.0RC2 -> Mac 2.0.0RC3 = Issues
>> Due to a recent change in hardware, I have just tried to load my book >> on to LyX for Mac. >> >> Upon opening the file I get two errors about missing elements: >> - document.cls > > This suggests to me that you haven't installed LaTeX. The easiest way > on Mac is to install MacTeX (http://www.tug.org/mactex/). Then > reconfigure LyX, restart, and it should recognize document.cls and > allow you to generate .pdfs. Thanks. Downloading now. >> - languages module > > This may be in your user's directory on your Linux machine (~/.lyx) > and if so should be moved to the appropriate location on Mac > (~/Library/Application Support/LyX-2.0). This was indeed missing and has now been copied in. Fingers crossed for success post download! Thanks a lot for your quick and accurate assistance: much appreciated. - Walter
Timeline generation
Hi all, Does anyone have a good solution to generate timelines? Features that are required: - Allows marking of both specific events (point in time) and periods (range in time) Features that are highly desired: - Properly functional unicode support (right to left support not required at this stage, but otherwise font switching for arbitrary languages) Features that would be a bonus: - Handles the case of 'so many elements you'd be lucky to get them to fit on a page' elegantly (eg: by scaling layout down to a minimum threshold size for legibility, then page-splitting) - Accepts input as a simply delimited text file (ala graphviz .dot files or mscgen .msc files) Any recommendations would be appreciated. I have seen a few non-LyX specific solutions already but they all seem to lack what I want. Having said that, if all else fails I suppose I could try to write one (with only required features), maybe call it 'escgen' (event sequent chart generator) in deference to its high quality predecessor. However, it seems like a good example in raw TeX would be enough for me to get some macros going and a more elegant solution (ie: no need to re-implement unicode font support, no need to step out to an external generation/update process). Could anyone point one out? Cheers - Walter
Re: ** ERROR ** Invalid font: -1 (8)
My LyX file references a number of fonts however I have not been able to successfully convert to PDF for some time due to various reasons. I have solved them all bar this one, and am quite stumped. To help anyone else with equivalent strangeness (for the record), I was able to resolve the error using the following method of debugging: 1. Create a totally new LyX document 2. Test render (result = ok) 3. Copy my real document's LyX preamble in to the new document 4. Test render (result = fail) 5. Isolate the preamble portion causing issues by repeated commenting in the preamble/re-rendering 6. Test render (result = ok) 7. Copy my real document's content in to the new document 8. Test render (result = fail) 9. Delete portions of the content until isolating the cause, which was some language/style related commands that were previously prerequisites for functional multilingual rendering with proper fonts and may have been related to the legacy preamble. After some experimenting with the recent builds (now LyX 2.0.0 RC2) the language setting is not required for rendering properly, only setting a text-style per foreign language section, plus ensuring some equivalent preamble to set the font. (Originally I had to do both!) I now have a document that correctly mixes Chinese, English, Greek and will render out to PDF. UTF-16 warnings remain but do not appear to affect the output. Thus far I have been unable to get Farsi text to render out correctly, but have not spent too much time on the problem. - Walter
Timeline generation
Hi all, Does anyone have a good solution to generate timelines? Features that are required: - Allows marking of both specific events (point in time) and periods (range in time) Features that are highly desired: - Properly functional unicode support (right to left support not required at this stage, but otherwise font switching for arbitrary languages) Features that would be a bonus: - Handles the case of 'so many elements you'd be lucky to get them to fit on a page' elegantly (eg: by scaling layout down to a minimum threshold size for legibility, then page-splitting) - Accepts input as a simply delimited text file (ala graphviz .dot files or mscgen .msc files) Any recommendations would be appreciated. I have seen a few non-LyX specific solutions already but they all seem to lack what I want. Having said that, if all else fails I suppose I could try to write one (with only required features), maybe call it 'escgen' (event sequent chart generator) in deference to its high quality predecessor. However, it seems like a good example in raw TeX would be enough for me to get some macros going and a more elegant solution (ie: no need to re-implement unicode font support, no need to step out to an external generation/update process). Could anyone point one out? Cheers - Walter
Re: ** ERROR ** Invalid font: -1 (8)
My LyX file references a number of fonts however I have not been able to successfully convert to PDF for some time due to various reasons. I have solved them all bar this one, and am quite stumped. To help anyone else with equivalent strangeness (for the record), I was able to resolve the error using the following method of debugging: 1. Create a totally new LyX document 2. Test render (result = ok) 3. Copy my real document's LyX preamble in to the new document 4. Test render (result = fail) 5. Isolate the preamble portion causing issues by repeated commenting in the preamble/re-rendering 6. Test render (result = ok) 7. Copy my real document's content in to the new document 8. Test render (result = fail) 9. Delete portions of the content until isolating the cause, which was some language/style related commands that were previously prerequisites for functional multilingual rendering with proper fonts and may have been related to the legacy preamble. After some experimenting with the recent builds (now LyX 2.0.0 RC2) the language setting is not required for rendering properly, only setting a text-style per foreign language section, plus ensuring some equivalent preamble to set the font. (Originally I had to do both!) I now have a document that correctly mixes Chinese, English, Greek and will render out to PDF. UTF-16 warnings remain but do not appear to affect the output. Thus far I have been unable to get Farsi text to render out correctly, but have not spent too much time on the problem. - Walter
Timeline generation
Hi all, Does anyone have a good solution to generate timelines? Features that are required: - Allows marking of both specific events ("point in time") and periods ("range in time") Features that are highly desired: - Properly functional unicode support (right to left support not required at this stage, but otherwise font switching for arbitrary languages) Features that would be a bonus: - Handles the case of 'so many elements you'd be lucky to get them to fit on a page' elegantly (eg: by scaling layout down to a minimum threshold size for legibility, then page-splitting) - Accepts input as a simply delimited text file (ala graphviz .dot files or mscgen .msc files) Any recommendations would be appreciated. I have seen a few non-LyX specific solutions already but they all seem to lack what I want. Having said that, if all else fails I suppose I could try to write one (with only required features), maybe call it 'escgen' (event sequent chart generator) in deference to its high quality predecessor. However, it seems like a good example in raw TeX would be enough for me to get some macros going and a more elegant solution (ie: no need to re-implement unicode font support, no need to step out to an external generation/update process). Could anyone point one out? Cheers - Walter
Re: ** ERROR ** Invalid font: -1 (8)
>> My LyX file references a number of fonts however I have not been able to >> successfully convert to PDF for some time due to various reasons. I have >> solved them all bar this one, and am quite stumped. To help anyone else with equivalent strangeness (for the record), I was able to resolve the error using the following method of debugging: 1. Create a totally new LyX document 2. Test render (result = ok) 3. Copy my real document's LyX preamble in to the new document 4. Test render (result = fail) 5. Isolate the preamble portion causing issues by repeated commenting in the preamble/re-rendering 6. Test render (result = ok) 7. Copy my real document's content in to the new document 8. Test render (result = fail) 9. Delete portions of the content until isolating the cause, which was some language/style related commands that were previously prerequisites for functional multilingual rendering with proper fonts and may have been related to the legacy preamble. After some experimenting with the recent builds (now LyX 2.0.0 RC2) the language setting is not required for rendering properly, only setting a text-style per foreign language section, plus ensuring some equivalent preamble to set the font. (Originally I had to do both!) I now have a document that correctly mixes Chinese, English, Greek and will render out to PDF. UTF-16 warnings remain but do not appear to affect the output. Thus far I have been unable to get Farsi text to render out correctly, but have not spent too much time on the problem. - Walter
Re: A basic requested feature
On Thu, April 14, 2011 10:43, Stephan Witt wrote: Nowadays modern desktop systems are providing the capability to search your files, e. g. by content. Normally it is supported by indexing services, so it should give you quick answer to arbitrary questions. Proposing a filename is not such an importing feature, IMHO. And it is not easy to get it right. I' always expect different points of view, how this should work. It definitely is not easy to get 100% right, 80% would be interesting enough. I disagree on the desktop search bit, that is mostly helpful if you know a lot about the document you are looking for. I would find a name-suggester that would take: The current date, e.g. 20110414, an abbreviation of the style you are using, for example 'LTR' for letters and the subject of the document plus a version number useful. The most work is probably expanding the various document styles to include a field that refers to another field that is the most suitable source for the subject and an abbreviation scheme. And this assumes of course that people rarely use their own document styles. Regards, Walter
Re: A basic requested feature
On Thu, April 14, 2011 10:43, Stephan Witt wrote: Nowadays modern desktop systems are providing the capability to search your files, e. g. by content. Normally it is supported by indexing services, so it should give you quick answer to arbitrary questions. Proposing a filename is not such an importing feature, IMHO. And it is not easy to get it right. I' always expect different points of view, how this should work. It definitely is not easy to get 100% right, 80% would be interesting enough. I disagree on the desktop search bit, that is mostly helpful if you know a lot about the document you are looking for. I would find a name-suggester that would take: The current date, e.g. 20110414, an abbreviation of the style you are using, for example 'LTR' for letters and the subject of the document plus a version number useful. The most work is probably expanding the various document styles to include a field that refers to another field that is the most suitable source for the subject and an abbreviation scheme. And this assumes of course that people rarely use their own document styles. Regards, Walter
Re: A basic requested feature
On Thu, April 14, 2011 10:43, Stephan Witt wrote: > Nowadays modern desktop systems are providing the capability to search > your files, e. g. by content. > Normally it is supported by indexing services, so it should give you > quick answer to > arbitrary questions. Proposing a filename is not such an importing > feature, IMHO. > And it is not easy to get it right. I' always expect different points > of view, how this should work. It definitely is not easy to get 100% right, 80% would be interesting enough. I disagree on the desktop search bit, that is mostly helpful if you know a lot about the document you are looking for. I would find a name-suggester that would take: The current date, e.g. 20110414, an abbreviation of the style you are using, for example 'LTR' for letters and the subject of the document plus a version number useful. The most work is probably expanding the various document styles to include a field that refers to another field that is the most suitable source for the subject and an abbreviation scheme. And this assumes of course that people rarely use their own document styles. Regards, Walter
** ERROR ** Invalid font: -1 (8)
Could someone please enlighten me as to the correct method of resolving this error? My LyX file references a number of fonts however I have not been able to successfully convert to PDF for some time due to various reasons. I have solved them all bar this one, and am quite stumped. I don't recall changing any fonts since the last time I successfully output to PDF (albeit back on 1.6, this is now 2.0rc2). Other than going in to the LyX file manually and replacing all font references with a 'known good' one, is there any way to know which line this error actually references? As error messages go, this one seems pretty opaque. Full output of progress/debug messages follow... 12:30:55.079: Previewing ... 12:30:55.108: (buffer-view: Ctrl+R) 12:30:55.284: xelatex story.tex 12:30:55.318: This is XeTeX, Version 3.1415926-2.2-0.9997.4 (TeX Live 2010) 12:30:55.319: restricted \write18 enabled. 12:30:55.468: entering extended mode 12:30:55.472: (./story.tex 12:30:55.475: LaTeX2e 2009/09/24 12:30:55.477: Babel v3.8l and hyphenation patterns for english, dumylang, nohyphenation, pi 12:30:55.478: nyin, ukenglish, usenglishmax, loaded. 12:30:55.480: 12:30:55.934: 12:30:55.936: ** WARNING ** Failed to convert input string to UTF16... 12:30:56.070: ** ERROR ** Invalid font: -1 (8) 12:30:56.072: 12:30:56.073: Output file removed. 12:30:56.082: The process crashed some time after starting successfully. 12:30:56.119: xelatex story.tex 12:30:56.156: This is XeTeX, Version 3.1415926-2.2-0.9997.4 (TeX Live 2010) 12:30:56.161: restricted \write18 enabled. 12:30:56.311: entering extended mode 12:30:56.312: (./story.tex 12:30:56.312: LaTeX2e 2009/09/24 12:30:56.313: Babel v3.8l and hyphenation patterns for english, dumylang, nohyphenation, pi 12:30:56.313: nyin, ukenglish, usenglishmax, loaded. 12:30:56.314: 12:30:56.774: 12:30:56.775: ** WARNING ** Failed to convert input string to UTF16... 12:30:56.909: ** ERROR ** Invalid font: -1 (8) 12:30:56.910: 12:30:56.910: Output file removed. 12:30:56.920: The process crashed some time after starting successfully.Error: Cannot view file File does not exist: /tmp/lyx_tmpdir.M22972/lyx_tmpbuf0/story.pdf 12:30:58.133: Error while previewing format: pdf4 - Walter
** ERROR ** Invalid font: -1 (8)
Could someone please enlighten me as to the correct method of resolving this error? My LyX file references a number of fonts however I have not been able to successfully convert to PDF for some time due to various reasons. I have solved them all bar this one, and am quite stumped. I don't recall changing any fonts since the last time I successfully output to PDF (albeit back on 1.6, this is now 2.0rc2). Other than going in to the LyX file manually and replacing all font references with a 'known good' one, is there any way to know which line this error actually references? As error messages go, this one seems pretty opaque. Full output of progress/debug messages follow... 12:30:55.079: Previewing ... 12:30:55.108: (buffer-view: Ctrl+R) 12:30:55.284: xelatex story.tex 12:30:55.318: This is XeTeX, Version 3.1415926-2.2-0.9997.4 (TeX Live 2010) 12:30:55.319: restricted \write18 enabled. 12:30:55.468: entering extended mode 12:30:55.472: (./story.tex 12:30:55.475: LaTeX2e 2009/09/24 12:30:55.477: Babel v3.8l and hyphenation patterns for english, dumylang, nohyphenation, pi 12:30:55.478: nyin, ukenglish, usenglishmax, loaded. 12:30:55.480: 12:30:55.934: 12:30:55.936: ** WARNING ** Failed to convert input string to UTF16... 12:30:56.070: ** ERROR ** Invalid font: -1 (8) 12:30:56.072: 12:30:56.073: Output file removed. 12:30:56.082: The process crashed some time after starting successfully. 12:30:56.119: xelatex story.tex 12:30:56.156: This is XeTeX, Version 3.1415926-2.2-0.9997.4 (TeX Live 2010) 12:30:56.161: restricted \write18 enabled. 12:30:56.311: entering extended mode 12:30:56.312: (./story.tex 12:30:56.312: LaTeX2e 2009/09/24 12:30:56.313: Babel v3.8l and hyphenation patterns for english, dumylang, nohyphenation, pi 12:30:56.313: nyin, ukenglish, usenglishmax, loaded. 12:30:56.314: 12:30:56.774: 12:30:56.775: ** WARNING ** Failed to convert input string to UTF16... 12:30:56.909: ** ERROR ** Invalid font: -1 (8) 12:30:56.910: 12:30:56.910: Output file removed. 12:30:56.920: The process crashed some time after starting successfully.Error: Cannot view file File does not exist: /tmp/lyx_tmpdir.M22972/lyx_tmpbuf0/story.pdf 12:30:58.133: Error while previewing format: pdf4 - Walter
** ERROR ** Invalid font: -1 (8)
Could someone please enlighten me as to the correct method of resolving this error? My LyX file references a number of fonts however I have not been able to successfully convert to PDF for some time due to various reasons. I have solved them all bar this one, and am quite stumped. I don't recall changing any fonts since the last time I successfully output to PDF (albeit back on 1.6, this is now 2.0rc2). Other than going in to the LyX file manually and replacing all font references with a 'known good' one, is there any way to know which line this error actually references? As error messages go, this one seems pretty opaque. Full output of progress/debug messages follow... 12:30:55.079: Previewing ... 12:30:55.108: (buffer-view: Ctrl+R) 12:30:55.284: xelatex "story.tex" 12:30:55.318: This is XeTeX, Version 3.1415926-2.2-0.9997.4 (TeX Live 2010) 12:30:55.319: restricted \write18 enabled. 12:30:55.468: entering extended mode 12:30:55.472: (./story.tex 12:30:55.475: LaTeX2e <2009/09/24> 12:30:55.477: Babel and hyphenation patterns for english, dumylang, nohyphenation, pi 12:30:55.478: nyin, ukenglish, usenglishmax, loaded. 12:30:55.480: 12:30:55.934: 12:30:55.936: ** WARNING ** Failed to convert input string to UTF16... 12:30:56.070: ** ERROR ** Invalid font: -1 (8) 12:30:56.072: 12:30:56.073: Output file removed. 12:30:56.082: The process crashed some time after starting successfully. 12:30:56.119: xelatex "story.tex" 12:30:56.156: This is XeTeX, Version 3.1415926-2.2-0.9997.4 (TeX Live 2010) 12:30:56.161: restricted \write18 enabled. 12:30:56.311: entering extended mode 12:30:56.312: (./story.tex 12:30:56.312: LaTeX2e <2009/09/24> 12:30:56.313: Babel and hyphenation patterns for english, dumylang, nohyphenation, pi 12:30:56.313: nyin, ukenglish, usenglishmax, loaded. 12:30:56.314: 12:30:56.774: 12:30:56.775: ** WARNING ** Failed to convert input string to UTF16... 12:30:56.909: ** ERROR ** Invalid font: -1 (8) 12:30:56.910: 12:30:56.910: Output file removed. 12:30:56.920: The process crashed some time after starting successfully.Error: Cannot view file File does not exist: /tmp/lyx_tmpdir.M22972/lyx_tmpbuf0/story.pdf 12:30:58.133: Error while previewing format: pdf4 - Walter
Re: Poll for the default icon theme in LyX 2.0
libreoffice ... since it will grow and support the holy grail of open source user experience consistency :) - Walter
Re: Poll for the default icon theme in LyX 2.0
libreoffice ... since it will grow and support the holy grail of open source user experience consistency :) - Walter
Re: Poll for the default icon theme in LyX 2.0
libreoffice ... since it will grow and support the holy grail of open source user experience consistency :) - Walter
Re: Subject: LyX 2.0beta3: Spell Checking + Multilingualism
which input in that unicode block automatically sets language markup) could also be 'primary dictionary' for language detection (eg: when pasting large blocks of text, opening legacy files, falling back to (1) from (2) as described above, or whatever...). Finally, some left-field techniques may also be available, like making API calls out to Google Translate for 'outsourced' language detection! 6. Dictionary Re-Use Support [*] - Another point is that of re-use. Which is to say that, when someone uses for example 'BibTeX' to compile a biliographic database, that database may easily be used with other projects and is considered portable. So for all physics papers I can use one bibliography, and I may have another for history papers. Whilst this is presently handled adequately by LyX, the equivalent functionality is not present for dictionary databases. It should be. This means both adding a 'manage multiple dictionaries in this project' feature-set, and adding a 'which dictionary do you want to add the word to' drop-down in the right hand spellchecker sidebar. This is a good idea (already mentioned on developers list, AFAICR). The idea is to incorporate a personal dictionary into the document. But it definitively will not happen tomorrow. Great, as long as the personal dictionary in the document is saved outside the document and as a file that can be: a) shared between multiple documents b) used with zero or more additional personal dictionaries within a single file c) identified as the target dictionary (vs. other active personal dictionaries) when spell-checking the document and adding words to personal dictionaries The externally saved personal dictionary is shared between multiple documents per se. I am unclear on the suggested implementation, however any assumption that all documents a user is editing should use the same personal dictionary is flawed. From your next comment, I think you see this... My idea was to provide the dictionary inside the document as an alternative. If you are sure a word is correctly spelled you want to transfer this know how with the document. This is a good idea however it is not nearly as flexible as the established and proven BiBTeX approach, ie: the storage of dictionaries in external dictionary files that can be linked to documents on a many-to-many basis. This approach facilitates control for the user (my physics dictionary, my history dictionary, my computer science dictionary) without making unnecessary assumptions about the similarity of ALL documents that a user edits or the number of such domains in which a user actively writes. To have multiple private dictionaries is a third option with - like the second one - a much higher demand on the usability of the spell checker interface. This is my suggestion and the only way I can see LyX providing a competent and future-proof solution for spell checking. Did your research reveal which interface(s) did or did not support this approach? This seems a legitimate need that should be pushed upstream if unavailable in hunspell and enchant. Enchant seems the sort of project where implementing a costly emulation layer against backends missing this support may occur for free, at least in terms of the LyX project's developer time, if a request is acknowledged. The motivation for enchant's developers is that this would further assist the enchant project to differentiate enchant's API/ABI from hunspell's API/ABI in the eyes of application developers, since hunspell seems to be rapidly subsuming prior systems and value of the enchant layer is therefore decreasing for some development scenarios. In addition, enchant probably already has code to read/write external dictionary files of the sort suggested (my x-domain dictionary...) and could expose an API/ABI for doing so that LyX could easily utilise. Any functionality identified as missing may be enthusiastically implemented by the enchant developers. Hell, they might even extend their scope slightly to throw in some critical functions for language detection! (Indeed, on the fact of it it would seem that there is little point in adding any such code to LyX vs. enchant, a cross-platform library that already provides concurrent access to multiple spellchecking engine's dictionaries. Do one thing and do it well, the KISS principle?) Sorry I do not have time to go back and snip all of this, I have been typing and researching the above since before the dawn (sunrise over Los Angeles is surprisingly beautiful!) and am now running late for work! Very keen to hear thoughts... - Walter
Re: Subject: LyX 2.0beta3: Spell Checking + Multilingualism
which input in that unicode block automatically sets language markup) could also be 'primary dictionary' for language detection (eg: when pasting large blocks of text, opening legacy files, falling back to (1) from (2) as described above, or whatever...). Finally, some left-field techniques may also be available, like making API calls out to Google Translate for 'outsourced' language detection! 6. Dictionary Re-Use Support [*] - Another point is that of re-use. Which is to say that, when someone uses for example 'BibTeX' to compile a biliographic database, that database may easily be used with other projects and is considered portable. So for all physics papers I can use one bibliography, and I may have another for history papers. Whilst this is presently handled adequately by LyX, the equivalent functionality is not present for dictionary databases. It should be. This means both adding a 'manage multiple dictionaries in this project' feature-set, and adding a 'which dictionary do you want to add the word to' drop-down in the right hand spellchecker sidebar. This is a good idea (already mentioned on developers list, AFAICR). The idea is to incorporate a personal dictionary into the document. But it definitively will not happen tomorrow. Great, as long as the personal dictionary in the document is saved outside the document and as a file that can be: a) shared between multiple documents b) used with zero or more additional personal dictionaries within a single file c) identified as the target dictionary (vs. other active personal dictionaries) when spell-checking the document and adding words to personal dictionaries The externally saved personal dictionary is shared between multiple documents per se. I am unclear on the suggested implementation, however any assumption that all documents a user is editing should use the same personal dictionary is flawed. From your next comment, I think you see this... My idea was to provide the dictionary inside the document as an alternative. If you are sure a word is correctly spelled you want to transfer this know how with the document. This is a good idea however it is not nearly as flexible as the established and proven BiBTeX approach, ie: the storage of dictionaries in external dictionary files that can be linked to documents on a many-to-many basis. This approach facilitates control for the user (my physics dictionary, my history dictionary, my computer science dictionary) without making unnecessary assumptions about the similarity of ALL documents that a user edits or the number of such domains in which a user actively writes. To have multiple private dictionaries is a third option with - like the second one - a much higher demand on the usability of the spell checker interface. This is my suggestion and the only way I can see LyX providing a competent and future-proof solution for spell checking. Did your research reveal which interface(s) did or did not support this approach? This seems a legitimate need that should be pushed upstream if unavailable in hunspell and enchant. Enchant seems the sort of project where implementing a costly emulation layer against backends missing this support may occur for free, at least in terms of the LyX project's developer time, if a request is acknowledged. The motivation for enchant's developers is that this would further assist the enchant project to differentiate enchant's API/ABI from hunspell's API/ABI in the eyes of application developers, since hunspell seems to be rapidly subsuming prior systems and value of the enchant layer is therefore decreasing for some development scenarios. In addition, enchant probably already has code to read/write external dictionary files of the sort suggested (my x-domain dictionary...) and could expose an API/ABI for doing so that LyX could easily utilise. Any functionality identified as missing may be enthusiastically implemented by the enchant developers. Hell, they might even extend their scope slightly to throw in some critical functions for language detection! (Indeed, on the fact of it it would seem that there is little point in adding any such code to LyX vs. enchant, a cross-platform library that already provides concurrent access to multiple spellchecking engine's dictionaries. Do one thing and do it well, the KISS principle?) Sorry I do not have time to go back and snip all of this, I have been typing and researching the above since before the dawn (sunrise over Los Angeles is surprisingly beautiful!) and am now running late for work! Very keen to hear thoughts... - Walter
Re: Subject: LyX 2.0beta3: Spell Checking + Multilingualism
t;From your next comment, I think you see this... > My idea was to provide the dictionary "inside" the document as an alternative. > If you are sure a word is correctly spelled you want to transfer this know how > with the document. This is a good idea however it is not nearly as flexible as the established and proven BiBTeX approach, ie: the storage of dictionaries in external dictionary files that can be linked to documents on a many-to-many basis. This approach facilitates control for the user ("my physics dictionary", "my history dictionary", "my computer science dictionary") without making unnecessary assumptions about the similarity of ALL documents that a user edits or the number of such domains in which a user actively writes. > To have multiple private dictionaries is a third option with - like the > second one - > a much higher demand on the usability of the spell checker interface. This is my suggestion and the only way I can see LyX providing a competent and future-proof solution for spell checking. Did your research reveal which interface(s) did or did not support this approach? This seems a legitimate need that should be pushed upstream if unavailable in hunspell and enchant. Enchant seems the sort of project where implementing a costly emulation layer against backends missing this support may occur "for free", at least in terms of the LyX project's developer time, if a request is acknowledged. The motivation for enchant's developers is that this would further assist the enchant project to differentiate enchant's API/ABI from hunspell's API/ABI in the eyes of application developers, since hunspell seems to be rapidly subsuming prior systems and value of the enchant layer is therefore decreasing for some development scenarios. In addition, enchant probably already has code to read/write external dictionary files of the sort suggested ("my dictionary"...) and could expose an API/ABI for doing so that LyX could easily utilise. Any functionality identified as missing may be enthusiastically implemented by the enchant developers. Hell, they might even extend their scope slightly to throw in some critical functions for language detection! (Indeed, on the fact of it it would seem that there is little point in adding any such code to LyX vs. enchant, a cross-platform library that already provides concurrent access to multiple spellchecking engine's dictionaries. Do one thing and do it well, the KISS principle?) Sorry I do not have time to go back and snip all of this, I have been typing and researching the above since before the dawn (sunrise over Los Angeles is surprisingly beautiful!) and am now running late for work! Very keen to hear thoughts... - Walter
Re: Subject: LyX 2.0beta3: Spell Checking + Multilingualism
: Did anyone ever wonder about the etymology of 'hardscrabble'? I think aspell's default English dictionary could be involved in at least one definition...) This one I have to investigate, cannot comment on this now. But, AFAIK there is no default aspell dictionary. It depends on the software packager what gets distributed. You may have an installation with german dictionary only. And there are different english dictionaries available... This is, what my aspell installation has to offer for english: * en, en-w_accents, en-wo_accents * en-variant_0, en-variant_1, en-variant_2 * en_CA, en_CA-w_accents, en_CA-wo_accents * en_GB, en_GB-w_accents, en_GB-wo_accents * en_GB-ise, en_GB-ise-w_accents, en_GB-ise-wo_accents * en_GB-ize, en_GB-ize-w_accents, en_GB-ize-wo_accents * en_US, en_US-w_accents, en_US-wo_accents Some of them are combined dictionaries. Perhaps a summary could be made available of dictionary contents, either through built-in descriptions and/or the proposed pan-spellchecker- engine abstraction/unification library, hmmm? Another option is to switch to hunspell and use the openoffice dictionaries. It is said that these dictionaries are superior. Thanks, I will try it. An excellent tip! (Of course it would be better if the UI suggested this or even detected availability...) 5. Right sidebar spellchecker interface: word addition [*] --- At various points throughout my document I use accepted phrases within the sphere of my writing such as Proto-Austro-Tai and Tai-Kadai. Whilst Tai and Kadai are also used as individual words, Proto and Austro are not. With the present spellchecker interface, when such 'word portions' occur, I am only given two options: 1. Adding these 'word portions' as words in their own right 2. Ignoring them as words in their own right Both options are less than ideal because they will subsequently allow the individual words to occur alone, ie: such that human input could conceivably render Come hither, pronto! as Come hither, proto! and the spellchecker would consider this to be correct, despite the fact that proto should possibly not occur as a word in its own right. (OK well that's probably arguable, but you still see the point!) The best option for resolving this would be to modify the LyX spellchecker sidebar interface to allow adding arbitrary words or entire words rather than simply word portions thereof that have been identified by aspell as unknown. (ie: When presented with Proto-Austro-Tai, and Proto is highlighted, then the user should be able to add Proto-Austro-Tai as a word in its own right rather than only the 'word portion' Proto itself.) (If I recall, 'other' word processing solutions include this feature.) Here LyX relies on the spell checker interface. Most checkers are able to do the checks at word level only. Consequently you cannot add compound words to your personal dictionary, AFAIK. Here I want to wait for an improvement of the spell checker libraries. It's possible to check complete sentences - the apple spell checker has this capability. It's even able to auto-dectect the language... (Well they do say that Apple is very good at usability, and that open source generally isn't. Perhaps they are correct in this assertion, sometimes...) I will make a note to research aspell dictionaries and capabilities further with the intention of issuing a goodly whinge on our collective behalf to the spellcheck library people, if indeed this functionality is unavailable. (No ETA...) 6. Dictionary Re-Use Support [*] - Another point is that of re-use. Which is to say that, when someone uses for example 'BibTeX' to compile a biliographic database, that database may easily be used with other projects and is considered portable. So for all physics papers I can use one bibliography, and I may have another for history papers. Whilst this is presently handled adequately by LyX, the equivalent functionality is not present for dictionary databases. It should be. This means both adding a 'manage multiple dictionaries in this project' feature-set, and adding a 'which dictionary do you want to add the word to' drop-down in the right hand spellchecker sidebar. This is a good idea (already mentioned on developers list, AFAICR). The idea is to incorporate a personal dictionary into the document. But it definitively will not happen tomorrow. Great, as long as the personal dictionary in the document is saved outside the document and as a file that can be: a) shared between multiple documents b) used with zero or more additional personal dictionaries within a single file c) identified as the target dictionary (vs. other active personal dictionaries) when spell-checking the document and adding words to personal dictionaries - Walter
Re: Subject: LyX 2.0beta3: Spell Checking + Multilingualism
This sounds ugly. Is there any similarity between spell checking APIs? Is there a cross platform, spell checking library unification / abstraction layer available? Would it be worth developing one? How difficult is it to detect known dictionaries and spell checkers on a cross-platform basis? Possible answer: http://www.abisource.com/projects/enchant/ - Walter
Re: Subject: LyX 2.0beta3: Spell Checking + Multilingualism
: Did anyone ever wonder about the etymology of 'hardscrabble'? I think aspell's default English dictionary could be involved in at least one definition...) This one I have to investigate, cannot comment on this now. But, AFAIK there is no default aspell dictionary. It depends on the software packager what gets distributed. You may have an installation with german dictionary only. And there are different english dictionaries available... This is, what my aspell installation has to offer for english: * en, en-w_accents, en-wo_accents * en-variant_0, en-variant_1, en-variant_2 * en_CA, en_CA-w_accents, en_CA-wo_accents * en_GB, en_GB-w_accents, en_GB-wo_accents * en_GB-ise, en_GB-ise-w_accents, en_GB-ise-wo_accents * en_GB-ize, en_GB-ize-w_accents, en_GB-ize-wo_accents * en_US, en_US-w_accents, en_US-wo_accents Some of them are combined dictionaries. Perhaps a summary could be made available of dictionary contents, either through built-in descriptions and/or the proposed pan-spellchecker- engine abstraction/unification library, hmmm? Another option is to switch to hunspell and use the openoffice dictionaries. It is said that these dictionaries are superior. Thanks, I will try it. An excellent tip! (Of course it would be better if the UI suggested this or even detected availability...) 5. Right sidebar spellchecker interface: word addition [*] --- At various points throughout my document I use accepted phrases within the sphere of my writing such as Proto-Austro-Tai and Tai-Kadai. Whilst Tai and Kadai are also used as individual words, Proto and Austro are not. With the present spellchecker interface, when such 'word portions' occur, I am only given two options: 1. Adding these 'word portions' as words in their own right 2. Ignoring them as words in their own right Both options are less than ideal because they will subsequently allow the individual words to occur alone, ie: such that human input could conceivably render Come hither, pronto! as Come hither, proto! and the spellchecker would consider this to be correct, despite the fact that proto should possibly not occur as a word in its own right. (OK well that's probably arguable, but you still see the point!) The best option for resolving this would be to modify the LyX spellchecker sidebar interface to allow adding arbitrary words or entire words rather than simply word portions thereof that have been identified by aspell as unknown. (ie: When presented with Proto-Austro-Tai, and Proto is highlighted, then the user should be able to add Proto-Austro-Tai as a word in its own right rather than only the 'word portion' Proto itself.) (If I recall, 'other' word processing solutions include this feature.) Here LyX relies on the spell checker interface. Most checkers are able to do the checks at word level only. Consequently you cannot add compound words to your personal dictionary, AFAIK. Here I want to wait for an improvement of the spell checker libraries. It's possible to check complete sentences - the apple spell checker has this capability. It's even able to auto-dectect the language... (Well they do say that Apple is very good at usability, and that open source generally isn't. Perhaps they are correct in this assertion, sometimes...) I will make a note to research aspell dictionaries and capabilities further with the intention of issuing a goodly whinge on our collective behalf to the spellcheck library people, if indeed this functionality is unavailable. (No ETA...) 6. Dictionary Re-Use Support [*] - Another point is that of re-use. Which is to say that, when someone uses for example 'BibTeX' to compile a biliographic database, that database may easily be used with other projects and is considered portable. So for all physics papers I can use one bibliography, and I may have another for history papers. Whilst this is presently handled adequately by LyX, the equivalent functionality is not present for dictionary databases. It should be. This means both adding a 'manage multiple dictionaries in this project' feature-set, and adding a 'which dictionary do you want to add the word to' drop-down in the right hand spellchecker sidebar. This is a good idea (already mentioned on developers list, AFAICR). The idea is to incorporate a personal dictionary into the document. But it definitively will not happen tomorrow. Great, as long as the personal dictionary in the document is saved outside the document and as a file that can be: a) shared between multiple documents b) used with zero or more additional personal dictionaries within a single file c) identified as the target dictionary (vs. other active personal dictionaries) when spell-checking the document and adding words to personal dictionaries - Walter
Re: Subject: LyX 2.0beta3: Spell Checking + Multilingualism
This sounds ugly. Is there any similarity between spell checking APIs? Is there a cross platform, spell checking library unification / abstraction layer available? Would it be worth developing one? How difficult is it to detect known dictionaries and spell checkers on a cross-platform basis? Possible answer: http://www.abisource.com/projects/enchant/ - Walter
Re: Subject: LyX 2.0beta3: Spell Checking + Multilingualism
ood at usability, and that open source generally isn't. Perhaps "they" are correct in this assertion, sometimes...) I will make a note to research aspell dictionaries and capabilities further with the intention of issuing a goodly whinge on our collective behalf to the spellcheck library people, if indeed this functionality is unavailable. (No ETA...) >> 6. Dictionary Re-Use Support [*] >> - >> Another point is that of re-use. Which is to say that, when someone uses >> for example 'BibTeX' to compile a biliographic database, that database >> may easily be used with other projects and is considered portable. So >> for all physics papers I can use one bibliography, and I may have another >> for history papers. Whilst this is presently handled adequately by LyX, >> the equivalent functionality is not present for dictionary databases. >> It should be. This means both adding a 'manage multiple dictionaries in >> this project' feature-set, and adding a 'which dictionary do you want to >> add the word to' drop-down in the right hand spellchecker sidebar. > > This is a good idea (already mentioned on developers list, AFAICR). > The idea is to incorporate a personal dictionary into the document. > But it definitively will not happen tomorrow. Great, as long as the personal dictionary "in" the document is saved "outside" the document and as a file that can be: a) shared between multiple documents b) used with zero or more additional personal dictionaries within a single file c) identified as the target dictionary (vs. other active personal dictionaries) when spell-checking the document and adding words to personal dictionaries - Walter
Re: Subject: LyX 2.0beta3: Spell Checking + Multilingualism
> This sounds ugly. Is there any similarity between spell checking APIs? Is > there a cross platform, spell checking library unification / abstraction layer > available? Would it be worth developing one? How difficult is it to detect > known dictionaries and spell checkers on a cross-platform basis? Possible answer: http://www.abisource.com/projects/enchant/ - Walter
Subject: LyX 2.0beta3: Spell Checking + Multilingualism
to make proper use of available databases and let the user assign fonts to unicode blocks and/or languages and/or custom defined text-types for font selection purposes, a forward-looking, integrated solution should also take in to account spellchecker requirements. Otherwise, we poor users are laboured with having to make 1000 manual markups just to include a short bit of text! This is exemplified if, for instance, one wishes to quote a place name with translations and their romanised equivalents in situ at many points throughout a document (my unfortunate situation, and before anyone asks: no I cannot switch to compiling a reference table, for reasons of readership and readability) In summary, a short list of user-side 'wants' for such a future upgrade to multilingual support would be: - works with unicode TeX systems (XeTeX) - works with TTF - provides dialog based font selection (see previous post) - provides dialog based language selection (see previous post) - does not require duplicate language markup for the font subsystem and the spellchecker subsystem - upgrades the spellchecker subsystem to be more multilingual aware Please do reference the previous message which included a UI mockup for further details on the proposed genre of solution: http://www.mail-archive.com/lyx-users@lists.lyx.org/msg83635.html http://pratyeka.org/unicode-font-mockup.png (hosted copy of mockup) 4. Weird behaviour with common prefixes and specialist compounds [X] - Common prefixes such as micro and proto seem to confuse aspell. Not sure if this is somehow related to how it is linked from LyX, but I assume the issue is with them. For example, 'proto-known word' does not seem to be accepted, forcing 'proto' to be added manually as a valid word. Unfortunately, the LyX interface does not offer a proper workaround. (Please see point 5.) (Note: Upon further investigation, actually a lot of words appear to be missing from the default dictionary, including hewn, proven, romanised. A scrabble player would be dismayed: for many points!) (PS: Did anyone ever wonder about the etymology of 'hardscrabble'? I think aspell's default English dictionary could be involved in at least one definition...) 5. Right sidebar spellchecker interface: word addition [*] --- At various points throughout my document I use accepted phrases within the sphere of my writing such as Proto-Austro-Tai and Tai-Kadai. Whilst Tai and Kadai are also used as individual words, Proto and Austro are not. With the present spellchecker interface, when such 'word portions' occur, I am only given two options: 1. Adding these 'word portions' as words in their own right 2. Ignoring them as words in their own right Both options are less than ideal because they will subsequently allow the individual words to occur alone, ie: such that human input could conceivably render Come hither, pronto! as Come hither, proto! and the spellchecker would consider this to be correct, despite the fact that proto should possibly not occur as a word in its own right. (OK well that's probably arguable, but you still see the point!) The best option for resolving this would be to modify the LyX spellchecker sidebar interface to allow adding arbitrary words or entire words rather than simply word portions thereof that have been identified by aspell as unknown. (ie: When presented with Proto-Austro-Tai, and Proto is highlighted, then the user should be able to add Proto-Austro-Tai as a word in its own right rather than only the 'word portion' Proto itself.) (If I recall, 'other' word processing solutions include this feature.) 6. Dictionary Re-Use Support [*] - Another point is that of re-use. Which is to say that, when someone uses for example 'BibTeX' to compile a biliographic database, that database may easily be used with other projects and is considered portable. So for all physics papers I can use one bibliography, and I may have another for history papers. Whilst this is presently handled adequately by LyX, the equivalent functionality is not present for dictionary databases. It should be. This means both adding a 'manage multiple dictionaries in this project' feature-set, and adding a 'which dictionary do you want to add the word to' drop-down in the right hand spellchecker sidebar. A big thank you to the hard working developers, please do not interpret the above as anything but forward looking ideas and constructive criticism, your hard work is brilliant and very well received! Sincerely, Walter Stanish (Written while dodging wild boar trophy tusks in Ain Drahim, Tunisia. Cleaned up and rechecked for LyX
Subject: LyX 2.0beta3: Spell Checking + Multilingualism
to make proper use of available databases and let the user assign fonts to unicode blocks and/or languages and/or custom defined text-types for font selection purposes, a forward-looking, integrated solution should also take in to account spellchecker requirements. Otherwise, we poor users are laboured with having to make 1000 manual markups just to include a short bit of text! This is exemplified if, for instance, one wishes to quote a place name with translations and their romanised equivalents in situ at many points throughout a document (my unfortunate situation, and before anyone asks: no I cannot switch to compiling a reference table, for reasons of readership and readability) In summary, a short list of user-side 'wants' for such a future upgrade to multilingual support would be: - works with unicode TeX systems (XeTeX) - works with TTF - provides dialog based font selection (see previous post) - provides dialog based language selection (see previous post) - does not require duplicate language markup for the font subsystem and the spellchecker subsystem - upgrades the spellchecker subsystem to be more multilingual aware Please do reference the previous message which included a UI mockup for further details on the proposed genre of solution: http://www.mail-archive.com/lyx-users@lists.lyx.org/msg83635.html http://pratyeka.org/unicode-font-mockup.png (hosted copy of mockup) 4. Weird behaviour with common prefixes and specialist compounds [X] - Common prefixes such as micro and proto seem to confuse aspell. Not sure if this is somehow related to how it is linked from LyX, but I assume the issue is with them. For example, 'proto-known word' does not seem to be accepted, forcing 'proto' to be added manually as a valid word. Unfortunately, the LyX interface does not offer a proper workaround. (Please see point 5.) (Note: Upon further investigation, actually a lot of words appear to be missing from the default dictionary, including hewn, proven, romanised. A scrabble player would be dismayed: for many points!) (PS: Did anyone ever wonder about the etymology of 'hardscrabble'? I think aspell's default English dictionary could be involved in at least one definition...) 5. Right sidebar spellchecker interface: word addition [*] --- At various points throughout my document I use accepted phrases within the sphere of my writing such as Proto-Austro-Tai and Tai-Kadai. Whilst Tai and Kadai are also used as individual words, Proto and Austro are not. With the present spellchecker interface, when such 'word portions' occur, I am only given two options: 1. Adding these 'word portions' as words in their own right 2. Ignoring them as words in their own right Both options are less than ideal because they will subsequently allow the individual words to occur alone, ie: such that human input could conceivably render Come hither, pronto! as Come hither, proto! and the spellchecker would consider this to be correct, despite the fact that proto should possibly not occur as a word in its own right. (OK well that's probably arguable, but you still see the point!) The best option for resolving this would be to modify the LyX spellchecker sidebar interface to allow adding arbitrary words or entire words rather than simply word portions thereof that have been identified by aspell as unknown. (ie: When presented with Proto-Austro-Tai, and Proto is highlighted, then the user should be able to add Proto-Austro-Tai as a word in its own right rather than only the 'word portion' Proto itself.) (If I recall, 'other' word processing solutions include this feature.) 6. Dictionary Re-Use Support [*] - Another point is that of re-use. Which is to say that, when someone uses for example 'BibTeX' to compile a biliographic database, that database may easily be used with other projects and is considered portable. So for all physics papers I can use one bibliography, and I may have another for history papers. Whilst this is presently handled adequately by LyX, the equivalent functionality is not present for dictionary databases. It should be. This means both adding a 'manage multiple dictionaries in this project' feature-set, and adding a 'which dictionary do you want to add the word to' drop-down in the right hand spellchecker sidebar. A big thank you to the hard working developers, please do not interpret the above as anything but forward looking ideas and constructive criticism, your hard work is brilliant and very well received! Sincerely, Walter Stanish (Written while dodging wild boar trophy tusks in Ain Drahim, Tunisia. Cleaned up and rechecked for LyX
Subject: LyX 2.0beta3: Spell Checking + Multilingualism
s direction, but "there's a ways to go yet". As per previous posts whereby I suggested revising the user interface to make proper use of available databases and let the user assign fonts to unicode blocks and/or languages and/or custom defined text-types for font selection purposes, a forward-looking, integrated solution should also take in to account spellchecker requirements. Otherwise, we poor users are laboured with having to make 1000 manual markups just to include a short bit of text! This is exemplified if, for instance, one wishes to quote a place name with translations and their romanised equivalents in situ at many points throughout a document (my unfortunate situation, and before anyone asks: no I cannot switch to compiling a reference table, for reasons of readership and readability) In summary, a short list of user-side 'wants' for such a future upgrade to multilingual support would be: - works with unicode TeX systems (XeTeX) - works with TTF - provides dialog based font selection (see previous post) - provides dialog based language selection (see previous post) - does not require duplicate language markup for the font subsystem and the spellchecker subsystem - upgrades the spellchecker subsystem to be more multilingual aware Please do reference the previous message which included a UI mockup for further details on the proposed genre of solution: http://www.mail-archive.com/lyx-users@lists.lyx.org/msg83635.html http://pratyeka.org/unicode-font-mockup.png (hosted copy of mockup) 4. Weird behaviour with common prefixes and specialist compounds [X] - Common prefixes such as micro and proto seem to confuse aspell. Not sure if this is somehow related to how it is linked from LyX, but I assume the issue is with them. For example, 'proto-' does not seem to be accepted, forcing 'proto' to be added manually as a valid word. Unfortunately, the LyX interface does not offer a proper workaround. (Please see point 5.) (Note: Upon further investigation, actually a lot of words appear to be missing from the default dictionary, including "hewn", "proven", "romanised". A scrabble player would be dismayed: for many points!) (PS: Did anyone ever wonder about the etymology of 'hardscrabble'? I think aspell's default English dictionary could be involved in at least one definition...) 5. Right sidebar spellchecker interface: word addition [*] --- At various points throughout my document I use accepted phrases within the sphere of my writing such as "Proto-Austro-Tai" and "Tai-Kadai". Whilst "Tai" and "Kadai" are also used as individual words, "Proto" and "Austro" are not. With the present spellchecker interface, when such 'word portions' occur, I am only given two options: 1. Adding these 'word portions' as words in their own right 2. Ignoring them as words in their own right Both options are less than ideal because they will subsequently allow the individual words to occur alone, ie: such that human input could conceivably render "Come hither, pronto!" as "Come hither, proto!" and the spellchecker would consider this to be correct, despite the fact that proto should possibly not occur as a word in its own right. (OK well that's probably arguable, but you still see the point!) The best option for resolving this would be to modify the LyX spellchecker sidebar interface to allow adding arbitrary words or entire words rather than simply word portions thereof that have been identified by aspell as unknown. (ie: When presented with "Proto-Austro-Tai", and "Proto" is highlighted, then the user should be able to add "Proto-Austro-Tai" as a word in its own right rather than only the 'word portion' "Proto" itself.) (If I recall, 'other' word processing solutions include this feature.) 6. Dictionary Re-Use Support [*] - Another point is that of re-use. Which is to say that, when someone uses for example 'BibTeX' to compile a biliographic database, that database may easily be used with other projects and is considered portable. So for all physics papers I can use one bibliography, and I may have another for history papers. Whilst this is presently handled adequately by LyX, the equivalent functionality is not present for dictionary databases. It should be. This means both adding a 'manage multiple dictionaries in this project' feature-set, and adding a 'which dictionary do you want to add the word to' drop-down in the right hand spellchecker sidebar. A big thank you to the hard working developer
Foreign Language Support + Font Setup
Hi there, I am a recent convert to LyX, currently using v1.6.5 on Gentoo Linux. It's been working quite alright, though I now have a need for some pretty heavy duty multilingual text in a single document, specifically at least Burmese, Chinese, Lao, Thai and Vietnamese in addition to English, French and German, and this is causing a huge headache. My problem at present is that if I type Chinese characters in to my document, and the Document Settings Language Encoding options is set to something other than 'Unicode (XeTeX) (utf8)', then attempting to view the document as PDF generates a LaTeX error. Yesterday I spent a fair amount of time going back and forth between the Unicode page (http://wiki.lyx.org/LyX/Unicode) and other web CJK / TeX resources trying to solve the problem, but have thus far had no luck. A lot of the resources mentioned 'old' font processing techniques (using fontforge?), and the path /usr/share/texmf/fonts/ however I found that entering font names from there did not seem to work, and my distribution's Cyberbit and some other mentioned fonts are TTF only, installing in to /usr/share/fonts instead. Turning to command line foo, I found that 'lyx -dbg font' told me that the location of fonts being accessed on program startup was in fact /usr/share/lyx/fonts: Setting debug level to font Debugging `font' (Font handling) GuiFontLoader.cpp(209): Adding font /usr/share/lyx/fonts//cmex10.ttf OK GuiFontLoader.cpp(209): Adding font /usr/share/lyx/fonts//cmmi10.ttf OK GuiFontLoader.cpp(209): Adding font /usr/share/lyx/fonts//cmr10.ttf OK GuiFontLoader.cpp(209): Adding font /usr/share/lyx/fonts//cmsy10.ttf OK GuiFontLoader.cpp(209): Adding font /usr/share/lyx/fonts//eufm10.ttf OK GuiFontLoader.cpp(209): Adding font /usr/share/lyx/fonts//msam10.ttf OK GuiFontLoader.cpp(209): Adding font /usr/share/lyx/fonts//msbm10.ttf OK GuiFontLoader.cpp(209): Adding font /usr/share/lyx/fonts//wasy10.ttf OK GuiFontLoader.cpp(209): Adding font /usr/share/lyx/fonts//esint10.ttf OK This would appear to be an entirely different path to the rest of my system, which uses /usr/share/fonts, and an entirely different path to /usr/share/texmf/fonts/ I am appealing for help with getting arbitrary fonts to display (including, if possible, Thai/Lao/Burmese style combining glyphs) in my output as I do not wish or have time to become an expert in the historical inadequacies of font formats, their various commercial restrictions, format conversions, the evolution of TeX or LyX, or the reason why LyX has not yet moved to the otherwise universal default of utf8 for everything. - Walter
Re: Foreign Language Support + Font Setup
My problem at present is that if I type Chinese characters in to my document, and the Document Settings Language Encoding options is set to something other than 'Unicode (XeTeX) (utf8)', then attempting to view the document as PDF generates a LaTeX error. Sorry, forgot to specify that if I do this and leave the default LaTeX processing options in place, I get garbage where the Chinese should be. I was unable to find a way to select a font that fixed this, even by following the Unicode wiki page. I discovered the XeTeX settings on another wiki page, however using these makes the quick PDF preview button on the toolbar unusable (it's still LaTeX-linked) and exporting via XeTeX using File Export PDF (xelatex) makes the text disappear altogether. I am appealing for help with getting arbitrary fonts to display (including, if possible, Thai/Lao/Burmese style combining glyphs) in my output as I do not wish or have time to become an expert in the historical inadequacies of font formats, their various commercial restrictions, format conversions, the evolution of TeX or LyX, or the reason why LyX has not yet moved to the otherwise universal default of utf8 for everything. Realised the latter point is possibly because LyX cannot assume that the local TeX processing environment includes XeTeX. However, it would be nice to auto-detect. In my particular situation on Gentoo my system is set up exclusively with UTF8-enabled locales, so the lyx package installation process should probably set intelligent defaults. I have filed a bug for this @ http://bugs.gentoo.org/show_bug.cgi?id=344509 Still no idea how to get this working... - Walter
Foreign Language Support + Font Setup
Hi there, I am a recent convert to LyX, currently using v1.6.5 on Gentoo Linux. It's been working quite alright, though I now have a need for some pretty heavy duty multilingual text in a single document, specifically at least Burmese, Chinese, Lao, Thai and Vietnamese in addition to English, French and German, and this is causing a huge headache. My problem at present is that if I type Chinese characters in to my document, and the Document Settings Language Encoding options is set to something other than 'Unicode (XeTeX) (utf8)', then attempting to view the document as PDF generates a LaTeX error. Yesterday I spent a fair amount of time going back and forth between the Unicode page (http://wiki.lyx.org/LyX/Unicode) and other web CJK / TeX resources trying to solve the problem, but have thus far had no luck. A lot of the resources mentioned 'old' font processing techniques (using fontforge?), and the path /usr/share/texmf/fonts/ however I found that entering font names from there did not seem to work, and my distribution's Cyberbit and some other mentioned fonts are TTF only, installing in to /usr/share/fonts instead. Turning to command line foo, I found that 'lyx -dbg font' told me that the location of fonts being accessed on program startup was in fact /usr/share/lyx/fonts: Setting debug level to font Debugging `font' (Font handling) GuiFontLoader.cpp(209): Adding font /usr/share/lyx/fonts//cmex10.ttf OK GuiFontLoader.cpp(209): Adding font /usr/share/lyx/fonts//cmmi10.ttf OK GuiFontLoader.cpp(209): Adding font /usr/share/lyx/fonts//cmr10.ttf OK GuiFontLoader.cpp(209): Adding font /usr/share/lyx/fonts//cmsy10.ttf OK GuiFontLoader.cpp(209): Adding font /usr/share/lyx/fonts//eufm10.ttf OK GuiFontLoader.cpp(209): Adding font /usr/share/lyx/fonts//msam10.ttf OK GuiFontLoader.cpp(209): Adding font /usr/share/lyx/fonts//msbm10.ttf OK GuiFontLoader.cpp(209): Adding font /usr/share/lyx/fonts//wasy10.ttf OK GuiFontLoader.cpp(209): Adding font /usr/share/lyx/fonts//esint10.ttf OK This would appear to be an entirely different path to the rest of my system, which uses /usr/share/fonts, and an entirely different path to /usr/share/texmf/fonts/ I am appealing for help with getting arbitrary fonts to display (including, if possible, Thai/Lao/Burmese style combining glyphs) in my output as I do not wish or have time to become an expert in the historical inadequacies of font formats, their various commercial restrictions, format conversions, the evolution of TeX or LyX, or the reason why LyX has not yet moved to the otherwise universal default of utf8 for everything. - Walter
Re: Foreign Language Support + Font Setup
My problem at present is that if I type Chinese characters in to my document, and the Document Settings Language Encoding options is set to something other than 'Unicode (XeTeX) (utf8)', then attempting to view the document as PDF generates a LaTeX error. Sorry, forgot to specify that if I do this and leave the default LaTeX processing options in place, I get garbage where the Chinese should be. I was unable to find a way to select a font that fixed this, even by following the Unicode wiki page. I discovered the XeTeX settings on another wiki page, however using these makes the quick PDF preview button on the toolbar unusable (it's still LaTeX-linked) and exporting via XeTeX using File Export PDF (xelatex) makes the text disappear altogether. I am appealing for help with getting arbitrary fonts to display (including, if possible, Thai/Lao/Burmese style combining glyphs) in my output as I do not wish or have time to become an expert in the historical inadequacies of font formats, their various commercial restrictions, format conversions, the evolution of TeX or LyX, or the reason why LyX has not yet moved to the otherwise universal default of utf8 for everything. Realised the latter point is possibly because LyX cannot assume that the local TeX processing environment includes XeTeX. However, it would be nice to auto-detect. In my particular situation on Gentoo my system is set up exclusively with UTF8-enabled locales, so the lyx package installation process should probably set intelligent defaults. I have filed a bug for this @ http://bugs.gentoo.org/show_bug.cgi?id=344509 Still no idea how to get this working... - Walter
Foreign Language Support + Font Setup
Hi there, I am a recent convert to LyX, currently using v1.6.5 on Gentoo Linux. It's been working quite alright, though I now have a need for some pretty heavy duty multilingual text in a single document, specifically at least Burmese, Chinese, Lao, Thai and Vietnamese in addition to English, French and German, and this is causing a huge headache. My problem at present is that if I type Chinese characters in to my document, and the Document > Settings > Language > Encoding options is set to something other than 'Unicode (XeTeX) (utf8)', then attempting to view the document as PDF generates a LaTeX error. Yesterday I spent a fair amount of time going back and forth between the Unicode page (http://wiki.lyx.org/LyX/Unicode) and other web CJK / TeX resources trying to solve the problem, but have thus far had no luck. A lot of the resources mentioned 'old' font processing techniques (using fontforge?), and the path /usr/share/texmf/fonts/ however I found that entering font names from there did not seem to work, and my distribution's Cyberbit and some other mentioned fonts are TTF only, installing in to /usr/share/fonts instead. Turning to command line foo, I found that 'lyx -dbg font' told me that the location of fonts being accessed on program startup was in fact /usr/share/lyx/fonts: Setting debug level to font Debugging `font' (Font handling) GuiFontLoader.cpp(209): Adding font /usr/share/lyx/fonts//cmex10.ttf OK GuiFontLoader.cpp(209): Adding font /usr/share/lyx/fonts//cmmi10.ttf OK GuiFontLoader.cpp(209): Adding font /usr/share/lyx/fonts//cmr10.ttf OK GuiFontLoader.cpp(209): Adding font /usr/share/lyx/fonts//cmsy10.ttf OK GuiFontLoader.cpp(209): Adding font /usr/share/lyx/fonts//eufm10.ttf OK GuiFontLoader.cpp(209): Adding font /usr/share/lyx/fonts//msam10.ttf OK GuiFontLoader.cpp(209): Adding font /usr/share/lyx/fonts//msbm10.ttf OK GuiFontLoader.cpp(209): Adding font /usr/share/lyx/fonts//wasy10.ttf OK GuiFontLoader.cpp(209): Adding font /usr/share/lyx/fonts//esint10.ttf OK This would appear to be an entirely different path to the rest of my system, which uses /usr/share/fonts, and an entirely different path to /usr/share/texmf/fonts/ I am appealing for help with getting arbitrary fonts to display (including, if possible, Thai/Lao/Burmese style combining glyphs) in my output as I do not wish or have time to become an expert in the historical inadequacies of font formats, their various commercial restrictions, format conversions, the evolution of TeX or LyX, or the reason why LyX has not yet moved to the otherwise universal default of utf8 for everything. - Walter
Re: Foreign Language Support + Font Setup
> My problem at present is that if I type Chinese characters in to my > document, and the Document > Settings > Language > Encoding options is > set to something other than 'Unicode (XeTeX) (utf8)', then attempting > to view the document as PDF generates a LaTeX error. Sorry, forgot to specify that if I do this and leave the default LaTeX processing options in place, I get garbage where the Chinese should be. I was unable to find a way to select a font that fixed this, even by following the Unicode wiki page. I discovered the XeTeX settings on another wiki page, however using these makes the quick PDF preview button on the toolbar unusable (it's still LaTeX-linked) and exporting via XeTeX using File > Export > PDF (xelatex) makes the text disappear altogether. > I am appealing for help with getting arbitrary fonts to display > (including, if possible, Thai/Lao/Burmese style combining glyphs) in > my output as I do not wish or have time to become an expert in the > historical inadequacies of font formats, their various commercial > restrictions, format conversions, the evolution of TeX or LyX, or the > reason why LyX has not yet moved to the otherwise universal default of > utf8 for everything. Realised the latter point is possibly because LyX cannot assume that the local TeX processing environment includes XeTeX. However, it would be nice to auto-detect. In my particular situation on Gentoo my system is set up exclusively with UTF8-enabled locales, so the lyx package installation process should probably set intelligent defaults. I have filed a bug for this @ http://bugs.gentoo.org/show_bug.cgi?id=344509 Still no idea how to get this working... - Walter
Re: ANNOUNCE: LyX version 2.0.0 (alpha 6)
On Thu, 16 Sep 2010 08:33:08 -0700 (PDT), Marcelo Acuña mv...@yahoo.com.ar wrote: Tarballs can be found at ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.0/ What is LyX-2.0.0alpha6+qt4.dmg? That is for those among us who sacrifice loads of money on their translucent white altars of Steve, the demi-god with the Reality Distortion Field, cultists of OS X. Regards, Walter
Re: ANNOUNCE: LyX version 2.0.0 (alpha 6)
On Thu, 16 Sep 2010 08:33:08 -0700 (PDT), Marcelo Acuña mv...@yahoo.com.ar wrote: Tarballs can be found at ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.0/ What is LyX-2.0.0alpha6+qt4.dmg? That is for those among us who sacrifice loads of money on their translucent white altars of Steve, the demi-god with the Reality Distortion Field, cultists of OS X. Regards, Walter
Re: ANNOUNCE: LyX version 2.0.0 (alpha 6)
On Thu, 16 Sep 2010 08:33:08 -0700 (PDT), Marcelo Acuña <mv...@yahoo.com.ar> wrote: >> Tarballs can be found at >> ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.0/ > > What is LyX-2.0.0alpha6+qt4.dmg? That is for those among us who sacrifice loads of money on their translucent white altars of Steve, the demi-god with the Reality Distortion Field, cultists of OS X. Regards, Walter
Re: Fwd: Re: things that I miss in lyx
On Tue, 23 Mar 2010 09:15:08 +0100, Julio Rojas jcredbe...@gmail.com wrote: Yup, this is what I think, but when you have several coworkers working on collaborative papers in several different LaTeX classes, they finally have the last laugh. This is why a layout editor would do wonders to convert our main target, people that already uses LaTeX directly who wants to speed up their writing and track changes on the document. I would love to have a layout editor in LyX. There is still lots of untapped potential for LyX. I'm a legal professional and none in that profession doesn't have a visceral hate for Word's abilities to destroy a contract's structure. Regards, Walter
Re: Fwd: Re: things that I miss in lyx
On Tue, 23 Mar 2010 09:15:08 +0100, Julio Rojas jcredbe...@gmail.com wrote: Yup, this is what I think, but when you have several coworkers working on collaborative papers in several different LaTeX classes, they finally have the last laugh. This is why a layout editor would do wonders to convert our main target, people that already uses LaTeX directly who wants to speed up their writing and track changes on the document. I would love to have a layout editor in LyX. There is still lots of untapped potential for LyX. I'm a legal professional and none in that profession doesn't have a visceral hate for Word's abilities to destroy a contract's structure. Regards, Walter
Re: Fwd: Re: things that I miss in lyx
On Tue, 23 Mar 2010 09:15:08 +0100, Julio Rojas <jcredbe...@gmail.com> wrote: > Yup, this is what I think, but when you have several coworkers working > on collaborative papers in several different LaTeX classes, they > finally have the last laugh. This is why a layout editor would do > wonders to convert our main target, people that already uses LaTeX > directly who wants to speed up their writing and track changes on the > document. I would love to have a layout editor in LyX. There is still lots of untapped potential for LyX. I'm a legal professional and none in that profession doesn't have a visceral hate for Word's abilities to destroy a contract's structure. Regards, Walter
Fwd: Re: things that I miss in lyx
Original Message Subject: Re: things that I miss in lyx Date: Mon, 22 Mar 2010 13:51:24 +0100 From: Walter van Holst walter.van.ho...@xs4all.nl To: Jose Quesada ques...@gmail.com On Sun, 21 Mar 2010 02:23:34 +0100, Jose Quesada ques...@gmail.com wrote: Hi all, In no special order, things that I miss in lyx... 1. incremental search 2. sentence autocapitalization As others have written, NO! IN THE NAME OF EVERYTHING THAT IS HOLY, DON'T! 3. grammar check (not crucial) Grammar checks are non-trivial, it would be nice to have this in a modular way so we can share this with other open source efforts in this field. 4. search highlight occurences Even nicer, the search implemented by Apple's Preview document viewer provides a side bar with frequency bars of the search term's occurence on each page. 7. the rest of the world operates on rich text/html. LyX doesn't (clipboard integration is poor, copy-pasting from/to web loses formatting) Actuall, I prefer the current default of losing formatting. The whole point of LyX is that you focus on structure and content and have LaTeX take care of formatting. The rest of the world operates on a fundamentally braindead paradigm and if I wanted to use that paradigm I'd be a happy OOo camper. Which I am not. 8. 'pasted from' and url for every paste from the web (onenote uses this and it's damn inspired) That sounds good. Some Zotero-like stuff might be helpful too. Regards, Walter
Fwd: Re: things that I miss in lyx
Original Message Subject: Re: things that I miss in lyx Date: Mon, 22 Mar 2010 13:51:24 +0100 From: Walter van Holst walter.van.ho...@xs4all.nl To: Jose Quesada ques...@gmail.com On Sun, 21 Mar 2010 02:23:34 +0100, Jose Quesada ques...@gmail.com wrote: Hi all, In no special order, things that I miss in lyx... 1. incremental search 2. sentence autocapitalization As others have written, NO! IN THE NAME OF EVERYTHING THAT IS HOLY, DON'T! 3. grammar check (not crucial) Grammar checks are non-trivial, it would be nice to have this in a modular way so we can share this with other open source efforts in this field. 4. search highlight occurences Even nicer, the search implemented by Apple's Preview document viewer provides a side bar with frequency bars of the search term's occurence on each page. 7. the rest of the world operates on rich text/html. LyX doesn't (clipboard integration is poor, copy-pasting from/to web loses formatting) Actuall, I prefer the current default of losing formatting. The whole point of LyX is that you focus on structure and content and have LaTeX take care of formatting. The rest of the world operates on a fundamentally braindead paradigm and if I wanted to use that paradigm I'd be a happy OOo camper. Which I am not. 8. 'pasted from' and url for every paste from the web (onenote uses this and it's damn inspired) That sounds good. Some Zotero-like stuff might be helpful too. Regards, Walter
Fwd: Re: things that I miss in lyx
Original Message Subject: Re: things that I miss in lyx Date: Mon, 22 Mar 2010 13:51:24 +0100 From: Walter van Holst <walter.van.ho...@xs4all.nl> To: Jose Quesada <ques...@gmail.com> On Sun, 21 Mar 2010 02:23:34 +0100, Jose Quesada <ques...@gmail.com> wrote: > Hi all, > > In no special order, things that I miss in lyx... > > 1. incremental search > > 2. sentence autocapitalization As others have written, NO! IN THE NAME OF EVERYTHING THAT IS HOLY, DON'T! > 3. grammar check (not crucial) Grammar checks are non-trivial, it would be nice to have this in a modular way so we can share this with other open source efforts in this field. > 4. search highlight occurences Even nicer, the search implemented by Apple's Preview document viewer provides a side bar with frequency bars of the search term's occurence on each page. > 7. the rest of the world operates on rich text/html. LyX doesn't (clipboard > integration is poor, copy-pasting from/to web loses formatting) Actuall, I prefer the current default of losing formatting. The whole point of LyX is that you focus on structure and content and have LaTeX take care of formatting. The rest of the world operates on a fundamentally braindead paradigm and if I wanted to use that paradigm I'd be a happy OOo camper. Which I am not. > 8. 'pasted from' and url for every paste from the web (onenote uses this > and > it's damn inspired) That sounds good. Some Zotero-like stuff might be helpful too. Regards, Walter
Re: Unavailable document classes [OSX]
BH schreef: I really have no idea. We check all the standard locations for LaTeX installations, and I don't remember other reports of such problems. (Does anyone else experience this? If so, please give some details about your system and LaTeX installation ... and anything unusual you might have done.) It turns out to be a somewhat outdated LaTeX installation. And me overlooking the red tick in the LyX installer. :-( Regards, Walter
Re: Unavailable document classes [OSX]
BH schreef: I really have no idea. We check all the standard locations for LaTeX installations, and I don't remember other reports of such problems. (Does anyone else experience this? If so, please give some details about your system and LaTeX installation ... and anything unusual you might have done.) It turns out to be a somewhat outdated LaTeX installation. And me overlooking the red tick in the LyX installer. :-( Regards, Walter
Re: Unavailable document classes [OSX]
BH schreef: I really have no idea. We check all the standard locations for LaTeX installations, and I don't remember other reports of such problems. (Does anyone else experience this? If so, please give some details about your system and LaTeX installation ... and anything unusual you might have done.) It turns out to be a somewhat outdated LaTeX installation. And me overlooking the red tick in the LyX installer. :-( Regards, Walter
Unavailable document classes
Hello, I'm a somewhat infrequent user of LyX on Mac OS X. About every other update (my current version is 1.6.1), most of the document classes become unavailable. That is LyX can edit documents in them, but not produce output. How do I prevent this from happening? This is an exceedingly annoying 'feature' of LyX. Regards, Walter
Unavailable document classes
Hello, I'm a somewhat infrequent user of LyX on Mac OS X. About every other update (my current version is 1.6.1), most of the document classes become unavailable. That is LyX can edit documents in them, but not produce output. How do I prevent this from happening? This is an exceedingly annoying 'feature' of LyX. Regards, Walter
Unavailable document classes
Hello, I'm a somewhat infrequent user of LyX on Mac OS X. About every other update (my current version is 1.6.1), most of the document classes become unavailable. That is LyX can edit documents in them, but not produce output. How do I prevent this from happening? This is an exceedingly annoying 'feature' of LyX. Regards, Walter
Re: multiplatform vector drawing program to use
Of course, there are also other vector drawing programs (besides Xfig), so what is outlined here is not the only option you have. If only Linux and Windows are required, I'd recommend Inkscape. It is much more polished and user friendly than Xfig whose UI is a bit daunting. Regards, Walter
Re: multiplatform vector drawing program to use
Of course, there are also other vector drawing programs (besides Xfig), so what is outlined here is not the only option you have. If only Linux and Windows are required, I'd recommend Inkscape. It is much more polished and user friendly than Xfig whose UI is a bit daunting. Regards, Walter
Re: multiplatform vector drawing program to use
> Of course, there are also other vector drawing programs (besides > Xfig), so > what is outlined here is not the only option you have. If only Linux and Windows are required, I'd recommend Inkscape. It is much more polished and user friendly than Xfig whose UI is a bit daunting. Regards, Walter
Re: LyX discussion boards?
of users helping other users. But I find it quite uncomfortable to use a mailing list. I had a subscription for a while but got way too many emails each day and ended up deleting them without reading them. A common solution for that is to use a separate folder and filters for mailinglists. Most mail client packages have that feature, some even have the ability to delete unread messages after a certain period. Regards, Walter
Re: LyX discussion boards?
of users helping other users. But I find it quite uncomfortable to use a mailing list. I had a subscription for a while but got way too many emails each day and ended up deleting them without reading them. A common solution for that is to use a separate folder and filters for mailinglists. Most mail client packages have that feature, some even have the ability to delete unread messages after a certain period. Regards, Walter
Re: LyX discussion boards?
> of users helping other users. But I find it quite uncomfortable to > use a mailing list. I had a subscription for a while but got way too > many emails each day and ended up deleting them without reading them. A common solution for that is to use a separate folder and filters for mailinglists. Most mail client packages have that feature, some even have the ability to delete unread messages after a certain period. Regards, Walter
ftp.lyx.org down?
Hello all, Is ftp.lyx.org down or is it just me? Regards, Walter
ftp.lyx.org down?
Hello all, Is ftp.lyx.org down or is it just me? Regards, Walter
ftp.lyx.org down?
Hello all, Is ftp.lyx.org down or is it just me? Regards, Walter
Re: Self-publishing with LyX
Typhoon wrote: I have recompiled it with \usepackage{lmodern} as suggested earlier. Could you, and others with problems, download it from http://web.aanet.com.au/sage/lyx.pdf and report the results? It now looks much better on my system. Thanks! Regards, Walter
Re: Self-publishing with LyX
Typhoon wrote: I have recompiled it with \usepackage{lmodern} as suggested earlier. Could you, and others with problems, download it from http://web.aanet.com.au/sage/lyx.pdf and report the results? It now looks much better on my system. Thanks! Regards, Walter
Re: Self-publishing with LyX
Typhoon wrote: I have recompiled it with \usepackage{lmodern} as suggested earlier. Could you, and others with problems, download it from http://web.aanet.com.au/sage/lyx.pdf and report the results? It now looks much better on my system. Thanks! Regards, Walter
Re: Self-publishing with LyX
Typhoon wrote: Hmmm. I guess so. If that offends, you can download from http://web.aanet.com.au/sage/lyx.pdf Thanks for that. The bad news is that Apple Preview doesn't render it too nicely. I guess it suffers from the same font problem that others have mentioned. Regards, Walter
Re: Self-publishing with LyX
Typhoon wrote: Hmmm. I guess so. If that offends, you can download from http://web.aanet.com.au/sage/lyx.pdf Thanks for that. The bad news is that Apple Preview doesn't render it too nicely. I guess it suffers from the same font problem that others have mentioned. Regards, Walter
Re: Self-publishing with LyX
Typhoon wrote: Hmmm. I guess so. If that offends, you can download from http://web.aanet.com.au/sage/lyx.pdf Thanks for that. The bad news is that Apple Preview doesn't render it too nicely. I guess it suffers from the same font problem that others have mentioned. Regards, Walter
Re: lyx 1.3.6 on mac os tiger
Bennett Helm wrote: This was a bug in the 1st version of the installer file. The fix for those who have already run the installer is: In Preferences Paths PATH Prefix, enter /usr/bin:/usr/local/bin:/usr/local/teTeX/bin/powerpc-apple-darwin- current:/usr/X11R6/bin:/sw/bin:/opt/local/teTeX/bin (without the quotes). Now try reconfiguring LyX; restart; reconfigure LyX; restart again. That should fix it. (I'm not sure why 2 reconfigures and restarts are needed, but I don't have 10.4 to experiment on.) This did the trick for me, are there any plans to fix this in the installer? Or at least to mention it on the Wiki? What I stil don't get is that several document classes that used to work in 1.3.4 are now gone, such as curriculum vitae and several article document klasses (Kluwer, Elsevier, Springer). Regards, Walter
Re: lyx 1.3.6 on mac os tiger
Bennett Helm wrote: The installer has been fixed; the trouble is that those who used the 1st version of the installer have to implement the fix manually. (Sorry.) Well, it works now, so never mind. Putting a message on the Wiki regarding this particular issue might be helpful though. What I stil don't get is that several document classes that used to work in 1.3.4 are now gone, such as curriculum vitae and several article document klasses (Kluwer, Elsevier, Springer). Support for these classes should be there. Look in LyX.app/Contents/ Resources/lyx/layouts for the .layout files LyX uses. You'll need to be sure your TeX installation includes the relevant .cls files, though. The .layout files are there and I am using the TeX i-packages, how do I check whether those .cls files are included or not? Regards, Walter
Re: lyx 1.3.6 on mac os tiger
Bennett Helm wrote: This was a bug in the 1st version of the installer file. The fix for those who have already run the installer is: In Preferences Paths PATH Prefix, enter /usr/bin:/usr/local/bin:/usr/local/teTeX/bin/powerpc-apple-darwin- current:/usr/X11R6/bin:/sw/bin:/opt/local/teTeX/bin (without the quotes). Now try reconfiguring LyX; restart; reconfigure LyX; restart again. That should fix it. (I'm not sure why 2 reconfigures and restarts are needed, but I don't have 10.4 to experiment on.) This did the trick for me, are there any plans to fix this in the installer? Or at least to mention it on the Wiki? What I stil don't get is that several document classes that used to work in 1.3.4 are now gone, such as curriculum vitae and several article document klasses (Kluwer, Elsevier, Springer). Regards, Walter
Re: lyx 1.3.6 on mac os tiger
Bennett Helm wrote: The installer has been fixed; the trouble is that those who used the 1st version of the installer have to implement the fix manually. (Sorry.) Well, it works now, so never mind. Putting a message on the Wiki regarding this particular issue might be helpful though. What I stil don't get is that several document classes that used to work in 1.3.4 are now gone, such as curriculum vitae and several article document klasses (Kluwer, Elsevier, Springer). Support for these classes should be there. Look in LyX.app/Contents/ Resources/lyx/layouts for the .layout files LyX uses. You'll need to be sure your TeX installation includes the relevant .cls files, though. The .layout files are there and I am using the TeX i-packages, how do I check whether those .cls files are included or not? Regards, Walter
Re: lyx 1.3.6 on mac os tiger
Bennett Helm wrote: This was a bug in the 1st version of the installer file. The fix for those who have already run the installer is: In Preferences > Paths > PATH Prefix, enter "/usr/bin:/usr/local/bin:/usr/local/teTeX/bin/powerpc-apple-darwin- current:/usr/X11R6/bin:/sw/bin:/opt/local/teTeX/bin" (without the quotes). Now try reconfiguring LyX; restart; reconfigure LyX; restart again. That should fix it. (I'm not sure why 2 reconfigures and restarts are needed, but I don't have 10.4 to experiment on.) This did the trick for me, are there any plans to fix this in the installer? Or at least to mention it on the Wiki? What I stil don't get is that several document classes that used to work in 1.3.4 are now gone, such as curriculum vitae and several article document klasses (Kluwer, Elsevier, Springer). Regards, Walter
Re: lyx 1.3.6 on mac os tiger
Bennett Helm wrote: The installer has been fixed; the trouble is that those who used the 1st version of the installer have to implement the fix manually. (Sorry.) Well, it works now, so never mind. Putting a message on the Wiki regarding this particular issue might be helpful though. What I stil don't get is that several document classes that used to work in 1.3.4 are now gone, such as curriculum vitae and several article document klasses (Kluwer, Elsevier, Springer). Support for these classes should be there. Look in LyX.app/Contents/ Resources/lyx/layouts for the .layout files LyX uses. You'll need to be sure your TeX installation includes the relevant .cls files, though. The .layout files are there and I am using the TeX i-packages, how do I check whether those .cls files are included or not? Regards, Walter