## latex2rtf-users — usage of the latex to rtf converter

You can subscribe to this list here.

2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 Jan Feb Mar Apr May Jun Jul Aug Sep Oct (5) Nov Dec Jan Feb Mar Apr May Jun (3) Jul (1) Aug Sep Oct Nov Dec Jan Feb Mar Apr (1) May Jun (1) Jul (2) Aug Sep (1) Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep (1) Oct (2) Nov (12) Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec (2) Jan (3) Feb (2) Mar Apr May Jun Jul (1) Aug Sep Oct Nov Dec Jan (2) Feb Mar (7) Apr (3) May Jun (2) Jul (12) Aug (6) Sep (1) Oct (9) Nov (10) Dec (3) Jan Feb Mar Apr (8) May (6) Jun (10) Jul (9) Aug (3) Sep Oct Nov Dec (2) Jan Feb Mar Apr May Jun (3) Jul (2) Aug (7) Sep (1) Oct (1) Nov (4) Dec (6) Jan Feb (6) Mar (1) Apr (3) May Jun (2) Jul Aug Sep (2) Oct (2) Nov (7) Dec Jan (7) Feb (5) Mar Apr (5) May (4) Jun (3) Jul (10) Aug (3) Sep Oct (2) Nov Dec Jan Feb Mar (7) Apr (1) May Jun (3) Jul (2) Aug Sep Oct Nov (3) Dec Jan Feb (4) Mar Apr (7) May (2) Jun Jul Aug Sep Oct Nov (1) Dec Jan Feb Mar Apr May Jun Jul (2) Aug Sep (2) Oct Nov Dec Jan (2) Feb Mar Apr May (2) Jun Jul Aug (5) Sep (6) Oct (3) Nov Dec Jan (3) Feb Mar Apr (4) May Jun (5) Jul (2) Aug Sep Oct Nov (5) Dec Jan (5) Feb Mar Apr (7) May (3) Jun (2) Jul Aug Sep Oct Nov Dec

Showing results of 304

