This question now has my own answers that I redacted in accordance to work instructions. I would have tried to redact my own answers again, but my workplace has decided that my answers do indeed fall under public domain since my answers are composed of open-source or public material. (I just can't give anymore answers from now on.)
I'll leave this question here, but I must let the site administrators know that this question isn't useful. It was just a test (like a few other questions) to assess the barriers-to-entry to LaTeX et al. It would be best to just delete this question.
A fuller answer (I posted) on doing CJK is at a very tangentially related question.
To Davislor who diligently answered nigh every possible facet of my question: Thank you! I am going to keep this question here to showcase your diligence and resourcefulness. Do note in my answer (in another question) how I avoided potentially problematic automatic font lookup via font name; in certain scenarios, that lookup can actually loop badly as to break TeX processing. The demographics of LaTeX newbies turned away tend overwhelmingly towards software engineers, and they are very wary of "automagic" features that "provide no consistently reliable function, and yet no way to fully control".
MWE:
\documentclass{scrbook}
\usepackage[utf8]{inputenc} % For non-English languages
% Install cjk for Chinese, zhmetrics for font size.
\usepackage{CJKutf8}
% OT1 for Chinese. T1 for English.
\usepackage[OT1, T1]{fontenc} % T1 will be active encoding.
\begin{document}
This is mainly an English document.
\begin{CJK}{UTF8}{song}
With a smattering of Chinese: {\fontencoding{OT1}\selectfont 中文}
\end{CJK}
\end{document}
The error:
!pdfTeX error: pdflatex (file cyberb65): Font cyberb65 at 657 not found
I would at least like to know which fonts come default with which packages. In the MWE, the packages I installed are:
- koma-script
- inputenc
- cjk
- fontenc
For some unknown reason, I already have access to the gbsn font. Am on MacOS.
Side question: Is it difficult to transition to an engine that better supports UTF-8 and non-English languages?
Working answer: Don't use song font family. Use gbsn. If you wanna know how/where that font got installed by default, private message Jon who wrote this question.
And thanks to @cfr, I'm not using OT1 font encoding anymore. Not needed with gbsn font family.
Updated MWE:
\documentclass{scrbook}
\usepackage[utf8]{inputenc} % For non-English languages.
% Install babel-vietnamese, vntex for Vietnamese.
\usepackage[vietnamese, english]{babel} % English will be active language.
% Install cjk for Chinese, zhmetrics for font size.
\usepackage{CJKutf8}
% T5 for Vietnamese.
\usepackage[T5, T1]{fontenc} % T1 will be active encoding.
\begin{document}
This is mainly an English document.
\begin{CJK}{UTF8}{gbsn}
With a smattering of Chinese: 中文
\end{CJK}
And some Vietnamese: {\fontencoding{T5}\selectfont Tiếng Việt}
\end{document}
\fontencoding{OT1}\selectfontis wrong. Whatever else is or isn't right or wrong about your code, that part surely needs to go. – cfr Jun 11 '18 at 00:27\fontencoding? – Jun 11 '18 at 01:02\fontencoding. The problem is the encoding you're using. That said, you should rarely, if ever, need to use\fontencodingdirectly in a document. – cfr Jun 11 '18 at 01:04xecjk. It doesn't mean much to me, but it presumably will to you. – cfr Jun 11 '18 at 01:21\fontenconding? Or should I use something else? – Jun 11 '18 at 03:32\fontencodingthat's the problem per se. Rather, OT1 is the problem. That said, if you use XeTeX, you won't have to worry about font encodings at all. – cfr Jun 11 '18 at 04:04\fontencodingcan be wrapped in macros. Thesongfont family requiredOT1encoding, so I don't need it anymore now that I use the defaultgbsn. By the way, have a look at the updated MWE that includes Vietnamese. – Jun 11 '18 at 14:36\fontencoding. I said thatOT1was not the right encoding for what you wanted. OT1 is a 7-bit Latin encoding, good for English and used for text in mathematics. Also, you're not using microtypography, as far as I can tell. But perhaps you didn't mean that literally. – cfr Jun 11 '18 at 23:52\fontencodingin the body of your document. For one thing, all your new documents should use Unicode, not obsolete 7- or 8-bit encodings. You’d use a package such as Polyglossia or Babel that provide higher-level commands to change the language, or else write your own that change the font, the script and the text direction as needed. – Davislor Jan 16 '19 at 15:15\fontencoding). – Jan 17 '19 at 11:30basic scheme) already serves the same purpose (yes, without auto-install of packages on-the-fly). Also, it's good to keep a clean list of dependencies, rather than let MikTeX install dependencies with possibly unintended consequences. Already, at work, we have over 10 different types of TeX installations, and I'm being pressed to shut down the entire TeX initiative altogether. – Jan 22 '19 at 01:17texlivepackage, runapt-file searchto find out which OS packages contain the font. For example, theumingfont needed byctexis in the Ubuntu packagefonts-arphic-uming:. – Davislor Jan 31 '19 at 02:28tlmgr; and also created MikTeX-like functionality in it) We did this CTAN lookup in-house, but it's really very simple scripts. If you're a lecturer in a varsity, I would advise you to just pose a question to your 1st year computer science students. A massive majority of my know-how I need to withhold from this community (work instructions) isn't even at all specialized. – Jan 31 '19 at 02:34