paper-polish

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Polishing and reviewing research papers in LaTeX

润色与审核LaTeX研究论文

On writing

写作相关

内容要点

Your paper should be easily comprehensible by its reviewers. They are far less familiar with your work than you. They may not be an expert on the topic and may not be able to afford much time on your paper.
The introduction should convey curiosity or excitement (new problem, new solution, improved solution, impressive results, or high impact), the design novelty, substantiality, and correctness, and the evaluation relevancy and comprehensiveness.
Conciseness: Remove every word that contributes no meaning, such as
```
kind of
```
.
Use proper tenses:
- 1
- 2
- 3

你的论文应让审稿人易于理解。他们对你的研究远不如你熟悉，可能并非该领域专家，也可能无法为你的论文投入过多时间。
引言部分应传递出吸引力或兴奋点（如新问题、新解决方案、改进方案、亮眼成果或高影响力），同时要体现设计的创新性、充实性与正确性，以及评估的相关性和全面性。
简洁性：删除所有无意义的词汇，例如
```
kind of
```
。
正确使用时态：
- 1
- 2
- 3

Grammar

语法规范

Section titles should have consistent capitalization.
- Title Case: Capitalize the first and last words and all major words in between.
  - Good: Introduction to Fuzzing with LLMs
- Sentence case: Capitalize only the first word and proper nouns.
  - Good: Introduction to fuzzing with LLMs
- Choose one style and be consistent throughout the paper.
Avoid passive voice unless strongly justifiable. Passive voice is ambiguous because it has no subject unless followed by "by...".
- Bad: LLM was applied to fuzzing. (Who applied it? The authors or someone else?)
- Good: We applied LLM to fuzzing.
Avoid nominalization.
- Bad: He made a proposal to use Rust.
- Good: He proposed to use Rust.
Avoid "There is/are".
- Bad: There are many developers of Rust.
- Good: Many developers use Rust.
- Good: Rust has many developers.
"Which" vs "that": Use "which" in a nonrestrictive clause and "that" in a restrictive clause. More...
- Wrong: Rust that is safe is popular. (This is wrong because there is only one Rust.)
- Right: Rust, which is safe, is popular.
Distinguish coordinating conjunction vs conjunctive adverbs.
- Wrong: C is dangerous, Rust is safe. (Cannot join two sentences by a comma)
- Right: C is dangerous, but Rust is safe.
- Wrong: C is dangerous, however Rust is safe.
- Right: C is dangerous; however, Rust is safe.
"Fewer" modifies countable nouns whereas "less" uncountable nouns.
- Wrong: ten items or less
- Right: ten items or fewer
- Wrong: fewer feedback
- Right: less feedback
Use articles (
```
a
```
,
```
an
```
,
```
the
```
) properly.
- A singular countable noun must be preceded by an article.
  - Wrong: I wrote Rust program.
  - Right: I wrote a Rust program.
  - Right: I wrote Rust programs.
- ```
The
```
  must have a reference that is unique either by fact or in the context.
  - Right: the first Rust programmer (unique by fact)
  - Right: Our team has a Rust and a C++ programmer. The Rust programmer produces the fastest, most robust code. (unique in the context)
  - Wrong: Our team has two Rust and two C++ programmers. The Rust programmer is more productive than the C++ programmer.
Distinguish between compare with and compare to
- Right: Rust is safer compared with C.
- Right: Some people compare Rust to a panacea for memory safety problems.

章节标题的大小写格式应保持一致。
- 标题式大小写：首词、尾词以及中间所有主要词汇首字母大写。
  - 示例：Introduction to Fuzzing with LLMs
- 句子式大小写：仅首词和专有名词首字母大写。
  - 示例：Introduction to fuzzing with LLMs
