Back to Details

chinese-copyright-application

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

中国软件著作权申请材料生成

Generation of Chinese Software Copyright Application Materials

核心原则

Core Principles

所有文档直接生成 
.tex
文件，用 XeLaTeX 编译为 PDF。
All documents are directly generated as 
.tex
files and compiled into PDF using XeLaTeX.

快速开始

Quick Start

  1. 环境检查与安装引导
  2. 收集著作权人信息与关键参数
  3. 分析项目结构和代码
  4. 生成四份 LaTeX 文档 + 编译脚本
  5. 生成截图清单
  6. 运行一致性校验
  1. Environment Check and Installation Guidance
  2. Collect Copyright Owner Information and Key Parameters
  3. Analyze Project Structure and Code
  4. Generate Four LaTeX Documents + Compilation Script
  5. Generate Screenshot List
  6. Run Consistency Check

工作流程

Workflow

第零步：环境检查

Step 0: Environment Check

在开始生成前，主动询问用户是否已安装 XeLaTeX 环境。执行 
xelatex --version
检测。
如已安装：继续下一步。
如未安装：告知用户需要安装 LaTeX 环境才能将 .tex 编译为 PDF，询问是否立即安装。用户同意后按以下命令执行：
  • macOS：
    brew install --cask basictex && sudo tlmgr update --self && sudo tlmgr install ctex xecjk fancyhdr lastpage fancyvrb tabularx enumitem float xcolor longtable collection-fontsrecommended
  • Linux：
    sudo apt install texlive-xetex texlive-lang-chinese texlive-latex-extra texlive-fonts-recommended
  • Windows：引导用户安装 TeX Live 完整版（https://www.tug.org/texlive/）
