<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: xianye huang</title>
    <description>The latest articles on DEV Community by xianye huang (@xianye_huang_4becb58afe1a).</description>
    <link>https://dev.to/xianye_huang_4becb58afe1a</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4193899%2Fdd1d7896-6895-46f3-b2a6-91b34314f4d1.jpg</url>
      <title>DEV Community: xianye huang</title>
      <link>https://dev.to/xianye_huang_4becb58afe1a</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/xianye_huang_4becb58afe1a"/>
    <language>en</language>
    <item>
      <title>Why copying AI answers into Word still breaks (and how I built a client-side converter for LaTeX &amp; tables)</title>
      <dc:creator>xianye huang</dc:creator>
      <pubDate>Sun, 25 Oct 2026 03:07:33 +0000</pubDate>
      <link>https://dev.to/xianye_huang_4becb58afe1a/why-copying-ai-answers-into-word-still-breaks-and-how-i-built-a-client-side-converter-for-latex--445o</link>
      <guid>https://dev.to/xianye_huang_4becb58afe1a/why-copying-ai-answers-into-word-still-breaks-and-how-i-built-a-client-side-converter-for-latex--445o</guid>
      <description>&lt;p&gt;Aitoword at aitoword.online turns AI answers and Markdown into editable Word documents. Paste the source text, or import an .md or .txt file, check the preview, and download .docx. Supported equations become native Word equations, and basic Markdown tables become editable Word cells. This converter works from text and does not perform OCR on equation screenshots.&lt;/p&gt;

&lt;p&gt;I am the developer of &lt;a href="https://aitoword.online/en/" rel="noopener noreferrer"&gt;Aitoword&lt;/a&gt;. This is a description of the tool's current workflow and limits, rather than an independent product review.&lt;/p&gt;

&lt;h2&gt;
  
  
  Start with a small example
&lt;/h2&gt;

&lt;p&gt;Copy the content inside this code block without its surrounding fence:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight markdown"&gt;&lt;code&gt;&lt;span class="gh"&gt;# Editable Word example&lt;/span&gt;

Energy relation: $E=mc^2$.

| Task | Status |
| --- | --- |
| Check the exported document | Ready |
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;ol&gt;
&lt;li&gt;Paste it into &lt;a href="https://aitoword.online/en/" rel="noopener noreferrer"&gt;Aitoword&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Check that the heading, equation and table appear in the preview.&lt;/li&gt;
&lt;li&gt;Choose a formatting preset and download Word.&lt;/li&gt;
&lt;li&gt;Open the .docx in Word. Check that you can edit the equation and table cells, then inspect the final layout.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The preview illustrates the content and formatting. Word can use different fonts, wrapping and pagination, so the downloaded document is the result to check.&lt;/p&gt;

&lt;h2&gt;
  
  
  What becomes editable in Word?
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Source content&lt;/th&gt;
&lt;th&gt;Export behavior&lt;/th&gt;
&lt;th&gt;Limit to check&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Markdown headings and lists&lt;/td&gt;
&lt;td&gt;Editable Word document structures&lt;/td&gt;
&lt;td&gt;Check the result rather than expecting arbitrary source styling to carry over&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;A basic Markdown table&lt;/td&gt;
&lt;td&gt;Native Word table cells&lt;/td&gt;
&lt;td&gt;Inspect column counts, widths and page breaks&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Supported LaTeX expressions&lt;/td&gt;
&lt;td&gt;Native Word equations stored as OMML&lt;/td&gt;
&lt;td&gt;Unsupported or invalid expressions retain their source with a notice&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Code blocks&lt;/td&gt;
&lt;td&gt;Code content remains in the document&lt;/td&gt;
&lt;td&gt;Ordinary code is different from an equation to convert&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The tool does not perform OCR on equation screenshots or import a complete LaTeX project. Supporting a formula's math boundaries does not mean every command or macro inside it can be converted.&lt;/p&gt;

&lt;h2&gt;
  
  
  If an equation or table stays as source text
&lt;/h2&gt;

&lt;p&gt;For equations, keep explicit math boundaries and check whether the expression is inside ordinary code. Review any notice for invalid or unsupported syntax. See the &lt;a href="https://aitoword.online/en/resources/ai-equations-to-word/" rel="noopener noreferrer"&gt;editable equation guide and Word example&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;For tables, keep the header, separator row and data rows together. Check for an outer ordinary code fence and unintended pipe characters inside cells. See the &lt;a href="https://aitoword.online/en/resources/markdown-tables-to-word/" rel="noopener noreferrer"&gt;Markdown table troubleshooting guide&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;For a whole AI answer wrapped in a code fence, or for copying problems such as visible Markdown markers, see the &lt;a href="https://aitoword.online/en/resources/ai-answers-to-word/" rel="noopener noreferrer"&gt;AI answer copying and formatting guide&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What local processing means
&lt;/h2&gt;

&lt;p&gt;The current tool is free and requires no account. As described in the &lt;a href="https://aitoword.online/en/privacy/" rel="noopener noreferrer"&gt;privacy notice&lt;/a&gt;, source text, document titles and descriptions, and generated files are processed in the browser rather than uploaded to a conversion server. There are no saved cloud drafts or conversion history; refreshing or closing the page does not restore source text.&lt;/p&gt;

&lt;p&gt;The website still loads its scripts, styles and fonts, and its hosting service processes basic access data. Local document conversion does not mean loading the website makes no network requests.&lt;/p&gt;

