Re: Importing a text file with German accented characters
Nicholas Allen wrote: I hope someone can help me. I am trying to import a text file that contains German accented characters. The file is saved in UTF-8 format. How do I do this? If I use the import ASCII the accented characters appear as two junk characters. Can you do a find and replace for the junk characters? Or find and replace the accented characters in the source document with your own junk string, then find and replace with accented e in the document once it's been imported to LyX? Or open the document in another word processor and change the encoding? Those are awkward work-arounds but until LyX is supporting UTF-8 those are the only options I know. regards, Beth -- Friends don't let friends write junk. http://slobbit.livejournal.com
Re: Importing a text file with German accented characters
Nicholas Allen wrote: I hope someone can help me. I am trying to import a text file that contains German accented characters. The file is saved in UTF-8 format. How do I do this? If I use the import ASCII the accented characters appear as two junk characters. Can you do a find and replace for the junk characters? Or find and replace the accented characters in the source document with your own junk string, then find and replace with accented e in the document once it's been imported to LyX? Or open the document in another word processor and change the encoding? Those are awkward work-arounds but until LyX is supporting UTF-8 those are the only options I know. regards, Beth -- Friends don't let friends write junk. http://slobbit.livejournal.com
Re: Importing a text file with German accented characters
Nicholas Allen wrote: I hope someone can help me. I am trying to import a text file that contains German accented characters. The file is saved in UTF-8 format. How do I do this? If I use the import ASCII the accented characters appear as two junk characters. Can you do a find and replace for the junk characters? Or find and replace the accented characters in the source document with your own junk string, then find and replace with accented e in the document once it's been imported to LyX? Or open the document in another word processor and change the encoding? Those are awkward work-arounds but until LyX is supporting UTF-8 those are the only options I know. regards, Beth -- "Friends don't let friends write junk." http://slobbit.livejournal.com
Mac LaTex to HTML Conversion
I'm using LyX 1.4.0 on a G4 PowerBook with OS 10.4.5, and 1.3.5 on a G5 iMac with OS 10.4.5. Has LyX moved away from allowing choice in use of a LaTeX to HTML converter? With 1.3.5 when I run reconfigure, I see this: checking for a LaTeX - HTML converter... (tth latex2html hevea) +checking for tth... no +checking for latex2html... yes OK, this is good, because I have macros set up in jEdit to convert the html for posting on my blog and other forums, and converting this output to rtf is fairly trivial. But on the PowerBook with 1.4.0 (and previously 1.3.8), I see this: checking for a LaTex - HTML converter... +checking for htlatex... yes checking LaTeX configuration... auto This is BAD for my purposes, because htlatex is using classes and spans to format output, instead of simple italics or bold tags. Even worse, the span tags straddle a linebreak, so I can't even do a simple find and replace for them. And that doesn't even bring up the issue of the commented line numbering htlatex does, which also needs to go. Does someone have a workaround for this that doesn't involve delving into the morass that is the documentation for the new converter? Perhaps, getting LyX 1.4.0 to recognize my Fink install of LaTeX2HTML? In short, new LyX (though I really love new features like Word Count), is no longer seamlessly doing a large part of what I need to do in terms of output on a daily basis. This makes me sad. regards, Beth -- Friends don't let friends write junk.
Re: Mac LaTex to HTML Conversion
Bennett Helm wrote: *snip most excellent instructions* You should now be able to use latex2html -- and you can produce it from the View menu if you've added open in the Viewer field as I suggested. Perfect! That worked like a charm, and I added my latex2rtf converter as well, so I'm back in business. Off now to install 1.4.0 on the desktop. Clearly I was overthinking the problem and getting myself confused. Thanks, Beth -- Friends don't let friends write junk. http://slobbit.livejournal.com
Mac LaTex to HTML Conversion
I'm using LyX 1.4.0 on a G4 PowerBook with OS 10.4.5, and 1.3.5 on a G5 iMac with OS 10.4.5. Has LyX moved away from allowing choice in use of a LaTeX to HTML converter? With 1.3.5 when I run reconfigure, I see this: checking for a LaTeX - HTML converter... (tth latex2html hevea) +checking for tth... no +checking for latex2html... yes OK, this is good, because I have macros set up in jEdit to convert the html for posting on my blog and other forums, and converting this output to rtf is fairly trivial. But on the PowerBook with 1.4.0 (and previously 1.3.8), I see this: checking for a LaTex - HTML converter... +checking for htlatex... yes checking LaTeX configuration... auto This is BAD for my purposes, because htlatex is using classes and spans to format output, instead of simple italics or bold tags. Even worse, the span tags straddle a linebreak, so I can't even do a simple find and replace for them. And that doesn't even bring up the issue of the commented line numbering htlatex does, which also needs to go. Does someone have a workaround for this that doesn't involve delving into the morass that is the documentation for the new converter? Perhaps, getting LyX 1.4.0 to recognize my Fink install of LaTeX2HTML? In short, new LyX (though I really love new features like Word Count), is no longer seamlessly doing a large part of what I need to do in terms of output on a daily basis. This makes me sad. regards, Beth -- Friends don't let friends write junk.
Re: Mac LaTex to HTML Conversion
Bennett Helm wrote: *snip most excellent instructions* You should now be able to use latex2html -- and you can produce it from the View menu if you've added open in the Viewer field as I suggested. Perfect! That worked like a charm, and I added my latex2rtf converter as well, so I'm back in business. Off now to install 1.4.0 on the desktop. Clearly I was overthinking the problem and getting myself confused. Thanks, Beth -- Friends don't let friends write junk. http://slobbit.livejournal.com
Mac LaTex to HTML Conversion
I'm using LyX 1.4.0 on a G4 PowerBook with OS 10.4.5, and 1.3.5 on a G5 iMac with OS 10.4.5. Has LyX moved away from allowing choice in use of a LaTeX to HTML converter? With 1.3.5 when I run reconfigure, I see this: checking for a LaTeX -> HTML converter... (tth latex2html hevea) +checking for "tth"... no +checking for "latex2html"... yes OK, this is good, because I have macros set up in jEdit to convert the html for posting on my blog and other forums, and converting this output to rtf is fairly trivial. But on the PowerBook with 1.4.0 (and previously 1.3.8), I see this: checking for a LaTex -> HTML converter... +checking for "htlatex"... yes checking LaTeX configuration... auto This is BAD for my purposes, because htlatex is using classes and spans to format output, instead of simple italics or bold tags. Even worse, the span tags straddle a linebreak, so I can't even do a simple find and replace for them. And that doesn't even bring up the issue of the commented line numbering htlatex does, which also needs to go. Does someone have a workaround for this that doesn't involve delving into the morass that is the documentation for the new converter? Perhaps, getting LyX 1.4.0 to recognize my Fink install of LaTeX2HTML? In short, new LyX (though I really love new features like Word Count), is no longer seamlessly doing a large part of what I need to do in terms of output on a daily basis. This makes me sad. regards, Beth -- "Friends don't let friends write junk."
Re: Mac LaTex to HTML Conversion
Bennett Helm wrote: *snip most excellent instructions* You should now be able to use latex2html -- and you can produce it from the View menu if you've added "open" in the Viewer field as I suggested. Perfect! That worked like a charm, and I added my latex2rtf converter as well, so I'm back in business. Off now to install 1.4.0 on the desktop. Clearly I was overthinking the problem and getting myself confused. Thanks, Beth -- "Friends don't let friends write junk." http://slobbit.livejournal.com
