diff --git a/README.md b/README.md index 207ee93..65c4e96 100644 --- a/README.md +++ b/README.md @@ -16,6 +16,7 @@ | [`成绩构成说明/`](成绩构成说明/) | **成绩构成说明**(理论课/实验课比例分解表 + 教师签字栏) | `成绩构成说明.tex` | | [`幻灯片/`](幻灯片/) | 演示文稿(**beamer** 主题,海大配色) | `slides.tex` | | [`科技报告/`](科技报告/) | **科技报告**、实验讲义、说明文档 | `report.tex` | +| [`简历/`](简历/) | **个人简历**(中文,A4 两栏式,含圆形头像与分区条目) | `简历.tex` | ## 编译 @@ -27,11 +28,11 @@ xelatex slides.tex xelatex slides.tex # 跑两遍,第二遍才能取到正确的目录、交叉引用与总页数 ``` -目录名含中文不影响编译(已实测 10 个模板目录在中文目录下零报错编译通过)。 +目录名含中文不影响编译(已实测 11 个模板目录在中文目录下零报错编译通过)。 ## 说明 -- **字体单一来源**:全库字体集中在根目录 [`fonts/`](fonts/),由 [`fonts.tex`](fonts.tex) 统一加载。十个模板通过 `\input{../fonts.tex}` 取字体,**不自带字体、不依赖系统字体**——换机器(Windows / macOS / Linux / Overleaf)编译结果一致。 +- **字体单一来源**:全库字体集中在根目录 [`fonts/`](fonts/),由 [`fonts.tex`](fonts.tex) 统一加载。十一个模板通过 `\input{../fonts.tex}` 取字体,**不自带字体、不依赖系统字体**——换机器(Windows / macOS / Linux / Overleaf)编译结果一致。 - **全部开源可商用**:无方正、无 SimSun / SimHei / KaiTi / FangSong、无 Times New Roman、无微软雅黑。用的是思源宋体/黑体、霞鹜文楷、朱雀仿宋、TeX Gyre Termes、鸿蒙 HarmonyOS Sans(各字体授权见 [`fonts/LICENSE`](fonts/LICENSE),来源与字符集见 [`fonts/README.md`](fonts/README.md))。 - **每个子目录自包含**:样式文件(`.sty` / `.cls`)、图片都在各目录内,编译时不需要额外的宏包搜索路径;只有字体是共享的上层目录。 - **各目录的 `README.md`** 写明该模板的用法、可改参数、版式数据来源与书写注意事项,改之前先看。 diff --git a/fonts.tex b/fonts.tex index 1042c88..bc4f975 100644 --- a/fonts.tex +++ b/fonts.tex @@ -1,7 +1,7 @@ %====================================================================== % oucfonts.tex —— 中国海洋大学模板库的公共字体入口 % -% 本文件是仓库内**唯一**允许声明字体的地方。十个模板全部通过 +% 本文件是仓库内**唯一**允许声明字体的地方。十一个模板全部通过 % \input{../fonts.tex} % 取字体,不再各自写 \setCJKmainfont / \setmainfont。 % @@ -134,6 +134,41 @@ }, ] +% ------------------------------------------------------------------ +% 小型大写(sc):用**字体形状替换**,不用 SmallCapsFont 选项 +% +% 为什么需要它:简历模板的 \user / \resumetitle / \experience 都用了 +% \textsc,而中文没有小型大写字形,不处理就每页刷 6 条 +% LaTeX Font Warning: Font shape `TU/OUCSerif(0)/m/sc' undefined +% 惯例做法是让 sc 档**指回常规体**:\textsc{中文} 看起来不变(中文 +% 本来也没有大小写),而 \textsc{English} 里的西文仍然走 \setmainfont +% 的 Termes 小型大写,行为正确。 +% +% 为什么不写 SmallCapsFont —— 这里踩了整整一轮坑,结论留下免得重来: +% +% 1) SmallCapsFont 这个选项**与本文件上面的 ItalicFeatures / +% BoldItalicFeatures 互斥**。最小复现实测: +% 只有 SmallCapsFont + SmallCapsFeatures → 通过 +% 再加 ItalicFeatures(带跨目录 Path) → 立刻报 +% Package fontspec Error: +% The font "OUCSerif-Regular" cannot be found. +% 写 *-Regular、写全名 OUCSerif-Regular、写带 .otf 的、把两个键 +% 挪到最后,全都报同一个错;把斜体换成同目录字体 +% (ItalicFont = *-Bold)就又能过 —— 所以是**跨目录 Path 的相互作用**, +% 不是文件名写法问题。照着"IralicFont 怎么写的就怎么写"去改会一直失败。 +% +% 2) 绕开的办法就是干脆不用那个选项,改用 LaTeX 原生的字体形状替换 +% (\DeclareFontShape + <->ssub)。这条机制在 fontspec 选项之下, +% 不受选项间相互作用影响,效果完全等价。 +% +% ⚠️ 第二个参数 OUCSerif(0) 里的 (0) 是 fontspec 给该字体生成的内部 +% 族编号,不是笔误。若将来 \setCJKmainfont 换了字体名,这两行必须 +% 同步改;写错**不会报错**,只会让 sc 警告悄悄回来 —— 改完看日志。 +% ------------------------------------------------------------------ +\DeclareFontShape{TU}{OUCSerif(0)}{m}{sc}{<->ssub * OUCSerif(0)/m/n}{} +\DeclareFontShape{TU}{OUCSerif(0)}{b}{sc}{<->ssub * OUCSerif(0)/b/n}{} + + %====================================================================== % 三、字族命令 % diff --git a/fonts/README.md b/fonts/README.md index 29c9b8b..963ab5c 100644 --- a/fonts/README.md +++ b/fonts/README.md @@ -1,6 +1,6 @@ # fonts/ —— 模板库公共字体目录 -本目录是**中国海洋大学 LaTeX 模板库唯一的一份字体来源**。仓库里七个模板全部通过 +本目录是**中国海洋大学 LaTeX 模板库唯一的一份字体来源**。仓库里十一个模板全部通过 根目录的 [`../fonts.tex`](../fonts.tex) 取字体,不再有任何模板自带字体、也不依赖 操作系统里装了什么字体。换一台机器、换一个操作系统(Windows / macOS / Linux / Overleaf),编译出来的样子都一样。 @@ -12,7 +12,8 @@ fonts/ ├── ouc-kai/ OUC Kai 楷体 2 个,7.0 MB ├── zhuque-fangsong/ Zhuque Fangsong 仿宋 1 个,8.4 MB ├── tex-gyre-termes/ TeX Gyre Termes 西文 Times 等价 4 个,550 KB -└── harmonyos-sans/ HarmonyOS Sans 鸿蒙(中英各一档) 6 个,16 MB +├── harmonyos-sans/ HarmonyOS Sans 鸿蒙(中英各一档) 6 个,16 MB +└── fontawesome/ FontAwesome 简历模板的图标符号 1 个,130 KB ``` 合计约 **49 MB**(改造前是 141 MB:幻灯片 49 MB + 科技报告 92 MB 各自带一份, @@ -104,6 +105,25 @@ fonts/ > 不是 `族名-字重` 格式。所以在 fontspec 里不能写 `*-Regular` 通配, > 必须显式给完整文件名。 +### 5. FontAwesome —— 简历模板的图标符号 + +| | | +|---|---| +| 上游 | Font Awesome 4.x(原项目 Fonticons, Inc.) | +| 授权 | SIL OFL 1.1(字体本身)/ CC BY 4.0(图标设计) | +| 保留原因 | `简历/` 模板的联系方式行用 `\smartphone` / `\email` / `\address` 等命令,每个前缀都要印一个图标 | +| 版本 | 与 TeX Live 2022 内置的那份逐字节相同(md5 `9f6ff7d7cfd6f76d7a9c242bdd48c144`) | + +只有 `FontAwesome.otf` 一个文件(130 KB)。TeX Live 里本来就带这份字体,之所以 +还是拷进仓库,是为了守住「字体单一来源」这个约定 —— 否则 `简历/` 就成了唯一一个 +字体来自 TeX Live 安装的模板,换一台没装 fontawesome 宏包用字体的机器就编不出来。 + +> ⚠️ 引用它的不是 `fonts.tex`,而是 `简历/fontawesome.sty` 里的 +> `\newfontfamily{\FA}[Path=../fonts/fontawesome/,Extension=.otf]{FontAwesome}`。 +> 原因:`\FA` 是在 `\RequirePackage{fontawesome}` 时就被定义好的(早于 `.cls` +> 后面所有语句),`awesome-source-cv.cls` 里再声明一次会报 `Font \FA already +> defined`;所以只能改 `fontawesome.sty` 本体。 + --- ## 三、字体是怎么被调用的 diff --git a/fonts/fontawesome/FontAwesome.otf b/fonts/fontawesome/FontAwesome.otf new file mode 100644 index 0000000..efc8427 Binary files /dev/null and b/fonts/fontawesome/FontAwesome.otf differ diff --git a/简历/LICENSE b/简历/LICENSE new file mode 100644 index 0000000..4db9b5a --- /dev/null +++ b/简历/LICENSE @@ -0,0 +1,415 @@ +The LaTeX Project Public License +=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- + +LPPL Version 1.3c 2008-05-04 + +Copyright 1999 2002-2008 LaTeX3 Project + Everyone is allowed to distribute verbatim copies of this + license document, but modification of it is not allowed. + + +PREAMBLE +======== + +The LaTeX Project Public License (LPPL) is the primary license under +which the LaTeX kernel and the base LaTeX packages are distributed. + +You may use this license for any work of which you hold the copyright +and which you wish to distribute. This license may be particularly +suitable if your work is TeX-related (such as a LaTeX package), but +it is written in such a way that you can use it even if your work is +unrelated to TeX. + +The section `WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE', +below, gives instructions, examples, and recommendations for authors +who are considering distributing their works under this license. + +This license gives conditions under which a work may be distributed +and modified, as well as conditions under which modified versions of +that work may be distributed. + +We, the LaTeX3 Project, believe that the conditions below give you +the freedom to make and distribute modified versions of your work +that conform with whatever technical specifications you wish while +maintaining the availability, integrity, and reliability of +that work. If you do not see how to achieve your goal while +meeting these conditions, then read the document `cfgguide.tex' +and `modguide.tex' in the base LaTeX distribution for suggestions. + + +DEFINITIONS +=========== + +In this license document the following terms are used: + + `Work' + Any work being distributed under this License. + + `Derived Work' + Any work that under any applicable law is derived from the Work. + + `Modification' + Any procedure that produces a Derived Work under any applicable + law -- for example, the production of a file containing an + original file associated with the Work or a significant portion of + such a file, either verbatim or with modifications and/or + translated into another language. + + `Modify' + To apply any procedure that produces a Derived Work under any + applicable law. + + `Distribution' + Making copies of the Work available from one person to another, in + whole or in part. Distribution includes (but is not limited to) + making any electronic components of the Work accessible by + file transfer protocols such as FTP or HTTP or by shared file + systems such as Sun's Network File System (NFS). + + `Compiled Work' + A version of the Work that has been processed into a form where it + is directly usable on a computer system. This processing may + include using installation facilities provided by the Work, + transformations of the Work, copying of components of the Work, or + other activities. Note that modification of any installation + facilities provided by the Work constitutes modification of the Work. + + `Current Maintainer' + A person or persons nominated as such within the Work. If there is + no such explicit nomination then it is the `Copyright Holder' under + any applicable law. + + `Base Interpreter' + A program or process that is normally needed for running or + interpreting a part or the whole of the Work. + + A Base Interpreter may depend on external components but these + are not considered part of the Base Interpreter provided that each + external component clearly identifies itself whenever it is used + interactively. Unless explicitly specified when applying the + license to the Work, the only applicable Base Interpreter is a + `LaTeX-Format' or in the case of files belonging to the + `LaTeX-format' a program implementing the `TeX language'. + + + +CONDITIONS ON DISTRIBUTION AND MODIFICATION +=========================================== + +1. Activities other than distribution and/or modification of the Work +are not covered by this license; they are outside its scope. In +particular, the act of running the Work is not restricted and no +requirements are made concerning any offers of support for the Work. + +2. You may distribute a complete, unmodified copy of the Work as you +received it. Distribution of only part of the Work is considered +modification of the Work, and no right to distribute such a Derived +Work may be assumed under the terms of this clause. + +3. You may distribute a Compiled Work that has been generated from a +complete, unmodified copy of the Work as distributed under Clause 2 +above, as long as that Compiled Work is distributed in such a way that +the recipients may install the Compiled Work on their system exactly +as it would have been installed if they generated a Compiled Work +directly from the Work. + +4. If you are the Current Maintainer of the Work, you may, without +restriction, modify the Work, thus creating a Derived Work. You may +also distribute the Derived Work without restriction, including +Compiled Works generated from the Derived Work. Derived Works +distributed in this manner by the Current Maintainer are considered to +be updated versions of the Work. + +5. If you are not the Current Maintainer of the Work, you may modify +your copy of the Work, thus creating a Derived Work based on the Work, +and compile this Derived Work, thus creating a Compiled Work based on +the Derived Work. + +6. If you are not the Current Maintainer of the Work, you may +distribute a Derived Work provided the following conditions are met +for every component of the Work unless that component clearly states +in the copyright notice that it is exempt from that condition. Only +the Current Maintainer is allowed to add such statements of exemption +to a component of the Work. + + a. If a component of this Derived Work can be a direct replacement + for a component of the Work when that component is used with the + Base Interpreter, then, wherever this component of the Work + identifies itself to the user when used interactively with that + Base Interpreter, the replacement component of this Derived Work + clearly and unambiguously identifies itself as a modified version + of this component to the user when used interactively with that + Base Interpreter. + + b. Every component of the Derived Work contains prominent notices + detailing the nature of the changes to that component, or a + prominent reference to another file that is distributed as part + of the Derived Work and that contains a complete and accurate log + of the changes. + + c. No information in the Derived Work implies that any persons, + including (but not limited to) the authors of the original version + of the Work, provide any support, including (but not limited to) + the reporting and handling of errors, to recipients of the + Derived Work unless those persons have stated explicitly that + they do provide such support for the Derived Work. + + d. You distribute at least one of the following with the Derived Work: + + 1. A complete, unmodified copy of the Work; + if your distribution of a modified component is made by + offering access to copy the modified component from a + designated place, then offering equivalent access to copy + the Work from the same or some similar place meets this + condition, even though third parties are not compelled to + copy the Work along with the modified component; + + 2. Information that is sufficient to obtain a complete, + unmodified copy of the Work. + +7. If you are not the Current Maintainer of the Work, you may +distribute a Compiled Work generated from a Derived Work, as long as +the Derived Work is distributed to all recipients of the Compiled +Work, and as long as the conditions of Clause 6, above, are met with +regard to the Derived Work. + +8. The conditions above are not intended to prohibit, and hence do not +apply to, the modification, by any method, of any component so that it +becomes identical to an updated version of that component of the Work as +it is distributed by the Current Maintainer under Clause 4, above. + +9. Distribution of the Work or any Derived Work in an alternative +format, where the Work or that Derived Work (in whole or in part) is +then produced by applying some process to that format, does not relax or +nullify any sections of this license as they pertain to the results of +applying that process. + +10. a. A Derived Work may be distributed under a different license + provided that license itself honors the conditions listed in + Clause 6 above, in regard to the Work, though it does not have + to honor the rest of the conditions in this license. + + b. If a Derived Work is distributed under a different license, that + Derived Work must provide sufficient documentation as part of + itself to allow each recipient of that Derived Work to honor the + restrictions in Clause 6 above, concerning changes from the Work. + +11. This license places no restrictions on works that are unrelated to +the Work, nor does this license place any restrictions on aggregating +such works with the Work by any means. + +12. Nothing in this license is intended to, or may be used to, prevent +complete compliance by all parties with all applicable laws. + + +NO WARRANTY +=========== + +There is no warranty for the Work. Except when otherwise stated in +writing, the Copyright Holder provides the Work `as is', without +warranty of any kind, either expressed or implied, including, but not +limited to, the implied warranties of merchantability and fitness for a +particular purpose. The entire risk as to the quality and performance +of the Work is with you. Should the Work prove defective, you assume +the cost of all necessary servicing, repair, or correction. + +In no event unless required by applicable law or agreed to in writing +will The Copyright Holder, or any author named in the components of the +Work, or any other party who may distribute and/or modify the Work as +permitted above, be liable to you for damages, including any general, +special, incidental or consequential damages arising out of any use of +the Work or out of inability to use the Work (including, but not limited +to, loss of data, data being rendered inaccurate, or losses sustained by +anyone as a result of any failure of the Work to operate with any other +programs), even if the Copyright Holder or said author or said other +party has been advised of the possibility of such damages. + + +MAINTENANCE OF THE WORK +======================= + +The Work has the status `author-maintained' if the Copyright Holder +explicitly and prominently states near the primary copyright notice in +the Work that the Work can only be maintained by the Copyright Holder +or simply that it is `author-maintained'. + +The Work has the status `maintained' if there is a Current Maintainer +who has indicated in the Work that they are willing to receive error +reports for the Work (for example, by supplying a valid e-mail +address). It is not required for the Current Maintainer to acknowledge +or act upon these error reports. + +The Work changes from status `maintained' to `unmaintained' if there +is no Current Maintainer, or the person stated to be Current +Maintainer of the work cannot be reached through the indicated means +of communication for a period of six months, and there are no other +significant signs of active maintenance. + +You can become the Current Maintainer of the Work by agreement with +any existing Current Maintainer to take over this role. + +If the Work is unmaintained, you can become the Current Maintainer of +the Work through the following steps: + + 1. Make a reasonable attempt to trace the Current Maintainer (and + the Copyright Holder, if the two differ) through the means of + an Internet or similar search. + + 2. If this search is successful, then enquire whether the Work + is still maintained. + + a. If it is being maintained, then ask the Current Maintainer + to update their communication data within one month. + + b. If the search is unsuccessful or no action to resume active + maintenance is taken by the Current Maintainer, then announce + within the pertinent community your intention to take over + maintenance. (If the Work is a LaTeX work, this could be + done, for example, by posting to comp.text.tex.) + + 3a. If the Current Maintainer is reachable and agrees to pass + maintenance of the Work to you, then this takes effect + immediately upon announcement. + + b. If the Current Maintainer is not reachable and the Copyright + Holder agrees that maintenance of the Work be passed to you, + then this takes effect immediately upon announcement. + + 4. If you make an `intention announcement' as described in 2b. above + and after three months your intention is challenged neither by + the Current Maintainer nor by the Copyright Holder nor by other + people, then you may arrange for the Work to be changed so as + to name you as the (new) Current Maintainer. + + 5. If the previously unreachable Current Maintainer becomes + reachable once more within three months of a change completed + under the terms of 3b) or 4), then that Current Maintainer must + become or remain the Current Maintainer upon request provided + they then update their communication data within one month. + +A change in the Current Maintainer does not, of itself, alter the fact +that the Work is distributed under the LPPL license. + +If you become the Current Maintainer of the Work, you should +immediately provide, within the Work, a prominent and unambiguous +statement of your status as Current Maintainer. You should also +announce your new status to the same pertinent community as +in 2b) above. + + +WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE +====================================================== + +This section contains important instructions, examples, and +recommendations for authors who are considering distributing their +works under this license. These authors are addressed as `you' in +this section. + +Choosing This License or Another License +---------------------------------------- + +If for any part of your work you want or need to use *distribution* +conditions that differ significantly from those in this license, then +do not refer to this license anywhere in your work but, instead, +distribute your work under a different license. You may use the text +of this license as a model for your own license, but your license +should not refer to the LPPL or otherwise give the impression that +your work is distributed under the LPPL. + +The document `modguide.tex' in the base LaTeX distribution explains +the motivation behind the conditions of this license. It explains, +for example, why distributing LaTeX under the GNU General Public +License (GPL) was considered inappropriate. Even if your work is +unrelated to LaTeX, the discussion in `modguide.tex' may still be +relevant, and authors intending to distribute their works under any +license are encouraged to read it. + +A Recommendation on Modification Without Distribution +----------------------------------------------------- + +It is wise never to modify a component of the Work, even for your own +personal use, without also meeting the above conditions for +distributing the modified component. While you might intend that such +modifications will never be distributed, often this will happen by +accident -- you may forget that you have modified that component; or +it may not occur to you when allowing others to access the modified +version that you are thus distributing it and violating the conditions +of this license in ways that could have legal implications and, worse, +cause problems for the community. It is therefore usually in your +best interest to keep your copy of the Work identical with the public +one. Many works provide ways to control the behavior of that work +without altering any of its licensed components. + +How to Use This License +----------------------- + +To use this license, place in each of the components of your work both +an explicit copyright notice including your name and the year the work +was authored and/or last substantially modified. Include also a +statement that the distribution and/or modification of that +component is constrained by the conditions in this license. + +Here is an example of such a notice and statement: + + %% pig.dtx + %% Copyright 2005 M. Y. Name + % + % This work may be distributed and/or modified under the + % conditions of the LaTeX Project Public License, either version 1.3 + % of this license or (at your option) any later version. + % The latest version of this license is in + % http://www.latex-project.org/lppl.txt + % and version 1.3 or later is part of all distributions of LaTeX + % version 2005/12/01 or later. + % + % This work has the LPPL maintenance status `maintained'. + % + % The Current Maintainer of this work is M. Y. Name. + % + % This work consists of the files pig.dtx and pig.ins + % and the derived file pig.sty. + +Given such a notice and statement in a file, the conditions +given in this license document would apply, with the `Work' referring +to the three files `pig.dtx', `pig.ins', and `pig.sty' (the last being +generated from `pig.dtx' using `pig.ins'), the `Base Interpreter' +referring to any `LaTeX-Format', and both `Copyright Holder' and +`Current Maintainer' referring to the person `M. Y. Name'. + +If you do not want the Maintenance section of LPPL to apply to your +Work, change `maintained' above into `author-maintained'. +However, we recommend that you use `maintained', as the Maintenance +section was added in order to ensure that your Work remains useful to +the community even when you can no longer maintain and support it +yourself. + +Derived Works That Are Not Replacements +--------------------------------------- + +Several clauses of the LPPL specify means to provide reliability and +stability for the user community. They therefore concern themselves +with the case that a Derived Work is intended to be used as a +(compatible or incompatible) replacement of the original Work. If +this is not the case (e.g., if a few lines of code are reused for a +completely different task), then clauses 6b and 6d shall not apply. + + +Important Recommendations +------------------------- + + Defining What Constitutes the Work + + The LPPL requires that distributions of the Work contain all the + files of the Work. It is therefore important that you provide a + way for the licensee to determine which files constitute the Work. + This could, for example, be achieved by explicitly listing all the + files of the Work near the copyright notice of each file or by + using a line such as: + + % This work consists of all files listed in manifest.txt. + + in that place. In the absence of an unequivocal list it might be + impossible for the licensee to determine what is considered by you + to comprise the Work and, in such a case, the licensee would be + entitled to make reasonable conjectures as to which files comprise + the Work. diff --git a/简历/README.md b/简历/README.md new file mode 100644 index 0000000..80bbe1e --- /dev/null +++ b/简历/README.md @@ -0,0 +1,112 @@ +# 中国海洋大学个人简历 LaTeX 模板 + +中文个人简历模板,A4 单页两栏式排版:左侧窄栏放时间与阶段,右侧宽栏放具体内容,抬头带圆形头像与联系方式图标行。 + +> 本目录的版式来自一份在用的中文简历(`awesome-source-cv` 系的衍生版)。**字体、占位内容、头像三处都已重做**,详见下文「与上游的差别」。 + +## 特性 + +- **字体全部取自仓库公共字体包**:中文 OUC Serif(宋体)/ OUC Sans(黑体)/ OUC Kai(楷体)/ Zhuque Fangsong(仿宋),西文 TeX Gyre Termes,图标 FontAwesome —— 没有任何一个字体来自系统或 TeX Live 安装,**换机器编译结果一致**; +- **真粗体**:标题、姓名、区块头用的都是字体自带的粗体,不是算法描边; +- **分区可拆**:`section_01` ~ `section_10` 各自一个文件,不想要哪块就把对应 `\input` 注释掉; +- **圆形头像**:`\photo{2.5cm}{photo}` 自动裁成圆形,尺寸随参数走; +- **条目化排版**:论文、专利、项目、获奖等用 `\emptySeparator` 分条,时间栏自动对齐。 + +## 环境要求 + +- TeX Live 2022 及以上,**必须 XeLaTeX** 编译; +- 不需要安装任何字体,`fonts/` 里有全套。 + +## 编译 + +在**本目录**下编译(不要在仓库根调用,`fonts.tex` 里的 `Path=../fonts/` 是相对当前工作目录的): + +```bash +cd 简历 +xelatex 简历.tex +xelatex 简历.tex # 跑两遍:第一遍写 .aux,第二遍才能取到正确的页码与交叉引用 +``` + +编译结果:3 页,日志零 error、零 Underfull、零 Overfull。嵌入字体只有 5 个,全部来自本仓库: + +| 字体 | 用途 | +|---|---| +| `OUCSerif-Regular` / `OUCSerif-Bold` | 中文正文与标题 | +| `TeXGyreTermes-Regular` / `-Bold` | 西文正文与标题 | +| `FontAwesome` | 联系方式行图标 | + +## 改什么、在哪儿改 + +| 要改的内容 | 位置 | +|---|---| +| 姓名、职称、联系方式 | `简历.tex` 的 `\name` / `\tagline` / `\socialinfo` | +| 头像 | 替换 `photo.jpg`(正方形,400×400 以上,会自动裁圆) | +| 各区块正文 | `section_01_headline.tex` ~ `section_10_awards.tex` | +| 不想显示的区块 | 在 `简历.tex` 里把对应 `\input` 注释掉 | +| 左侧时间栏宽度 | `awesome-source-cv.cls` 的 `\setlength{\leftcolumn}{2.5cm}`,右侧栏宽会自动跟着算 | +| 主题色 | `awesome-source-cv.cls` 的 `accentcolor` | + +## 与上游的差别(改动都在文件头注释里写明了原因) + +### 1. 字体:三层依赖全部拆掉 + +上游那份简历的字体走三条路,每条都不能随仓库分发或不可复现: + +| 上游做法 | 问题 | 本模板的处理 | +|---|---|---| +| `zh_cn-adobefonts_external.sty` 设 Adobe 宋/黑/楷/仿 | 56 MB 商业字体,无授权不可分发 | **删掉这两个文件**,改由 `../fonts.tex` 提供中文字体 | +| `awesome-source-cv.cls` 的 `localFont` 分支设 `SourceSansPro-*`(9 个 .otf) | 同上,且与仓库已有西文字体重复 | cls 里的 `\setmainfont` 整段删除,西文改走 `../fonts.tex` 的 TeX Gyre Termes | +| `fontawesome.sty` 用字体名找系统 FontAwesome | 机器上没装就编不过 | 改成显式 `Path=../fonts/fontawesome/`,字体文件已入仓库 | + +删掉的两个文件里还有个隐藏问题值得记一笔:原 `zh_cn-adobefonts_external.sty` 里 +`BoldFont` / `ItalicFont` / `SmallCapsFont` **全部指向 `Regular` 那一档** —— +等于加粗不变、斜体不变,标题层次全靠字号撑。换成真粗体后版面明显立起来了。 + +### 2. 占位:真人信息全部清空 + +模板必须能公开分发,所以姓名、手机、邮箱、住址、出生年月、论文题名与 DOI、专利号、 +软著登记号、获奖名称全部改成 `×××` / `20××` 形式。照着填即可,版式不受影响。 +`a.jpg` / `a.png`(2085×2085 的真人照)换成了 PIL 生成的 400×400 中性剪影 `photo.jpg`。 + +### 3. 排版小修 + +- **左栏宽度改自适应**:原来 `\leftcolumn 2.5cm + \rightcolumnlength 14.8cm` 看着 + 小于版心 18 cm,但两列共 4 个 `\tabcolsep`(≈0.85 cm)没算进去,实际 18.15 cm, + 日志有 `Overfull 4.48pt`。改成 + `\dimexpr\linewidth-\leftcolumn-4\tabcolsep\relax` 由版心反算,改页边距也不用再调数字。 +- **抬头去掉两处空盒**:`\vspace*{0.3cm}\\` 和 `\smallskip\\` 会在换行前多产生一个 + 空 hbox(日志刷 `Underfull \hbox (badness 10000)`),改成 `\\[0.3cm]` / + `\\[\smallskipamount]`,间距效果不变。 +- **`\socialinfo` 末尾不要留 `\\`**:`简历.tex` 里最后一行 `\address{...}` 后面加了 + `\\` 同样会多一个空行。中间的 `\\` 是分行,必须保留。 + +## 写的时候容易踩的三个坑 + +1. **`\newExperience` 的参数顺序是「结束在前、开始在后」** —— 上游定义就是先印 + `#1`(结束时间)再印 `#5`(开始时间),第一次用极易写反,写反了两栏内容会错位。 +2. **每条后面必须跟 `\emptySeparator`**,否则下一条会并进同一格,不换行。 +3. **关键词用英文逗号 `,` 分隔**(`\foreach` 按 `,` 切分)。用中文逗号会把整串当成 + 一个标签,撑出一个超宽的大框。 + +## 字体换成 SmallCaps 时的坑(已在 `../fonts.tex` 里解决) + +`\user` / `\resumetitle` / `\experience` 都用了 `\textsc`,而中文没有小型大写字形, +不处理会每页刷 6 条 `Font shape 'TU/OUCSerif(0)/m/sc' undefined`。 + +修的时候注意:`\setCJKmainfont` 里加 `SmallCapsFont` **与本仓库的 `ItalicFeatures` +互斥** —— 斜体那一档带跨目录 `Path`,会把小型大写的字体查找带偏,无论写 +`*-Regular`、全名、还是带 `.otf` 全报 +`The font "OUCSerif-Regular" cannot be found.`。 + +正解在 `../fonts.tex` 里用的是 LaTeX 原生的形状替换: + +```latex +\DeclareFontShape{TU}{OUCSerif(0)}{m}{sc}{<->ssub * OUCSerif(0)/m/n}{} +\DeclareFontShape{TU}{OUCSerif(0)}{b}{sc}{<->ssub * OUCSerif(0)/b/n}{} +``` + +比 fontspec 的选项低一层,不受选项间相互作用影响,效果等价。 + +## 授权 + +`LICENSE` 沿用上游。字体授权见仓库根 `../fonts/README.md`,全部允许免费商用与再分发。 \ No newline at end of file diff --git a/简历/awesome-source-cv.cls b/简历/awesome-source-cv.cls new file mode 100644 index 0000000..c184edf --- /dev/null +++ b/简历/awesome-source-cv.cls @@ -0,0 +1,451 @@ +%% Copyright 2016 Christophe Roger +% +% Author: +% Christophe Roger (Darwiin) +% +% This work may be distributed and/or modified under the +% conditions of the LaTeX Project Public License, either version 1.3c +% of this license or (at your option) any later version. +% The latest version of this license is in +% http://www.latex-project.org/lppl.txt +% and version 1.3 or later is part of all distributions of LaTeX +% version 2005/12/01 or later. +% +% This work has the LPPL maintenance status `maintained'. +% +% The Current Maintainer of this work is M. C. Roger. +% +% This work consists of the files awesome-source-cv.cls + +\ProvidesClass{awesome-source-cv}[2016/11/05 v1.6.1 Awesome Source CV Class] + +\LoadClass[a4paper]{article} + +\DeclareOption{green}{ + \def\@green{green} +} + +\DeclareOption{red}{ + \def\@red{red} +} + +\DeclareOption{indigo}{ + \def\@indigo{indigo} +} +\DeclareOption{orange}{ + \def\@orange{orange} +} + +\DeclareOption{localFont}{ + \def\@local{local} +} + +\DeclareOption{alternative}{ + \def\@alternative{alternate} +} + +\ProcessOptions + +% Dependences +%A Few Useful Packages +\RequirePackage[frenchb]{babel} +%\RequirePackage[utf8]{luainputenc} % luatex +\RequirePackage{fontspec} % for loading fonts +\RequirePackage{url,parskip} % other packages for formatting +\RequirePackage[usenames,dvipsnames]{xcolor} +\RequirePackage{fullpage} +\RequirePackage[margin=1.5cm]{geometry} +\RequirePackage{fontawesome} +\RequirePackage{hyperref}\hypersetup{hidelinks} +\RequirePackage{titlesec} +\RequirePackage{array} +\RequirePackage{enumitem} +\RequirePackage{longtable} +\RequirePackage{etoolbox} +\RequirePackage{tikz} +\RequirePackage[skins]{tcolorbox} + + +% \DeclareUnicodeCharacter{00E9}{\'{e}} %luatex + +% Define default accent colors +%\definecolor{basecolor}{HTML}{000066} %BLUE +\definecolor{basecolor}{HTML}{0f4c81} +\ifundef{\@green} { + \ifundef{\@red} { + \ifundef{\@indigo}{ + \ifundef{\@orange} {} + { \definecolor{basecolor}{HTML}{e68a00} } + } + { \definecolor{basecolor}{rgb}{0.2, 0.07, 0.48} } + } + { \definecolor{basecolor}{HTML}{b30000} } %RED +} +{ \definecolor{basecolor}{rgb}{0.0, 0.62, 0.38} } + +\definecolor{darkGrey}{HTML}{989898} + +\colorlet{linkcolor}{basecolor} +\colorlet{accentcolor}{linkcolor!90} +\colorlet{symbolcolor}{linkcolor!85} + +% Setup hyperref package, and colours for links +%\definecolor{linkcolour}{rgb}{0,0.2,0.6} +\hypersetup{breaklinks} + +\pagestyle{empty} % non-numbered pages +%\font\fb=''[cmr10]'' % for use with \LaTeX command + +% Setup CV sections +\titleformat{\section}{\Large\raggedright}{}{0em}{}[\titlerule] +\titlespacing{\section}{0pt}{2pt}{2pt} + +% Configure list +\setlist[itemize,1]{label=\faAngleRight, nosep, leftmargin=2em} + +% Setup Array : new column type +\newcolumntype{R}[1]{>{\hfill}m{#1}} + +%Italian hyphenation for the word: ''corporations'' +\hyphenation{im-pre-se} + +% Setup fonts +\defaultfontfeatures{Mapping=tex-text} +% + +%------------------------------------------------------------------------------- +% Configuration for fonts +%------------------------------------------------------------------------------- +% ⚠️⚠️ 本文件已被改写:字体**全部**取自仓库公共字体包 ../fonts.tex。 +% +% 上游 awesom e-cv 的中文版原来这么配(共三处,都已删除): +% ① zh_cn-adobefonts_external.sty 里 \setCJKmainfont{AdobeSongStd-Light.otf} +% —— Adobe 宋/黑/楷/仿四款共 56 MB,商业授权,**不能随仓库分发**。 +% 而且那份文件还拿 HarmonyOS Sans 去冒充 Bold/Italic/SmallCaps: +% BoldFont = HarmonyOS_Sans_SC_Regular.ttf +% ItalicFont = HarmonyOS_Sans_SC_Regular.ttf +% 等于"加粗=不变"、"斜体=不变",标题的层次全靠字号撑,是个将就做法。 +% ② \setmainfont{SourceSansPro-Light}(localFont 分支) +% 9 个 .otf,SIL OFL 1.1 可用,但本仓库不打算为一份字体再带 4 MB。 +% ③ \setfontfamily\FA[Path=fonts/]{FontAwesome} +% Path 指向本目录下不存在的 fonts/ —— 那份图标字体在 TeX Live 里。 +% +% 现在的映射: +% 西文正文 Source Sans Pro Light → TeX Gyre Termes(本仓库自带) +% 中文正文 Adobe Song / HarmonyOS → OUC Serif(思源宋体子集,自带) +% 中文粗体 (原来=不变) → OUC Serif Bold(真粗体) +% 中文斜体 无 → OUC Kai(楷体代斜体,中文惯例) +% FontAwesome TeX Live 系统包 → 仓库 fonts/fontawesome/ +% +% ⚠️ 字体文件本体在 ../fonts/ 下,由 ../fonts.tex 统一设置, +% **不要在本文档或 .tex 里再写 \setCJKmainfont / \setmainfont**。 +% 下面只做"西文用哪一档"的局部调整。 +%------------------------------------------------------------------------------- + +% FontAwesome:图标字体已经放进仓库公共字体目录, +% ⚠️ 但**不要在这里重新声明 \FA** —— fontawesome.sty 自己在正文里就做了 +% \newfontfamily{\FA}[Path=../fonts/fontawesome/]{FontAwesome.otf} +% 且它在 \RequirePackage{fontawesome} 时就执行(早于本 cls 的后面几句)。 +% 这里再声明一次会报 "Font \FA already defined"(LaTeX3 的 +% \NewDocumentCommand 语义),所以只留注释说明。 +% +% 上游原来是 \setfontfamily\FA[Path=fonts/]{FontAwesome}, +% Path 指向本目录下并不存在的 fonts/ —— 只能靠系统字体兜底。 +% 现在路径写进 fontawesome.sty 了。 + +% 西文正文:上游用 Source Sans Pro Light(很细),本模板改用 Termes。 +% 注意这里**不能**再 \setmainfont —— 那会把 fonts.tex 设好的 Termes +% 整套换掉。只把上游代码里对 Light/Semibold 的引用映射到 Termes 的 +% 常规/粗体两档,保持"正文常规、强调加粗"的层级不变。 +\providecommand{\sourcesanslight}{\tnr} +\providecommand{\sourcesanssemibold}{\tnrb} + +%New length definition +% +% ⚠️ 这两个长度原来写死 14.8cm / 2.5cm,加起来 17.3cm,看着小于版心宽 +% 18cm(A4 21cm − 2×1.5cm 边距)。但 longtable 每列还有 \tabcolsep +% 各占左右一侧(默认 6pt),两列共 4 个 \tabcolsep = 24pt ≈ 0.85cm, +% 于是实际占宽 18.15cm → 溢出 4.48pt,报 +% Overfull \hbox (4.48311pt too wide) in alignment at lines 20--70 +% 这种"算着够、实际差一点"的溢出,换字号/字体后会时有时无,很难查。 +% +% 改法:不让它猜,直接用 \linewidth 减去左列与列间距。 +% 这样改页边距(geometry)后不用再跟着调数字。 +\newlength{\rightcolumnlength} +\newlength{\leftcolumn} +\setlength{\leftcolumn}{2.5cm} +\setlength{\rightcolumnlength}{% + \dimexpr\linewidth-\leftcolumn-4\tabcolsep\relax} + +% Font Awesome icons aliases +\newcommand{\mailSymbol}{\faEnvelope} +\newcommand{\mailSymbolO}{\faEnvelopeO} +\newcommand{\locationSymbol}{\faMapMarker} +\newcommand{\infoSymbol}{\faInfo} +\newcommand{\homeSymbol}{\faLink} +\newcommand{\weiboSymbol}{\faWeibo} +\newcommand{\linkedinSymbol}{\faLinkedin} +\newcommand{\mobileSymbol}{\faMobilePhone} +\newcommand{\githubSymbol}{\faGithub} + +\newcommand\link[2]{\color{linkcolor}\href{#1}{#2}\color{Black} } +\newcommand\important[1]{\textbf #1} + +% Create a tag +% Usage: \cvtag{} +\newcommand{\cvtag}[1]{% + %\tikz[baseline]\node[anchor=base,draw=darkGrey!70,rounded corners=0.5ex,inner xsep=1ex,inner ysep =0.55ex,text height=1.3ex,text depth=.25ex]{#1}; +\begin{tikzpicture} + \node[anchor=base,draw=darkGrey!70,rounded corners=0.5ex,inner xsep=1ex,inner ysep =0.4ex,text height=2ex,text depth=.25ex]{#1}; +\end{tikzpicture} +} + +% Create a chinese tag +% Usage: \cvtag{} +\newcommand{\cvtagcn}[1]{% + %\tikz[baseline]\node[anchor=base,draw=darkGrey!70,rounded corners=0.5ex,inner xsep=1ex,inner ysep =0.55ex,text height=1.3ex,text depth=.25ex]{#1}; + \begin{tikzpicture} + \node[anchor=base,draw=darkGrey!70,rounded corners=0.5ex,inner xsep=1ex,inner ysep =0.4ex,text height=2ex,text depth=.25ex]{#1}; + \end{tikzpicture} +} + +% Render author's name +% Usage: \user{}{} +\newcommand\user[2]{\color{accentcolor}{\LARGE #1 \textbf{#2}}\color{Black}} + +% Render a text with its symbol +% Usage; \socialtext{}{