zh stringlengths 1 360 | en stringlengths 1 967 | sco float64 1 1 |
|---|---|---|
9.3 实现级别 2 | 9.3 Usage level 2 | 1 |
实现级别 2 包含实现级别 1。 | Level 2 execution incorporates Level 1 usage. | 1 |
此外 ,实现级别 2 还文持《通用 规范 汉字 表 }中的没有包合在实级别 1 之内的编码汉字。 | The coded Chinese characters within the "Common Detail Chinese Character Table," which are truant from the genuine level 1 execution, are moreover upheld. | 1 |
《 通用规范汉字表) 所收汉字在本文件中的代码位置和字形, 见附录下。 | See the reference section for the code areas and glyphs of the Chinese characters included in this document's "Common Standard Chinese Character List." | 1 |
系统软件及支撑软件,应满足实现级别 2 的要求 。 | Framework computer program and assistant program must follow to level 2 benchmarks. | 1 |
注: 系统软件及文撑软件包括但不限于操作系统,数据库管理系统.中间件( 软件产品分类的信息见 GB/ 工 36475)。 | Note: Working frameworks, database administration frameworks, and middleware are cases of framework program and supporting program. But they are not the as it were ones (see GB/Work 36475 for points of interest on computer program item classification). | 1 |
9.4 实现级别 3 | 9.4 Usage level 3 | 1 |
实现级别 3 包含实现级别 2。 | Execution level 3 contains execution level 2. | 1 |
此外,实现级别 3 还文持本文件规定的全部汉字及表 3 中的康黑部首。 | Besides, the Kanghe radicals in Table 3 and all of the Chinese characters depicted in this detail are upheld by execution level 3 as well. | 1 |
用于政务服务和公共服务的产品应满足实现级卉 3 的要求。 | Things utilized for open and administrative administrations must follow to level 3 determinations. | 1 |
注: 政务服务和 共服务行业包括但不限于铁路运输业.道路运输业 \ 水上运输业.航空运输业、多式联运和运输代理业、邮政业、货币金融服、保险业、土地、管理业、卫生、国家机构、社会保障等 (行业分类的信息见 GB/ 工 4754)。 | Government benefit and open benefit segments incorporate, but are not constrained to railroad. street, water, discuss, multimodal, and office of transportation, postal benefit, money related and budgetary administrations, protections, arrive, administration, wellbeing, state organizations, social security, etc. (for da... | 1 |
附录 A (规范性 ) | Reference section A (Regulating) | 1 |
双字字符表 | twofold character table | 1 |
A.1 表的内容 | A.1 Substance of the table | 1 |
本表给出双字节编码字符的字形及代码 ,同时给出了该字符对应的 GB/T 13000 代码位置。 | In expansion to giving the double-byte encoded character's glyph and code, this table moreover gives the character's identical GB/T 13000 code position. | 1 |
A.2 表的说明 | A.2 Clarification of the table | 1 |
示例如下: | Illustrations are as takes after: | 1 |
第一字节第二字节低位 | The primary and moment bytes are moo | 1 |
双字节 3 区 | Double-byte range 3 | 1 |
第二字节高位 GBCT 13000 代码位置 | Moment byte tall bit GBCT 13000 code position | 1 |
附录B (规苑性) | Reference section B (administrative) | 1 |
表意文字描述符 | Ideographic descriptor | 1 |
本附录收录了 GB/TI 13000 规定的表意文字描述符 13 个,并给出了它们的图形.代码位置和功能描述。 | The 13 ideographic descriptors recorded in GB/TI 13000 are compiled in this reference section along with their visuals. Code situations, and work portrayals. | 1 |
有具体内容见表 B.1。 | See Table B.1 for points of interest. | 1 |
表 B.1 表意文字描述符的图形、代码位置和功能描述 | Table B.1 gives utilitarian, realistic, and code-location definitions of ideographic descriptors | 1 |
本文件的码位 GB/T 13000 的码位功能描述相似而不等,用于借某字表达外字 | In terms of work portrayal, the code focuses in this report are comparable to those in GB/T 13000 and are utilized to communicate outside characters by appropriating a particular word | 1 |
左右结构 | Cleared out and right structure | 1 |
上下结构 | Upper and lower structure | 1 |
左中右结构 | Cleared out center right structure | 1 |
上中下结构 | Upper center lower structure | 1 |
全包围结构 | Completely encased structure | 1 |
回下包围结构 | Returning to the quick environment | 1 |
回上包围结构 | Returning to the quick environment | 1 |
回右包围结构 | Back right encasing structure | 1 |
回右下包围结构 | Return to the encasing structure within the lower right | 1 |
回左下包围结构 | Go back to the walled in area on the lower cleared out | 1 |
回右上包围结构 | Return to the upper right walled in area | 1 |
租套结构 | Rent structure | 1 |
附录 C (规范性) | Reference section C (Regulating) | 1 |
四字书字符表 | Character table for a four-character book | 1 |
C.1 表的内容 | C.1 Substance of the table | 1 |
本表给出了汉字和部分少数民族文字的字形及代码,同时还给出了该字符对应的 GB/TI 13000 代码但位置,其他部分的字形从略。 | The positions of the characters and the glyphs for other components are avoided from this table, which too gives the proportionate GB/TI 13000 code for Chinese characters and a few minority dialects. | 1 |
C.2表的说明 | Investigation of Table C.2 | 1 |
附录D(资料性) | Reference section D (instructive) | 1 |
部分字符和代码的说明 | Different characters and codes clarified | 1 |
D.1 调整过的 18 个GB/T 13000 代码位置 | 18 GB/T 13000 code places were balanced in D.1 | 1 |
B 18030 一 2005 规定了 10 个竖排标点和 8 个汉字构件 在 GB/I 13000 中的临时代码位置,这些代码位置在本文件中进行了调整,如表 D.1 所示。 | Ten vertical accentuation marks and eight Chinese character components' transitory code places in GB/I 13000 are indicated in B 18030-2005; these code positions have been altered in this report and are given in Table D.1. | 1 |
D.1 调整后的代码对应关系〈 续 ) | D.1 Balanced Code Correspondence <Proceeded) | 1 |
本文件及 GB 18030 一 2005 的GB 18030 一 2005 对应的本文件对应的GB/T 工 13000 码位 | The GB/T 13000 code point related to this record is this archive and GB 18030-2005 | 1 |
D.2 在双字闻区删除的 6 个汉字构件 | D.2 Within the Shuangzi Wen locale, six Chinese character components have been expelled | 1 |
表 D.2 代码位置和保留的字形 | Table D.2 Saved glyphs and code places | 1 |
D.3 在双字下区删除的 9 个 CJK 兼容汉字 | D.3 Lower Twofold Word Region Evacuated 9 CJK Compliant Chinese Characters | 1 |
本文件删除了 GB 18030 一 2005 所 收录的来目 GB/TI 13000 的9个 CJK 碌容汉字, 如表 D.3 所示 。 | Concurring to Table D.3, this archive kills the nine CJK Lurong Chinese characters from GB/TI 13000 that were included in GB 18030-2005. | 1 |
表 D.3 删除的 9 个 CJK 兼容汉字和它们的代码位置 | Table D.3: Code Areas for the Expelled Nine CJK Compliant Chinese Characters | 1 |
附录开 (资料性)《通用规范汉字表》 汉字的代码位置 | Open reference sections (instructive) Chinese characters' "Common Standard Chinese Character List" code positions | 1 |
本文件收录了 2013 年中华人民共和国国务院批准发布的 4 通用规范汉字表》 中的全部 8105 个规范汉字,它们的代码位置和字形见表1。 | This archive incorporates all 8,105 standardized Chinese characters from the 2013 discharge of the People's Republic of China's State Council's Fourth Common Standardized Chinese Character List, their code areas and glyphs are recorded in Table 1. | 1 |
表中汉字的排列顺序与 4 通用规范汉字表 》的规范汉字顺序一致,序号 1 一 序号 3500 的汉字为一级汉字,序号 3501 一 序号 6500 的汉字为二级汉字,序号 6501 一 序号 8105 的汉字为三级汉字。 | The Chinese characters within the table are orchestrated within the same arrange as the four common standard Chinese character list, which takes after standard Chinese character requesting, Chinese characters with serial numbers 1 to 3500 are first-level characters, those with serial numbers 3501 to 6500 are second-lev... | 1 |
表 E.1 《通用规范汉字表》汉字的字形和代码位置 | Table E.1 of the "Common Standard Chinese Character Table" records the glyphs and code areas for Chinese characters | 1 |
GB/ 工 4754 国民经济行业分类 | GB/ Industry 4754 National Financial Industry Classification | 1 |
GB/ 工 36475 软件产品分类 | GB/Work 36475 Computer program Item Classification | 1 |
通用规范汉字表.中华人民共和国国务院(国发(2013]23号). | List of Common Standard Chinese Characters. The People's Republic of China's State Chamber (Guo Fa (2013] Number 23). | 1 |
本手册页内容摘自 GNU C 编译器的完整文档,仅限于解释选项的含义. | This man page's substance, which is confined to characterizing the alternatives, is extricated from the GNU C Compiler's comprehensive documentation. | 1 |
除非有人自愿维护, EURo文件，Info文件是权威文档. | The EURo record and the Information record are definitive unless it is effectively kept up. | 1 |
如果发现手册页和软件之间有所矛盾,请查对Info | Check the Data area in the event that you find a contrast between the man page and the program | 1 |
如果我们发觉本手册页的内容由于过时而导致明显的混乱和抱怨时,我们就停止发布它.不可能有其他选择,象更新Info文件同时更新 man 手册, 因为其他维护 Gnu cc 的工作没有留给我们时间做这个.GNU 工程认为 man 手册是过时产物, 应该把时间用到别的地方. | We'll halt posting this manual page in case we find that the data on it is out of date and clearly causing issues and complaints, further maintenance work on Gnu cc isn't cleared out to the client, subsequently, there are no other options, such as updating the Information record and the man manual. There's time for thi... | 1 |
如果需要完整和最新的文档, 请查阅 Info 文件 `gee' 或 Using and Porting GNU CC (for version 2.0) (ft&/HAIZE#H GNU CC 2.0) 手册.二者均来自 Texinfo 原文件 gee. texinfo. | See the Information record "gee" or the Utilizing and Porting GNU CC (for adaptation 2.0) (ft&/HAIZE#H GNU CC 2.0) manual for the foremost later and comprehensive documentation. Both are taken from the gee.texinfo unique Texinfo record. | 1 |
描述 (DESCRIPTION) C 和 C++ 编译器是集成的.他们都要用四个步骤中的一个或多个处理输入文件: 预处理(preprocessing), Hii(compilation), (assembly) MERE (linking) . | Depiction (Portrayal) (Portrayal) Compilers for C and C++ are combined. Both of them perform one or more of the taking after four forms when handling input records: preprocessing (preprocessing), Hii (compilation), (get together), and Insignificant (connecting). | 1 |
源文件后级名标识源文件的语言, 但是对编译器来说, 后绥名控制着缺省设定: | The source record addition demonstrates the dialect of the source record, but it moreover decides the compiler's default arrangement: | 1 |
gcc 认为预处理后的文件(.i) 是 c 文件, 并且设定 c 形式的连接， | The preprocessed record (.i) is treated as a c record by gcc, who too sets the link's organize to c， | 1 |
g++ 认为预处理后的文件 (.i) 是 c++ 文件 ,并且设定 c++ 形式的连接. | g++ considers the preprocessed record (.i) to be a c++ record, and sets the interface in c++ shape. | 1 |
源文件后级名指出语言种类以及后期的操作: | The dialect sort and ensuing operations are shown by the post-level title of the source record: | 1 |
.c C 源程序; 预处理, 编译,汇编 | .C source code that does preprocessing, compilation, and gathering | 1 |
.C C++ 源程序; 预处理, 编译,汇编 | .C++ source code for preprocessing, compilation, and gathering | 1 |
.cc C++ 源程序; 预处理, 编译,汇编 | .C++ source code for preprocessing, compilation, and get together | 1 |
. CXX C++ 源程序; 预处理, 编译,汇编 | . amassing, compiling, and planning CXX C++ source code | 1 |
.m Objective-C 源程序; 预处理,编译,汇编 | Preprocessing, compilation, and gathering for the.m Objective-C source program | 1 |
.i 预处理后的 c 文件;编译,汇编 | Preprocessing, compilation, and gathering for the.m Objective-C source program | 1 |
.ii 预处理后的 c++ 文件;编译,汇编 | preprocessed.ii record for c++; compile and gather | 1 |
.s 汇编语言源程序; 汇编 | program in get together dialect (.s); gathering | 1 |
汇编语言源程序; 预处理,汇编 | gathering dialect preprocessing; source program | 1 |
.h 预处理器文件; 通常不出现在命令行上其他后级名的文件被传递给连接器 (Linker).通常包括: | .h Preprocessor records are given to the linker, along side records with different addition names that aren't regularly found on the command line (Linker). ordinarily comprise of | 1 |
.0 目标文件 (Object file) | .0 protest record (Question record) | 1 |
.a 归档库文件(Archive file) | .a File record (Document record) | 1 |
除非使用了 -cec，-s, 或 -E 选项(或者编译错误阻止了完整的过程),否则连接总是最后的步骤. | Within the nonattendance of the -cec, -s, or -E choices, connecting is continuously the final step (or compilation blunders avoid the total prepare). | 1 |
在连接阶段中,所有对应于源程序的.e 文件，-1 库文件, 无法识别的文件名(包括指定的.o H 标文件和 .a 库文件)按命令行中的顺序传递给连接器选项 (OPTIONS) | All source program.e records, -1 library records, and obscure record names (counting specified.o H standard records and.a library records) are conveyed to the linker within the association stage within the arrange indicated by the command line alternatives (Choices) | 1 |
选项必须分立给出 : de ' 完全不同于 `-d -r '. | Parameters must be indicated separately since "de" and "-d -r" are totally diverse. | 1 |
大多数 ` -=E :和 `-W' 选项有两个相反的格式 : -fname 和 -fno-name (或 -Wname 和 -Wno- name). | The larger part of "-=E:" and "-W" choices have two polar alternate extremes: -fname and -fno-name (or -Wname and -Wno-name). | 1 |
这里只列举不是默认选项的格式. | Here, as it were designs that are not among the standard choices are recorded. | 1 |
下面是所有选项的摘要, 按类型分组, 解释放在后面的章节中. | All of the alternatives are recorded here, organized by kind, with clarifications taking after. | 1 |
代码生成选项 (Code Generation Option) | Choice for Code Era | 1 |
总体选项 (Overall Option) | In general Choice | 1 |
明确指出后面输入文件的语言为 language (而不是从文件名后绥得到的默认选择). | Demonstrate clearly that dialect is the dialect of any extra input records (rather than the default choice from the conclusion of the filename). | 1 |
这个选项应用于后面所有的输入文件, 直到遇着下一个 `-x' 选项 .language 的可选 | This alternative is appropriate to all input records after that up until the following "-x" choice. dialect not required | 1 |
关闭任何对语种的明确说明, 因此依据文件名后级处理后面的文件 RE AS E ` -x' 选项). | To guarantee that taking after records are handled in agreement with the record title RE AS E "-x" choice, cripple any express dialect determination. | 1 |
如果只操作四个阶段( 预处理, 编译, 汇编, 连接)中的一部分, 可以使用 ` -x' 选项 (或文件名后 Ah) 告诉 geo 从哪里开始,用 `~-c' ，`-s' ,或 `-E' 选项告诉 geo 到哪里结束.注意,某些选项组合 (例如 ，`-x cpp-output -E') {i gee MEF =c 编译或汇编源文件, ETER. ERA ATI 缺省情况下， GCC 通过用 ` .o' 蔡换源文件名后级 ` .ec 标文件名. 可以使用-o 选项选择其他名字.GCC忽略 -ec 选项后面任何无法识别的输入文伯 -S F 何事情. | You'll be able utilize the "-x" choice (or Ok taking after the record title) to tell Geo where to begin in the event that you fair work a parcel of the four phases (preprocessing, compilation, get together, and connecting). You'll utilize the “-c,” “-s,” or the “-E” alternative to tell Geo where to end, be mindful that... | 1 |
了的目标文件. | The target record. | 1 |
编译后即停止, 不进行汇编件. | Stops after compilation and does not perform get together. | 1 |
在编译过程的不同阶段间使用管道而非临时文件进行工作, 因为那些系统的汇编器不能从管道读取数据，GNU 的汇编器没有这个问题，汇编器能够接受的 C "方言 ": 支持符合 ANSI 标准的 C 程序. | Since the constructing agents on those frameworks cannot examined from channels, utilize channels instead of brief records to move between the different compilation stages, this issue does not exist within the GNU constructing agent, constructing agents can utilize C "lingos" that bolster ANSI-compliant standard C prog... | 1 |
这样就会关闭 GNU Cc 中某些不兼容 ANSI Cc 的特性关键字, 以及诸如 unix 和 vax 这些表明当迎和极少使用的 ANSI trigraph 特性,以及禁上尽管使 用了(译注 :宿主环境 (hosted environment) 下所有的标准库可用，main 函数返回 一个 int 值, 典型例子是除了内核以外几乎所有的程序.对应的独立环境 (f£reestanding environment) 不存在标准库, 程序入口也不一定是 main, 最明显的例子就是操作系统内核.详情参考 gcc 网站最近的资料) | This would impair ANSI trigraph highlights like unix and vax, which are stamped as welcome but occasionally utilized, as well as those that are utilized indeed in case they are not welcome and a few include watchwords in GNU Cc that are contradictory with ANSI Cc, all standard libraries have get to to (Explanation: Fac... | 1 |
对于没有参数的函数声明, 例如 `int foo ();', 按 C 风格处理 --- 即不说明参数个数或类型. (仅针对 C++) . | Treat work statements that do not have parameters, like "int foo ();," within the C way, which implies you shouldn't indicate the number or kind of parameters. (C++ as it were) . | 1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.