&lt;p&gt;Image links retain text descriptions rather than automatically fetching the images. If your document needs those images, plan to add them separately in Word.&lt;/p&gt;

&lt;h2&gt;
  
  
  Choose a starting layout, then check the file
&lt;/h2&gt;

&lt;p&gt;Three formatting presets provide starting choices for fonts, spacing and margins. They do not guarantee a specific page count or compliance with a university thesis format.&lt;/p&gt;

&lt;p&gt;The current download format is .docx; the website does not provide a direct PDF download. Read the &lt;a href="https://aitoword.online/en/terms/" rel="noopener noreferrer"&gt;terms and formatting limits&lt;/a&gt; before relying on the result for an important document.&lt;/p&gt;

&lt;p&gt;Try a small input first, and compare the exported text, equations and table values with your source.&lt;/p&gt;

</description>
      <category>productivity</category>
      <category>markdown</category>
      <category>txt</category>
      <category>ai</category>
    </item>
    <item>
      <title>Why I built a temporary email tool with selectable lifetimes (10 minutes to 3 days)</title>
      <dc:creator>xianye huang</dc:creator>
      <pubDate>Mon, 19 Oct 2026 10:57:46 +0000</pubDate>
      <link>https://dev.to/xianye_huang_4becb58afe1a/a-loaded-inbox-is-not-a-delivery-test-checking-an-email-flow-in-five-states-1lek</link>
      <guid>https://dev.to/xianye_huang_4becb58afe1a/a-loaded-inbox-is-not-a-delivery-test-checking-an-email-flow-in-five-states-1lek</guid>
      <description>&lt;p&gt;I operate &lt;a href="https://dayfly.email/en" rel="noopener noreferrer"&gt;Dayfly Mail&lt;/a&gt;, a free, receive-only temporary inbox for short-lived tasks. The public service receives text and HTML email. It does not send email, store attachments, or offer a public API or CLI for automated integration.&lt;/p&gt;

&lt;p&gt;The browser workflow is small: choose a lifetime, create an inbox, read the message, and destroy the inbox when finished. No account or personal email address is required to create it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Choose the access window before creating the inbox
&lt;/h2&gt;

&lt;p&gt;The available lifetimes are &lt;strong&gt;10 minutes, 1 hour, 24 hours and 3 days&lt;/strong&gt;. The normal homepage defaults to &lt;strong&gt;1 hour&lt;/strong&gt;. You can use a random address or an available custom prefix.&lt;/p&gt;

&lt;p&gt;There is no option to extend an existing inbox. Pick a lifetime that leaves time for the sender and the task; the chosen duration does not establish when an email will arrive. The &lt;a href="https://dayfly.email/en/guides/mailbox-expiration" rel="noopener noreferrer"&gt;mailbox lifetime guide&lt;/a&gt; explains what the countdown controls.&lt;/p&gt;

&lt;h2&gt;
  
  
  Expiry and cleanup are separate events
&lt;/h2&gt;

&lt;p&gt;When the inbox expires, access ends. Scheduled cleanup removes expired records afterward. The countdown is an access deadline, rather than a promise that every stored copy is erased at that exact moment.&lt;/p&gt;

&lt;p&gt;You can also manually destroy the inbox when you are finished. The public service has no recovery feature for expired or destroyed inboxes. Keep important account recovery on an address you can continue accessing.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the public service supports
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Need&lt;/th&gt;
&lt;th&gt;Dayfly Mail's public service&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Read a text or HTML email in the browser&lt;/td&gt;
&lt;td&gt;Supported&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Choose an inbox lifetime before creation&lt;/td&gt;
&lt;td&gt;Four choices; normal default is 1 hour&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Destroy the inbox after a short task&lt;/td&gt;
&lt;td&gt;Supported; no recovery afterward&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Send or reply to email&lt;/td&gt;
&lt;td&gt;Not supported&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Store attachments&lt;/td&gt;
&lt;td&gt;Not supported&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Integrate through a public API or CLI&lt;/td&gt;
&lt;td&gt;Not supported&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;These limits describe the public Dayfly service. For a test suite that requires programmatic inbox access, use a setup with a supported automation interface.&lt;/p&gt;

&lt;h2&gt;
  
  
  Use it for a bounded task
&lt;/h2&gt;

&lt;p&gt;A permitted one-off download, short confirmation or manual email check in an app you own or are authorized to test can fit this workflow. For your own app, the &lt;a href="https://dayfly.email/en/guides/testing-signup-emails" rel="noopener noreferrer"&gt;manual signup-email checklist&lt;/a&gt; separates the send request, actual arrival, message reading and verification action.&lt;/p&gt;

&lt;p&gt;If a message is missing, start with the complete address, the current inbox and its remaining lifetime, then check the sender and whether the website accepts temporary email. The &lt;a href="https://dayfly.email/en/guides/verification-email-not-arriving" rel="noopener noreferrer"&gt;missing-email guide&lt;/a&gt; gives the steps.&lt;/p&gt;

&lt;p&gt;Websites decide which addresses they accept. Use an address they permit when temporary email is rejected. For ongoing communication or password recovery, use an address you can keep accessing; an expiring inbox is unsuitable for an important long-term account. See the &lt;a href="https://dayfly.email/en/faq" rel="noopener noreferrer"&gt;current FAQ&lt;/a&gt; for the service's features and limits.&lt;/p&gt;

</description>
      <category>testing</category>
      <category>free</category>
      <category>tempemail</category>
    </item>
  </channel>
</rss>
