如果你对https://www.codecogs.com/latex/eqneditor.php有问题，我发现https://alexanderrodin.com/github-latex-markdown/对我有用。它生成您需要的Markdown代码，因此您只需将其剪切并粘贴到README中。md文档。

自述文件2Tex

我一直在写一个脚本，它可以自动地把LaTeX排版很好地转换成github风格的markdown: https://github.com/leegao/readme2tex

在Github上渲染LaTeX有一些挑战。首先，github风格的markdown去掉了大多数标签和属性。这意味着没有基于Javascript的库(如Mathjax)，也没有任何CSS样式。

自然的解决方案似乎是嵌入预编译方程的图像。但是，您很快就会意识到，LaTeX不仅仅是将美元符号的封闭公式转换为图像。

简单地嵌入来自在线编译器的图像会给文档带来这种不自然的外观。事实上，我认为它在日常的x^2数学俚语中比跳跃更有可读性

我相信确保你的文档以自然和可读的方式排版是很重要的。这就是为什么我写了一个脚本，除了将公式编译成图像外，还确保生成的图像正确地拟合并与其余文本对齐。

例如，下面是一个.md文件的摘录，涉及正则表达式的一些枚举属性，使用readme2tex:

正如您所期望的，顶部的方程集是通过启动相应的align*环境来指定的

**Theorem**: The translation $[\![e]\!]$ given by
\begin{align*}
...
\end{align*}
...

注意，当内联方程($…$)与文本一起运行时，显示方程(那些由\begin{ENV}分隔的方程…\end{ENV}或$$…$$)居中。这使得那些已经习惯使用LaTeX的人可以很容易地保持工作效率。

如果这听起来有帮助，一定要去看看。https://github.com/leegao/readme2tex

我测试了其他人提出的一些解决方案，我想推荐TeXify在agurodriguez的评论中创建和提出，并由Tom Hale进一步描述-我想发展他的答案，并给出一些理由，为什么这是一个非常好的解决方案:

TeXify is wrapper of Readme2Tex (mention in Lee answer). To use Readme2Tex you must install a lot of software in your local machine (python, latex, ...) - but TeXify is github plugin so you don't need to install anything in your local machine - you only need to online installation that plugin in you github account by pressing one button and choose repositories for which TeXify will have read/write access to parse your tex formulas and generate pictures. When in your repository you create or update *.tex.md file, the TeXify will detect changes and generate *.md file where latex formulas will be exchanged by its pictures saved in tex directory in your repo. So if you create README.tex.md file then TeXify will generate README.md with pictures instead tex formulas. So parsing tex formulas and generate documentation is done automagically on each commit&push :) Because all your formulas are changed into pictures in tex directory and README.md file use links to that pictures, you can even uninstall TeXify and all your old documentation will still works :). The tex directory and *.tex.md files will stay on repository so you have access to your original latex formulas and pictures (you can also safely store in tex directory your other documentation pictures "made by hand" - TeXify will not touch them). You can use equations latex syntax directly in README.tex.md file (without loosing .md markdown syntax) which is very handy. Julii in his answer proposed to use special links (with formulas) to external service e.g . http://latex.codecogs.com/gif.latex?s%3D%5Ctext%20%7B%20sensor%20reading%20%7D which is good however has some drawbacks: the formulas in links are not easy (handy) to read and update, and if there will be some problem with that third-party service your old documentation will stop work... In TeXify your old documentation will works always even if you uninstall that plugin (because all your pictures generated from latex formulas are stay in repo in tex directory). The Yuchao Jiang in his answer, proposed to use Jupyter Notebook which is also nice however have som drawbacks: you cannot use formulas directly in README.md file, you need to make link there to other file *.ipynb in your repo which contains latex (MathJax) formulas. The file *.ipynb format is JSON which is not handy to maintain (e.g. Gist don't show detailed error with line number in *.ipynb file when you forgot to put comma in proper place...).

这里是我的一些回购的链接，我使用TeXify的文档是从README.tex.md文件生成的。

更新

今天2020.12.13我意识到TeXify插件停止工作-即使重新安装后:(

您还可以看看我的工具latexMarkdown2Markdown，它可以将LaTeX转换为SVG并生成带有章节编号的内容表。

你可以获得持续集成服务(例如Travis CI)来呈现LaTeX并将结果提交到github。CI将在每次新提交后部署一个“云”worker。工作人员将您的文档编译为pdf，并使用ImageMagick将其转换为图像，或者使用PanDoc尝试LaTeX->HTML转换，其中成功与否可能取决于您的文档。Worker然后将图像或html提交到您的存储库，从那里可以在自述文件中显示。

示例TravisCi配置构建PDF，将其转换为PNG，并将其提交到您的repo的静态位置是粘贴下面。您需要添加一行来获取PDF，将PDF转换为图像

sudo: required
dist: trusty
os: linux
language: generic
services: docker
env:
  global:
  - GIT_NAME: Travis CI
  - GIT_EMAIL: builds@travis-ci.org
  - TRAVIS_REPO_SLUG: your-github-username/your-repo
  - GIT_BRANCH: master
# I recommend storing your GitHub Access token as a secret key in a Travis CI environment variable, for example $GH_TOKEN.
  - secure: ${GH_TOKEN}
script:
- wget https://raw.githubusercontent.com/blang/latex-docker/master/latexdockercmd.sh
- chmod +x latexdockercmd.sh
- "./latexdockercmd.sh latexmk -cd -f -interaction=batchmode -pdf yourdocument.tex -outdir=$TRAVIS_BUILD_DIR/"
- cd $TRAVIS_BUILD_DIR
- convert -density 300 -quality 90 yourdocument.pdf yourdocument.png
- git checkout --orphan $TRAVIS_BRANCH-pdf
- git rm -rf .
- git add -f yourdoc*.png
- git -c user.name='travis' -c user.email='travis' commit -m "updated PDF"
# note we are again using GitHub access key stored in the CI environment variable
- git push -q -f https://your-github-username:$GH_TOKEN@github.com/$TRAVIS_REPO_SLUG $TRAVIS_BRANCH-pdf
notifications:
  email: false

这个Travis Ci配置会启动一个Ubuntu worker，下载一个latex docker镜像，将文档编译为pdf，并将其提交到一个名为branchanme-pdf的分支。

要了解更多的例子，请参阅这个github回购及其附带的sx讨论，PanDoc示例， https://dfm.io/posts/travis-latex/，以及Medium上的这篇文章。

我一直在四处寻找，发现另一个问题中的这个答案最适合我。即使用githubcontent数学渲染器，例如显示:

使用这个链接 小心乳胶需要url编码，但其他工作对我来说很好。