latex2rtf-1.9.16a_win.exe
"Pavel Chebotarev" <[email protected]> Wed, 2 Mar 2005 15:08:02 +0300
| Newsgroups | gmane.comp.tex.latex.latex2rtf.devel |
|---|---|
| Message-ID | <004501c51f20$7fdd6f00$840ba8c0@ics65f20bc4861> |
This is a multi-part message in MIME format.
------=_NextPart_000_0042_01C51F39.A0CF1510
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Yesterday I downloaded latex2rtf-1.9.16a_win.exe .
It is a nice converter!
However, I encountered some problems, which are listed below.
My system is Windows2000 and I have MSOffice2000.
1. The major problem. When I double-click on an RTF equation field in =
order to improve it by transforming to an MS-Equation object, the font =
information is ignored, so the Greek letters (of the symbol font) =
become Latin ones: \alpha becomes a, and so on. =20
Experimenting with it, I tried to put a symbol field into the equation =
field, because symbol fields enable one to indicate the font explicitly =
by "\f symbol" key, but the Equation Editor simply ignores all symbol =
fields within equation fields. =20
Similarly, the symbols such as =E2=88=9E,=E2=89=88,=E2=89=A0,=E2=88=99 =
and so on are also transformed into completely different symbols.
2. It is not good that simple formulae like x=3Dy+z do not receive the =
RTF equation field form unlike more complex formulae. I think so, =
because the use of the Equation Editor might give them a better =
formatting/spacing such as x =3D y + z .=20
3. I think, it is not good that the Greek letters are not italicized in =
the formulae, because x =3D =CE=B2 + =CE=B4 would have been better =
than x=3D=CE=B2+=CE=B4.
4. Pre-defined (in the preamble) LaTeX macros such as=20
\def\a{\alpha}
worked fine in some formulae but did not work in some other ones.
5. The Bitmap format worked good for "displayed equations" but did not =
work at all for "inline equations".
With best regards,
Yours sincerely,
-------------------------------------------------------------------------=
--------------
Dr. Pavel Chebotarev
Russian Academy of Sciences: Institute of Control Sciences=20
65 Profsoyuznaya Street, Moscow 117997, Russia
Phone: +7-095-334-8869 Fax: +7-095-420-2016
E-mail: [email protected]; [email protected]
-------------------------------------------------------------------------=
--------------
------=_NextPart_000_0042_01C51F39.A0CF1510
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8">
<META content=3D"MSHTML 6.00.2800.1491" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>Yesterday I downloaded <U>latex2rtf-1.9.16a_win.exe=20
.</U></FONT></DIV>
<DIV><FONT size=3D2>It is a nice converter!</FONT></DIV>
<DIV><FONT size=3D2>However, I encountered some problems, which are =
listed=20
below.</FONT></DIV>
<DIV><FONT size=3D2>My system is Windows2000 and I have =
MSOffice2000.</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>1. The major problem. When I double-click on an RTF =
equation=20
field in order to improve it by transforming to an MS-Equation object, =
the font=20
information is ignored, </FONT><FONT size=3D2>so the Greek letters (of=20
the <EM>symbol </EM> font) become Latin ones: \alpha =
becomes=20
<FONT face=3D"Times New Roman" size=3D3><EM><FONT =
size=3D4>a</FONT></EM>,</FONT>=20
</FONT><FONT size=3D2>and so on. </FONT></DIV>
<DIV><FONT size=3D2>Experimenting with it, I tried to put a <U>symbol =
field</U>=20
into the <U>equation field</U>, because symbol fields enable one to =
indicate the=20
font explicitly by <FONT face=3D"Times New Roman" size=3D3>"</FONT><SPAN =
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA">\f=20
symbol" <FONT face=3DArial size=3D2>key,</FONT></SPAN> but the =
Equation Editor=20
simply ignores all <U>symbol fields</U><EM> </EM>within <U>equation =
fields</U>. </FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>Similarly, the symbols such as <SPAN=20
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; =
mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA">=E2=88=9E,=E2=89=88,=E2=89=A0,=E2=88=99</SPAN> and=20
so on are also transformed into completely different =
symbols.</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>2. It is not good that simple formulae like =20
<EM>x</EM>=3D<EM>y</EM><FONT face=3DArial><SPAN=20
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; =
mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA">+<EM>z</EM></SPAN> =20
</FONT></FONT><FONT size=3D3>do not receive the RTF <U>equation =
field</U>=20
form unlike more complex formulae. I think so, because the use of the =
Equation=20
Editor might give them a better formatting/spacing such as <FONT =
size=3D2><EM>x=20
</EM>=3D <EM>y </EM></FONT><FONT face=3DArial><SPAN=20
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA">+=20
<EM>z .</EM></SPAN></FONT> </FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>3. I think, it is not good that the Greek letters =
are not=20
italicized in the formulae, because <EM>x </EM>=3D <FONT =
face=3DArial><SPAN=20
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><EM>=CE=B2=20
+ </EM><SPAN=20
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><EM>=CE=B4 =20
</EM><FONT face=3DArial size=3D2>would have been better than</FONT> =
</SPAN></SPAN></FONT></FONT><FONT size=3D2><EM>x</EM>=3D<SPAN=20
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA">=CE=B2+<SPAN=20
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; =
mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA">=CE=B4</SPAN></SPAN></FONT><FONT=20
face=3DArial><SPAN=20
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; =
mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA">.</SPAN></FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>4. Pre-defined (in the preamble) LaTeX macros =
such as=20
</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2>\def\a{\alpha}</FONT></DIV>
<DIV><FONT size=3D2>worked fine in some formulae but did not work in =
some other=20
ones.</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>5. The Bitmap format worked good for "displayed =
equations" but=20
did not work at all for "inline equations".</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>With best regards,</FONT></DIV>
<DIV><FONT size=3D2>Yours sincerely,</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT=20
size=3D2>----------------------------------------------------------------=
-----------------------<BR>Dr.=20
Pavel Chebotarev</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>Russian Academy of Sciences: Institute of Control =
Sciences=20
<BR>65 Profsoyuznaya Street, Moscow 117997, Russia<BR>Phone:=20
+7-095-334-8869 Fax: +7-095-420-2016<BR>E-mail: <A=20
href=3D"mailto:[email protected]">[email protected]</A>; <A=20
href=3D"mailto:[email protected]">[email protected]</A><BR>----------------------------=
-----------------------------------------------------------</FONT></DIV><=
/BODY></HTML>
------=_NextPart_000_0042_01C51F39.A0CF1510--
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click