Before starting generation, proactively ask the user if the XeLaTeX environment is already installed. Execute 
xelatex --version
for detection.
If already installed: Proceed to the next step.
If not installed: Inform the user that a LaTeX environment is required to compile .tex files into PDF, and ask if they want to install it immediately. If the user agrees, execute the following commands:
  • macOS: 
    brew install --cask basictex && sudo tlmgr update --self && sudo tlmgr install ctex xecjk fancyhdr lastpage fancyvrb tabularx enumitem float xcolor longtable collection-fontsrecommended
  • Linux: 
    sudo apt install texlive-xetex texlive-lang-chinese texlive-latex-extra texlive-fonts-recommended
  • Windows: Guide the user to install the full version of TeX Live (https://www.tug.org/texlive/)

第一步：信息收集

Step 1: Information Collection

分两轮收集信息。
Collect information in two rounds.

第一轮：著作权人信息

Round 1: Copyright Owner Information

先检查项目根目录或用户工作目录下是否存在 
copyright-owner.json
。
如已存在：读取文件内容，向用户展示并确认是否有变更。用户确认无误则直接使用，跳到第二轮。
如不存在：首次使用，需引导用户提供信息并保存。先问著作权人是个人还是企业，然后收集对应信息。
个人需提供：姓名、身份证号、地址、邮编、联系人、电话、邮箱。
企业需提供完整工商信息（参考 requirements.md「著作权人信息」章节）：公司全称、统一社会信用代码、企业类型、法定代表人、注册资本、住所地址、登记机关、营业执照登记日期、联系人、电话、邮箱。
收集完成后将信息保存为 
copyright-owner.json
，格式如下：
json
{
  "type": "企业",
  "name": "星辰科技（北京）有限公司",
  "credit_code": "91110108MA01EXAMPLE",
  "enterprise_type": "有限责任公司",
  "legal_representative": "张三",
  "registered_capital": "伍佰万元整",
  "address": "北京市海淀区中关村大街1号",
  "registration_authority": "北京市海淀区市场监督管理局",
  "license_date": "2022年6月15日",
  "contact": "",
  "phone": "",
  "email": ""
}
此文件后续申请时直接复用，著作权人信息只需填一次。
First, check if 
copyright-owner.json
exists in the project root directory or the user's working directory.
If exists: Read the file content, display it to the user and confirm if there are any changes. If the user confirms it is correct, use it directly and proceed to the second round.
If not exists: For first-time use, guide the user to provide information and save it. First ask whether the copyright owner is an individual or an enterprise, then collect corresponding information.
For individuals, required information: Name, ID Card Number, Address, Postal Code, Contact Person, Phone Number, Email.
For enterprises, required complete industrial and commercial information (refer to the "Copyright Owner Information" section in requirements.md): Full Company Name, Unified Social Credit Code, Enterprise Type, Legal Representative, Registered Capital, Domicile Address, Registration Authority, Business License Registration Date, Contact Person, Phone Number, Email.
After collecting the information, save it as 
copyright-owner.json
in the following format:
json
{
  "type": "Enterprise",
  "name": "Star Technology (Beijing) Co., Ltd.",
  "credit_code": "91110108MA01EXAMPLE",
  "enterprise_type": "Limited Liability Company",
  "legal_representative": "Zhang San",
  "registered_capital": "Five Million Yuan",
  "address": "No.1, Zhongguancun Street, Haidian District, Beijing",
  "registration_authority": "Haidian District Market Supervision and Administration Bureau of Beijing",
  "license_date": "June 15, 2022",
  "contact": "",
  "phone": "",
  "email": ""
}
This file can be directly reused for subsequent applications, and the copyright owner information only needs to be filled in once.

第二轮：软件关键参数

Round 2: Key Software Parameters

自动分析项目后预填建议值，让用户确认：
参数说明
软件全称必须以"软件"二字结尾（如"智慧记账软件"），有辨识度，所有文档中完全一致。用户提供的名称若未以"软件"结尾，自动补上
版本号V1.0（首次申请统一使用 V1.0）
开发完成日期软件实际完成开发的日期
首次发表日期软件首次上线/发布的日期（≥ 开发完成日期）
源程序量项目实际总代码行数（可自动统计后让用户确认）
日期约束：开发完成日期 ≤ 首次发表日期 < 申请日期。生成时自动校验，不合规则提醒用户修改。
Automatically analyze the project and pre-fill suggested values for the user to confirm:
ParameterDescription
Full Software NameMust end with "Software" (e.g., "Smart Accounting Software"), with distinctiveness, and be completely consistent across all documents. If the name provided by the user does not end with "Software", automatically append it
Version NumberV1.0 (Unified use for first-time applications)
Development Completion DateActual date when software development was completed
First Publication DateDate when the software was first launched/published (≥ Development Completion Date)
Source Code VolumeActual total number of code lines in the project (can be automatically counted and confirmed by the user)
Date Constraints: Development Completion Date ≤ First Publication Date < Application Date. Automatically verify during generation and remind the user to modify if invalid.

第二步：项目分析与源程序生成

Step 2: Project Analysis and Source Code Generation

运行 
scripts/analyze_and_generate_source.py
完成项目分析和源程序 .tex 生成：
bash
python3 scripts/analyze_and_generate_source.py <项目路径> \
  --name "软件全称" \
  --version "V1.0" \
  --owner "著作权人名称" \
  --date "2025年4月30日" \
  --output copyright-materials/
脚本自动完成：
  1. 检测项目类型（微信小程序/Web/Node.js 等）
  2. 遍历代码文件，排除 node_modules 等无关目录
  3. 统计有效代码行数（排除空行和纯注释行），输出按文件类型的行数分布
  4. 按文件优先级排序，去除空行后提取前30页 + 后30页代码，生成源程序 .tex 文件
  5. 输出 
    project_analysis.json
    供后续文档生成参考
排版经验值（10pt + 
\small
Verbatim + 上下2cm左右1.5cm边距，基于实测校准）：
参数值说明
标准页容量50行/页满页代码行数
首页容量40行标题区域占约10行空间
后30页首页48行分隔标题占约2行空间
前30页目标1490行40 + 29×50
后30页目标1498行48 + 29×50
总目标2988行去除空行后的代码行数
代码量不足2988行时，脚本使用全部代码，不强凑60页。
脚本输出的 
total_lines_effective
即为申请表中的「源程序量」。
Run 
scripts/analyze_and_generate_source.py
to complete project analysis and source code .tex file generation:
bash
python3 scripts/analyze_and_generate_source.py <project-path> \
  --name "Full Software Name" \
  --version "V1.0" \
  --owner "Copyright Owner Name" \
  --date "April 30, 2025" \
  --output copyright-materials/
The script automatically completes:
  1. Detect project type (WeChat Mini Program/Web/Node.js, etc.)
  2. Traverse code files, exclude irrelevant directories such as node_modules
  3. Count valid code lines (exclude blank lines and pure comment lines), output line count distribution by file type
  4. Sort by file priority, extract first 30 pages + last 30 pages of code after removing blank lines, generate source code .tex file
  5. Output 
    project_analysis.json
    for reference in subsequent document generation
Typesetting Experience Values (10pt + 
\small
Verbatim + 2cm top/bottom margins, 1.5cm left/right margins, calibrated based on actual measurement):
ParameterValueDescription
Standard Page Capacity50 lines/pageNumber of code lines per full page
First Page Capacity40 linesTitle area occupies about 10 lines of space
First Page of Last 30 Pages48 linesSeparator title occupies about 2 lines of space
Target for First 30 Pages1490 lines40 + 29×50
Target for Last 30 Pages1498 lines48 + 29×50
Total Target2988 linesNumber of code lines after removing blank lines
If the code volume is less than 2988 lines, the script uses all code and does not force it to 60 pages.
The 
total_lines_effective
output by the script is the "Source Code Volume" in the application form.

第三步：生成四份文档

Step 3: Generate Four Documents

所有文档的 LaTeX 编写规范见 references/requirements.md。每份文档的模板见 references 目录下对应的 
.tex
模板文件。
LaTeX writing specifications for all documents can be found in references/requirements.md. Templates for each document are in the corresponding 
.tex
template files in the references directory.

输出文件夹与命名

Output Folder and Naming

输出目录：
copyright-materials/
生成文档前先创建目录结构：
bash
mkdir -p copyright-materials/images
文件命名规范为「软件全称 + 文档类型」，举例：
  • 智慧记账软件著作权登记申请表.tex
    / 
    .pdf
  • 智慧记账软件源程序.tex
    / 
    .pdf
  • 智慧记账软件用户手册.tex
    / 
    .pdf
  • 智慧记账软件设计说明书.tex
    / 
    .pdf
  • build_all.sh
  • images/
    （图片目录，用户后续在此放入截图）
Output directory: 
copyright-materials/
Create the directory structure before generating documents:
bash
mkdir -p copyright-materials/images
File naming convention: "Full Software Name + Document Type", example:
  • Smart Accounting Software Copyright Registration Application Form.tex
    / 
    .pdf
  • Smart Accounting Software Source Code.tex
    / 
    .pdf
  • Smart Accounting Software User Manual.tex
    / 
    .pdf
  • Smart Accounting Software Design Specification.tex
    / 
    .pdf
  • build_all.sh
  • images/
    (Image directory, where users will place screenshots later)

3.1 著作权登记申请表

3.1 Copyright Registration Application Form

模板：application-form-template.tex
格式要求：
  • documentclass: 
    a4paper,12pt,article
  • 表格使用 
    tabularx
    环境
  • 分为：基本信息、著作权人信息、开发者信息、软硬件环境信息、软件基础信息、软件技术特点、软件功能简介、备注
  • 申请表字段有严格字数限制（详见 requirements.md「字数限制」章节），生成后必须校验
字数限制速查：
  • 硬件环境/操作系统/开发工具/运行平台/支撑环境：各 ≤50 字符
  • 开发目的/面向领域：各 ≤50 字
  • 主要功能：≤200 字
  • 技术特点：≤100 字
Template: application-form-template.tex
Format Requirements:
  • documentclass: 
    a4paper,12pt,article
  • Use 
    tabularx
    environment for tables
  • Divided into: Basic Information, Copyright Owner Information, Developer Information, Software and Hardware Environment Information, Basic Software Information, Software Technical Features, Software Function Introduction, Remarks
  • Strict word count limits for application form fields (see the "Word Count Limits" section in requirements.md), must be verified after generation
Quick Reference for Word Count Limits:
  • Hardware Environment/Operating System/Development Tools/Running Platform/Support Environment: Each ≤50 characters
  • Development Purpose/Target Field: Each ≤50 words
  • Main Functions: ≤200 words
  • Technical Features: ≤100 words

3.2 源程序

3.2 Source Code

由第二步的脚本自动生成，无需手动编写。生成规则详见 requirements.md「源程序文档要求」。
Automatically generated by the script in Step 2, no manual writing required. Generation rules can be found in the "Source Code Document Requirements" section of requirements.md.

3.3 用户手册

3.3 User Manual

模板：user-manual-template.tex
内容结构：
  1. 软件简介（概述 + 主要特点）
  2. 功能概述（功能列表 + 适用场景）
  3. 安装与使用说明（系统要求 + 进入方式 + 登录说明）
  4. 主要功能说明（每个功能的操作步骤，配截图）
  5. 注意事项
  6. 技术支持
截图要求：
  • 定义 
    \screenshot{文件名}{标题}
    宏，宽度 0.35\textwidth
  • 对尚未提供的截图，LaTeX 中仍放置 
    \screenshot
    调用
  • 同时输出截图清单（见第四步）
Template: user-manual-template.tex
Content Structure:
  1. Software Introduction (Overview + Main Features)
  2. Function Overview (Function List + Application Scenarios)
  3. Installation and Usage Instructions (System Requirements + Access Method + Login Instructions)
  4. Main Function Instructions (Operation steps for each function, with screenshots)
  5. Notes
  6. Technical Support
Screenshot Requirements:
  • Define the 
    \screenshot{filename}{title}
    macro with width 0.35\textwidth
  • For screenshots not yet provided, still place the 
    \screenshot
    call in LaTeX
  • Output a screenshot list at the same time (see Step 4)

3.4 设计说明书

3.4 Design Specification

模板：design-doc-template.tex
内容结构：
  1. 软件概述（简介 + 开发背景 + 设计目标）
  2. 需求分析（功能/性能/安全需求）
  3. 总体设计（系统架构 + 模块划分 + 技术选型 + 运行环境）
  4. 详细设计（各模块功能、处理流程，配截图）
  5. 数据结构设计
  6. 接口设计（内部接口 + 外部 API 列表）
  7. 界面设计（配截图）
  8. 安全设计
  9. 测试设计
Template: design-doc-template.tex
Content Structure:
  1. Software Overview (Introduction + Development Background + Design Objectives)
  2. Requirements Analysis (Functional/Performance/Security Requirements)
  3. Overall Design (System Architecture + Module Division + Technology Selection + Running Environment)
  4. Detailed Design (Functions and processing flow of each module, with screenshots)
  5. Data Structure Design
  6. Interface Design (Internal Interfaces + External API List)
  7. Interface Design (with screenshots)
  8. Security Design
  9. Test Design

第四步：截图管理

Step 4: Screenshot Management

分析项目代码（页面文件、弹窗组件、模态框等），生成截图清单 
screenshot-list.md
：
| 编号 | 文件名 | 描述 | 触发方式 | 使用位置 |
|------|--------|------|----------|----------|
| 01 | 图1-首页空状态.png | 首页空状态 | 首次进入首页 | 用户手册§3、设计说明书§4.1 |
| 02 | 图2-搜索结果列表.png | 搜索结果 | 输入关键词搜索 | 用户手册§4.1、设计说明书§4.1 |
LaTeX 文档中 
\screenshot{文件名}{标题}
宏已内置 
images/
路径前缀，用户只需将截图放到 
images/
目录，文件名与清单中一致即可，编译时自动找到。
Analyze project code (page files, pop-up components, modal boxes, etc.) to generate the screenshot list 
screenshot-list.md
:
| No. | File Name | Description | Trigger Method | Usage Location |
|------|--------|------|----------|----------|
| 01 | Figure1-Homepage Empty State.png | Homepage empty state | First entry to homepage | User Manual §3, Design Specification §4.1 |
| 02 | Figure2-Search Result List.png | Search results | Enter keywords to search | User Manual §4.1, Design Specification §4.1 |
The 
\screenshot{filename}{title}
macro in LaTeX documents has a built-in 
images/
path prefix. Users only need to place screenshots in the 
images/
directory with filenames consistent with those in the list, and they will be automatically found during compilation.

交付截图任务给用户

Assign Screenshot Task to User

文档初版生成完毕后，暂停自动流程，向用户输出以下操作指引（将 
<输出目录>
替换为实际路径）：
文档初版已全部生成完毕，接下来需要你手动截取软件界面截图。
截图保存路径：
<输出目录>/images/
请按照上方截图清单，逐一截取对应的软件界面截图，保存到该目录。文件名与清单中的「文件名」列保持一致（如 
图1-首页.png
）。
截图添加完成后回复我一声，我会重新编译所有文档生成最终 PDF。
等用户确认截图完成后，再继续执行第五步（编译）和第六步（校验）。
After the initial version of the documents is generated, pause the automatic process and output the following operation guide to the user (replace 
<output directory>
with the actual path):
The initial version of all documents has been generated. Next, you need to manually capture screenshots of the software interface.
Screenshot save path: 
<output directory>/images/
Please follow the screenshot list above to capture the corresponding software interface screenshots one by one and save them to this directory. Keep the file names consistent with the "File Name" column in the list (e.g., 
Figure1-Homepage.png
).
Please let me know after adding all screenshots, and I will recompile all documents to generate the final PDF.
Continue to Step 5 (Compilation) and Step 6 (Verification) after the user confirms that screenshots are completed.

第五步：编译脚本

Step 5: Compilation Script

生成 
build_all.sh
，模板见 references/build-script-template.sh。
脚本要点：
  • 设置 PATH 包含 TeX 路径
  • 每个 .tex 文件编译两遍（确保页码引用正确）
  • 清理 .aux/.log/.out 等临时文件
  • 输出每个 PDF 的文件大小
Generate 
build_all.sh
, template can be found in references/build-script-template.sh.
Key Points of the Script:
  • Set PATH to include TeX path
  • Compile each .tex file twice (to ensure correct page number references)
  • Clean up temporary files such as .aux/.log/.out
  • Output the file size of each PDF

第六步：一致性校验

Step 6: Consistency Check

生成完所有文档后，自动校验以下内容并输出校验报告：
校验项校验位置
软件全称申请表、源程序页眉和首页、用户手册标题/页眉、设计说明书标题/页眉
版本号所有文档的页眉和正文中
源程序量申请表中的数字 = 源程序文档首页标注的数字
著作权人名称每个文档首页
日期各文档中引用的日期一致
字数限制申请表各字段不超限
校验通过则输出"✓ 一致性校验通过"，否则列出不一致项。
After generating all documents, automatically verify the following content and output a verification report:
Verification ItemVerification Location
Full Software NameApplication form, source code header and first page, user manual title/header, design specification title/header
Version NumberHeaders and main text of all documents
Source Code VolumeNumber in application form = Number marked on the first page of the source code document
Copyright Owner NameFirst page of each document
DateDates referenced in each document are consistent
Word Count LimitsAll fields in the application form do not exceed limits
Output "✓ Consistency Check Passed" if verified successfully, otherwise list inconsistent items.

统一 LaTeX 排版规范

Unified LaTeX Typesetting Specifications

以下规范适用于申请表、用户手册、设计说明书（源程序文档例外，有专门规范）：
The following specifications apply to the application form, user manual, and design specification (source code documents are exceptions with dedicated specifications):

页面设置

Page Settings

latex
\documentclass[a4paper,12pt]{article}
\usepackage[UTF8,heading=true]{ctex}
\usepackage[top=2.5cm,bottom=2.5cm,left=2.5cm,right=2.5cm]{geometry}
latex
\documentclass[a4paper,12pt]{article}
\usepackage[UTF8,heading=true]{ctex}
\usepackage[top=2.5cm,bottom=2.5cm,left=2.5cm,right=2.5cm]{geometry}

页眉页脚

Header and Footer

latex
\pagestyle{fancy}
\fancyhf{}
\fancyhead[C]{软件全称V1.0\quad 文档类型}
\fancyfoot[C]{第 \thepage\ 页\quad 共 \pageref{LastPage} 页}
\renewcommand{\headrulewidth}{0.5pt}
\renewcommand{\footrulewidth}{0.5pt}
\fancypagestyle{plain}{\pagestyle{fancy}}
页眉格式：
软件全称V版本号  文档类型
（如：智慧记账软件V1.0 用户手册） 页脚格式：
第 X 页  共 XX 页
页眉页脚均有分隔线（0.5pt）
latex
\pagestyle{fancy}
\fancyhf{}
\fancyhead[C]{Full Software NameV1.0\quad Document Type}
\fancyfoot[C]{Page \thepage\quad Total \pageref{LastPage} Pages}
\renewcommand{\headrulewidth}{0.5pt}
\renewcommand{\footrulewidth}{0.5pt}
\fancypagestyle{plain}{\pagestyle{fancy}}
Header format: 
Full Software NameVVersion Number  Document Type
(e.g., Smart Accounting SoftwareV1.0 User Manual) Footer format: 
Page X  Total XX Pages
Both header and footer have separators (0.5pt)

中文排版

Chinese Typesetting

latex
\setlength{\parindent}{2em}          % 段首缩进 2 字符
\setlength{\parskip}{0.3em}
\renewcommand{\baselinestretch}{1.3}  % 1.3 倍行距
latex
\setlength{\parindent}{2em}          % First-line indent of 2 characters
\setlength{\parskip}{0.3em}
\renewcommand{\baselinestretch}{1.3}  % 1.3 line spacing

列表

Lists

latex
\begin{itemize}[leftmargin=2em]
\begin{enumerate}[leftmargin=2em]
latex
\begin{itemize}[leftmargin=2em]
\begin{enumerate}[leftmargin=2em]

截图宏

Screenshot Macro

在文档 preamble 中设置图片搜索路径，并定义截图宏：
latex
\graphicspath{{images/}}

\newcommand{\screenshot}[2]{%
  \begin{figure}[H]
    \centering
    \includegraphics[width=0.35\textwidth]{#1}
    \caption{#2}
  \end{figure}
}
调用时只需 
\screenshot{图1-首页.png}{首页}
，LaTeX 会自动在 
images/
目录下查找图片文件。
Set the image search path in the document preamble and define the screenshot macro:
latex
\graphicspath{{images/}}

\newcommand{\screenshot}[2]{%
  \begin{figure}[H]
    \centering
    \includegraphics[width=0.35\textwidth]{#1}
    \caption{#2}
  \end{figure}
}
When calling, just use 
\screenshot{Figure1-Homepage.png}{Homepage}
, and LaTeX will automatically find the image file in the 
images/
directory.

文档首页结构

First Page Structure of Documents

每份文档首页统一格式：
latex
\begin{center}
  {\LARGE\bfseries 软件全称\quad 文档类型}
  \vspace{0.8em}
  {\large 著作权人：公司全称}
  \vspace{0.3em}
  软件版本：V1.0\qquad 发布日期：YYYY年M月D日
\end{center}
Unified format for the first page of each document:
latex
\begin{center}
  {\LARGE\bfseries Full Software Name\quad Document Type}
  \vspace{0.8em}
  {\large Copyright Owner: Full Company Name}
  \vspace{0.3em}
  Software Version: V1.0\qquad Release Date: YYYY-M-D
\end{center}

特殊项目类型处理

Special Project Type Handling

微信小程序

WeChat Mini Program

  • 软件分类：移动应用软件——小程序
  • 运行平台：iOS、Android、Windows、macOS、HarmonyOS（微信客户端）
  • 运行支撑环境：微信客户端（支持小程序的任意版本）
  • 技术特点类型选择：小程序
  • Software Category: Mobile Application Software — Mini Program
  • Running Platform: iOS, Android, Windows, macOS, HarmonyOS (WeChat Client)
  • Running Support Environment: WeChat Client (any version that supports Mini Programs)
  • Technical Feature Type Selection: Mini Program

Web 应用

Web Application

  • 软件分类：应用软件——Web应用
  • 运行平台：Windows、macOS、Linux（浏览器）
  • 运行支撑环境：Chrome/Firefox/Safari 等浏览器
  • Software Category: Application Software — Web Application
  • Running Platform: Windows, macOS, Linux (Browser)
  • Running Support Environment: Browsers such as Chrome/Firefox/Safari

移动 App

Mobile App

  • 软件分类：移动应用软件——App
  • 运行平台：根据实际支持列出（iOS/Android/HarmonyOS 等）
  • Software Category: Mobile Application Software — App
  • Running Platform: List according to actual support (iOS/Android/HarmonyOS, etc.)

跨平台项目

Cross-Platform Projects

  • Electron 应用：Windows、macOS、Linux
  • Flutter/React Native：iOS、Android（如支持桌面端则加上 Windows、macOS、Linux）
  • Electron Application: Windows, macOS, Linux
  • Flutter/React Native: iOS, Android (add Windows, macOS, Linux if desktop support is available)

LaTeX 环境依赖

LaTeX Environment Dependencies

环境检查与安装流程见「第零步」。
必需宏包：ctex、xecjk、fancyhdr、lastpage、fancyvrb、tabularx、enumitem、float、xcolor、longtable、graphicx、hyperref、array、geometry
编译命令：
xelatex -interaction=nonstopmode 文件名.tex
（运行两遍）
Environment check and installation process can be found in "Step 0".
Required Packages: ctex, xecjk, fancyhdr, lastpage, fancyvrb, tabularx, enumitem, float, xcolor, longtable, graphicx, hyperref, array, geometry
Compilation Command: 
xelatex -interaction=nonstopmode filename.tex
(run twice)

参考文档

Reference Documents

  • 申请要求详细说明
  • 申请表 LaTeX 模板
  • 源程序 LaTeX 模板
  • 用户手册 LaTeX 模板
  • 设计说明书 LaTeX 模板
  • 编译脚本模板
  • Detailed Application Requirements
  • LaTeX Template for Application Form
  • LaTeX Template for Source Code
  • LaTeX Template for User Manual
  • LaTeX Template for Design Specification
  • Compilation Script Template