Re: Plain Text that is not Plain
Jürgen Spitzmüller wrote: Les Denham wrote: Is there a way of making the quotes strictly ASCII? I'm getting into trouble with a mailing list which insists on plain ASCII text. Not without hacking the source, I'm afraid. Question to lyx-devel: is plain text supposed to produce ASCII? If so, we need to separate displayString() and asciiString() in InsetQuote. Having an unicode export and an ascii export is fine. Going ascii-only from what we have is a huge regression. Non-english languages tend to have more than ascii in the text itself, and of course we want to keep the text intact even with an export that loose all formatting/images/formulas. If quotes is the only problem, take a look at the dialog for selecting quote styles. There are many options there. Perhaps a ascii-only style could be added there, and solve this particular problem. It could have double and 'single' quotes using ascii. Helge Hafting
Re: Plain Text that is not Plain
On Monday 02 February 2009, Helge Hafting wrote: If quotes is the only problem, take a look at the dialog for selecting quote styles. There are many options there. Perhaps a ascii-only style could be added there, and solve this particular problem. It could have double and 'single' quotes using ascii. Helge, In this particular case, the quotes are the problem. But the purpose of the restriction on the mailing list is to make it accessible to everyone by banning Microsoft formats. The filters which catch RTF (for example) also catch Unicode, in this case quotes, but it could easily be accented characters or other non-ASCII characters such as ø. The ascii-only quote style would solve the problem with quotes, but leave any other unicode characters. Interestingly, the 1500 word post which raised the list administrator's ire included a single sentence in Spanish with two accented characters in it -- he didn't notice that. But I have solved the problem by adding an ASCII format and defining a conversion from text to ASCII using recode. -- Les ~~ Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html
Re: Plain Text that is not Plain
Jürgen Spitzmüller wrote: Les Denham wrote: Is there a way of making the quotes strictly ASCII? I'm getting into trouble with a mailing list which insists on plain ASCII text. Not without hacking the source, I'm afraid. Question to lyx-devel: is plain text supposed to produce ASCII? If so, we need to separate displayString() and asciiString() in InsetQuote. Having an unicode export and an ascii export is fine. Going ascii-only from what we have is a huge regression. Non-english languages tend to have more than ascii in the text itself, and of course we want to keep the text intact even with an export that loose all formatting/images/formulas. If quotes is the only problem, take a look at the dialog for selecting quote styles. There are many options there. Perhaps a ascii-only style could be added there, and solve this particular problem. It could have double and 'single' quotes using ascii. Helge Hafting
Re: Plain Text that is not Plain
On Monday 02 February 2009, Helge Hafting wrote: If quotes is the only problem, take a look at the dialog for selecting quote styles. There are many options there. Perhaps a ascii-only style could be added there, and solve this particular problem. It could have double and 'single' quotes using ascii. Helge, In this particular case, the quotes are the problem. But the purpose of the restriction on the mailing list is to make it accessible to everyone by banning Microsoft formats. The filters which catch RTF (for example) also catch Unicode, in this case quotes, but it could easily be accented characters or other non-ASCII characters such as ø. The ascii-only quote style would solve the problem with quotes, but leave any other unicode characters. Interestingly, the 1500 word post which raised the list administrator's ire included a single sentence in Spanish with two accented characters in it -- he didn't notice that. But I have solved the problem by adding an ASCII format and defining a conversion from text to ASCII using recode. -- Les ~~ Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html
Re: Plain Text that is not Plain
Jürgen Spitzmüller wrote: Les Denham wrote: > Is there a way of making the quotes strictly ASCII? I'm getting into > trouble with a mailing list which insists on plain ASCII text. Not without hacking the source, I'm afraid. Question to lyx-devel: is "plain text" supposed to produce ASCII? If so, we need to separate displayString() and asciiString() in InsetQuote. Having an unicode export and an ascii export is fine. Going ascii-only from what we have is a huge regression. Non-english languages tend to have more than ascii in the text itself, and of course we want to keep the text intact even with an export that loose all formatting/images/formulas. If quotes is the only problem, take a look at the dialog for selecting quote styles. There are many options there. Perhaps a "ascii-only" style could be added there, and solve this particular problem. It could have "double" and 'single' quotes using ascii. Helge Hafting
Re: Plain Text that is not Plain
On Monday 02 February 2009, Helge Hafting wrote: > If quotes is the only problem, take a look at the dialog for selecting > quote styles. There are many options there. Perhaps a "ascii-only" style > could be added there, and solve this particular problem. It could have > "double" and 'single' quotes using ascii. Helge, In this particular case, the quotes are the problem. But the purpose of the restriction on the mailing list is to make it accessible to everyone by banning Microsoft formats. The filters which catch RTF (for example) also catch Unicode, in this case quotes, but it could easily be accented characters or other non-ASCII characters such as ø. The ascii-only quote style would solve the problem with quotes, but leave any other unicode characters. Interestingly, the 1500 word post which raised the list administrator's ire included a single sentence in Spanish with two accented characters in it -- he didn't notice that. But I have solved the problem by adding an ASCII format and defining a conversion from text to ASCII using recode. -- Les ~~ Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html
Plain Text that is not Plain
Since upgrading from LyX 1.5.4 to LyX 1.6.1 I have found that Plain Text exports from LyX are no longer Plain Text, especially when it comes to quotes. The difference is shown in the two attachments, one from my office computer, which is still running 1.5.4, and one from my laptop, which is running 1.6.1. Both have Gentoo Linux as the OS. The 1.5.4 has TeXLive-2007, and the 1.6.1 has TeXLive-2008. Is there a way of making the quotes strictly ASCII? I'm getting into trouble with a mailing list which insists on plain ASCII text. -- Les ~~ Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ``This is a test''. âThis is a Testâ.
Re: Plain Text that is not Plain
Les Denham wrote: Is there a way of making the quotes strictly ASCII? I'm getting into trouble with a mailing list which insists on plain ASCII text. Not without hacking the source, I'm afraid. Question to lyx-devel: is plain text supposed to produce ASCII? If so, we need to separate displayString() and asciiString() in InsetQuote. Jürgen
Re: Plain Text that is not Plain
On Tuesday 27 January 2009, Jürgen Spitzmüller wrote: Les Denham wrote: Is there a way of making the quotes strictly ASCII? I'm getting into trouble with a mailing list which insists on plain ASCII text. Not without hacking the source, I'm afraid. Question to lyx-devel: is plain text supposed to produce ASCII? If so, we need to separate displayString() and asciiString() in InsetQuote. Jürgen, Thanks for the prompt reply. I rather think there should be an option to export 7-bit ASCII. Oh well. There's always sed . . . -- Les ~~ Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html
Re: Plain Text that is not Plain
Jürgen Spitzmüller juer...@spitzmueller.org writes: Les Denham wrote: Is there a way of making the quotes strictly ASCII? I'm getting into trouble with a mailing list which insists on plain ASCII text. Not without hacking the source, I'm afraid. Question to lyx-devel: is plain text supposed to produce ASCII? If so, we need to separate displayString() and asciiString() in InsetQuote. the methods produce unicode. We could afterwards run all sorts of iconv translation to output plain text in whatever encoding we choose. This could be set in preferences. I do not know however whether iconv translates weird quotes to normal ones. JMarc
Re: Plain Text that is not Plain
On Tuesday 27 January 2009 03:52:57 pm Jean-Marc Lasgouttes wrote: Jürgen Spitzmüller juer...@spitzmueller.org writes: Les Denham wrote: Is there a way of making the quotes strictly ASCII? I'm getting into trouble with a mailing list which insists on plain ASCII text. Not without hacking the source, I'm afraid. Question to lyx-devel: is plain text supposed to produce ASCII? If so, we need to separate displayString() and asciiString() in InsetQuote. the methods produce unicode. We could afterwards run all sorts of iconv translation to output plain text in whatever encoding we choose. This could be set in preferences. I do not know however whether iconv translates weird quotes to normal ones. All, I have worked out a solution to the problem which appears to work perfectly, and is simple to implement. The only dependency introduced is recode (http://directory.fsf.org/project/recode/). I'd guess uni2ascii would also work, but I haven't tried it. To export Plain Text (ASCII) from LyX 1.6.1 or newer: == 1. Define the new format Tools-Preferences-File Handling-File Formats Click on New Format: ASCII Short Name: ascii Extension: txt Click on Apply 2. Define the converter Tools-Preferences-File Handling-Converters From format: Plain Text To format: ASCII Converter: recode UTF-8..ASCII $i $$o Click on Add Click on Apply You should now be able to see ASCII as an Export option. Les
Plain Text that is not Plain
Since upgrading from LyX 1.5.4 to LyX 1.6.1 I have found that Plain Text exports from LyX are no longer Plain Text, especially when it comes to quotes. The difference is shown in the two attachments, one from my office computer, which is still running 1.5.4, and one from my laptop, which is running 1.6.1. Both have Gentoo Linux as the OS. The 1.5.4 has TeXLive-2007, and the 1.6.1 has TeXLive-2008. Is there a way of making the quotes strictly ASCII? I'm getting into trouble with a mailing list which insists on plain ASCII text. -- Les ~~ Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ``This is a test''. âThis is a Testâ.
Re: Plain Text that is not Plain
Les Denham wrote: Is there a way of making the quotes strictly ASCII? I'm getting into trouble with a mailing list which insists on plain ASCII text. Not without hacking the source, I'm afraid. Question to lyx-devel: is plain text supposed to produce ASCII? If so, we need to separate displayString() and asciiString() in InsetQuote. Jürgen
Re: Plain Text that is not Plain
On Tuesday 27 January 2009, Jürgen Spitzmüller wrote: Les Denham wrote: Is there a way of making the quotes strictly ASCII? I'm getting into trouble with a mailing list which insists on plain ASCII text. Not without hacking the source, I'm afraid. Question to lyx-devel: is plain text supposed to produce ASCII? If so, we need to separate displayString() and asciiString() in InsetQuote. Jürgen, Thanks for the prompt reply. I rather think there should be an option to export 7-bit ASCII. Oh well. There's always sed . . . -- Les ~~ Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html
Re: Plain Text that is not Plain
Jürgen Spitzmüller juer...@spitzmueller.org writes: Les Denham wrote: Is there a way of making the quotes strictly ASCII? I'm getting into trouble with a mailing list which insists on plain ASCII text. Not without hacking the source, I'm afraid. Question to lyx-devel: is plain text supposed to produce ASCII? If so, we need to separate displayString() and asciiString() in InsetQuote. the methods produce unicode. We could afterwards run all sorts of iconv translation to output plain text in whatever encoding we choose. This could be set in preferences. I do not know however whether iconv translates weird quotes to normal ones. JMarc
Re: Plain Text that is not Plain
On Tuesday 27 January 2009 03:52:57 pm Jean-Marc Lasgouttes wrote: Jürgen Spitzmüller juer...@spitzmueller.org writes: Les Denham wrote: Is there a way of making the quotes strictly ASCII? I'm getting into trouble with a mailing list which insists on plain ASCII text. Not without hacking the source, I'm afraid. Question to lyx-devel: is plain text supposed to produce ASCII? If so, we need to separate displayString() and asciiString() in InsetQuote. the methods produce unicode. We could afterwards run all sorts of iconv translation to output plain text in whatever encoding we choose. This could be set in preferences. I do not know however whether iconv translates weird quotes to normal ones. All, I have worked out a solution to the problem which appears to work perfectly, and is simple to implement. The only dependency introduced is recode (http://directory.fsf.org/project/recode/). I'd guess uni2ascii would also work, but I haven't tried it. To export Plain Text (ASCII) from LyX 1.6.1 or newer: == 1. Define the new format Tools-Preferences-File Handling-File Formats Click on New Format: ASCII Short Name: ascii Extension: txt Click on Apply 2. Define the converter Tools-Preferences-File Handling-Converters From format: Plain Text To format: ASCII Converter: recode UTF-8..ASCII $i $$o Click on Add Click on Apply You should now be able to see ASCII as an Export option. Les
Plain Text that is not Plain
Since upgrading from LyX 1.5.4 to LyX 1.6.1 I have found that Plain Text exports from LyX are no longer Plain Text, especially when it comes to quotes. The difference is shown in the two attachments, one from my office computer, which is still running 1.5.4, and one from my laptop, which is running 1.6.1. Both have Gentoo Linux as the OS. The 1.5.4 has TeXLive-2007, and the 1.6.1 has TeXLive-2008. Is there a way of making the quotes strictly ASCII? I'm getting into trouble with a mailing list which insists on plain ASCII text. -- Les ~~ Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ``This is a test''. âThis is a Testâ.
Re: Plain Text that is not Plain
Les Denham wrote: > Is there a way of making the quotes strictly ASCII? I'm getting into > trouble with a mailing list which insists on plain ASCII text. Not without hacking the source, I'm afraid. Question to lyx-devel: is "plain text" supposed to produce ASCII? If so, we need to separate displayString() and asciiString() in InsetQuote. Jürgen
Re: Plain Text that is not Plain
On Tuesday 27 January 2009, Jürgen Spitzmüller wrote: > Les Denham wrote: > > Is there a way of making the quotes strictly ASCII? I'm getting into > > trouble with a mailing list which insists on plain ASCII text. > > Not without hacking the source, I'm afraid. > Question to lyx-devel: is "plain text" supposed to produce ASCII? If so, we > need to separate displayString() and asciiString() in InsetQuote. > Jürgen, Thanks for the prompt reply. I rather think there should be an option to export 7-bit ASCII. Oh well. There's always sed . . . -- Les ~~ Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html
Re: Plain Text that is not Plain
Jürgen Spitzmüller <juer...@spitzmueller.org> writes: > Les Denham wrote: >> Is there a way of making the quotes strictly ASCII? I'm getting into >> trouble with a mailing list which insists on plain ASCII text. > > Not without hacking the source, I'm afraid. > Question to lyx-devel: is "plain text" supposed to produce ASCII? If so, we > need to separate displayString() and asciiString() in InsetQuote. the methods produce unicode. We could afterwards run all sorts of iconv translation to output plain text in whatever encoding we choose. This could be set in preferences. I do not know however whether iconv translates weird quotes to normal ones. JMarc
Re: Plain Text that is not Plain
On Tuesday 27 January 2009 03:52:57 pm Jean-Marc Lasgouttes wrote: > Jürgen Spitzmüller <juer...@spitzmueller.org> writes: > > Les Denham wrote: > >> Is there a way of making the quotes strictly ASCII? I'm getting into > >> trouble with a mailing list which insists on plain ASCII text. > > > > Not without hacking the source, I'm afraid. > > Question to lyx-devel: is "plain text" supposed to produce ASCII? If so, > > we need to separate displayString() and asciiString() in InsetQuote. > > the methods produce unicode. We could afterwards run all sorts of iconv > translation to output plain text in whatever encoding we choose. This > could be set in preferences. > > I do not know however whether iconv translates weird quotes to normal ones. All, I have worked out a solution to the problem which appears to work perfectly, and is simple to implement. The only dependency introduced is recode (http://directory.fsf.org/project/recode/). I'd guess uni2ascii would also work, but I haven't tried it. To export Plain Text (ASCII) from LyX 1.6.1 or newer: == 1. Define the new format Tools->Preferences->File Handling->File Formats Click on New Format: ASCII Short Name: ascii Extension: txt Click on Apply 2. Define the converter Tools->Preferences->File Handling->Converters From format: Plain Text To format: ASCII Converter: recode UTF-8..ASCII <$i >$$o Click on Add Click on Apply You should now be able to see ASCII as an Export option. Les
