2.3 Special characters 2.3.1 Whitespace characters Aside from the line terminator sequence, the ASCII horizontal space char- acter (0x20) is the only whitespace character that appears anywhere in a source the corresponding octal (e.g. \012) or Unicode (e.g. \u000a) escape. 2.3.3 Non-ASCII characters For the remaining non-ASCII characters, either the actual Unicode character (e.g. ∞) or the equivalent Unicode Tip: Never make your code less readable simply out of fear that some programs might not handle non-ASCII characters properly. If that should happen, those programs are broken and they must be fixed. 3 Source

length. Non-ASCII Characters Non-ASCII characters should be rare, and must use UTF-8 formatting. You shouldn’t hard-code user-facing text in source, even English, so use of non- ASCII characters should appropriate to hard-code the non-ASCII string(s) used in those data files as delimiters. More commonly, unittest code (which does not need to be localized) might contain non-ASCII strings. In such cases, you should use UTF-8, since that is an encoding understood by most tools able to handle more than just ASCII. Hex encoding is also OK, and encouraged where it enhances readability — for example, "\xEF\xBB\xBF"

only has an effect if the smart extension is enabled for the input format used.) --ascii[=true|false] Use only ASCII characters in output. Currently supported for XML and HTML formats (which use entities line defaults file --self-contained self-contained: true --html-q-tags html-q-tags: true --ascii ascii: true --reference-links reference-links: true --reference-location block reference-location: using JavaScript or treated differently in CSS. Extension: ascii_identifiers Causes the identifiers produced by auto_identifiers to be pure ASCII. Accents are stripped off of accented Latin letters, and

files (Excellon format), for fabrication. *.pos Position files (ASCII format), for automatic insertion machines. *.rpt Report files (ASCII format), for documentation. *.ps Plot files (Postscript), for PCB *.CMPcbDoc Altium Circuit Maker PCB *.CSPcbDoc Altium Circuit Studio PCB *.pcb P-Cad 200x ASCII PCB *.txt , *.fab Fabmaster PCB 10 NOTE KiCad does not support schematics with multiple top-level

files (Excellon format), for fabrication. *.pos Position files (ASCII format), for automatic insertion machines. *.rpt Report files (ASCII format), for documentation. *.ps Plot files (Postscript), for PCB *.CMPcbDoc Altium Circuit Maker PCB *.CSPcbDoc Altium Circuit Studio PCB *.pcb P-Cad 200x ASCII PCB *.txt , *.fab Fabmaster PCB NOTE KiCad does not support schematics with multiple top-level

files. 4 制造和文档文件 *.gbr Gerber 文件，用于制造。 *.drl 钻孔文件（Excellon 格式），用于制造。 *.pos 位置文件（ASCII 格式），用于自动贴片机。 *.rpt 报告文件（ASCII 格式），用于记录。 *.ps 图表文件（Postscript），用于文档。 *.pdf 图表文件(PDF 格式)，用于文档。 *.svg 绘图文件（SVG 格式），用于文档。 PCB *.CMPcbDoc Altium Circuit Maker PCB *.CSPcbDoc Altium Circuit Studio PCB *.pcb P-Cad 200x ASCII PCB *.txt , *.fab Fabmaster PCB NOTE KiCad does not support schematics with multiple top-level

files (Excellon format), for fabrication. *.pos Position files (ascii format), for automatic insertion machines. *.rpt Report files (ascii format), for documentation. *.ps Plot files (postscript), for

files (Excellon format), for fabrication. *.pos Position files (ascii format), for automatic insertion machines. *.rpt Report files (ascii format), for documentation. *.ps Plot files (postscript), for

files (Excellon format), for fabrication. *.pos Position files (ASCII format), for automatic insertion machines. *.rpt Report files (ASCII format), for documentation. *.ps Plot files (Postscript), for

files (Excellon format), for fabrication. *.pos Position files (ASCII format), for automatic insertion machines. *.rpt Report files (ASCII format), for documentation. *.ps Plot files (Postscript), for