Examples of using Documentation should in English and their translations into Chinese
{-}
-
Political
-
Ecclesiastic
-
Programming
The documentation should read:.
The goal/orientation of an SDK is that its documentation should be focused and clear.
Similarly, documentation should be thorough and rigorous.
Therefore, at the earliest stages of the design process, project documentation should definitely include the data about USP.
Final documentation should be circulated as early as possible.
For people who are proficient in JavaScript, this documentation should be easy enough to breeze through.
Final documentation should be circulated as early as possible.
The Working Party should be supplied with as much information as possible, and documentation should be provided in good time.
The secretariat documentation should stress specific themes.
Documentation should be ready in time for the consideration of each agenda item.
Protection plan submitted to the approval documentation should be attached to the provisions of article 18th review adoption and reason;
Such documentation should be available in all languages one week prior to the opening of the session.
Protection plan submitted to the approval documentation should be attached to the provisions of article 18th review adoption and reason;
Such documentation should indicate current practices and suggestions for possible areas of harmonization.
Your technical documentation should support your compliance with the requirements of the Directive.
All documentation should be published in the open access literature and shared with appropriate communities.
Future specifications and related documentation should use the general term"URI" rather than the more restrictive terms"URL" and"URN"[RFC3305].
The documentation should make it easy for someone else to take over the database design, development or administration.
Special session documentation should be made available to all states in a timely and transparent manner.
All documentation should be provided within the specified timetables and in all the official languages of the United Nations.
The project documentation should clearly define the roles and responsibilities of all stakeholders.
The outcome documentation should include messages that map out converging and diverging opinions on given questions.
System documentation should be communicated to the relevant personnel and be understood, accessible and applicable to them.
System documentation should be communicated to the relevant personnel and be understood, accessible and applicable to them.
All documentation should be provided within the specified timetables and page limits and in all official United Nations languages.
System documentation should be communicated to the relevant personnel and be understood, accessible and applicable to them.
Finally, proper documentation should include shop records with any system analysis and scheduled maintenance or test results as well.
The Emacs online documentation should be sufficient to get you on track for learning more about the system and growing accustomed to it.
Formal documentation should be completed as part of the commissioning process, including final specifications, as-built drawings, test scripts and results, and other records.
Your documentation should identify the disability, describe the limitations caused by the disability, and, if possible, it should recommend accommodations to be provided.