00000003.htm

一份很好的linux入门资料

interface.&nbsp;It&nbsp;is&nbsp;assumed&nbsp;that&nbsp;End&nbsp;User&nbsp;Environment&nbsp;has&nbsp;a&nbsp;set&nbsp;of&nbsp;<BR>
utilities&nbsp;for&nbsp;user&nbsp;interaction.&nbsp;<BR>
&nbsp;<BR>
This&nbsp;environment&nbsp;includes&nbsp;all&nbsp;the&nbsp;interfaces&nbsp;and&nbsp;functionalities&nbsp;provided&nbsp;<BR>
by&nbsp;Application&nbsp;Execution&nbsp;Environment.&nbsp;Additional&nbsp;interfaces&nbsp;and&nbsp;<BR>
utilities&nbsp;are&nbsp;defined&nbsp;for&nbsp;the&nbsp;following&nbsp;sub-environments:&nbsp;<BR>
&nbsp;<BR>
(a)&nbsp;Server&nbsp;Environment&nbsp;<BR>
&nbsp;<BR>
Server&nbsp;environment&nbsp;is&nbsp;an&nbsp;operating&nbsp;system&nbsp;environment&nbsp;suitable&nbsp;for&nbsp;<BR>
backend&nbsp;server&nbsp;purposes.&nbsp;Graphical&nbsp;user&nbsp;interfaces&nbsp;are&nbsp;not&nbsp;required&nbsp;<BR>
in&nbsp;this&nbsp;environment.&nbsp;<BR>
&nbsp;<BR>
The&nbsp;following&nbsp;sections&nbsp;are&nbsp;applied&nbsp;to&nbsp;Server&nbsp;Environment:&nbsp;<BR>
&nbsp;<BR>
3.&nbsp;Base&nbsp;Libraries&nbsp;<BR>
4.&nbsp;Graphic&nbsp;Libraries&nbsp;<BR>
5.&nbsp;Shells&nbsp;and&nbsp;Utilities&nbsp;<BR>
6.&nbsp;Programming&nbsp;Languages&nbsp;(with&nbsp;Software&nbsp;Development&nbsp;Option)&nbsp;<BR>
7.&nbsp;Graphic&nbsp;Toolkit&nbsp;<BR>
10.&nbsp;Network&nbsp;Servers&nbsp;<BR>
&nbsp;<BR>
(b)&nbsp;Desktop&nbsp;Environment&nbsp;<BR>
&nbsp;<BR>
Desktop&nbsp;environment&nbsp;is&nbsp;an&nbsp;operating&nbsp;system&nbsp;environment&nbsp;suitable&nbsp;for&nbsp;<BR>
end&nbsp;user&nbsp;interaction.&nbsp;Graphical&nbsp;user&nbsp;interface&nbsp;is&nbsp;required&nbsp;in&nbsp;this&nbsp;<BR>
environment.&nbsp;<BR>
&nbsp;<BR>
The&nbsp;following&nbsp;sections&nbsp;are&nbsp;applied&nbsp;to&nbsp;Desktop&nbsp;Environment:&nbsp;<BR>
&nbsp;<BR>
3.&nbsp;Base&nbsp;Libraries&nbsp;<BR>
4.&nbsp;Graphic&nbsp;Libraries&nbsp;<BR>
5.&nbsp;Shells&nbsp;and&nbsp;Utilities&nbsp;<BR>
6.&nbsp;Programming&nbsp;Languages&nbsp;(with&nbsp;Software&nbsp;Development&nbsp;Option)&nbsp;<BR>
7.&nbsp;Graphic&nbsp;Toolkit&nbsp;<BR>
8.&nbsp;Input&nbsp;Methods&nbsp;<BR>
9.&nbsp;Output&nbsp;Methods&nbsp;<BR>
11.&nbsp;Internet&nbsp;Tools&nbsp;<BR>
12.&nbsp;X&nbsp;Clients&nbsp;<BR>
&nbsp;<BR>
If&nbsp;an&nbsp;interface&nbsp;or&nbsp;utility&nbsp;is&nbsp;defined&nbsp;as&nbsp;&quot;supported&nbsp;in&nbsp;End&nbsp;User&nbsp;<BR>
Environment&quot;,&nbsp;that&nbsp;interface&nbsp;or&nbsp;utility&nbsp;shall&nbsp;be&nbsp;available&nbsp;in&nbsp;both&nbsp;<BR>
Server&nbsp;and&nbsp;Desktop&nbsp;environments.&nbsp;<BR>
&nbsp;<BR>
[***&nbsp;Editor's&nbsp;Note:&nbsp;More&nbsp;restricted&nbsp;environment,&nbsp;such&nbsp;as&nbsp;&quot;embedded&quot;&nbsp;<BR>
systems,&nbsp;may&nbsp;be&nbsp;defined&nbsp;in&nbsp;the&nbsp;future&nbsp;version&nbsp;of&nbsp;this&nbsp;document.&nbsp;***]&nbsp;<BR>
&nbsp;<BR>
The&nbsp;following&nbsp;option&nbsp;can&nbsp;be&nbsp;supported&nbsp;in&nbsp;each&nbsp;environment:&nbsp;<BR>
&nbsp;<BR>
(3)&nbsp;Software&nbsp;Development&nbsp;Option&nbsp;<BR>
If&nbsp;this&nbsp;option&nbsp;is&nbsp;supported,&nbsp;utilities,&nbsp;libraries&nbsp;and&nbsp;associated&nbsp;modules&nbsp;<BR>
to&nbsp;develop&nbsp;internationalized&nbsp;software&nbsp;(such&nbsp;as&nbsp;compilers&nbsp;or&nbsp;interpreters)&nbsp;<BR>
shall&nbsp;be&nbsp;provided.&nbsp;<BR>
&nbsp;<BR>
1.3.2&nbsp;Conformance&nbsp;Levels&nbsp;<BR>
&nbsp;<BR>
Several&nbsp;levels&nbsp;are&nbsp;defined&nbsp;for&nbsp;conformance&nbsp;for&nbsp;each&nbsp;environment.&nbsp;These&nbsp;levels&nbsp;<BR>
are&nbsp;defined&nbsp;as&nbsp;follows:&nbsp;<BR>
&nbsp;<BR>
(1)&nbsp;Level&nbsp;1&nbsp;<BR>
&nbsp;<BR>
The&nbsp;level&nbsp;1&nbsp;is&nbsp;the&nbsp;bottom-line&nbsp;level&nbsp;of&nbsp;conformance.&nbsp;All&nbsp;conforming&nbsp;<BR>
implementations&nbsp;shall&nbsp;provide&nbsp;this&nbsp;level&nbsp;of&nbsp;interfaces&nbsp;and&nbsp;utilities&nbsp;to&nbsp;<BR>
conform&nbsp;to&nbsp;this&nbsp;specification.&nbsp;If&nbsp;level&nbsp;is&nbsp;not&nbsp;specified&nbsp;in&nbsp;the&nbsp;specification,&nbsp;<BR>
that&nbsp;specification&nbsp;shall&nbsp;be&nbsp;considered&nbsp;as&nbsp;Level&nbsp;1.&nbsp;<BR>
&nbsp;<BR>
(2)&nbsp;Level&nbsp;2&nbsp;<BR>
&nbsp;<BR>
The&nbsp;level&nbsp;2&nbsp;is&nbsp;more&nbsp;advanced&nbsp;or&nbsp;extended&nbsp;level&nbsp;of&nbsp;conformance.&nbsp;Conforming&nbsp;<BR>
implementations&nbsp;are&nbsp;encouraged&nbsp;to&nbsp;provide&nbsp;this&nbsp;level&nbsp;of&nbsp;interfaces&nbsp;and&nbsp;<BR>
utilities&nbsp;to&nbsp;conform&nbsp;to&nbsp;this&nbsp;specification,&nbsp;but&nbsp;it&nbsp;is&nbsp;not&nbsp;mandatory.&nbsp;<BR>
&nbsp;<BR>
&nbsp;<BR>
2.&nbsp;Terminology&nbsp;<BR>
2.1&nbsp;Definition&nbsp;of&nbsp;Terms&nbsp;<BR>
&nbsp;<BR>
The&nbsp;following&nbsp;terms&nbsp;are&nbsp;used&nbsp;in&nbsp;this&nbsp;specification:&nbsp;<BR>
&nbsp;<BR>
Implementation-defined&nbsp;<BR>
A&nbsp;value&nbsp;or&nbsp;behavior&nbsp;is&nbsp;implementation-defined&nbsp;when&nbsp;it&nbsp;is&nbsp;left&nbsp;to&nbsp;<BR>
the&nbsp;implementation&nbsp;to&nbsp;define&nbsp;[and&nbsp;document]&nbsp;the&nbsp;corresponding&nbsp;<BR>
requirements&nbsp;for&nbsp;correct&nbsp;application&nbsp;behavior.&nbsp;<BR>
&nbsp;<BR>
May&nbsp;<BR>
With&nbsp;respect&nbsp;to&nbsp;implementations,&nbsp;the&nbsp;word&nbsp;&quot;may&quot;&nbsp;is&nbsp;to&nbsp;be&nbsp;interpreted&nbsp;as&nbsp;<BR>
an&nbsp;optional&nbsp;feature&nbsp;that&nbsp;is&nbsp;not&nbsp;required&nbsp;in&nbsp;this&nbsp;<BR>
specification&nbsp;but&nbsp;can&nbsp;be&nbsp;provided.&nbsp;With&nbsp;respect&nbsp;to&nbsp;application,&nbsp;the&nbsp;word&nbsp;<BR>
&quot;may&quot;&nbsp;means&nbsp;that&nbsp;the&nbsp;feature&nbsp;is&nbsp;optional.&nbsp;The&nbsp;term&nbsp;&quot;optional&quot;&nbsp;has&nbsp;<BR>
the&nbsp;same&nbsp;definition&nbsp;as&nbsp;&quot;may&quot;.&nbsp;<BR>
&nbsp;<BR>
Shall&nbsp;<BR>
In&nbsp;this&nbsp;specification,&nbsp;the&nbsp;word&nbsp;&quot;shall&quot;&nbsp;is&nbsp;to&nbsp;be&nbsp;interpreted&nbsp;as&nbsp;a&nbsp;<BR>
mandatory&nbsp;requirement&nbsp;on&nbsp;the&nbsp;implementation&nbsp;or&nbsp;on&nbsp;application,&nbsp;depending&nbsp;<BR>
upon&nbsp;the&nbsp;context.&nbsp;The&nbsp;term&nbsp;&quot;must&quot;&nbsp;has&nbsp;the&nbsp;same&nbsp;definition&nbsp;as&nbsp;&quot;shall&quot;.&nbsp;<BR>
&nbsp;<BR>
Should&nbsp;<BR>
With&nbsp;respect&nbsp;to&nbsp;implementations,&nbsp;the&nbsp;word&nbsp;&quot;should&quot;&nbsp;is&nbsp;to&nbsp;be&nbsp;interpreted&nbsp;<BR>
as&nbsp;an&nbsp;implementation&nbsp;recommendation,&nbsp;but&nbsp;not&nbsp;a&nbsp;requirement.&nbsp;With&nbsp;respect&nbsp;<BR>
to&nbsp;application,&nbsp;the&nbsp;word&nbsp;&quot;should&quot;&nbsp;is&nbsp;to&nbsp;be&nbsp;interpreted&nbsp;as&nbsp;recommended&nbsp;<BR>
programming&nbsp;practice.&nbsp;<BR>
&nbsp;<BR>
Supported&nbsp;<BR>
Certain&nbsp;facilities&nbsp;in&nbsp;this&nbsp;specification&nbsp;are&nbsp;optional.&nbsp;If&nbsp;a&nbsp;facility&nbsp;is&nbsp;<BR>
supported,&nbsp;it&nbsp;behaves&nbsp;as&nbsp;specified&nbsp;by&nbsp;this&nbsp;specification.&nbsp;<BR>
&nbsp;<BR>
If&nbsp;a&nbsp;facility&nbsp;is&nbsp;&quot;supported&quot;&nbsp;by&nbsp;an&nbsp;implementation,&nbsp;the&nbsp;implementation&nbsp;<BR>
must&nbsp;document&nbsp;how&nbsp;to&nbsp;obtain&nbsp;and&nbsp;install&nbsp;the&nbsp;facility,&nbsp;or&nbsp;the&nbsp;facility&nbsp;is&nbsp;<BR>
installed&nbsp;by&nbsp;installer&nbsp;of&nbsp;the&nbsp;implementation&nbsp;by&nbsp;explicitly&nbsp;selected&nbsp;by&nbsp;<BR>
the&nbsp;user&nbsp;or&nbsp;implicitly&nbsp;installed&nbsp;with&nbsp;other&nbsp;system&nbsp;components.&nbsp;If&nbsp;an&nbsp;<BR>
implementation&nbsp;&quot;supports&quot;&nbsp;a&nbsp;facility,&nbsp;the&nbsp;distributor&nbsp;of&nbsp;the&nbsp;<BR>
implementation&nbsp;shall&nbsp;commit&nbsp;that&nbsp;the&nbsp;facility&nbsp;can&nbsp;run&nbsp;on&nbsp;the&nbsp;<BR>
implementation.&nbsp;<BR>
&nbsp;<BR>
Unspecified&nbsp;<BR>
When&nbsp;a&nbsp;value&nbsp;or&nbsp;behavior&nbsp;is&nbsp;unspecified,&nbsp;the&nbsp;specification&nbsp;defines&nbsp;no&nbsp;<BR>
portability&nbsp;requirements&nbsp;for&nbsp;a&nbsp;facility&nbsp;on&nbsp;an&nbsp;implementation&nbsp;even&nbsp;when&nbsp;<BR>
faced&nbsp;with&nbsp;an&nbsp;application&nbsp;that&nbsp;uses&nbsp;the&nbsp;facility.&nbsp;An&nbsp;application&nbsp;that&nbsp;<BR>
requires&nbsp;specific&nbsp;behavior&nbsp;in&nbsp;such&nbsp;an&nbsp;instance,&nbsp;rather&nbsp;than&nbsp;tolerating&nbsp;<BR>
any&nbsp;behavior&nbsp;when&nbsp;using&nbsp;that&nbsp;facility,&nbsp;is&nbsp;not&nbsp;a&nbsp;portable&nbsp;application.&nbsp;<BR>
&nbsp;<BR>
Provided&nbsp;<BR>
Certain&nbsp;facilities&nbsp;in&nbsp;this&nbsp;specification&nbsp;are&nbsp;mandatory&nbsp;and&nbsp;implemented&nbsp;<BR>
in&nbsp;all&nbsp;conforming&nbsp;implementations.&nbsp;<BR>
&nbsp;<BR>
2.2&nbsp;General&nbsp;Terms&nbsp;<BR>
&nbsp;<BR>
character&nbsp;<BR>
A&nbsp;sequence&nbsp;of&nbsp;one&nbsp;or&nbsp;more&nbsp;bytes&nbsp;representing&nbsp;a&nbsp;single&nbsp;graphic&nbsp;symbol&nbsp;or&nbsp;<BR>
control&nbsp;code.&nbsp;<BR>
&nbsp;<BR>
This&nbsp;term&nbsp;corresponds&nbsp;to&nbsp;the&nbsp;ISO&nbsp;C&nbsp;standard&nbsp;term&nbsp;multibyte&nbsp;character&nbsp;<BR>
(multi-byte&nbsp;character),&nbsp;where&nbsp;a&nbsp;single-byte&nbsp;character&nbsp;is&nbsp;a&nbsp;special&nbsp;case&nbsp;<BR>
of&nbsp;a&nbsp;multi-byte&nbsp;character.&nbsp;Unlike&nbsp;the&nbsp;usage&nbsp;in&nbsp;the&nbsp;ISO&nbsp;C&nbsp;standard,&nbsp;<BR>
character&nbsp;here&nbsp;has&nbsp;no&nbsp;necessary&nbsp;relationship&nbsp;with&nbsp;storage&nbsp;space,&nbsp;and&nbsp;<BR>
byte&nbsp;is&nbsp;used&nbsp;when&nbsp;storage&nbsp;space&nbsp;is&nbsp;discussed.&nbsp;<BR>
[Single&nbsp;UNIX&nbsp;Specification,&nbsp;Version&nbsp;2&nbsp;(derived&nbsp;from&nbsp;ISO/IEC&nbsp;9945-2:1993)]&nbsp;<BR>
&nbsp;<BR>
byte&nbsp;<BR>
An&nbsp;individually&nbsp;addressable&nbsp;unit&nbsp;of&nbsp;data&nbsp;storage&nbsp;that&nbsp;is&nbsp;equal&nbsp;to&nbsp;or&nbsp;<BR>
larger&nbsp;than&nbsp;an&nbsp;octet,&nbsp;used&nbsp;to&nbsp;store&nbsp;a&nbsp;character&nbsp;or&nbsp;a&nbsp;portion&nbsp;of&nbsp;a&nbsp;<BR>
character;&nbsp;see&nbsp;character.&nbsp;<BR>
&nbsp;<BR>
A&nbsp;byte&nbsp;is&nbsp;composed&nbsp;of&nbsp;a&nbsp;contiguous&nbsp;sequence&nbsp;of&nbsp;bits,&nbsp;the&nbsp;number&nbsp;of&nbsp;which&nbsp;<BR>
is&nbsp;implementation-dependent.&nbsp;The&nbsp;least&nbsp;significant&nbsp;bit&nbsp;is&nbsp;called&nbsp;the&nbsp;<BR>
low-order&nbsp;bit;&nbsp;the&nbsp;most&nbsp;significant&nbsp;is&nbsp;called&nbsp;the&nbsp;high-order&nbsp;bit.&nbsp;<BR>
&nbsp;<BR>
Note&nbsp;that&nbsp;this&nbsp;definition&nbsp;of&nbsp;byte&nbsp;deviates&nbsp;intentionally&nbsp;from&nbsp;the&nbsp;usage&nbsp;<BR>
of&nbsp;byte&nbsp;in&nbsp;some&nbsp;international&nbsp;standards,&nbsp;where&nbsp;it&nbsp;is&nbsp;used&nbsp;as&nbsp;a&nbsp;synonym&nbsp;<BR>
for&nbsp;octet&nbsp;(always&nbsp;eight&nbsp;bits).&nbsp;On&nbsp;a&nbsp;system&nbsp;based&nbsp;on&nbsp;the&nbsp;ISO/IEC&nbsp;<BR>
9945-2:1993&nbsp;standard,&nbsp;a&nbsp;byte&nbsp;may&nbsp;be&nbsp;larger&nbsp;than&nbsp;eight&nbsp;bits&nbsp;so&nbsp;that&nbsp;it&nbsp;<BR>
can&nbsp;be&nbsp;an&nbsp;integral&nbsp;portion&nbsp;of&nbsp;larger&nbsp;data&nbsp;objects&nbsp;that&nbsp;are&nbsp;not&nbsp;evenly&nbsp;<BR>
divisible&nbsp;by&nbsp;eight&nbsp;bits&nbsp;(such&nbsp;as&nbsp;a&nbsp;36-bit&nbsp;word&nbsp;that&nbsp;contains&nbsp;four&nbsp;9-bit&nbsp;<BR>
bytes).&nbsp;<BR>
[Single&nbsp;UNIX&nbsp;Specification,&nbsp;Version&nbsp;2&nbsp;(derived&nbsp;from&nbsp;ISO/IEC&nbsp;9945-2:1993)]&nbsp;<BR>
&nbsp;<BR>
repertoire&nbsp;<BR>
A&nbsp;specified&nbsp;set&nbsp;of&nbsp;characters&nbsp;that&nbsp;are&nbsp;represented&nbsp;in&nbsp;a&nbsp;coded&nbsp;character&nbsp;<BR>
set.&nbsp;<BR>
[ISO/IEC&nbsp;10646-1:2000]&nbsp;<BR>
&nbsp;<BR>
character&nbsp;boundary&nbsp;<BR>
Within&nbsp;a&nbsp;stream&nbsp;of&nbsp;octets&nbsp;the&nbsp;demarcation&nbsp;between&nbsp;the&nbsp;last&nbsp;octet&nbsp;of&nbsp;the&nbsp;<BR>
coded&nbsp;representation&nbsp;of&nbsp;a&nbsp;character&nbsp;and&nbsp;the&nbsp;first&nbsp;octet&nbsp;of&nbsp;that&nbsp;of&nbsp;the&nbsp;<BR>
next&nbsp;coded&nbsp;character.&nbsp;<BR>
[ISO/IEC&nbsp;10646-1:2000]&nbsp;<BR>
&nbsp;<BR>
control&nbsp;function&nbsp;<BR>
An&nbsp;action&nbsp;that&nbsp;affects&nbsp;the&nbsp;recording,&nbsp;processing,&nbsp;transmission,&nbsp;or&nbsp;<BR>
interpretation&nbsp;of&nbsp;data,&nbsp;and&nbsp;that&nbsp;has&nbsp;coded&nbsp;representation&nbsp;consisting&nbsp;of&nbsp;<BR>
one&nbsp;or&nbsp;more&nbsp;octets.&nbsp;<BR>
[ISO/IEC&nbsp;10646-1:2000]&nbsp;<BR>
&nbsp;<BR>
graphic&nbsp;character&nbsp;<BR>
A&nbsp;character,&nbsp;other&nbsp;than&nbsp;a&nbsp;control&nbsp;function,&nbsp;that&nbsp;has&nbsp;a&nbsp;visual&nbsp;<BR>
representation&nbsp;normally&nbsp;handwritten,&nbsp;printed,&nbsp;or&nbsp;displayed.&nbsp;<BR>
[ISO/IEC&nbsp;10646-1:2000]&nbsp;<BR>
&nbsp;<BR>
graphic&nbsp;symbol&nbsp;<BR>
The&nbsp;visual&nbsp;representation&nbsp;of&nbsp;a&nbsp;graphic&nbsp;character&nbsp;or&nbsp;of&nbsp;a&nbsp;composite&nbsp;<BR>
sequence.&nbsp;<BR>
[ISO/IEC&nbsp;10646-1:2000]&nbsp;<BR>
&nbsp;<BR>
coded&nbsp;character&nbsp;set&nbsp;[CCS]&nbsp;<BR>
&nbsp;<BR>
A&nbsp;Coded&nbsp;Character&nbsp;Set&nbsp;(CCS)&nbsp;is&nbsp;a&nbsp;mapping&nbsp;from&nbsp;a&nbsp;set&nbsp;of&nbsp;abstract&nbsp;<BR>
characters&nbsp;to&nbsp;a&nbsp;set&nbsp;of&nbsp;integers.&nbsp;Examples&nbsp;of&nbsp;coded&nbsp;character&nbsp;sets&nbsp;<BR>
are&nbsp;ISO&nbsp;10646,&nbsp;US-ASCII,&nbsp;and&nbsp;ISO-8859&nbsp;series.&nbsp;<BR>
[RFC&nbsp;2130]&nbsp;<BR>
&nbsp;<BR>
character&nbsp;encoding&nbsp;scheme&nbsp;[CES]&nbsp;<BR>
&nbsp;<BR>
A&nbsp;Character&nbsp;Encoding&nbsp;Scheme&nbsp;(CES)&nbsp;is&nbsp;a&nbsp;mapping&nbsp;from&nbsp;a&nbsp;Coded&nbsp;Character&nbsp;<BR>
Set&nbsp;or&nbsp;several&nbsp;coded&nbsp;character&nbsp;sets&nbsp;to&nbsp;a&nbsp;set&nbsp;of&nbsp;octets.&nbsp;Examples&nbsp;of&nbsp;<BR>
Character&nbsp;Encoding&nbsp;Schemes&nbsp;are&nbsp;ISO&nbsp;2022&nbsp;and&nbsp;UTF-8.&nbsp;<BR>
A&nbsp;given&nbsp;CES&nbsp;is&nbsp;typically&nbsp;associated&nbsp;with&nbsp;a&nbsp;single&nbsp;CCS;&nbsp;for&nbsp;example,&nbsp;<BR>
UTF-8&nbsp;applies&nbsp;only&nbsp;to&nbsp;ISO&nbsp;10646.&nbsp;<BR>
[RFC&nbsp;2130]&nbsp;<BR>
&nbsp;<BR>
transfer&nbsp;encoding&nbsp;syntax&nbsp;[TES]&nbsp;<BR>
&nbsp;<BR>
It&nbsp;is&nbsp;frequently&nbsp;necessary&nbsp;to&nbsp;transform&nbsp;encoded&nbsp;text&nbsp;into&nbsp;a&nbsp;format&nbsp;<BR>
which&nbsp;is&nbsp;transmissible&nbsp;by&nbsp;specific&nbsp;protocols.&nbsp;The&nbsp;Transfer&nbsp;Encoding&nbsp;<BR>
Syntax&nbsp;(TES)&nbsp;is&nbsp;a&nbsp;transformation&nbsp;applied&nbsp;to&nbsp;character&nbsp;data&nbsp;encoded&nbsp;<BR>
using&nbsp;a&nbsp;CCS&nbsp;and&nbsp;possibly&nbsp;a&nbsp;CES&nbsp;to&nbsp;allow&nbsp;it&nbsp;to&nbsp;be&nbsp;transmitted.&nbsp;<BR>
Examples&nbsp;of&nbsp;Transfer&nbsp;Encoding&nbsp;Syntaxes&nbsp;are&nbsp;Base64&nbsp;Encoding,&nbsp;<BR>
gzip&nbsp;encoding,&nbsp;and&nbsp;so&nbsp;forth.&nbsp;<BR>
[RFC&nbsp;2130]&nbsp;<BR>
&nbsp;<BR>
internationalization&nbsp;<BR>
The&nbsp;process&nbsp;of&nbsp;designing&nbsp;and&nbsp;developing&nbsp;an&nbsp;implementation&nbsp;with&nbsp;a&nbsp;set&nbsp;of&nbsp;<BR>
features,&nbsp;functions,&nbsp;and&nbsp;options&nbsp;intended&nbsp;to&nbsp;facilitate&nbsp;the&nbsp;adaptation&nbsp;<BR>
of&nbsp;the&nbsp;implementation&nbsp;to&nbsp;satisfy&nbsp;a&nbsp;variety&nbsp;of&nbsp;cultural&nbsp;environments.&nbsp;<BR>
[P1003.0/D16]&nbsp;<BR>
&nbsp;<BR>
localization&nbsp;<BR>
The&nbsp;process&nbsp;of&nbsp;utilizing&nbsp;the&nbsp;internationalization&nbsp;features&nbsp;to&nbsp;create&nbsp;a&nbsp;<BR>
version&nbsp;of&nbsp;the&nbsp;product&nbsp;for&nbsp;a&nbsp;specific&nbsp;culture.&nbsp;<BR>
[P1003.0/D16]&nbsp;<BR>
&nbsp;<BR>
local&nbsp;adaptation&nbsp;<BR>
The&nbsp;process&nbsp;of&nbsp;modifying&nbsp;a&nbsp;product&nbsp;that&nbsp;is&nbsp;specific&nbsp;to&nbsp;one&nbsp;culture&nbsp;to&nbsp;<BR>
make&nbsp;it&nbsp;specific&nbsp;to&nbsp;another&nbsp;culture.&nbsp;<BR>
[P1003.0/D16]&nbsp;<BR>
&nbsp;<BR>
locale&nbsp;<BR>
A&nbsp;description&nbsp;of&nbsp;a&nbsp;cultural&nbsp;environment.&nbsp;<BR>
[P1003.0/D16]&nbsp;<BR>
&nbsp;<BR>
&nbsp;<BR>
3.&nbsp;Base&nbsp;Libraries&nbsp;<BR>
&nbsp;<BR>
(1)&nbsp;Scope&nbsp;<BR>
&nbsp;<BR>
This&nbsp;chapter&nbsp;defines&nbsp;runtime&nbsp;library&nbsp;interfaces&nbsp;required&nbsp;to&nbsp;conform&nbsp;to&nbsp;this&nbsp;<BR>
specification.&nbsp;Conforming&nbsp;implementations&nbsp;shall&nbsp;provide&nbsp;the&nbsp;C&nbsp;language&nbsp;<BR>
APIs&nbsp;defined&nbsp;by&nbsp;[ISO&nbsp;C]&nbsp;and&nbsp;[POSIX.1].&nbsp;In&nbsp;addition&nbsp;to&nbsp;the&nbsp;C&nbsp;language&nbsp;<BR>
interface,&nbsp;conforming&nbsp;level&nbsp;2&nbsp;implementations&nbsp;shall&nbsp;provide&nbsp;interfaces&nbsp;for&nbsp;<BR>