<div dir="ltr">Thank you! From my perspective, this is nothing short of miraculous, and I wish I had consulted you back when I converted my article to .doc format! It would have saved me much work and countless errors.<div>
<br></div><div>Based on what you have sent me, I have been able to convert longer documents. This convinces me that I will be able to compose in the TeX world and still speak to the Word world. I only have a few small questions as to how I can develop a workflow which smooths out this communication even further.</div>
<div><br></div><div><div><u>Current workflow</u></div><div>1. paste all tex into word.converter.tex</div><div>2. run CVR’s perl script: perl <a href="http://utf2ent.pl">utf2ent.pl</a> word.converter.tex > word.converter-ent.tex</div>
<div>3. run SimpleTeX4ht (ODT option) on word.converter-ent.tex</div><div>4. biber word.converter-ent</div><div>5. run SimpleTeX4ht (ODT option) on word.converter-ent.tex (again)</div><div>6. open word.converter-ent.odt in OpenOffice</div>
<div>7. Save As *word.converter-ent.doc*, which is the final result</div></div><div><br></div><div style><u>Remaining issue</u></div><div style><br></div><div style>Unicode in my BibTeX entries: while Unicode in my main text and footnotes now shows up perfectly, the Unicode characters in my BibTeX entries still don't make it through. (step 4) Is there a way to get this Unicode to make it as well without modifying my .bib file?<br>
</div><div style><br></div><div style><u>Two additional minor issues of convenience</u></div><div style><br></div><div style>1. Since my goal is to produce Word documents from my tex source, I would like tex4ht to produce ODT documents rather than HTML. Right now I have managed to do this with SimpleTeX4ht (steps 3 and 5); is there a simpler way to do this from the command-line using htlatex?</div>
<div style><br></div><div style>2. Is there a way to automate step 1? I am writing various sections of my chapter in different tex files and then use \input{} in the tex file which I compile. I imagine it must be straightforward to have the perl script begin by replacing each "\input{file}" with the contents of "file.tex" in the output, but I don't know how to do that.<br>
</div><div><div><br></div><div><br></div><div style>I would again be most grateful for your help on this matter as well. I have attached a sample of what my ordinary xelatex output looks like (sample-xelatex.pdf), as well as the same code converted to Word format using my revision of your workflow (word.converter-ent.x). I also included a bib file with the entries I cite in my sample (mn.bib).</div>
<div style><br></div><div style>Best wishes,</div><div style>Alex</div>
</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Feb 17, 2013 at 9:41 PM, Radhakrishnan CV <span dir="ltr"><<a href="mailto:cvr@river-valley.org" target="_blank">cvr@river-valley.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Sun, Feb 17, 2013 at 4:25 AM, Alexandre Roberts <span dir="ltr"><<a href="mailto:alexandre.roberts@gmail.com" target="_blank">alexandre.roberts@gmail.com</a>></span> wrote:<br>
</div><div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Dear tex4ht list members,<div><br></div><div>I am about to begin drafting the first chapter of my dissertation in Byzantine and Middle Eastern history. This is the moment when I will commit to the format I will use for writing my entire dissertation. I want it to be XeLaTeX/BibLaTeX, but unless I can come up with a simple workflow for converting the content of my documents to Word format -- the only format that publishers in my field accept -- I will have to give this up and turn to Word/Endnote or Mellel/Bookends for the next three years.</div>
</div></blockquote></div><div><br>As far as I understand, TeX4ht won't support fontspec or XeLaTeX technologies of using system fonts that do not have *.tfm's. In effect, by adopting TeX4ht, one is likely to loose the features brought in by XeTeX. However, here is another approach.<br>
<ol><li>We translate all the Unicode character representations in the document to Unicode code points in 7bit ascii which is very much palatable to TeX4ht. A simple perl script, <a href="http://etf2ent.pl" target="_blank">etf2ent.pl</a> in the attached archive does the job.</li>
<li>We run TeX4ht on the output of step 1.</li><li>Open the *html in a browser, I believe, we get what you wanted. See the attached screen shot as it appeared in Firefox in my Linux box.<br></li></ol>Here is what I did with your specimen document.<br>
<ol><li>commented out lines that related to fontspec package from your sources named as alex.tex. <br></li><li>added four lines of macro code to digest the converted TeX sources</li><li>ran the command: perl <a href="http://utf2ent.pl" target="_blank">utf2ent.pl</a> alex.tex > alex-ent.tex <br>
</li><li>ran the command: htlatex alex-ent "xhtml,charset=utf-8,fn-in" -utf8 (fn-in option is to keep the footnotes in the same document). I have used a local bib file, mn.bib as I didn't have your bib database. biber was also run in the meantime to process the bibliography database.<br>
</li><li>open the output, alex-ent.html in a browser. I got it as you see in the attached alex.png.</li></ol><p>Hope this might help you.<br></p>Best regards<span class="HOEnZb"><font color="#888888"><br></font></span></div>
</div><span class="HOEnZb"><font color="#888888"><br>-- <br>Radhakrishnan<br><a href="https://maps.google.com/maps?q=River%20Valley,%20Thiruvananthapuram%20Neyyardam%20Road,%20Kerala,%20India&vector=1" target="_blank">River Valley</a><br>
<br>
</font></span></blockquote></div><br></div>