luong-komorebi / begin-latex-in-minutes Goto Github PK

The URLs https://s14.postimg.org/deg0kqhu9/multi_file.png and https://postimg.org/image/hnkqmwl3h/ give Server Not Found error.

The amsmath example writes sqrt where \sqrt was perhaps meant?

TeXstudio is a fork of TeXmaker with more features. Perhaps you should promote that instead?

Some languages won't work right out of the box. You will need to include some packages for the font to render. Also, you will learn about "packages" later. For example:

\documentclass[a4paper]{article}

\usepackage[T5]{fontenc}
\usepackage[utf8]{inputenc}

\begin{document}

Xin chào thế giới. This is Hellow World in Vietnamese.

\end{document}

It looks like you’re still living in the 90s where Unicode support was neglected. You see, two projects have solved this problem: XeTeX and LuaTeX. Those are two compilers with Unicode support.

\documentclass[a4paper]{article}
\usepackage{fontspec}
\usepackage{polyglossia}
\setmainfont[]{Baskerville} % any TTF or OTF fonts from my system will do
\begin{document}
Xin chào thế giới. This is Hello World in Vietnamese.

The quick brown fox jumps over the lazy dog.

Pchnąć w tę łódź jeża lub ośm skrzyń fig.

Quiere la boca exhausta vid, kiwi, piña y fugaz jamón.

Vogt Nyx: »Büß du ja zwölf Qirsch, Kämpe!«

Любя, съешь щипцы, — вздохнёт мэр, — кайф жгуч.
\end{document}

If I don’t set any font (remove line with comment), the font will default to Latin Modern, which is a reworking of Computer Modern with support for many Latin diacritic characters. The Russian part fails.

In TeXstudio (and probably TeXMaker): change Build → Default Compiler in the settings. I’m using LuaLaTeX.

Currently the part that talks about available translations looks very different across Translation:* files. Moreover, some of them are outdated. And finally, it does not make much sense to say that there is Spanish translation available in French. :)

Would be nice to make language selection blocks identical. And every language should be written "in itself". I think it could look like this.

If you like the idea I can take care of pull request.

If this repository is going to be a thing, we should impose some sort of review process to vet incoming information.

A large problem the LaTeX community has been facing has been the rampant misinformation spread by outdated oral tradition and simple misunderstandings. (Such discussions are available in the TeX.SX chat archives, the meta site, and of course LaTeX-L.) At present, this repository is not helping the situation, but I can hold out hope that it could become a very valuable resource with a bit of work and a lot of discipline.

I propose that all incoming pull requests be reviewed for technical accuracy and current best practice (as far as a repository like this can hope to manage; 'best practice' often relies on the specific application). Hopefully this can curb issues like #18 cropping up again. Such reviews should be completed before a pull request is accepted.

Most PDF viewers on Windows, especially Acrobat readers block writing to the pdf when it is opened. This leads to an error if you compile again.

There are some viewers which don't block and also update if the pdf was updatet, e. g. Sumatra PDF

Many tools require special build steps (eg. #12 or anything that uses bibliographies), but there is no mention of this in the document. In my own examples, I use cereda/arara to explicitly define how to compile each example in the repository. I'd suggest using that since the compilation steps can be inlined with the examples themselves.

こんにちは、私はあなたのすべてを愛しています。
Hello, I love you all.

If you mean "you all" is like "you guys", you should translate to "こんにちは、私はあなた達みんなを愛しています。".
"あなたのすべて" refers to "everything you have", so you should use "あなた達みんな" as "you all".

It should read

Brief Intro to LaTeX for programmers/developers… that helps you use LaTeX with ease. Comments and Contributions are welcomed

The actual wording should also be revised. It's… a little awkward.

See also #3.

I think the author may not handle all the issues and PRs, so @Voluong needs 2-3 mans to manage this project because he is a student as we are.

In windows, filename cannot contain colon (:).

Short and long file names must not contain the following characters:

slash (/) or (\)
question mark (?)
vertical bar (|)
right angle bracket (>)
left angle bracket (<)
colon (:)

• Filename - Windows applications | Microsoft Docs

When I use github desktop for windows or git in cmd or powershell, I only got a readme.md and a 0 KB Translation file.

and If I use git in wsl, all the : in filename are replace to  automatically.

Naming your file "shit.tex" isn't very helpful for encouraging beginners ...

See the first screenshot

https://camo.githubusercontent.com/c3da4b68c38084a999bf10b9a984251bbc9ff6d7/687474703a2f2f692e696d6775722e636f6d2f584a786f5879492e6a7067

There's a broken link to an image present in the Multiple files in LaTeX section

clicking the link result in a "Cannot proxy the given URL" error

We should consider splitting this document into multiple files to avoid complicated merges and allow for a clearer structure. I'd recommend a file structure like this:

/README.md                                ; actual summary of the project; annotated TOC
/guide/01-introduction-and-goals/README.md           ; introduction and goals
/guide/01-introduction-and-goals/image-for-ch1.png   ; some picture
/guide/02-your-first-document/REAMDE.md              ; first doc
...

Before I actually make the PR though, I'd like to nail down what the TOC should look like. This is what we have right now:

• What is LaTeX?
• Why use LaTeX?
• Set up for LaTeX
• First LaTeX file
• A deeper look
• Multilingual usage
• Paragraph and section
• Making a table of contents
• Footnotes
• What is a package?
• Table
• Adding images
• Insert code into LaTeX
• Additional Tools

Here's what I'd propose:

• Preface and Installation

  Encompasses what/why, setup, and 'hello, world'. Gives a link to the section on multilingual support. Uses TeXworks as a 'click play' editor that's already installed with all major distributions.

• Introduction

  Explains 'hello, world' example and introduces the concept of packages via another example. Introduces build tools like Arara that will be used in the rest of the document's examples (#22). Introduces other editors like Texmaker, TeXShop, Kile, Emacs, and Vim. Drives home the 'LaTeX is a markup language' point -- it's editor-agnostic.

• Organizing Your Document

  Sectioning, tables of contents, and cross-referencing. Footnotes, images, tables, and LOFs/LOTs.

• More sections as time goes on…

IMHO minted is much better than lstlistings for code: https://www.ctan.org/tex-archive/macros/latex/contrib/minted/

Anyone interested in translating this into your language is welcomed.