1 2 3 .. 13 > >> (Page 1 of 13)
 Re: [Latex2rtf-users] Virus detected From: Wilfried Hennings - 2017-06-29 13:51:28 At 29.06.2017 13:03 Francesco Biccari wrote: > Hello, > > this is my first message. I've tried to download latex2rtf-win 2.3.16 > several times in the last two days, but every time my antivirus > detects a trojan in the exe file > ( https://www.microsoft.com/security/portal/threat/encyclopedia/Entry.aspx?Name=Trojan:Win32/Pellate.A!plock > ). > > I tried with two different laptops, one with Microsoft Security > Essential and the other with Norton. > > Is it a real threat? Hello, I am the one who compiles and packages the windows version. I just downloaded latex2rtf-win 2.3.16 myself to make sure that the version on sourceforge wasn't modified by someone else. It is identical to the version I uploaded. The latex2rtf-2.3.16_win.exe is not reported as virus or trojan by Windows Defender and Kaspersky Endpoint Security on a Windows 7 system, and Avira on a Windows 10 system. Sometimes the installer is incorrectly reported as a virus or trojan. You may check this by downloading the installer software NSIS 3.01 from https://sourceforge.net/projects/nsis/ If your antivirus also reports this as a trojan, please report both cases to Norton and Microsoft as false positives. Hope this helps. Wilfried 
 [Latex2rtf-users] Virus detected From: Francesco Biccari - 2017-06-29 11:04:07 Hello, this is my first message. I've tried to download latex2rtf-win 2.3.16 several times in the last two days, but every time my antivirus detects a trojan in the exe file ( https://www.microsoft.com/security/portal/threat/encyclopedia/Entry.aspx?Name=Trojan:Win32/Pellate.A!plock ). I tried with two different laptops, one with Microsoft Security Essential and the other with Norton. Is it a real threat? Thank you in advance for your help. Best regards. Francesco 
 [Latex2rtf-users] Donations? From: Villads Egede Johansen - 2017-05-16 15:08:45 Attachments: Message as HTML Hello, This converter is a real life saver! Is there a way to donate to the developers? Cheers, Villads ~~~~~~~ Dr Villads Egede Johansen University of Cambridge Dept. of Chemistry Lensfield Road, CB2 1EW Cambridge, UK Tel: +44-1223-336410 http://www.ch.cam.ac.uk/group/vignolini/ ; 
 Re: [Latex2rtf-users] error message -- only a single file can be processed at a time From: Wilfried Hennings - 2017-05-09 07:13:47 Hello, At 08.05.2017 22:07 Neil Siegel wrote: > I just installed latex2rtf v2.3.15. I have long had TexStudio (v2.3) on > this same computer. Windows 10 64-bit. > > When I try to run a conversion, I receive the following error message: > > (Not set):1 Only a single file can be processed at a time. > > I assume that something did not set up correctly. I did set the system > environment variable RTFPATH to point at the cfg directory under the > c:\Program Files (x86)/latex2rtf directory, but I get the same result. Although setting the environment variable RTFPATH is a good idea, the error message has nothing to do with this. It could be that any of the folders in the path to the .tex file or the .tex file itself contains one or more blanks in its name. We tried to make the program compatible with names containing blanks, but it is hard to achieve this under all circumstances. The converter program latex2rt.exe is a command line application, and the input file ID (consisting of the path and the filename) is part of the command line calling latex2rt.exe. If there is a blank in the file ID, the file ID has to be surrounded by quotes, otherwise the blanks are interpreted as option delimiters, which would result in the cited error message. For any further help, you should specify how you call latex2rtf, i.e. from the latex2rtf gui shell, from the command prompt, or from a third party program as e.g. TexStudio. (But I don't know whether TexStudio has an option to do this.) Regards Wilfried 
 [Latex2rtf-users] error message -- only a single file can be processed at a time From: Neil Siegel - 2017-05-08 20:07:57 Attachments: Message as HTML I just installed latex2rtf v2.3.15. I have long had TexStudio (v2.3) on this same computer. Windows 10 64-bit. When I try to run a conversion, I receive the following error message: (Not set):1 Only a single file can be processed at a time. I assume that something did not set up correctly. I did set the system environment variable RTFPATH to point at the cfg directory under the c:\Program Files (x86)/latex2rtf directory, but I get the same result. Any ideas? Neil 
 Re: [Latex2rtf-users] Can I get rid of Table-of-contents references in captions? From: Wilfried Hennings - 2017-04-27 09:52:19 Hi Scott, nice to get a message from you. OK, I didn't think of the -f option, and I just tested it. But -f1 suppresses \ref and \cite fields (and -f0 also \eq fields), but it does not suppress the \TC fields. Regards Wilfried At 26.04.2017 20:39 Scott Prahl wrote: > You can turn off field generation totally with the command line option -f0 > >> On Apr 24, 2017, at 5:31 AM, Wilfried Hennings wrote: >> >> At 18.04.2017 15:07 Martin Gilje Jaatun wrote: >>> I want to use LaTeX2rtf for conversion of papers for a specific journal >>> that only accepts MS Word submissions. LaTeX2rtf seems to do the trick, >>> but figure captions are messed up by code designed to add caption text >>> to the Table of Contents (or, presumably, table of figures): >>> >>> Figure 1: Acknowledgement of the problem in popular culture{TC "1 >>> Acknowledgement of the problem in popular culture" \f f} >>> >>> The weird thing is that although this is obviously treated as a field >>> code by MS Word, I cannot get rid of it by pressing Alt-F9. If I select >>> the text and copy it to another program (say, Emacs) the field code >>> disappears. >>> >>> Clearly, I do not need ToC entries in a paper, so is there any way I can >>> suppress this feature for captions? >>> >>> -Martin >>> _______________________________________________ >>> Latex2rtf-users mailing list >>> Latex2rtf-users@... >>> https://lists.sourceforge.net/lists/listinfo/latex2rtf-users >> >> Up to now there is no switch in latex2rtf to suppress these field codes. >> In Word they are displayed only if the option "display hidden text" is set. >> And it is easy to remove them after opening the rtf in Word. >> Following steps would be valid for MS Word 2010: >> choose: File - options - display - display hidden text >> choose: Start - replace - >> replace: ^dTC >> by: (nothing) >> replace all >> >> That's it. >> >> And here is a Word VBA macro code to perform these actions: >> >> Sub remove_TC_fields() >> ' >> ' removes hidden TC fields >> ' >> Dim SHT As Boolean >> SHT = ActiveWindow.View.ShowHiddenText >> ActiveWindow.View.ShowHiddenText = True >> >> Selection.Find.ClearFormatting >> Selection.Find.Replacement.ClearFormatting >> With Selection.Find >> .Text = "^dTC" >> .Replacement.Text = "" >> .Forward = True >> .Wrap = wdFindContinue >> .Format = False >> .MatchCase = False >> .MatchWholeWord = False >> .MatchWildcards = False >> .MatchSoundsLike = False >> .MatchAllWordForms = False >> End With >> Selection.Find.Execute Replace:=wdReplaceAll >> ActiveWindow.View.ShowHiddenText = SHT >> >> End Sub >> >> regards >> Wilfried >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Latex2rtf-users mailing list >> Latex2rtf-users@... >> https://lists.sourceforge.net/lists/listinfo/latex2rtf-users > > 
 Re: [Latex2rtf-users] Can I get rid of Table-of-contents references in captions? From: Scott Prahl - 2017-04-26 18:56:08 You can turn off field generation totally with the command line option -f0 > On Apr 24, 2017, at 5:31 AM, Wilfried Hennings wrote: > > At 18.04.2017 15:07 Martin Gilje Jaatun wrote: >> I want to use LaTeX2rtf for conversion of papers for a specific journal >> that only accepts MS Word submissions. LaTeX2rtf seems to do the trick, >> but figure captions are messed up by code designed to add caption text >> to the Table of Contents (or, presumably, table of figures): >> >> Figure 1: Acknowledgement of the problem in popular culture{TC "1 >> Acknowledgement of the problem in popular culture" \f f} >> >> The weird thing is that although this is obviously treated as a field >> code by MS Word, I cannot get rid of it by pressing Alt-F9. If I select >> the text and copy it to another program (say, Emacs) the field code >> disappears. >> >> Clearly, I do not need ToC entries in a paper, so is there any way I can >> suppress this feature for captions? >> >> -Martin >> _______________________________________________ >> Latex2rtf-users mailing list >> Latex2rtf-users@... >> https://lists.sourceforge.net/lists/listinfo/latex2rtf-users > > Up to now there is no switch in latex2rtf to suppress these field codes. > In Word they are displayed only if the option "display hidden text" is set. > And it is easy to remove them after opening the rtf in Word. > Following steps would be valid for MS Word 2010: > choose: File - options - display - display hidden text > choose: Start - replace - > replace: ^dTC > by: (nothing) > replace all > > That's it. > > And here is a Word VBA macro code to perform these actions: > > Sub remove_TC_fields() > ' > ' removes hidden TC fields > ' > Dim SHT As Boolean > SHT = ActiveWindow.View.ShowHiddenText > ActiveWindow.View.ShowHiddenText = True > > Selection.Find.ClearFormatting > Selection.Find.Replacement.ClearFormatting > With Selection.Find > .Text = "^dTC" > .Replacement.Text = "" > .Forward = True > .Wrap = wdFindContinue > .Format = False > .MatchCase = False > .MatchWholeWord = False > .MatchWildcards = False > .MatchSoundsLike = False > .MatchAllWordForms = False > End With > Selection.Find.Execute Replace:=wdReplaceAll > ActiveWindow.View.ShowHiddenText = SHT > > End Sub > > regards > Wilfried > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Latex2rtf-users mailing list > Latex2rtf-users@... > https://lists.sourceforge.net/lists/listinfo/latex2rtf-users 
 Re: [Latex2rtf-users] Can I get rid of Table-of-contents references in captions? From: Wilfried Hennings - 2017-04-24 12:32:13 At 18.04.2017 15:07 Martin Gilje Jaatun wrote: > I want to use LaTeX2rtf for conversion of papers for a specific journal > that only accepts MS Word submissions. LaTeX2rtf seems to do the trick, > but figure captions are messed up by code designed to add caption text > to the Table of Contents (or, presumably, table of figures): > > Figure 1: Acknowledgement of the problem in popular culture{TC "1 > Acknowledgement of the problem in popular culture" \f f} > > The weird thing is that although this is obviously treated as a field > code by MS Word, I cannot get rid of it by pressing Alt-F9. If I select > the text and copy it to another program (say, Emacs) the field code > disappears. > > Clearly, I do not need ToC entries in a paper, so is there any way I can > suppress this feature for captions? > > -Martin > _______________________________________________ > Latex2rtf-users mailing list > Latex2rtf-users@... > https://lists.sourceforge.net/lists/listinfo/latex2rtf-users Up to now there is no switch in latex2rtf to suppress these field codes. In Word they are displayed only if the option "display hidden text" is set. And it is easy to remove them after opening the rtf in Word. Following steps would be valid for MS Word 2010: choose: File - options - display - display hidden text choose: Start - replace - replace: ^dTC by: (nothing) replace all That's it. And here is a Word VBA macro code to perform these actions: Sub remove_TC_fields() ' ' removes hidden TC fields ' Dim SHT As Boolean SHT = ActiveWindow.View.ShowHiddenText ActiveWindow.View.ShowHiddenText = True Selection.Find.ClearFormatting Selection.Find.Replacement.ClearFormatting With Selection.Find .Text = "^dTC" .Replacement.Text = "" .Forward = True .Wrap = wdFindContinue .Format = False .MatchCase = False .MatchWholeWord = False .MatchWildcards = False .MatchSoundsLike = False .MatchAllWordForms = False End With Selection.Find.Execute Replace:=wdReplaceAll ActiveWindow.View.ShowHiddenText = SHT End Sub regards Wilfried 
 [Latex2rtf-users] Can I get rid of Table-of-contents references in captions? From: Martin Gilje Jaatun - 2017-04-18 13:26:13 Attachments: Message as HTML Hi, I want to use LaTeX2rtf for conversion of papers for a specific journal that only accepts MS Word submissions. LaTeX2rtf seems to do the trick, but figure captions are messed up by code designed to add caption text to the Table of Contents (or, presumably, table of figures): Figure 1: Acknowledgement of the problem in popular culture{TC "1 Acknowledgement of the problem in popular culture" \f f} The weird thing is that although this is obviously treated as a field code by MS Word, I cannot get rid of it by pressing Alt-F9. If I select the text and copy it to another program (say, Emacs) the field code disappears. Clearly, I do not need ToC entries in a paper, so is there any way I can suppress this feature for captions? -Martin 
 Re: [Latex2rtf-users] Bug From: Patrick Dupre - 2017-04-06 17:28:44 OK, but then it should not fails with M0 If I do not need to the conversion of the equations It still fails with -M0 =========================================================================== Patrick DUPRÉ | | email: pdupre@... Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France =========================================================================== > Sent: Thursday, April 06, 2017 at 7:08 PM > From: "Wilfried Hennings" > To: "Patrick Dupre" , latex2rtf > Subject: Re: [Latex2rtf-users] Bug > > Hello, > the error messages > > Document format unknown, using article format > Package/option 'american' unknown. > Unknown command '\bm' > > say it all: > These commands aren't yet supported. > This is not a bug but a known limitation of the program. > > If you use latex2rtf with the option -M12, conversion will succeed, > because the equation with the unsupported command will be processed by > LaTeX and converted to a bitmap. > > Regards > Wilfried > > At 06.04.2017 14:28 Patrick Dupre wrote: > > Hello, > > > > I am use latex2rtf 2.3.13 r1248 (released Mar 22 2017) > > on a fedora 24 > > > > The code fails when I try to generate a rtf file > > > > \documentclass[10pt,american]{revtex4-1} > > > > \usepackage[T1]{fontenc} > > \usepackage[latin9]{inputenc} > > \usepackage[a4paper]{geometry} > > \usepackage{babel} > > \pagestyle{plain} > > > > > > \begin{document} > > > > > > \section{Introduction} > > > > In a > > > > $$> > {\rm d}\bm{\alpha}_{m_{u}m_{l}}\left(\omega,\delta,r\right)=\frac{\frac{{\rm d}}{{\rm d}z}\left[{\rm i}\int\left[\omega\,{\rm d}\bm{P}_{m_{u}m_{l}}^{*}\left(\omega,\delta,r,z\right)\right]\otimes\bm{E}\left(\omega,r,z\right)\,{\rm d}V\right]}{c\epsilon_{0}\int\int\bm{E}^{*}\left(\omega,r,z\right)\otimes\bm{E}\left(\omega,r,z\right)\,{\rm d}S\,{\rm d}\omega},%\label{eq:alpha_cmpx} > >$$ > > > > > > \subsection{Liouville Equation} > > > > When > > > > > > \end{document} > > > > =========================================================================== > > Patrick DUPRÉ | | email: pdupre@... > > Laboratoire de Physico-Chimie de l'Atmosphère | | > > Université du Littoral-Côte d'Opale | | > > Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 > > 189A, avenue Maurice Schumann | | 59140 Dunkerque, France > > =========================================================================== > > _______________________________________________ > > Latex2rtf-users mailing list > > Latex2rtf-users@... > > https://lists.sourceforge.net/lists/listinfo/latex2rtf-users > > > > 
 Re: [Latex2rtf-users] Bug From: Wilfried Hennings - 2017-04-06 17:07:03 Hello, the error messages Document format unknown, using article format Package/option 'american' unknown. Unknown command '\bm' say it all: These commands aren't yet supported. This is not a bug but a known limitation of the program. If you use latex2rtf with the option -M12, conversion will succeed, because the equation with the unsupported command will be processed by LaTeX and converted to a bitmap. Regards Wilfried At 06.04.2017 14:28 Patrick Dupre wrote: > Hello, > > I am use latex2rtf 2.3.13 r1248 (released Mar 22 2017) > on a fedora 24 > > The code fails when I try to generate a rtf file > > \documentclass[10pt,american]{revtex4-1} > > \usepackage[T1]{fontenc} > \usepackage[latin9]{inputenc} > \usepackage[a4paper]{geometry} > \usepackage{babel} > \pagestyle{plain} > > > \begin{document} > > > \section{Introduction} > > In a > > $$> {\rm d}\bm{\alpha}_{m_{u}m_{l}}\left(\omega,\delta,r\right)=\frac{\frac{{\rm d}}{{\rm d}z}\left[{\rm i}\int\left[\omega\,{\rm d}\bm{P}_{m_{u}m_{l}}^{*}\left(\omega,\delta,r,z\right)\right]\otimes\bm{E}\left(\omega,r,z\right)\,{\rm d}V\right]}{c\epsilon_{0}\int\int\bm{E}^{*}\left(\omega,r,z\right)\otimes\bm{E}\left(\omega,r,z\right)\,{\rm d}S\,{\rm d}\omega},%\label{eq:alpha_cmpx} >$$ > > > \subsection{Liouville Equation} > > When > > > \end{document} > > =========================================================================== > Patrick DUPRÉ | | email: pdupre@... > Laboratoire de Physico-Chimie de l'Atmosphère | | > Université du Littoral-Côte d'Opale | | > Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 > 189A, avenue Maurice Schumann | | 59140 Dunkerque, France > =========================================================================== > _______________________________________________ > Latex2rtf-users mailing list > Latex2rtf-users@... > https://lists.sourceforge.net/lists/listinfo/latex2rtf-users > 
 [Latex2rtf-users] Bug From: Patrick Dupre - 2017-04-06 12:28:30 Hello, I am use latex2rtf 2.3.13 r1248 (released Mar 22 2017) on a fedora 24 The code fails when I try to generate a rtf file \documentclass[10pt,american]{revtex4-1} \usepackage[T1]{fontenc} \usepackage[latin9]{inputenc} \usepackage[a4paper]{geometry} \usepackage{babel} \pagestyle{plain} \begin{document} \section{Introduction} In a $${\rm d}\bm{\alpha}_{m_{u}m_{l}}\left(\omega,\delta,r\right)=\frac{\frac{{\rm d}}{{\rm d}z}\left[{\rm i}\int\left[\omega\,{\rm d}\bm{P}_{m_{u}m_{l}}^{*}\left(\omega,\delta,r,z\right)\right]\otimes\bm{E}\left(\omega,r,z\right)\,{\rm d}V\right]}{c\epsilon_{0}\int\int\bm{E}^{*}\left(\omega,r,z\right)\otimes\bm{E}\left(\omega,r,z\right)\,{\rm d}S\,{\rm d}\omega},%\label{eq:alpha_cmpx}$$ \subsection{Liouville Equation} When \end{document} =========================================================================== Patrick DUPRÉ | | email: pdupre@... Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France =========================================================================== 
 Re: [Latex2rtf-users] Installing LaTeX2rtf (Unix/Mac) From: S.N. - 2017-01-20 09:35:53 Attachments: Message as HTML Thanks indeed for that detailed, and very generous, reply. Steve >> [S. Noble] >> >> This is a question from a Unix novice. I've searched for clarification but found precious little. > > I'll try to help. I'm not a Unix expert, so hopefully what I say will > be less cryptic than what an expert would say. > >> Would anyone be able and willing to post a detailed explanation of how to install LaTeX2rtf on the MAC (10.7 Lion & 10.11 El Cap.)? I use TeX and need to collaborate with people who want RTF files. >> >> I've read closely the instructions in the LaTeX2rtf manual, but, my apologies, I'm a Unix novice and much of the instructions are just not that easy to follow. > >> I know I have to install the developer tools, but after that the procedure gets cloudy. >> >> For example, §2.3.1 of the manual reads as follows: >> "1. Edit Makefile for your local configuration. In particular, pay attention to the PREFIX variable. If you do not have root access you might wish to set the makefile variable PREFIX to be your home directory.  On some machines the cc compiler will issue errors. Therefore the default compiler command in the Makefile is CC=gcc". > >> First of all, what does "Edit Makefile for your local configuration" actually mean, or, in other words, how do you do this? > > A brief description of the 'make' program: 'make' is the principle > tool for defining and building software packages in Unix. When you > run 'make' (at the command line, or in a shell, as we say in > Unix-land), what actually happens is governed by a file normally > called 'Makefile' (no extension). This file contains a set of "goal > definitions," which gives a set of shell commands for (re)building a > piece of a software package; plus a set of subgoals. All 'make G' > does is look up G in the Makefile, first recursively achieve all its > subgoals, then follow the commands defining G. The normal case is > that these commands compile and combine various C programs, but they > can do anything at all. For instance, by convention 'make clean' just > deletes a lot of files. (Sometimes it uninstalls the application, but > sometimes it means "delete files generated along the way that are no > longer useful and have become clutter.") > > Okay, to edit the Makefile it is important to use a text editor, NOT a > word processor. You want to see the chracters in a "naked" text file, > with no formatting commands of any kind. You can use 'emacs', 'vi', > 'vim', or 'Textedit' (but make sure you set Textedit to edit plain > text, not Rich Text), or any of hundreds of other editors. > >> Secondly, what edits do you actually have to make to Makefile? Thirdly, what is the "PREFIX variable"? > > Variables are used in a Makefile so the same strings don't have to be > typed repeatedly. This makes it easy to change program versions, > directory locations, command-line options, or any other string. I'm > looking at the Makefile for latex2rtf-2.3.12. The first line is > > CC?=gcc > > which means "set the variable CC to 'gcc' if it isn't set to something > else (usually in your .profile or .bash_profile file)." Variables are > uppercase, and behave like regular shell variables. > > The first goal where CC occurs is latex2rtf, defined thus: > > latex2rtf: $(OBJS)$(HDRS) > $(CC)$(CFLAGS) $(LDFLAGS)$(OBJS) $(LIBS) -o$(BINARY_NAME) > > The first line gives all the subgoals, after a colon. These are the > files that are the values of the OBJS variable and the HDRS variable. > > The next line says "Call the compiler (CC) with options given by the > FLAGS variables, output file given by the BINARY_NAME variable, > etc. etc. The default compiler will be 'gcc', because the CC variable > is set to 'gcc'. > > What's crazy is that there is no PREFIX variable! It looks to me like > someone decided DESTDIR was a much more mnemonic name, and changed > every occurrence of PREFIX to DESTDIR. Sure enough, in the Changelog > it says "Change PREFIX to DESTDIR to follow the GNU standard". > Unfortunately, they didn't change the README file. You have to be > forgiving to deal with open-source software. > > Okay, so let's pretend they did make that change, so that the README > file said "If you do not have root access you might need to set > DESTDIR ...". (If you have an old enough distribution, you'll stick > with PREFIX.) The relevant line of the Makefile is > > DESTDIR?=/usr/local > > If you install compiled files there, then all users will profit from > your action. (Check to make sure no one has already done this; if > they have, and if make sure '/usr/local' is in your PATH, then you > don't need to install Latex2rtf, unless you're installing a later > version.) > > Let me explain that parenthesis a bit more. You can check the value > of PATH by executing > > echo $PATH > > This will print out the value of PATH, which should be a list of > directories separated by colons. E.g., when I do this I see a long > string that includes this substring: > > ...:/opt/local/bin:/usr/local/bin:/Applications/scala/bin:... > > meaning that when I execute a Unix command, if it starts with the name > of a program, that program will be searched for in all these > directories. /usr/local/bin will be searched after /opt/local/bin and > before /Applications/scala/bin . The order usually reflect the > vagaries of how the (code setting the) PATH variable has been modified > over the years, and is usually irrelevant, because the program will be > found in at most one of these directories. (E.g., 'scalac' is found in > /Applications/scala/bin and nowhere else.) > > If /usr/local is not in your PATH, and you want it to be, add the line > > export PATH=/usr/local/bin:$PATH > > to your .bash_profile file, assuming you use the 'bash' shell. (The > instructions are slightly different for the C shell and other shells. > These initializations files are executed when you create a shell; they > are ordinary shell scripts. The details of exactly which > initialization file is run when are intricate and painful to read > about, which is why the PATH variable is often set more than once and > contains duplicate occurrences of many directory names.) > > The only problem with using /usr/local as your DESTDIR is that > ordinary users do not have write access to it. You can get around > this by using the 'sudo' program, but that's not always available. > Ask your local system administrator (who may volunteer to install > latex2rtf for you, which will solve all your problems). If it's a > computer you own all by yourself, then you _are_ the system > administrator, and you _do_ have access to all the directories, at > least if you log in as root, which you normally wouldn't do, but > installing software, at least the 'make install' step, might be an > exception. > > The other way to get around the access problem is to install latex2rtf > in a directory you do control. You can create a directory 'software' > in your home directory, /Users/noble, say. Then in the Makefile you > would edit the DESTDIR line to: > > DESTDIR?=/Users/noble/software > > (Make sure /Users/noble/software is in your PATH. Left as an > exercise.) The latext2rtf goal compiles the entire program (most of > which has been compiled in the course of achieving subgoals). It puts > the resulting executable file (named simply 'latex2rtf' in Unix) in > the same directory as the Makefile. 'make install' moves the > executable to $DESTDIR. If you don't have write permission in that > directory, the goal will fail. (Unix programs return an integer > corresponding to how they fail. There's only one success value: 0. > Any other value describes some error condition. As Tolstoy said, "All > successful programs are alike, every unsuccessful programs is > unsuccessful in its own way.") > >> I gather that, in Terminal, you then have to type "make", then "make install" then "make check" and "make install -info" (§2.3.3--§2.3.6). So do you just type the first command on a Terminal line, press return, then the second, and so on, or should the commands "make" etc. be followed by something else? I know how to use Terminal, but I'm not familiar with installing software from source. > > You guessed right. However, if any step failed, there's no point in > continuing with the sequence, because, if the Makefile is designed > appropriately, every followup goal will have an unachieved subgoal if > the step designed to achieve that subgoal failed. > > I hope this was the right amount and kind of information. > > -- Drew McDermott > Professor of Computer Science > Yale Computer Science Department  Re: [Latex2rtf-users] Installing LaTeX2rtf (Unix/Mac) From: Drew McDermott - 2017-01-18 05:39:16 > [S. Noble] > > This is a question from a Unix novice. I've searched for clarification but found precious little. I'll try to help. I'm not a Unix expert, so hopefully what I say will be less cryptic than what an expert would say. > Would anyone be able and willing to post a detailed explanation of how to install LaTeX2rtf on the MAC (10.7 Lion & 10.11 El Cap.)? I use TeX and need to collaborate with people who want RTF files. > > I've read closely the instructions in the LaTeX2rtf manual, but, my apologies, I'm a Unix novice and much of the instructions are just not that easy to follow. > > I know I have to install the developer tools, but after that the procedure gets cloudy. > > For example, §2.3.1 of the manual reads as follows: > "1. Edit Makefile for your local configuration. In particular, pay attention to the PREFIX variable. If you do not have root access you might wish to set the makefile variable PREFIX to be your home directory. On some machines the cc compiler will issue errors. Therefore the default compiler command in the Makefile is CC=gcc". > First of all, what does "Edit Makefile for your local configuration" actually mean, or, in other words, how do you do this? A brief description of the 'make' program: 'make' is the principle tool for defining and building software packages in Unix. When you run 'make' (at the command line, or in a shell, as we say in Unix-land), what actually happens is governed by a file normally called 'Makefile' (no extension). This file contains a set of "goal definitions," which gives a set of shell commands for (re)building a piece of a software package; plus a set of subgoals. All 'make G' does is look up G in the Makefile, first recursively achieve all its subgoals, then follow the commands defining G. The normal case is that these commands compile and combine various C programs, but they can do anything at all. For instance, by convention 'make clean' just deletes a lot of files. (Sometimes it uninstalls the application, but sometimes it means "delete files generated along the way that are no longer useful and have become clutter.") Okay, to edit the Makefile it is important to use a text editor, NOT a word processor. You want to see the chracters in a "naked" text file, with no formatting commands of any kind. You can use 'emacs', 'vi', 'vim', or 'Textedit' (but make sure you set Textedit to edit plain text, not Rich Text), or any of hundreds of other editors. > Secondly, what edits do you actually have to make to Makefile? Thirdly, what is the "PREFIX variable"? Variables are used in a Makefile so the same strings don't have to be typed repeatedly. This makes it easy to change program versions, directory locations, command-line options, or any other string. I'm looking at the Makefile for latex2rtf-2.3.12. The first line is CC?=gcc which means "set the variable CC to 'gcc' if it isn't set to something else (usually in your .profile or .bash_profile file)." Variables are uppercase, and behave like regular shell variables. The first goal where CC occurs is latex2rtf, defined thus: latex2rtf:$(OBJS) $(HDRS)$(CC) $(CFLAGS)$(LDFLAGS) $(OBJS)$(LIBS) -o $(BINARY_NAME) The first line gives all the subgoals, after a colon. These are the files that are the values of the OBJS variable and the HDRS variable. The next line says "Call the compiler (CC) with options given by the FLAGS variables, output file given by the BINARY_NAME variable, etc. etc. The default compiler will be 'gcc', because the CC variable is set to 'gcc'. What's crazy is that there is no PREFIX variable! It looks to me like someone decided DESTDIR was a much more mnemonic name, and changed every occurrence of PREFIX to DESTDIR. Sure enough, in the Changelog it says "Change PREFIX to DESTDIR to follow the GNU standard". Unfortunately, they didn't change the README file. You have to be forgiving to deal with open-source software. Okay, so let's pretend they did make that change, so that the README file said "If you do not have root access you might need to set DESTDIR ...". (If you have an old enough distribution, you'll stick with PREFIX.) The relevant line of the Makefile is DESTDIR?=/usr/local If you install compiled files there, then all users will profit from your action. (Check to make sure no one has already done this; if they have, and if make sure '/usr/local' is in your PATH, then you don't need to install Latex2rtf, unless you're installing a later version.) Let me explain that parenthesis a bit more. You can check the value of PATH by executing echo$PATH This will print out the value of PATH, which should be a list of directories separated by colons. E.g., when I do this I see a long string that includes this substring: ...:/opt/local/bin:/usr/local/bin:/Applications/scala/bin:... meaning that when I execute a Unix command, if it starts with the name of a program, that program will be searched for in all these directories. /usr/local/bin will be searched after /opt/local/bin and before /Applications/scala/bin . The order usually reflect the vagaries of how the (code setting the) PATH variable has been modified over the years, and is usually irrelevant, because the program will be found in at most one of these directories. (E.g., 'scalac' is found in /Applications/scala/bin and nowhere else.) If /usr/local is not in your PATH, and you want it to be, add the line export PATH=/usr/local/bin:$PATH to your .bash_profile file, assuming you use the 'bash' shell. (The instructions are slightly different for the C shell and other shells. These initializations files are executed when you create a shell; they are ordinary shell scripts. The details of exactly which initialization file is run when are intricate and painful to read about, which is why the PATH variable is often set more than once and contains duplicate occurrences of many directory names.) The only problem with using /usr/local as your DESTDIR is that ordinary users do not have write access to it. You can get around this by using the 'sudo' program, but that's not always available. Ask your local system administrator (who may volunteer to install latex2rtf for you, which will solve all your problems). If it's a computer you own all by yourself, then you _are_ the system administrator, and you _do_ have access to all the directories, at least if you log in as root, which you normally wouldn't do, but installing software, at least the 'make install' step, might be an exception. The other way to get around the access problem is to install latex2rtf in a directory you do control. You can create a directory 'software' in your home directory, /Users/noble, say. Then in the Makefile you would edit the DESTDIR line to: DESTDIR?=/Users/noble/software (Make sure /Users/noble/software is in your PATH. Left as an exercise.) The latext2rtf goal compiles the entire program (most of which has been compiled in the course of achieving subgoals). It puts the resulting executable file (named simply 'latex2rtf' in Unix) in the same directory as the Makefile. 'make install' moves the executable to$DESTDIR. If you don't have write permission in that directory, the goal will fail. (Unix programs return an integer corresponding to how they fail. There's only one success value: 0. Any other value describes some error condition. As Tolstoy said, "All successful programs are alike, every unsuccessful programs is unsuccessful in its own way.") > I gather that, in Terminal, you then have to type "make", then "make install" then "make check" and "make install -info" (§2.3.3--§2.3.6). So do you just type the first command on a Terminal line, press return, then the second, and so on, or should the commands "make" etc. be followed by something else? I know how to use Terminal, but I'm not familiar with installing software from source. You guessed right. However, if any step failed, there's no point in continuing with the sequence, because, if the Makefile is designed appropriately, every followup goal will have an unachieved subgoal if the step designed to achieve that subgoal failed. I hope this was the right amount and kind of information. -- Drew McDermott Professor of Computer Science Yale Computer Science Department 
 [Latex2rtf-users] Installing LaTeX2rtf (Unix/Mac) From: S. Noble - 2017-01-16 14:50:58 Hello, This is a question from a Unix novice. I've searched for clarification but found precious little. Would anyone be able and willing to post a detailed explanation of how to install LaTeX2rtf on the MAC (10.7 Lion & 10.11 El Cap.)? I use TeX and need to collaborate with people who want RTF files. I've read closely the instructions in the LaTeX2rtf manual, but, my apologies, I'm a Unix novice and much of the instructions are just not that easy to follow. I know I have to install the developer tools, but after that the procedure gets cloudy. For example, §2.3.1 of the manual reads as follows: "1. Edit Makefile for your local configuration. In particular, pay attention to the PREFIX variable. If you do not have root access you might wish to set the makefile variable PREFIX to be your home directory.  On some machines the cc compiler will issue errors. Therefore the default compiler command in the Makefile is CC=gcc". First of all, what does "Edit Makefile for your local configuration" actually mean, or, in other words, how do you do this? Secondly, what edits do you actually have to make to Makefile? Thirdly, what is the "PREFIX variable"? I gather that, in Terminal, you then have to type "make", then "make install" then "make check" and "make install -info" (§2.3.3--§2.3.6). So do you just type the first command on a Terminal line, press return, then the second, and so on, or should the commands "make" etc. be followed by something else? I know how to use Terminal, but I'm not familiar with installing software from source. Thanks in advance for any clarification anyone might be able to provide. Steve 
 Re: [Latex2rtf-users] latex2rtf error From: Wilfried Hennings - 2017-01-13 09:52:32 Hello Arthur, thanks for the investigation. It seems you are right. If I open the file selection dialogue for the rtf file by clicking on "...", the pre-filled file-ID has the .tex extension, not the .rtf extension. I am no C++ expert, but at a look into the source code of the latex2rtf gui shell it seems to me that the handling of the "..." buttons is not correct. I will test my fix as soon as possible. Furthermore, the latex2rtf converter should not open the same (.tex) file for writing if it is already opened for reading. I will try to fix this, too. Regards Wilfried At 13.01.2017 03:52, Bass, Arthur wrote: > Hello, > > Just now subscribed to the list. > > I just had the exact same experience as Eric Doherty who posted on Nov > 2, 2016. Here is his post: > > latex2rtf support > > I have received this message > > Error! end of file reached before '\begin|{|document|}' was found > > and now the whole file is wiped. Like gone. 0 kB, no text, nothing. > > How do I recover it and what happened?!?!?!?!? > > My tex file has been wiped, 0 kb, absolutely nothing in it. I got the > exact same error message. I know for a fact that the file was there > because I had just compiled it in texniccenter from the location where > LaTeX2RTF was looking for it. Furthermore, I had successfully converted > it to RTF on multiple previous occassions. I am using version 2.3.11 on > Windows 10. > > I believe I know what happened, although not exactly why it happened. I > wanted to save the RTF file in another folder (not the one the latex > files are in). I clicked the "..." toggle to the right of the "RTF > file:" pane and navigated to the location where I intended to save the > file as an RTF. However, upon re-examination of the "RTF file:" pane, > the intended file name in the pane is the name of my tex file > (myfile.tex) and the location is the folder that all the latex files are > in! So I overwrote the tex file with what the product of the conversion > was supposed to be (if that makes sense). > > Upon further investigation, this appears to be a problem with how the > RTF file pane responds to being changed by selecting a destination > folder. Often times when you go to a destination folder and enter a file > name, it still reverts to the source folder and enters the myfile.tex > name into the pane. Strange behavior. I tried opening and closing > latex2rtf a few times and it continued to do this. > > Now all I have on my computer (which backs up to the OneDrive cloud) is > the most recent pdf that I compiled in texniccenter. I am hoping I can > access an older version of the tex file on a computer at home that is > not connected to the cloud at the moment - but unfortunately that will > entail redoing a lot of revisions that I have made recently. Hopefully > that works though, because otherwise that is a LOT of work right out the > window (including some ridiculously large tables). > > If you have any suggestions, I'm all ears. But I suspect that it is > gone. Since this looks to be a re-occurring phenomenon, it might be > worthwhile for people to create a duplicate of their latex files in a > safe place before trying to use LaTex2RTF. As I mentioned, I have had no > problems before and have good success with LaTex2RTF until now. > > Thanks, > Art > > > ------------------------------------------------------------------------------ > Developer Access Program for Intel Xeon Phi Processors > Access to Intel Xeon Phi processor-based developer platforms. > With one year of Intel Parallel Studio XE. > Training and support from Colfax. > Order your platform today. http://sdm.link/xeonphi > > > > _______________________________________________ > Latex2rtf-users mailing list > Latex2rtf-users@... > https://lists.sourceforge.net/lists/listinfo/latex2rtf-users > 
 [Latex2rtf-users] latex2rtf error From: Bass, Arthur - 2017-01-13 03:14:48 Attachments: Message as HTML Hello, Just now subscribed to the list. I just had the exact same experience as Eric Doherty who posted on Nov 2, 2016. Here is his post: latex2rtf support I have received this message Error! end of file reached before '\begin|{|document|}' was found and now the whole file is wiped. Like gone. 0 kB, no text, nothing. How do I recover it and what happened?!?!?!?!? My tex file has been wiped, 0 kb, absolutely nothing in it. I got the exact same error message. I know for a fact that the file was there because I had just compiled it in texniccenter from the location where LaTeX2RTF was looking for it. Furthermore, I had successfully converted it to RTF on multiple previous occassions. I am using version 2.3.11 on Windows 10. I believe I know what happened, although not exactly why it happened. I wanted to save the RTF file in another folder (not the one the latex files are in). I clicked the "..." toggle to the right of the "RTF file:" pane and navigated to the location where I intended to save the file as an RTF. However, upon re-examination of the "RTF file:" pane, the intended file name in the pane is the name of my tex file (myfile.tex) and the location is the folder that all the latex files are in! So I overwrote the tex file with what the product of the conversion was supposed to be (if that makes sense). Upon further investigation, this appears to be a problem with how the RTF file pane responds to being changed by selecting a destination folder. Often times when you go to a destination folder and enter a file name, it still reverts to the source folder and enters the myfile.tex name into the pane. Strange behavior. I tried opening and closing latex2rtf a few times and it continued to do this. Now all I have on my computer (which backs up to the OneDrive cloud) is the most recent pdf that I compiled in texniccenter. I am hoping I can access an older version of the tex file on a computer at home that is not connected to the cloud at the moment - but unfortunately that will entail redoing a lot of revisions that I have made recently. Hopefully that works though, because otherwise that is a LOT of work right out the window (including some ridiculously large tables). If you have any suggestions, I'm all ears. But I suspect that it is gone. Since this looks to be a re-occurring phenomenon, it might be worthwhile for people to create a duplicate of their latex files in a safe place before trying to use LaTex2RTF. As I mentioned, I have had no problems before and have good success with LaTex2RTF until now. Thanks, Art 
 Re: [Latex2rtf-users] cannot run command line in windows 10 From: Wilfried Hennings - 2016-11-07 20:16:17 At 07.11.2016 17:37, Jay A. Leavitt, PhD, wrote: > rtf2latex2e is installed in folder in Program Files (x86). When cmd > run in that directory getting this error. > Cannot find the rtf2latex2e support file 'rtf-encoding.cp1250' > > The default install location for these files is > /usr/local/share/rtf2latex2e/ > When this program was compiled the location was > C:/PROGRA~1/rtf2latex2e/pref > > After locating the proper directory you can > (1) define the environment variable \$RTFPATH, *or* > (2) use command line path option '-P /path/to/prefs' *or* > (3) recompile rtf2latex2e (after modifying datadir in Makefile) > Giving up. Please don't hate me. The compiled-in path is "C:/PROGRA~1/rtf2latex2e/pref" which would be OK for Windows 32 bit, but you seem to have Windows 64 bit. So you need to specify the path where the support files are, either by defining the environment variable with the command: SET RTFPATH="C:/Program Files (x86)/rtf2latex2e/pref" or by specifying it in the call: rtf2latex2e -P "C:/Program Files (x86)/rtf2latex2e/pref" conv.rtf But you should not normally run programs in admin mode. Put the file to be converted in a user data folder, then call the program like this: "C:/Program Files (x86)/rtf2latex2e/rtf2latex2e" -P "C:/Program Files (x86)/rtf2latex2e/pref" conv.rtf One problem is that the path contains blanks. When the path contains no blanks, the quotes can be omitted. Maybe the following would be better: C:/PROGRA~2/rtf2latex2e/rtf2latex2e -P C:/PROGRA~2/rtf2latex2e/pref conv.rtf Hope this helps Wilfried 
 [Latex2rtf-users] cannot run command line in windows 10 From: Jay A. Leavitt, PhD - 2016-11-07 16:37:40 Attachments: text/plain > rtf2latex2e is installed in folder in Program Files (x86). When cmd > run in that directory getting this error. 
 [Latex2rtf-users] cannot run command line in windows 10 From: Jay A. Leavitt, PhD - 2016-11-07 16:20:11 Attachments: text/plain rtf2latex2e is installed in folder in Program Files (x86). When cmd run in that directory getting this error. 
 Re: [Latex2rtf-users] Support From: Wilfried Hennings - 2016-11-03 10:42:01 At 02.11.2016 19:48 Eric Doherty wrote: > latex2rtf support This is a misconception: There is no official support. However in this mailing list, volunteers try to help. Moreover, to post to the mailing list and to receive replies, you have first to subscribe to the list. > > I have received this message > > Error! end of file reached before '\begin|{|document|}' was found > > and now the whole file is wiped. Like gone. 0 kB, no text, nothing. > > How do I recover it and what happened?!?!?!?!? 1. Before being able to figure out what has happened, we need to know - the operating system on which you run latex2rtf (MS Windows? Apple? Unix? Which version?) - the latex2rtf version - how latex2rtf was invoked 2. Most probably latex2rtf did not do anything to your file. I guess the file is not at the location which latex2rtf was told it were, so an empty file was created when latex2rtf tried to read it. Wilfried 
 [Latex2rtf-users] Support From: eric doherty - 2016-11-02 18:48:53 Attachments: Message as HTML latex2rtf support I have received this message Error! end of file reached before '\begin|{|document|}' was found and now the whole file is wiped. Like gone. 0 kB, no text, nothing. How do I recover it and what happened?!?!?!?!? 
 Re: [Latex2rtf-users] how to proceed? From: Wilfried Hennings - 2016-07-14 08:30:14 At 12.07.2016 12:09, Manuel Ortigueira wrote: > I would like to install the latex2rtf converter, but I'm not an > expert in informatics. I use regularly texstudio and I need to > convert a paper into a given format stated in word. > I do not know how to install the converter. Can you help me? That depends on the operating system (Windows / Linux / OSX) in which you want to install it. But the latex2rtf converter will not take care of the requested format but convert your LaTeX document as is, or - if your document uses LaTeX packages which are not supported by the converter - may fail to convert most or all of your document. Therefore, if you are "not an expert in informatics" and you have to convert just one document, I recommend doing this by copying and pasting the text from the LaTeX document into the given Word template. If you don't have Microsoft Word / Microsoft Office, you can use LibreOffice instead. Wilfried 
 [Latex2rtf-users] how to proceed? From: Manuel Ortigueira - 2016-07-12 10:35:43 Dear colleagues I would like to install the latex2rtf converter, but I'm not an expert in informatics. I use regularly texstudio and I need to convert a paper into a given format stated in word. I do not know how to install the converter. Can you help me? Sincerely M. Ortigueira -- ---------------------------------------------------------------------------------------- Este e-mail foi escrito com intencional desrespeito pelo famigerado Acordo Ortográfico! ---------------------------------------------------------------------------------------- Manuel Duarte Ortigueira UNINOVA and DEE/ Faculdade de Ciências e Tecnologia da UNL Campus da FCT Quinta da Torre 2829-516 Caparica Portugal Tel. +351 212948520 extº 11943 Mob. Phone +351 938610658 Fax. +351 212948532 and +351 212947786 http://http://docentes.fct.unl.pt/mdo XXmdo@... 
 Re: [Latex2rtf-users] latex2rtf segmentation fault when equation is transformed into bitmap From: Ronan Arraes Jardim Chagas - 2016-06-02 17:13:19 Wilfried, We have a memory leak in abbreviate function! I could fix the problem by changing:     t = (char *) malloc(len * sizeof(char)); to     t = (char *) malloc((len+1) * sizeof(char)); Notice that in the last for (graphics.c:1895), the last parameter written is:     t[half + 6 + half] Since:     half = (len - 6)/2; and len = 50, then half = 22. Therefore, we are writing to t[50], or the 51st term. However, the malloc allocates only 50 terms, which leaded to the problem. I will submit a patch to the openSUSE package. Can you explain me how can I also send the patch to the official latex2rtf tree? Regards, Ronan Arraes 

Showing results of 304

1 2 3 .. 13 > >> (Page 1 of 13)