- 选择一种格式后，整篇论文需保持统一。
除非有充分理由，否则避免使用被动语态。被动语态存在歧义，因为它没有主语，除非后续跟上“by...”。
- 错误示例：LLM was applied to fuzzing.（谁应用的？作者还是其他人？）
- 正确示例：We applied LLM to fuzzing.
避免使用名词化结构。
- 错误示例：He made a proposal to use Rust.
- 正确示例：He proposed to use Rust.
避免使用“There is/are”结构。
- 错误示例：There are many developers of Rust.
- 正确示例：Many developers use Rust.
- 正确示例：Rust has many developers.
“Which”与“that”的区别：在非限制性定语从句中使用“which”，在限制性定语从句中使用“that”。更多说明...
- 错误示例：Rust that is safe is popular.（错误，因为Rust只有一种）
- 正确示例：Rust, which is safe, is popular.
区分并列连词与连接副词。
- 错误示例：C is dangerous, Rust is safe.（不能仅用逗号连接两个句子）
- 正确示例：C is dangerous, but Rust is safe.
- 错误示例：C is dangerous, however Rust is safe.
- 正确示例：C is dangerous; however, Rust is safe.
“Fewer”修饰可数名词，“less”修饰不可数名词。
- 错误示例：ten items or less
- 正确示例：ten items or fewer
- 错误示例：fewer feedback
- 正确示例：less feedback
正确使用冠词（
```
a
```
、
```
an
```
、
```
the
```
）。
- 单数可数名词前必须加冠词。
  - 错误示例：I wrote Rust program.
  - 正确示例：I wrote a Rust program.
  - 正确示例：I wrote Rust programs.
- ```
The
```
  用于指代在事实或上下文语境中唯一的事物。
  - 正确示例：the first Rust programmer（事实层面唯一）
  - 正确示例：Our team has a Rust and a C++ programmer. The Rust programmer produces the fastest, most robust code. （上下文语境中唯一）
  - 错误示例：Our team has two Rust and two C++ programmers. The Rust programmer is more productive than the C++ programmer.
区分compare with与compare to
- 正确示例：Rust is safer compared with C.
- 正确示例：Some people compare Rust to a panacea for memory safety problems.

On LaTeX

LaTeX相关

Use modern implementations of LaTeX to take advantage of Unicode and other useful features.
- Use LuaLaTeX instead of LaTeX or pdfLaTeX
- Use BibLaTeX for
```
acmart
```
  and
```
ieeetrans
```
  templates instead of BibTex
Use correct typefaces. Particularly, italics should be used for variables but not for descriptive terms. More...
- Wrong: $t_{max}$
- Right: $t_\text{max}$
Do not manually add separators in large numbers.
```
\usepackage{siunitx}
```
. Then, wrap large numbers in
```
\num{}
```
.
- Bad: 12,345
- Good:
```
\num{12345}
```
Do not manually type reference names, such as Table, Figure, Theorem. Instead,
```
\usepackage{hyperref}
```
, and then
```
\autoref{fig:xxx}
```
,
```
\autoref{sec:xxx}
```
,
```
\autoref{table:xxx}
```
.
- Not recommended: In Figure~\ref{fig:overview}
- Good: In \autoref{fig:overview}

使用LaTeX的现代实现版本，以支持Unicode等实用功能。
- 使用LuaLaTeX替代LaTeX或pdfLaTeX
- 对于
```
acmart
```
  和
```
ieeetrans
```
  模板，使用BibLaTeX而非BibTex
使用正确的字体。特别注意，斜体应用于变量而非描述性术语。更多说明...
- 错误示例：$t_{max}$
- 正确示例：$t_\text{max}$
不要手动为大数字添加分隔符。使用
```
\usepackage{siunitx}
```
包，然后将大数字包裹在
```
\num{}
```
中。
- 错误示例：12,345
- 正确示例：
```
\num{12345}
```
不要手动输入引用名称，如Table、Figure、Theorem。应使用
```
\usepackage{hyperref}
```
包，然后使用
```
\autoref{fig:xxx}
```
、
```
\autoref{sec:xxx}
```
、
```
\autoref{table:xxx}
```
。
- 不推荐：In Figure~\ref{fig:overview}
- 推荐：In \autoref{fig:overview}

Structure

文档结构

```
main.tex
```
is the entry root of the LaTeX project, containing the
```
usepackage
```
commands and the document structure.
```
src/
```
contains all the sections.
```
tables/
```
contains all the tables.
```
figures/
```
or
```
fig/
```
contains the figures. Figures are PDF files or
```
.tex
```
files.
```
.tex
```
in figures are algorithms.
```
code/
```
contains code listings used in the text.

```
main.tex
```
是LaTeX项目的入口文件，包含
```
usepackage
```
命令和文档结构。
```
src/
```
目录存放所有章节内容。
```
tables/
```
目录存放所有表格。
```
figures/
```
或
```
fig/
```
目录存放图片。图片格式可为PDF或
```
.tex
```
文件，其中
```
.tex
```
文件用于编写算法。
```
code/
```
目录存放正文中引用的代码清单。

paper-polish

Original

Translation

Polishing and reviewing research papers in LaTeX

润色与审核LaTeX研究论文

On writing

写作相关

Contents

内容要点

Grammar

语法规范

On LaTeX

LaTeX相关

Structure

文档结构