You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
- Unless you plan to do something very unusual, understanding the source of TeX is not necessary to use TeX. Certainly I would not claim to know much Pascal, but I'm quite good at programming TeX.Joseph Wright– Joseph Wright ♦2013-04-29 12:29:24 +00:00Commented Apr 29, 2013 at 12:29
- 2One piece of advise from an old fart: Concentrate on what is (more or less) immediately useful. That way you have more motivation, and the risk of getting sidetracked is much less. TeX is not a good way to learn how to build packages, it uses a very idiosyncratic language (web), and was written to install on all sort of extremely weird machines/operating systems (most of them long defunct).vonbrand– vonbrand2013-04-29 18:51:33 +00:00Commented Apr 29, 2013 at 18:51
- 3Like you, I also wanted to study the TeX code. After all, it was written by an eminent computer scientist, and, for a large piece of software, it is remarkably free of bugs. It looked like something significant could be learned. But, I gave up after a while. Mostly because the code is full of clever tricks to pack data into memory locations to save space. This made sense 30 years ago, but not so much today, and it makes the code very difficult to read (for me, anyway). There is a system called JavaTex, by Tim Murphy, which might be a bit easier to read, maybe. But I ran out of time.bubba– bubba2013-04-30 10:31:01 +00:00Commented Apr 30, 2013 at 10:31
- 1Also, I agree with vonbrand -- Tex includes a lot of exotic code that was required to make things portable 30 years ago.bubba– bubba2013-04-30 10:34:13 +00:00Commented Apr 30, 2013 at 10:34
- 1ctan.math.illinois.edu/info/knuth-pdf/tex/tex.pdfRafael Beirigo– Rafael Beirigo2021-05-31 18:58:37 +00:00Commented May 31, 2021 at 18:58
Add a comment |
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. tikz-pgf), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you
lang-tex