├── home.md ├── .gitignore ├── images ├── table.png ├── columns.png ├── text001.png ├── text002.png ├── baselines.png ├── label_code.png ├── lists_code.png ├── mixed_cjk.png ├── bookbinding.png ├── cursor_shape.png ├── fieldset_code.png ├── label_display.png ├── lists_display.png ├── mixed_media.png ├── mouse_pointer.png ├── page_numbers.png ├── page_turning.png ├── select_code.png ├── cursor_movement.png ├── input_controls.png ├── mixed_alphanum.png ├── mongolian_space.png ├── newline_correct.png ├── paper_direction.png ├── select_display.png ├── text_decoration.png ├── fieldset_display.png ├── first_line_indents.png ├── newline_incorrect.png ├── punctuation_sample.png ├── textarea_display.png ├── writing_direction.png ├── scrollbag_direction.png ├── selection_multiline.png ├── text_decoration_gaps.png ├── width_height_spacing.png ├── correct_mongolian_space.png ├── paper_rolling_direction.png ├── selection_single_line.png ├── text_decoration_mixed.png ├── incorrect_mongolian_space.png └── punctuation_text_alignment.png ├── .pr-preview.json ├── variants ├── ds01.pdf └── document-log.html ├── mong └── echidna ├── gap-analysis ├── images │ ├── vertical-lists.png │ ├── 73818998-73daf100-47e6-11ea-9a7d-d77b3f687e10.png │ ├── 105961907-09663500-6077-11eb-9034-13afb495de68.png │ └── 167632640-cb805b08-59a1-4c73-a28f-b47f7048f153.png ├── echidna-mong-gap └── index.html ├── w3c.json ├── homepage ├── index-data │ ├── translations.js │ └── local.css └── index.html ├── .github └── ISSUE_TEMPLATE │ ├── other.md │ ├── ask-a-question.md │ └── add-a-new-gap-analysis-topic.md ├── echidna ├── local.css ├── CONTRIBUTING.md ├── README.md ├── charter ├── charter2019.html └── index.html └── index.html /home.md: -------------------------------------------------------------------------------- 1 | README.md -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | *.DS_Store 2 | -------------------------------------------------------------------------------- /images/table.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/table.png -------------------------------------------------------------------------------- /.pr-preview.json: -------------------------------------------------------------------------------- 1 | { 2 | "src_file": "index.html", 3 | "type": "respec" 4 | } -------------------------------------------------------------------------------- /images/columns.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/columns.png -------------------------------------------------------------------------------- /images/text001.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/text001.png -------------------------------------------------------------------------------- /images/text002.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/text002.png -------------------------------------------------------------------------------- /variants/ds01.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/variants/ds01.pdf -------------------------------------------------------------------------------- /images/baselines.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/baselines.png -------------------------------------------------------------------------------- /images/label_code.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/label_code.png -------------------------------------------------------------------------------- /images/lists_code.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/lists_code.png -------------------------------------------------------------------------------- /images/mixed_cjk.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/mixed_cjk.png -------------------------------------------------------------------------------- /images/bookbinding.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/bookbinding.png -------------------------------------------------------------------------------- /images/cursor_shape.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/cursor_shape.png -------------------------------------------------------------------------------- /images/fieldset_code.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/fieldset_code.png -------------------------------------------------------------------------------- /images/label_display.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/label_display.png -------------------------------------------------------------------------------- /images/lists_display.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/lists_display.png -------------------------------------------------------------------------------- /images/mixed_media.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/mixed_media.png -------------------------------------------------------------------------------- /images/mouse_pointer.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/mouse_pointer.png -------------------------------------------------------------------------------- /images/page_numbers.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/page_numbers.png -------------------------------------------------------------------------------- /images/page_turning.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/page_turning.png -------------------------------------------------------------------------------- /images/select_code.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/select_code.png -------------------------------------------------------------------------------- /images/cursor_movement.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/cursor_movement.png -------------------------------------------------------------------------------- /images/input_controls.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/input_controls.png -------------------------------------------------------------------------------- /images/mixed_alphanum.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/mixed_alphanum.png -------------------------------------------------------------------------------- /images/mongolian_space.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/mongolian_space.png -------------------------------------------------------------------------------- /images/newline_correct.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/newline_correct.png -------------------------------------------------------------------------------- /images/paper_direction.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/paper_direction.png -------------------------------------------------------------------------------- /images/select_display.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/select_display.png -------------------------------------------------------------------------------- /images/text_decoration.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/text_decoration.png -------------------------------------------------------------------------------- /images/fieldset_display.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/fieldset_display.png -------------------------------------------------------------------------------- /images/first_line_indents.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/first_line_indents.png -------------------------------------------------------------------------------- /images/newline_incorrect.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/newline_incorrect.png -------------------------------------------------------------------------------- /images/punctuation_sample.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/punctuation_sample.png -------------------------------------------------------------------------------- /images/textarea_display.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/textarea_display.png -------------------------------------------------------------------------------- /images/writing_direction.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/writing_direction.png -------------------------------------------------------------------------------- /mong/echidna: -------------------------------------------------------------------------------- 1 | # ECHIDNA configuration 2 | index.html?specStatus=DNOTE&shortName=mong-lreq respec 3 | -------------------------------------------------------------------------------- /images/scrollbag_direction.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/scrollbag_direction.png -------------------------------------------------------------------------------- /images/selection_multiline.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/selection_multiline.png -------------------------------------------------------------------------------- /images/text_decoration_gaps.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/text_decoration_gaps.png -------------------------------------------------------------------------------- /images/width_height_spacing.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/width_height_spacing.png -------------------------------------------------------------------------------- /images/correct_mongolian_space.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/correct_mongolian_space.png -------------------------------------------------------------------------------- /images/paper_rolling_direction.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/paper_rolling_direction.png -------------------------------------------------------------------------------- /images/selection_single_line.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/selection_single_line.png -------------------------------------------------------------------------------- /images/text_decoration_mixed.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/text_decoration_mixed.png -------------------------------------------------------------------------------- /images/incorrect_mongolian_space.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/incorrect_mongolian_space.png -------------------------------------------------------------------------------- /gap-analysis/images/vertical-lists.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/gap-analysis/images/vertical-lists.png -------------------------------------------------------------------------------- /images/punctuation_text_alignment.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/images/punctuation_text_alignment.png -------------------------------------------------------------------------------- /w3c.json: -------------------------------------------------------------------------------- 1 | { 2 | "group": [109474, 72665, 32113] 3 | , "contacts": "rishida" 4 | , "repo-type": "note" 5 | , "policy": "restricted" 6 | } 7 | -------------------------------------------------------------------------------- /gap-analysis/images/73818998-73daf100-47e6-11ea-9a7d-d77b3f687e10.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/gap-analysis/images/73818998-73daf100-47e6-11ea-9a7d-d77b3f687e10.png -------------------------------------------------------------------------------- /gap-analysis/images/105961907-09663500-6077-11eb-9034-13afb495de68.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/gap-analysis/images/105961907-09663500-6077-11eb-9034-13afb495de68.png -------------------------------------------------------------------------------- /gap-analysis/images/167632640-cb805b08-59a1-4c73-a28f-b47f7048f153.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/w3c/mlreq/HEAD/gap-analysis/images/167632640-cb805b08-59a1-4c73-a28f-b47f7048f153.png -------------------------------------------------------------------------------- /homepage/index-data/translations.js: -------------------------------------------------------------------------------- 1 | var trans = { } 2 | 3 | trans.versions = ['en'] 4 | 5 | trans.outofdatetranslations = [] 6 | 7 | trans.updatedtranslations = [] 8 | 9 | trans.unlinkedtranslations = [] -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/other.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Other 3 | about: Please use links or pictures for examples and sources where possible. 4 | title: '' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | 11 | -------------------------------------------------------------------------------- /gap-analysis/echidna-mong-gap: -------------------------------------------------------------------------------- 1 | # ECHIDNA configuration 2 | index.html?specStatus=DNOTE&shortName=mong-gap respec 3 | images/105961907-09663500-6077-11eb-9034-13afb495de68.png 4 | images/73818998-73daf100-47e6-11ea-9a7d-d77b3f687e10.png 5 | images/167632640-cb805b08-59a1-4c73-a28f-b47f7048f153.png -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/ask-a-question.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Ask a question 3 | about: Use to ask about how people use the Mongolian language or script. 4 | title: Short_version_of_the_question? 5 | labels: question 6 | assignees: '' 7 | 8 | --- 9 | 10 | Ask_the_question_here_Use_pictures_and_links 11 | -------------------------------------------------------------------------------- /homepage/index-data/local.css: -------------------------------------------------------------------------------- 1 | table { 2 | border-collapse: collapse; 3 | width: 100%; 4 | } 5 | th { 6 | background-color: #eee; 7 | border: 1px solid #ccc; 8 | } 9 | .date { 10 | white-space:nowrap; 11 | width: 8em; 12 | } 13 | td { 14 | font-size: 90%; 15 | padding: 0 .3em; 16 | border: 1px solid #ccc; 17 | } 18 | .labels { 19 | float: right; 20 | height: 11px; 21 | width: 11px; 22 | border-radius: 2px; 23 | margin: 3px; 24 | font-size: .2em; 25 | color: rgba(0,0,0,0.00); 26 | } 27 | #internal-links { 28 | display: none; 29 | } 30 | .hidden { 31 | display: none; 32 | } -------------------------------------------------------------------------------- /echidna: -------------------------------------------------------------------------------- 1 | # ECHIDNA configuration 2 | index.html?specStatus=DNOTE&shortName=mlreq respec 3 | local.css 4 | images/baselines.png 5 | images/bookbinding.png 6 | images/columns.png 7 | images/correct_mongolian_space.png 8 | images/cursor_movement.png 9 | images/cursor_shape.png 10 | images/fieldset_code.png 11 | images/fieldset_display.png 12 | images/incorrect_mongolian_space.png 13 | images/input_controls.png 14 | images/label_code.png 15 | images/label_display.png 16 | images/lists_code.png 17 | images/lists_display.png 18 | images/mixed_alphanum.png 19 | images/mixed_cjk.png 20 | images/mixed_media.png 21 | images/mongolian_space.png 22 | images/mouse_pointer.png 23 | images/newline_correct.png 24 | images/newline_incorrect.png 25 | images/page_numbers.png 26 | images/page_turning.png 27 | images/paper_direction.png 28 | images/paper_rolling_direction.png 29 | images/punctuation_sample.png 30 | images/punctuation_text_alignment.png 31 | images/scrollbag_direction.png 32 | images/select_code.png 33 | images/select_display.png 34 | images/selection_multiline.png 35 | images/selection_single_line.png 36 | images/table.png 37 | images/text_decoration_gaps.png 38 | images/text_decoration_mixed.png 39 | images/text_decoration.png 40 | images/text001.png 41 | images/text002.png 42 | images/textarea_display.png 43 | images/width_height_spacing.png 44 | images/writing_direction.png 45 | -------------------------------------------------------------------------------- /local.css: -------------------------------------------------------------------------------- 1 | :lang(mn) { font-family: "Mongolian Universal White", "Mongolian Baiti", "Noto Sans Mongolian WF", serif; font-size: 120%; } 2 | 3 | h2 { 4 | margin-top: 4em !important; 5 | margin-bottom: 0em !important; 6 | } 7 | .head h2, #abstract h2, #sotd h2 { 8 | margin-top: 0 !important; 9 | } 10 | h3 { 11 | margin-top: 3em !important; 12 | } 13 | h4 { 14 | font-size: 100%; 15 | font-weight: normal; 16 | color: #005a9c; 17 | margin-top: 2em; 18 | } 19 | .leadin { 20 | font-weight: bold; 21 | } 22 | 23 | ins { 24 | background-color: #99FF99; 25 | text-decoration: none; 26 | } 27 | del { 28 | display: inline; 29 | color: silver; 30 | } 31 | 32 | figure { 33 | margin-bottom: 2em; 34 | text-align: center; 35 | } 36 | figcaption { 37 | text-align: center; 38 | margin: 0.5em 2em; 39 | font-style: italic; 40 | font-size: 90%; 41 | } 42 | 43 | figcaption .figno:after { 44 | content: ':\00A0 '; 45 | } 46 | 47 | a.termref:link { 48 | color:#C60; 49 | text-decoration:none; 50 | border-bottom: 1px dotted #FC0; 51 | } 52 | a.termref:hover { 53 | color:#C60; 54 | text-decoration:none; 55 | border-bottom: 1px dotted #FC0; 56 | } 57 | a.termref:visited { 58 | color:#C60; 59 | text-decoration:none; 60 | border-bottom: 1px dotted #FC0; 61 | } 62 | a.termref:active { 63 | color:#C60; 64 | text-decoration:none; 65 | border-bottom: 1px dotted #FC0; 66 | } 67 | 68 | .qterm:before, .qchar:before { content: "'"; } 69 | .qterm:after, .qchar:after { content: "'"; } 70 | .quote:before { content: '"'; } 71 | .quote:after { content: '"'; } 72 | code { 73 | color: #A52A2A; 74 | font-family: Consolas, "Andale Mono", "Lucida Console", "Lucida Sans Typewriter", Monaco, "Courier New", monospace; 75 | font-size: 100%; 76 | } 77 | samp, kbd { 78 | font-family: Consolas, "Andale Mono", "Lucida Console", "Lucida Sans Typewriter", Monaco, "Courier New", monospace; 79 | font-size: 100%; 80 | } 81 | .uname { 82 | text-transform: uppercase; 83 | font-size: 85%; 84 | letter-spacing:0.03em; 85 | } 86 | .prompt { 87 | font-style: italic; 88 | color: #aaa; 89 | font-size: 90%; 90 | margin-bottom: 4em; 91 | } 92 | 93 | 94 | 95 | 96 | 97 | 98 | 99 | 100 | .reslinks dt { 101 | font-size: 80%; 102 | } 103 | .reslinks dd { 104 | font-size: 90%; 105 | } 106 | 107 | .prompts { font-style: italic; color: #999; font-size: 90%; } 108 | 109 | dl.reslinks { 110 | border-block-end: 1px solid #ccc; 111 | margin-block-end: 3em; 112 | } 113 | 114 | .nobullet { 115 | list-style-type: none; 116 | } 117 | 118 | 119 | 120 | #linkWarning { 121 | margin-inline: 2.5%; 122 | background-color: antiquewhite; 123 | border-radius: 1em; 124 | font-size: 90%; 125 | padding: 1em; 126 | z-index: 2000; 127 | } 128 | #closeLinkWarning { 129 | float:right; 130 | font-size:120%; 131 | margin-inline:1em; 132 | cursor:pointer; 133 | color: #999; 134 | } 135 | 136 | 137 | 138 | .variable.empty[href], .variable.empty[href]:visited { 139 | color: gray; 140 | font-style: italic; 141 | } 142 | 143 | 144 | .reslinks a[href] { 145 | color: darkorange; 146 | } 147 | .reslinks a[href]:visited { 148 | color: darkorange; 149 | } 150 | 151 | 152 | .reflink { 153 | vertical-align: super; 154 | font-size: 70%; 155 | } 156 | 157 | 158 | 159 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | ## Contributions 2 | 3 | Contributions to this repository are intended to become part of the Internationalization Interest Group and Internationalization Working Group documents governed by the [Software and Document License](http://www.w3.org/Consortium/Legal/copyright-software). By committing here, you agree to that licensing of your contributions. 4 | 5 | If you are not the sole contributor to a contribution (pull request), please identify all contributors in the pull request comment. 6 | 7 | To add a contributor (other than yourself, that's automatic), mark them one per line as follows: 8 | 9 | ``` 10 | +@github_username 11 | ``` 12 | 13 | If you added a contributor by mistake, you can remove them in a comment with: 14 | 15 | ``` 16 | -@github_username 17 | ``` 18 | 19 | If you are making a pull request on behalf of someone else but you had no part in designing the feature, you can remove yourself with the above syntax. 20 | 21 | 22 | 23 | ## Copyright 24 | 25 | Copyright is a very important part of standardization activities. It allows the standards development organization to maintain vendor neutral control over a specification, and thus protect the consensus found within a Working Group. 26 | 27 | In the course of the development of materials within the W3C, Task Force Participants will make contributions. Those contributions will be integrated into the jointly developed work thus creating shared copyright on the Task Force Participant's contribution. Most W3C Specifications contain a section with acknowledgement of contributions. 28 | 29 | Task Force Participants grant to the W3C a perpetual, nonexclusive, royalty-free, world-wide right and license under any Task Force Participant's copyrights on his or her contributions, to copy, publish and distribute the contribution under a license of W3C's choosing. Additionally, the Task Force Participant grants a right and license of the same scope to any derivative works prepared by the W3C and based on, or incorporating all or part of, his or her contribution and that any derivative works of this contribution prepared by the W3C shall be solely owned by the W3C. Furthermore, the Task Force Participant understands that W3C will be able to exercise all rights as a copyright owner of Task Force Participant's contribution, including enforcement against infringers without additional agreement or notice. 30 | 31 | Nothing in this agreement restricts the Task Force Participant from using their individual contributions as they wish, even if those have later been amalgamated into joint works. Where W3C releases materials under a permissive license such as the W3C Software License or CC-BY, nothing in this agreement should be read to restrict the Task Force Participant from exercising the permissions granted by that license. The Task Force Participant represents that they are legally entitled to grant the above license. If their employer(s) have rights to intellectual property that the Task Force Participant creates that includes the contributions, they represent that they have received permission to make contributions on behalf of that employer or that the employer has waived such rights for the contributions to W3C. 32 | 33 | 34 | ## Decency 35 | 36 | The Task Force Participant will participate in the W3C Group in a decent way. Task Force Participants will refrain from defaming, harassing or otherwise offending other participants. The [Section 3.1 of the Process Document](https://www.w3.org/2015/Process-20150901/#ParticipationCriteria) applies, as does the W3C [Code of Ethics and Professional Conduct](https://www.w3.org/Consortium/cepc/). 37 | 38 | The Task Force Participant will refrain from sending unsolicited commercial messages to W3C mailing-lists and other promotional activities for personal matters or for third parties. This is especially required from Task Force Participants sending messages to public W3C Groups. 39 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/add-a-new-gap-analysis-topic.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Add a new gap-analysis topic 3 | about: Only those in the mlreq group should use this template. 4 | title: Brief_description_of_the_problem 5 | labels: gap, doc:mong 6 | assignees: '' 7 | 8 | --- 9 | 10 | This issue is applicable to most_languages. 11 | 12 | Brief_intro_illustrating_the_requirements 13 | 14 | More: 15 | - [requirements_doc]() 16 | - [etc]() 17 | 18 | 19 | IF THIS IS NOT THE ISSUE THAT IS BEING TRACKED BY THE GAP-ANALYSIS PIPELINE, ADD A POINTER TO THAT ISSUE. THE INITIAL BRIEF INTRO SHOULD REMAIN, AND MAY BE TAILORED WITH EXAMPLES RELEVANT TO THIS LANGUAGE. YOU MAY, OPTIONALLY, ALSO ADD OTHER DETAILS BELOW IF THEY ARE SPECIFIC TO THIS LANGUAGE. THEN ADD THIS: 20 | 21 | For more details, see [this GitHub issue](https://github.com/w3c/XXXX/issues/XX), which is being used to track this gap. Please add any discussion there, and not to this issue. 22 | 23 | THEN ADD THESE 2 PARAS TO THE SECOND COMMENT FIELD AND DELETE THE REST OF THIS TEMPLATE. 24 | 25 | _The first comment in this issue contains text that will automatically appear in one or more gap-analysis documents as a subsection with the same title as this issue. Any edits made to that comment will be immediately available in the Editor's draft of the document._ 26 | 27 | _**Please add any discussion to the GitHub issue being used to track this gap, and not to this issue**_ 28 | 29 | 30 | 31 | 32 | 33 | ### The GAP 34 | 35 | Description_of_the_problem_and_summary_of_test_results 36 | 37 | Brief_description_of_what_spec_says_on_the_matter 38 | [shortname](url_to_section) describe_what_it_says 39 | 40 | Gecko, Blink, and Webkit 41 | 42 | More: 43 | - [relevant_issues]() 44 | - [etc]() 45 | 46 | 47 | 48 | 49 | ### Priority 50 | Why_you_chose_the_priority 51 | 52 | 53 | 54 | 55 | 56 | ### Tests & results 57 | 58 | Interactive test, [assertion](url)
59 | I18n test suite, [section_head](url) 60 | 61 | Summarise_the_results_for_each_major_engine_only_if_useful 62 | 63 | 64 | 65 | 66 | 67 | ### Action taken 68 | Issue, [XXX](url) Closed. 69 | 70 | [Gecko](url) • [Blink](url) • [Webkit](url) 71 | 72 | 73 | 74 | 75 | ### Outcomes 76 | Brief_description_of_developments 77 | 78 | 79 | 80 | 81 | TEXT FOR THE SECOND COMMENT FIELD: ADAPT THE LINKS AS NEEDED; IF THE DOCS SPAN REPOS, BOLD THE ONE THAT IS REFERRED TO FROM THE PIPELINE 82 | _The first comment in this issue contains text that will automatically appear in one or more gap-analysis documents as a subsection with the same title as this issue. Any edits made to that comment will be immediately available in the Editor's draft of the document. Proposals for changes or discussion of the content can be made by adding comments below this point._ 83 | 84 | _Relevant gap analysis documents include:_ 85 | _[Adlam](https://www.w3.org/TR/adlm-gap#fragmentid) • [Arabic/Persian](https://www.w3.org/TR/alreq-gap#fragmentid) • [Bengali](https://www.w3.org/TR/beng-gap/#fragmentid) • [Cherokee](https://www.w3.org/TR/cher-gap#fragmentid) • [Chinese](https://www.w3.org/TR/clreq-gap#fragmentid) • [Dutch](https://www.w3.org/TR/latn-nl-gap#fragmentid) • [Ethiopic](https://www.w3.org/TR/elreq-gap#fragmentid) • [French](https://www.w3.org/TR/latn-fr-gap#fragmentid) • [Georgian](https://www.w3.org/TR/geor-gap#fragmentid) • [German](https://www.w3.org/TR/latn-de-gap#fragmentid) • [Greek](https://www.w3.org/TR/grek-gap#fragmentid) • [Gujarati](https://www.w3.org/TR/gujr-gap#fragmentid) • [Hebrew](https://www.w3.org/TR/hebr-gap#fragmentid) • [Hindi](https://www.w3.org/TR/deva-gap#fragmentid) • [Hungarian](https://w3c.github.io/eurlreq/gap-analysis/latn-nl-gap#fragmentid) • [Inuktitut/Cree](https://www.w3.org/TR/cans-iu-cr-gap#fragmentid) • [Japanese](https://www.w3.org/TR/jpan-gap#fragmentid) • [Javanese](https://www.w3.org/TR/java-gap#fragmentid) • [Kashmiri](https://www.w3.org/TR/arab-ks-gap#fragmentid) • [Khmer](https://www.w3.org/TR/khmr-gap#fragmentid) • [Korean](https://www.w3.org/TR/kore-gap#fragmentid) • [Lao](https://www.w3.org/TR/laoo-gap#fragmentid) • [Mongolian](https://www.w3.org/TR/mong-gap#fragmentid) • [N'Ko](https://www.w3.org/TR/nkoo-gap#fragmentid) • [Osage](https://www.w3.org/TR/osge-osa-gap#fragmentid) • [Punjabi](https://www.w3.org/TR/guru-gap#fragmentid) • [Tamil](https://www.w3.org/TR/taml-gap#fragmentid) • [Thai](https://www.w3.org/TR/thai-gap#fragmentid) • [Tibetan](https://www.w3.org/TR/tibt-gap#fragmentid) • [Uighur](https://www.w3.org/TR/arab-ug-gap#fragmentid)_ 86 | 87 | SETTING LABELS (delete before submitting) 88 | gap should already be assigned 89 | doc:... should point to each document _in this repo_ where this gap report will appear 90 | i:... should indicate the section in those documents where this will appear 91 | x:blink/gecko/webkit should be set for browser engines that don't resolve the gap (and removed when they do) 92 | x:... language or script related tags should be set for all affected languages 93 | p:... should indicate the priority of this gap 94 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Traditional Mongolian Language Enablement (mlreq) 2 | 3 | This is the place to explore gaps in support for languages that use the Traditional Mongolian script on the Web and in eBooks, and to document requirements. 4 | 5 | We aim to address the problem that local users don't know how to tell the W3C what problems exist for support of their language on the Web, and the W3C doesn't know how to contact people who can help when questions arise. 6 | 7 | Topics for discussion are suggested by [the gap-analysis template](https://www.w3.org/International/i18n-activity/templates/gap-analysis/gap-analysis_template.html). This work feeds into the [language matrix](https://www.w3.org/International/typography/gap-analysis/language-matrix.html) which provides a heat-map for language issues on the Web. 8 | 9 | 10 | ### Key links 11 | [GitHub repo](https://github.com/w3c/mlreq) • [Discussion threads](https://github.com/w3c/mlreq/issues) • [Charter](https://www.w3.org/International/mlreq/charter/) 12 | 13 | 14 | --- 15 | ## Help wanted! ### 16 | **We're looking for information about this writing system. Follow the link for specific questions.** 17 | 18 | **[Traditional Mongolian](https://github.com/w3c/mlreq/issues?q=is%3Aissue+is%3Aopen+label%3Aquestion)** 19 | 20 | --- 21 | 22 | 23 | 24 | 25 | ### Resource & requirement docs 26 | - **Mongolian Script Resources** • [DNOTE](https://www.w3.org/TR/mong-lreq) • [*Editor's draft*](https://www.w3.org/International/mlreq/mong/) • [*Latest commits*](https://github.com/w3c/mlreq/commits/gh-pages/mong/) 27 | - **Mongolian Layout Requirements** • [DNOTE](https://www.w3.org/TR/mlreq) • [*Editor's draft*](https://www.w3.org/International/mlreq/) • [*Latest commits*](https://github.com/w3c/mlreq/commits/gh-pages/index.html) 28 | 29 | 30 | 31 | ### Gap-analysis docs 32 | - **Mongolian Gap Analysis** • [DNOTE](https://www.w3.org/TR/mong-gap) • [*Editor's draft*](https://www.w3.org/International/mlreq/gap-analysis/) • [*Latest commits*](https://github.com/w3c/mlreq/commits/gh-pages/gap-analysis/index.html) 33 | 34 | 35 | 36 | ### Discussions 37 | - **Mongolian** • [*Questions*](https://github.com/w3c/mlreq/issues?q=is%3Aissue+is%3Aopen+label%3Aquestion) 38 | • [*Gap reports*](https://github.com/w3c/mlreq/labels/doc%3Among) 39 | • [*Other*](https://github.com/w3c/mlreq/issues?q=is%3Aopen+-label%3Aquestion+-label%3Agap) 40 | • [*Spec issues*](https://github.com/w3c/i18n-activity/issues?q=is%3Aopen+label%3Amlreq+label%3Aspec-type-issue) 41 | 42 | 43 | ### Related documents 44 | - [Mongolian Variant Forms](https://r12a.github.io/mongolian-variants/) (tracked former discussions about variant glyph standardisation) 45 | - [Encoding discussion document log](https://w3c.github.io/mlreq/variants/document-log.html) 46 | - [Ready-made Counter Styles](https://www.w3.org/TR/predefined-counter-styles/) 47 | 48 | 49 | ### Feedback 50 | Please use the [GitHub issue list](https://github.com/w3c/mlreq/issues) to report issues for language support, for discussions, and to send feedback about documents. (Learn [how GitHub issues work](https://www.w3.org/International/i18n-activity/guidelines/issues.html).) 51 | 52 | Note that the [public-i18n-mongolian](https://lists.w3.org/Archives/Public/public-i18n-mongolian/) mailing list is used to send notification digests & meeting minutes. It is **not** for technical discussion. 53 | 54 | **You may raise issues in Chinese, however any substantive discussions should be summarised in English at some point, so that non-Chinese speakers can follow the rationale and contribute comments.** 55 | 56 | ### Participate 57 | You can participate in the work at various levels. In order of increasing commitment, these include List subscriber, Participant, Editor, and Chair. [Explore the options](https://www.w3.org/International/i18n-drafts/pages/languagedev_participation.html). 58 | 59 | **To just follow the work:** Rather than 'Watch' this repository, [subscribe](mailto:public-i18n-mongolian-request@w3.org?subject=subscribe) to the [public-i18n-mongolian](https://lists.w3.org/Archives/Public/public-i18n-mongolian/) mailing list. That list is notified (no more than once a day, and in digest form), about changes to issues in this repository, but also about other W3C Working Group issues related to the Mongolian writing systems. 60 | 61 | **To contribute content:** All contributors should read and agree with [CONTRIBUTING.md](CONTRIBUTING.md). 62 | 63 | **To become a participant, editor, or chair:** contact [Richard Ishida](mailto:ishida@w3.org). We welcome participation requests. 64 | 65 | To get an idea about what's involved, see [Get involved with Language Enablement!](https://www.w3.org/International/i18n-drafts/pages/languagedev_participation). 66 | 67 | 68 | 69 | ### Contacts 70 | 71 | - Chairs: Nasun-urt, 胡其图 (Hu Qitu) 72 | - W3C staff: [Fuqiao Xue](mailto:xfq@w3.org), [Richard Ishida](mailto:ishida@w3.org) 73 | - [Group participants](https://www.w3.org/groups/tf/i18n-mlreq/participants) 74 | 75 | 76 | ### Links 77 | - [Mail archive](https://lists.w3.org/Archives/Public/public-i18n-mongolian/) 78 | - [Writing i18n tests](https://github.com/w3c/i18n-tests/wiki/Writing-i18n-tests) 79 | - [Practical tips for task forces](https://www.w3.org/International/i18n-activity/guidelines/process.html) (See also the github and editorial guidelines below) 80 | - Action tracker (tbd) 81 | - Meeting info (tbd) 82 | 83 | 84 | ### Links to background information 85 | The following information describes work going on at the W3C to support languages on the Web. 86 | - [Language support heatmap (matrix)](https://www.w3.org/International/typography/gap-analysis/language-matrix.html) 87 | - [Analysing support for text layout on the Web](https://www.w3.org/International/i18n-drafts/nav/languagedev) 88 | - [Overview of language enablement work in progress](https://www.w3.org/International/i18n-drafts/nav/languagedev) 89 | - [Get involved with Language Enablement](https://www.w3.org/International/i18n-drafts/pages/languagedev_participation) 90 | - [Setting up a Gap Analysis Project](https://github.com/w3c/typography/wiki/Setting-up-a-Gap-Analysis-Project) 91 | - [Internationalization Sponsorship Program](https://www.w3.org/International/sponsorship/) 92 | 93 | 94 | ### Links for editors 95 | If you end up creating a document, you should be familiar with and use the following: 96 | 97 | - [Github guidelines for working with i18n documents](https://www.w3.org/International/i18n-activity/guidelines/github) 98 | - [Editorial guidelines for working with i18n documents](https://www.w3.org/International/i18n-activity/guidelines/editing) 99 | -------------------------------------------------------------------------------- /homepage/index.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Mongolian Layout Task Force Home Page 6 | 7 | 8 | 9 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 51 | 52 | 53 | 54 |
55 | 56 | 57 | 58 | 59 |

Mongolian Layout Task Force
60 | Home Page

61 |
62 | 63 | 64 |

Key information: Mission - Charter - News - Work aims - Github repo - Communication - How to join

65 | 66 | 67 |
68 | 69 |
70 |

Mission

71 |

This task force does gap analysis and documents requirements, related to the layout and presentation of text in languages that use the Mogolian script, in the context of Web standards and technologies such as HTML, CSS, Mobile Web, Digital Publications, and Unicode.

72 |

How to Join

73 |

We welcome participation requests from people who are interested 74 | in contributing to the work of the Task Force. There are two ways to get involved:

75 |
    76 |
  1. Task force members are expert contributors 77 | who participate actively in producing the work of the group, regularly 78 | contributing text and advice to create the outputs, and participating in 79 | meetings. For more information about becoming a task force member 80 | contact Richard Ishida.
    2. 81 |
  2. It is also possible to follow and contribute to 82 | discussions without the commitment required in being an expert 83 | contributor. See the github home page for details.
    3. 84 |
85 |

Organisation of the task force

86 |

The Mongolian Layout Task Force is part of the W3C W3C 87 | Internationalization Interest Group (i18n IG). The Internationalization Working Group (i18n WG) oversees the work of the task force, and publishes the task force's document to the TR space.

88 |

The Task Force works closely with the Chinese National Committee 89 | for Standardization (Standardization Administration of China, SAC) 90 | , the National Information Technology Standardization Technical 91 | Committee TC28 / SC2 (IT / character set and encoding), TC28 / 92 | SC30 (IT / Chinese platform especially technology).

93 | The co-chairs of the task force are tbd. 94 | The chair of the Interest Group is Martin 95 | Dürst. 96 |

Internationalization at W3C

97 |

You can access the resources and news for the W3C Internationalization work at http://www.w3.org/International/.

98 |

The output of the task force is pointed to by the International text layout and typography index, and sits alongside similar work for other writing systems.

99 |

For information about layout and typographic requirements work for other scripts, see the page Layout & typography.

100 |
101 | 102 | 103 |
104 |

Work aims

105 |

The Mongolian Layout Task Force will not produce 106 | Recommendation-track deliverables but expects to produce Working 107 | Group Notes, published by the Internationalization 108 | Working Group.

109 |

To find and follow progress on deliverables, see the Github repo.

110 |

The main deliverables include the following:

111 | 117 |

The group charter also allows review of draft specifications 118 | produced by other working groups, and provision of translations of 119 | relevant W3C specifications and resources. The group may also choose to produce other non-normative deliverables, 120 | such as test cases and error reports, under the terms of the Policies 121 | for Contribution of Test Cases to W3C, and in coordination 122 | with any relevant working groups.

123 |

Communication

124 |

Most of the technical discussion takes place in the GitHub issues list. If you want to raise an issue with the documents, this is the place to raise it.

125 |

To follow the work, you can 'Watch' the repository, or subscribe to the public-i18n-mongolian mailing list, which is notified once a day about changes to the repo. The www-international list is also notified daily. (Please use github issues rather than the mailing list to send feedback.) Meeting minutes are sent to public-i18n-mongolian.

126 |

The group will use the W3C Internationalization home page and W3C China Website to disseminate public information about 127 | its activities.

128 |

There is also a public-mlreq-admin mailing list for internal and administrative use by the TF 129 | participants, for example for announcing teleconference agendas, new 130 | participants, preparing for publication, etc. or for discussing other 131 | non-technical, practical arrangements related to the group. Only 132 | participants in the task force are subscribed to that list.

133 |

The task force aims to hold teleconference or face-to-face 134 | meetings at least once a month, with additional 135 | meetings as needed to enable discussion and review status of the 136 | work.

137 |

The #mlreq IRC channel is used for supplementary communication and minute-taking during meetings. Instructions for use are sent out with the meeting agenda.

138 |
139 | 140 |
141 | 142 | 143 |
144 |

Chair: tbd
145 | Staff contact: Li Anqi, Richard Ishida
146 | $Id: Overview.html,v 1.77 2010/03/02 12:12:01 rishida Exp $

147 |

Copyright © 2018 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document 148 | use and software 149 | licensing rules apply. Your interactions with this site are in 150 | accordance with our public and Member privacy statements.

151 | 152 | -------------------------------------------------------------------------------- /charter/charter2019.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Mongolian Text Layout Task Force Charter 6 | 8 | 10 | 12 | 16 | 17 | 18 | 19 | 20 |
21 | 31 | 32 |

W3C

34 | 35 |

DRAFT Mongolian Layout Task Force Charter

36 |

The mission of this task force is to discuss and document gaps, document requirements, and offer advice for the layout and presentation of text in languages written in the Traditional Mongolian script when those languages are used by Web standards and technologies, such as HTML, CSS, Mobile Web, Digital Publications and Unicode.

37 |

The Traditional Mongolian script is used by various communities in 38 | north and east Asia, speaking different languages, 39 | and participation in this work by those communities is welcomed. 40 | This task force will gather and integrate feedback from the 41 | participating members about the need for and technical 42 | feasibility of various requirements.

43 |

The Task Force is part of the W3C Internationalization Interest Group. The Task Force will report the results of its activities as a group back to the W3C Internationalization Working Group, as well as to other relevant groups and to the W3C membership and community.

44 |

This charter is intended to reflect the current direction of the group, so that there is common agreement. It may be altered at any point in order to reflect new priorities or work items.

45 |
46 |

Join the Mongolian Text Layout Task Force.

47 |
48 | 49 | 50 | 51 | 52 | 53 | 54 | 55 | 56 | 59 | 60 | 61 | 62 | 63 | 64 | 65 | 67 | 68 | 69 | 70 | 71 | 74 | 75 | 76 |
End date31 December 2020
ConfidentialityProceedings are public
Initial ChairsNasun-urt, Hu Qitu
Initial Team Contacts
66 | (FTE %: 2)		Richard Ishida, Fuqiao Xue
Usual Meeting ScheduleTeleconferences: On an as-needed basis. Preferably, a minimum of two status meetings per month.
72 | Face-to-face meetings: On an as-needed basis.
73 | Video Conferences: On an as-needed basis.
77 | 78 |
79 |

Scope

80 |

This work aims to ensure that the W3C is developing a Web for All, with a particular emphasis on Traditional Mongolian script.

81 |

The group exists to allow a network of experts to share information about gaps and requirements for support of Traditional Mongolian script on the Web and in digital publications.

82 |

Topics for discussion are suggested by the gap-analysis document. This work supports the development of the matrix indicating hot-spots for language support. The focus is especially on typographic features for which information in English is hard to find, such as justification, letter-spacing, vertical text, text decoration, page layout, emphasis, etc. We want to ensure that we have captured local user needs in CSS, HTML, Timed Text, Web Payments, Web Publishing, and the many other specifications that the W3C produces.

83 |

A significant problem faced by the Web is that experts don't know how to tell the W3C what problems exist for support of their script or language, and the W3C doesn't know how to contact people who can help when questions arise. This network of experts should help to significantly reduce that problem. They will be asked to consider and advise on issues that arise during the development of technologies at W3C. See the i18n WG's Layout tracker page for examples of such issues.

84 |

Experts who are contributing members of the task force will go a step further, and contribute to documents produced by the group, as described in the section on deliverables below.

85 |

The information produced in documents or discussed via GitHub issues needs to be relayed to the appropriate groups at W3C (and perhaps in other groups), and task force participants will probably want to be involved in those discussions. The notification framework already in place helps participants track issues raised against W3C working groups.

86 |

In addition to the above, the group may do the following: 87 | 88 |

89 | 95 |

Initial set of languages

96 |

Several languages use the Traditional Mongolian script. The initial focus of this task force will be on the script as used for Mongolian in Mongolia and Inner Mongolia. 97 | Information regarding other languages will be included based 98 | on the availability of linguistic and typographic experts.

99 |
100 |

Deliverables

101 |

The Mongolian Text Layout Task Force will not produce Recommendation-track deliverables but will produce documents that can be published by the Internationalization Working Group as Working Group Notes. Such work is expected to include the following. The completion of the work depends upon resource availability.

102 |

The main deliverables are:

103 |
    104 |
  • A gap-analysis document, which is one of many similar documents that radiate out from the language matrix to help us track areas where better support is needed. The gap analysis document uses a standard structure to list issues that content users and content authors face relating to particular apects of text layout, provide pointers to tests, and prioritise the importance of the barriers documented. Work on the gap-analysis document may procede in phases, starting with a quick preliminary report.
    • 105 |
  • A document describing requirements for Mongolian text layout and presentation on the Web.
    • 106 |
  • Other documents advising standards developers and application developers on how to cater for Mongolian needs. Some of those documents may be developed elsewhere and brought to this group for review and subsequent publication.
    • 107 |
108 |

The format of the deliverables must conform to standard formats developed across the W3C language enablement work, so that the work can be integrated into the larger picture. The wider W3C framework into which this work fits is described in Analysing support for text layout on the Web.

109 |

Technology-specific information about Mongolian support should be included in the gap analysis resources, not in the layout requirements document. The latter should just describe how Mongolian is expected to work, in a technology agnostic way, so that it is enduringly relevant.

110 |

The group may also choose to produce other non-normative deliverables, such as test cases and error reports – under the terms of the Policies for Contribution of Test Cases to W3C, and in coordination with any relevant working groups.

111 |

Documents may be produced in Mongolian or Chinese, but must be translated into English. The English version will be the authoritative version at the W3C, since people who don't speak Mongolian are an important part of the target audience for the documents. In fact, making available information to an international audience is an important aspect of the group's mission. English snapshots of the document must be produced at regular intervals, so that the international community is able to review and comment on the work in progress.

112 |
113 |
114 | 115 |
116 |

Relationships to External Groups

117 | 118 |

Working Drafts and Notes will be published by the i18n WG, and the i18n WG will work with the task force closely to assist with development and review of the documents. For information about the wider framework into which the Mongolian layout work fits, see Analysing support for text layout on the Web.

119 | 120 |

Dependencies

121 |
122 |
The Mongolian Layout Task Force has no formal dependencies on any other W3C Working Groups. Important points of contact include:
123 |
124 | 134 |
135 |

136 |
Other Groups
137 |
The Mongolian Text Layout Task Force is also expected to take advantage of opportunities for discussion and collaboration with existing groups and communities in Mongolia and China as well as groups and communities elsewhere.
138 |
139 |
140 | 141 |
142 |

Participation

143 | 144 |

The Task Force provides for two levels of participation.

145 |

Followers are subscribed to the public-i18n-mongolian mailing list, where they can track discussions, and contribute opinions via the GitHub issue list. Rather than just 'Watch' the GitHub repository, it is best to subscribe to the mailing list, because that list is notified once a day (in digest form) about activity in the mlreq repository, but also about activity for other W3C Working Group issues related to Japanese. (Participants are expected to use github issues rather than the mailing list to send feedback.)

146 |

Task force members are expert contributors who participate actively in producing the work of the group, contributing text and advice to create the outputs, and participating in any meetings. These people are subscribed to the task force group by W3C staff.

147 |

All TF members and people making contributions (via issues or pull requests) must read and agree with CONTRIBUTING.md.

148 |

Participants are reminded of the Good 150 | Standing requirements of the W3C Process.

151 |

People contributing substantive text to the deliverables must be public invited experts or work for W3C member organizations, in order to meet the policy requirements of section 7 of this charter.

152 |
153 | 154 |
155 |

Communication

156 | 157 |

The mlreq GitHub repository and its issue list are the main vehicles for technical discussion. Discussion can be in Chinese, Mongolian and English but, where useful, discussions should be summarised in English when a conclusion is reached, so that the wider community can follow.

158 |

The public-i18n-mongolian@w3.org list receives notifications of changes in the mlreq repository, and also of changes to issues in other repositories when those issues are tagged with a mlreq label. This includes the CSS and HTML repositories, amongst others. That mailing list should not be used for technical discussion.

159 |

The public-i18n-mongolian@w3.org list must archive or point to 160 | minutes and summaries of all teleconferences and face-to-face 161 | meetings. Meeting minutes will list all attendees at a given 162 | meeting.

163 |

An administrative list, public-mlreq-admin, will also be 164 | used for internal communication about practical matters, such 165 | as meeting agenda, which should be published before each 166 | teleconference or face-to-face meeting.

167 | 168 |

The group will use the Internationalization Activity home page and W3C China Website to provide updated public information about its activities. 170 |

171 |

Information about the group (deliverables, participants, face-to-face meetings, teleconferences, etc.) is available from the mlreq GitHub repository.

172 |

Meetings may be held in Mongolian or Chinese, but an effort should be made to communicate key findings and conclusions in English in the minutes.

173 |
174 | 175 |
176 |

Decision Policy

177 | 178 |

As explained in the Process Document (section 3.3), 180 | this group will seek to make decisions when there is consensus. In cases where there is a need to formally produce a group resolution about a particular issue, its Chair will put a question about the issue to the group and gather responses (including any formal objections); then, after due consideration of all the responses, the Chair will record a group resolution (possibly after a formal vote and also along with responding to any formal objections).

181 |
182 | 183 |
184 |

Patent Policy

185 | 186 |

Participants in the Mongolian Text Layout Task Force are obligated to comply with W3C patent-disclosure policy as outlined out in Section 6 of the W3C Patent Policy document. Although the Mongolian Text Layout Task Force is not chartered to produce Recommendation-track documents that themselves require patent disclosure, participants in the group are nevertheless obligated to comply with W3C patent-disclosure policy for any Recommendation-track specifications that they review or comment on.

187 |

For more information about disclosure obligations for this group, please see 188 | the W3C Patent Policy 189 | Implementation.

190 |
191 | 192 |

About this Charter

193 | 194 |

This charter for the Mongolian Layout Task Force within the Internationalization Interest Group has been 195 | created according to section 6.2 of the Process Document. In the event of a conflict between this 198 | document or the provisions of any charter and the W3C Process, the W3C Process 199 | shall take precedence.

200 |
201 |
202 | Charter Author: Richard Ishida 203 |
204 | 205 |

Copyright© 2018 207 | W3C ® (MIT , ERCIM 213 | , Keio, 214 | Beihang) All Rights 215 | Reserved.

216 | 217 |

$Date: 2014/11/24 14:41:44 $

218 |
219 | 220 | 221 | -------------------------------------------------------------------------------- /charter/index.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Mongolian Layout Task Force Charter 6 | 8 | 10 | 12 | 16 | 17 | 18 | 19 | 20 |
21 | 31 | 32 |

W3C

34 | 35 |

Mongolian Layout Task Force Charter

36 |

The mission of this task force is to support the use of languages using the Traditional Mongolian script by Web standards and technologies, such as HTML, CSS, Mobile Web, Digital Publications and Unicode. It does this by establishing a network of experts who explore, discuss and document gaps and requirements for the languages in scope.

37 |

The Traditional Mongolian script is used by various communities in north and east Asia, speaking different languages, and participation in this work by those communities is welcomed. This task force will gather and integrate feedback from the participating members about the need for and technical feasibility of various requirements.

38 |

The Mongolian Layout Task Force is part of the W3C Internationalization Interest Group (i18n IG). The W3C Internationalization Working Group (i18n WG) oversees the work of the task force, and publishes the task force's documents to the TR space. The group uses the W3C Internationalization Activity home page to disseminate public information about its activities.

39 |

The output of the task force is pointed to by the International text layout and typography index, and sits alongside similar work for other writing systems. For information about layout and typographic requirements work for other scripts, see Layout & typography.

40 |

The wider W3C framework into which this work fits is described in Analysing support for text layout on the Web.

41 |

This charter is intended to reflect the current direction of the group, so that there is common agreement. It may be altered at any point in order to reflect new priorities or work items.

42 |
43 |

Join the Mongolian Layout Task Force.

44 |
45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 | 53 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | 63 | 64 | 65 | 66 | 67 | 70 | 71 | 72 |
End dateNo fixed end date.
ConfidentialityProceedings are public
Chair(s)Nasun-urt, Hu Qitu
Team Contact(s)Fuqiao Xue, Richard Ishida
Usual Meeting ScheduleTeleconferences: On an as-needed basis. Preferably, a minimum of one status meeting per month.
68 | Face-to-face meetings: On an as-needed basis.
69 | Video Conferences: On an as-needed basis.
73 | 74 |
75 |

Scope

76 |

The use of the GitHub issue list is not restricted to any particular language other than that the group is focused on languages using the Traditional Mongolian script.

77 |

Several languages use the Traditional Mongolian script. The initial focus of this task force is on the script as used for Mongolian in Mongolia and Inner Mongolia. Information regarding other languages will be included based on the availability of linguistic and typographic experts.

78 |
79 |

Deliverables

80 |

The Mongolian Text Layout Task Force will not produce Recommendation-track deliverables but will produce documents that can be published by the Internationalization Working Group as Working Group Notes or articles.

81 |

The group will also assist in developing tests for language features, most of which will be made available via the Internationalization Test Suite, and some of which may be ported to the Web Platform Tests repository.

82 |

The major deliverables of the program are:

83 |
    84 |
  1. a network of experts who receive notifications of issues raised in GitHub and respond when needed with advice about requirements for languages using Traditional Mongolian script on the Web. It aims to address the problem that experts don't know how to tell the W3C what problems exist for support of their language on the Web, and the W3C doesn't know how to contact people who can help when questions arise. This network of experts should help to significantly reduce that problem.
    2. 85 |
  2. gap-analysis documents focused on specific languages, which describe features that need attention and prioritise them. The gap-analysis document describes the problems, demonstrates them using tests or screen grabs, and describes whether work is needed on specifications (such as the CSS spec) or implementations (such as major web browsers). This work feeds into the language matrix which provides a heat-map for language issues on the Web.
    3. 86 |
  3. requirements document, which describe in a technology-agnostic way how the script/language works. The requirements document may be developed piecemeal, to match progress in the gap analysis documents, ie. as a new section is created for the latter, content may be added to the requirements document to indicate the expected result.
    4. 87 |
88 |

Note that the requirements document should always remain technology-agnostic, so that it is evergreen. The gap analysis document, however, should be technology-specific, and as issues are addressed parts of the gap analysis document will eventually become merely historical records (and should be labelled as such).

89 |

Documents may be produced in Mongolian or Chinese, but must be translated into English. The English version will be the authoritative version at the W3C, since people who don't speak Mongolian are an important part of the target audience for the documents. In fact, making available information to an international audience is an important aspect of the group's mission. English snapshots of the document must be produced at regular intervals, so that the international community is able to review and comment on the work in progress.

90 |

 

91 | 116 | 117 |
118 | 119 |

Success Criteria

120 | 121 |

The success of the Task Force will be evaluated based on:

122 |
    123 |
  1. the number of experts recruited to participate in or follow discussions
    2. 124 |
  2. the number of issues raised and dealt with
    3. 125 |
  3. the number of documents produced
    4. 126 |
  4. how successful the group is in advancing support for Mongolian languages and scripts on the Web
    5. 127 |
128 |

 

129 |
130 | 131 |
132 |

Relationships to other groups

133 | 134 |

Working Drafts and Notes will be published by the i18n WG, and the i18n WG will work with the task force closely to assist with development and review of the documents.

135 | 136 |

Dependencies

137 |
138 |
W3C Internationalization WG
139 |
The W3C i18n WG will oversee the work of the Task Force, and will 140 | publish the Working Drafts and Notes on their behalf. The i18n WG will also help the Task Force produce work that fits with the work of other Task Forces, and wider initiatives at the W3C.
141 |

142 |
143 |
W3C Publishing Working Group
144 |
The group will work with the Digital Publishing 145 | Working Group to ensure the work it is doing is known to 146 | that group and any issues that are common to the two groups are 147 | identified and tracked appropriately.
148 |

149 |
150 |
The group has no formal dependencies on any 151 | other W3C Working Groups, but important points of contact include:
152 |
153 | 160 |
161 |
Other Groups
162 |
The Task Force is also expected to take advantage of opportunities for discussion and collaboration with existing groups and communities in Mongolian countries as well as groups and communities elsewhere.
163 |
164 |
165 | 166 |
167 |

Participation

168 | 169 |

A number of types of participation are possible, ranging from very low commitment (eg. 'Followers') to significant (eg. 'Editors' and 'Chairs'). These are described in a wiki page.

170 | 171 |

The GitHub home page for the group describes how to participate.

172 |

Everyone participating in the work of the task force, be it through the issue list, by contributing content or tests, or any other communication, must do so in conformance with the provisions of the CONTRIBUTING document.

173 |

People contributing substantive text to the deliverables must be public invited experts or work for W3C member organizations, in order to meet the policy requirements of section 7 of this charter.

174 |

 

175 |
176 | 177 |
178 |

Communication

179 | 180 |

The group primarily conducts its work on the 181 | GitHub repository at https://github.com/w3c/mlreq/. Discussion can be in Chinese, Mongolian and English but, where useful, discussions should be summarised in English when a conclusion is reached, so that the wider community can follow.

182 |

The GitHub issue list is used to report issues for language support, for discussions, and to send feedback about documents.

183 |

The public-i18n-mongolian mailing list is used to send notification digests & meeting minutes. It is not for technical discussion.

184 |

There is also a public-alreq-admin mailing list for internal and administrative use by the TF participants, for example for announcing teleconference agendas, new participants, preparing for publication, etc. or for discussing other non-technical, practical arrangements related to the group. Only participants in the task force are subscribed to that list.

185 |

The group uses the W3C Internationalization Activity home page and W3C China Website to disseminate public information about its activities.

186 |

When there is a quorum of Participants, the task force should aim to hold teleconference or face-to-face meetings at least once a month, with additional meetings as needed to enable discussion and review status of the work. Such meetings have proven to be extremely useful in maintaining the heartbeat of the work. Meetings may be held in Mongolian or Chinese, but an effort should be made to communicate key findings and conclusions in English in the minutes.

187 |

The #mlreq IRC channel is used for supplementary communication and for minute-taking during meetings. Instructions for use are sent out with the meeting agenda.

188 |

 

189 |
190 | 191 |
192 |

Decision Policy

193 | 194 |

As explained in the Process Document (section 3.3), 196 | this group will seek to make decisions when there is consensus. In cases where there is a need to formally produce a group resolution about a particular issue, its Chair will put a question about the issue to the group and gather responses (including any formal objections); then, after due consideration of all the responses, the Chair will record a group resolution (possibly after a formal vote and also along with responding to any formal objections).

197 |
198 | 199 |
200 |

Patent Policy

201 | 202 |

Participants in the Task Force are obligated to comply with W3C patent-disclosure policy as outlined in Section 6 of the W3C Patent Policy document. Although the Task Force is not chartered to produce Recommendation-track documents that themselves require patent disclosure, participants in the group are nevertheless obligated to comply with W3C patent-disclosure policy for any Recommendation-track specifications that they review or comment on.

203 |

For more information about disclosure obligations for this group, please see 204 | the W3C Patent Policy 205 | Implementation.

206 |
207 | 208 |

About this Charter

209 | 210 |

This charter for the Task Force within the Internationalization Interest Group is not a formal document and does not require W3C management or Advisory Committee review or approval. It is intended to summarise the goals and procedures of the group at any given time, and can be changed at any time to realign with changed priorities for the group.

211 |
212 |
213 | Charter Authors: Richard Ishida 214 |
215 | 216 |

Copyright © 2019 218 | W3C ® (MIT , ERCIM 224 | , Keio, 225 | Beihang) All Rights 226 | Reserved.

227 |
228 | 229 | 230 | -------------------------------------------------------------------------------- /gap-analysis/index.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | Mongolian Gap Analysis 8 | 9 | 10 | 11 | 12 | 58 | 59 | 60 | 61 | 62 | 63 |
64 |

This document describes and prioritises gaps for the support of the Mongolian script on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, such as HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.

65 |
66 | 67 | 68 |
69 |

This document describes and prioritises gaps for the support of the Mongolian script on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders. 70 | It is linked to from the language matrix that tracks Web support for many languages.

71 | 72 |

The editor's draft of this document is being developed in the GitHub repository Mongolian Language Enablement (mlreq), with contributors from the W3C Internationalization Interest Group. It is published by the Internationalization Working Group. The end target for this document is a Working Group Note.

73 |
74 | 75 | 76 | 77 | 78 | 79 | 80 | 81 | 82 | 83 | 84 | 85 | 86 |
87 |

Contributors

88 | 89 |

The framework of this document was created by Richard Ishida. The text for most gap descriptions is automatically pulled from GitHub issues, and that text may have been written or contributed to by others.

90 | 91 | 96 | 97 |

See also the GitHub contributors list for the Mongolian Language Enablement project, and the discussions related to the Mongolian script.

98 |
99 | 100 | 101 | 102 | 103 | 104 | 105 |
106 |

About this document

107 | 108 | 109 |

The W3C needs to make sure that the needs of scripts and languages around the world are built in to technologies such as HTML, CSS, SVG, etc. so that Web pages and eBooks can look and behave as people expect around the world.

110 | 111 |

This page documents difficulties that people encounter when trying to use languages written in the Mongolian script on the Web.

112 | 113 |

Having identified an issue, it investigates the current status with regards to web specifications and implementations by user agents (browsers, e-readers, etc.), and attempts to prioritise the severity of the issue for web users.

114 | 115 | 116 | 117 | 118 | 119 | 120 | 121 |
122 |

Prioritization

123 | 124 |

This document not only describes gaps, it also attempts to prioritise them in terms of the impact on the local user. The prioritisation is indicated by colour.

125 | 126 |

Key:

127 | 135 | 136 |

It is important to note that these colours do not indicate to what extent a particular feature is broken. They indicate the impact of a broken or missing feature on the content author or end user.

137 | 138 |

A cell can be scored as OK if the feature in question is specified in an appropriate specification (including Candidate Recommendations), and is supported by at least two major browser engines.

139 | 140 |

Advanced level support includes features that one might expect to include in ebooks or other advanced typographic formats. If a feature of a script or language is not supported on the Web, but is not generally regarded as necessary (usually archaic or obscure features), even if the feature is described here, the status may be marked as OK. The decision as to what priority level is assigned to a described gap is down to the experts doing the gap analysis. It may not always be straightforward to decide.

141 | 142 |

If a given section in this document refers to more than one feature that is broken, each with different impacts on Web users, the priority for the section will be the lowest denominator.

143 |
144 | 145 | 146 | 147 | 148 | 149 | 150 | 151 | 160 |
161 | 162 | 163 | 164 | 165 | 166 | 167 | 168 | 169 | 170 | 171 | 172 | 173 | 174 | 175 |
176 |

Text direction

177 | 178 |

See also General page layout & progression for features such as column layout, page turning direction, etc. that are affected by text direction.

179 | 180 | 181 | 182 | 183 |
184 |

Writing mode

185 |

186 | 187 |
188 |
189 | 190 | 191 | 192 | 193 | 194 |
195 |

Bidirectional text

196 |

197 | 198 |
199 | 200 |
201 |
202 | 203 | 204 | 205 | 206 | 207 | 208 | 209 | 210 | 211 | 212 | 213 | 214 | 215 | 216 | 217 | 218 |
219 |

Glyph shaping & positioning

220 | 221 | 222 | 223 |
224 |

Fonts & font styles

225 |

226 | 227 | 228 |
229 |
230 | 231 | 232 | 233 | 234 | 235 | 236 | 237 | 238 | 239 |
240 |

Context-based shaping and positioning

241 |

242 | 243 | 244 |
245 |
246 | 247 | 248 | 249 | 250 | 251 | 252 | 253 | 254 | 255 |
256 |

Letterform slopes, weights, & italics

257 |

258 | 259 | 260 |
261 |
262 | 263 | 264 | 265 | 266 | 267 | 268 | 269 | 270 |
271 |

Cursive text

272 |

273 | 274 | 275 |
276 |
277 | 278 | 279 | 280 | 281 | 282 | 283 | 284 | 285 | 286 |
287 |

Case & other character transforms

288 |

289 | 290 | 291 |
292 |
293 |
294 | 295 | 296 | 297 | 298 | 299 | 300 | 301 | 302 | 303 | 304 | 305 | 306 | 307 | 308 | 309 | 310 | 311 | 312 |
313 |

Typographic units

314 | 315 | 316 |
317 |

Characters & encoding

318 |

319 | 320 |
321 |
322 | 323 | 324 | 325 | 326 | 327 | 328 | 329 | 330 | 331 |
332 |

Grapheme/word segmentation & selection

333 |

334 | 335 | 336 |
337 |
338 |
339 | 340 | 341 | 342 | 343 | 344 | 345 | 346 | 347 | 348 | 349 | 350 | 351 | 352 | 353 |
354 |

Punctuation & inline features

355 | 356 | 357 | 358 |
359 |

Phrase & section boundaries

360 |

361 | 362 | 363 |
364 |
365 | 366 | 367 | 368 | 369 | 370 | 371 | 372 | 373 |
374 |

Quotations & citations

375 |

376 | 377 | 378 |
379 |
380 | 381 | 382 | 383 | 384 | 385 | 386 | 387 | 388 |
389 |

Emphasis & highlighting

390 |

391 | 392 | 393 |
394 |
395 | 396 | 397 | 398 | 399 | 400 | 401 | 402 | 403 |
404 |

Abbreviation, ellipsis & repetition

405 |

406 | 407 | 408 |
409 |
410 | 411 | 412 | 413 | 414 | 415 | 416 | 417 | 418 | 419 |
420 |

Inline notes & annotations

421 |

422 | 423 | 424 |
425 |
426 | 427 | 428 | 429 | 430 | 431 | 432 | 433 |
434 |

Text decoration & other inline features

435 |

436 | 437 | 438 |
439 |
440 | 441 | 442 | 443 | 444 | 445 | 446 | 447 | 448 |
449 |

Data formats & numbers

450 |

451 | 452 | 453 |
454 |
455 | 456 | 457 | 458 | 459 | 460 | 461 | 462 | 463 | 470 | 471 |
472 | 473 | 474 | 475 | 476 | 477 | 478 | 479 | 480 | 481 | 482 | 483 | 484 | 485 | 486 | 487 |
488 |

Line and paragraph layout

489 | 490 | 491 |
492 |

Line breaking & hyphenation

493 |

494 | 495 | 496 |
497 |
498 | 499 | 500 | 501 | 502 | 503 | 504 | 505 | 506 |
507 |

Text alignment & justification

508 |

509 | 510 | 511 |
512 |
513 | 514 | 515 | 516 | 517 | 518 | 519 | 520 | 521 | 522 | 523 |
524 |

Text spacing

525 |

526 | 527 | 528 | 529 |
530 |
531 | 532 | 533 | 534 | 535 | 536 | 537 | 538 | 539 |
540 |

Baselines, line-height, etc

541 |

542 | 543 | 544 |
545 |
546 | 547 | 548 | 549 | 550 | 551 | 552 | 553 | 554 |
555 |

Lists, counters, etc.

556 |

557 | 558 | 559 |
560 |
561 | 562 | 563 | 564 | 565 | 566 | 567 | 568 | 569 |
570 |

Styling initials

571 |

572 | 573 | 574 |
575 |
576 | 577 | 578 | 579 | 580 | 581 | 582 | 583 | 584 | 591 | 592 |
593 | 594 | 595 | 596 | 597 | 598 | 599 | 600 | 601 | 602 | 603 | 604 | 605 | 606 | 607 | 608 | 609 | 610 | 611 |
612 |

Page & book layout

613 | 614 |
615 |

General page layout & progression

616 |

617 | 618 | 619 |
620 |
621 | 622 | 623 | 624 | 625 | 626 | 627 | 628 | 629 |
630 |

Grids & tables

631 |

632 | 633 | 634 |
635 |
636 | 637 | 638 | 639 | 640 | 641 | 642 | 643 | 644 |
645 |

Footnotes, endnotes, etc.

646 |

647 | 648 | 649 |
650 |
651 | 652 | 653 | 654 | 655 | 656 | 657 | 658 | 659 |
660 |

Page headers, footers, etc.

661 |

662 | 663 | 664 | 665 |
666 |
667 | 668 | 669 | 670 | 671 | 672 | 673 | 674 | 675 |
676 |

Forms & user interaction

677 |

678 | 679 | 680 |
681 |
682 | 683 | 684 | 685 | 686 | 687 | 688 | 689 | 690 | 696 |
697 | 698 | 699 | 700 | 701 | 702 | 703 | 704 | 705 | 706 | 707 | 708 | 709 | 710 | 711 | 712 | 713 | 714 |
715 |

Other

716 | 717 | 718 |
719 |

Culture-specific features

720 |

Sometimes a script or language does things that are not common outside of its sphere of influence. This is a loose bag of additional items that weren't previously mentioned. This section may also be relevant for observations related to locale formats (such as number, date, currency, format support).

721 | 722 | 723 |
724 |
725 | 726 | 727 | 728 |
729 |

What else?

730 |

There are many other CSS modules which may need review for script-specific requirements, not to mention the SVG, HTML, Speech, MathML and other specifications. What else is likely to cause problems for worldwide deployment of the Web, and what requirements need to be addressed to make the Web function well locally?

731 | 732 | 733 |
734 |
735 | 736 |
737 | 738 | 739 | 740 | 741 |
742 | Show summary 743 | 

744 | 

745 | 
748 | 
749 | 
750 | 
751 | 
752 | 
761 | 
762 | 
763 | 


--------------------------------------------------------------------------------
/variants/document-log.html:
--------------------------------------------------------------------------------
  1 | 
  2 | 
  3 | 
  4 | 
  5 | Document log for Mongolian Variants discussion
  6 | 
  7 | 
  8 | 
  9 | 
 10 | 

 11 | 
Document/example log for Mongolian Variants discussion

 12 | 

 13 | 
 14 | 
This document has links to documents discussed on the public-i18n-mongolian mailing list in discussions related to standardisation of Mongolian variant forms. For more information see Mongolian variant forms.

 15 | 
 16 | 
 17 |   
 18 |     
 19 |     
 20 |     
 21 |     
 22 |   
 23 |   
 24 |     
 25 |     
 27 |     
 28 |     
 29 |   
 30 |   
 31 |     
 32 |     
 34 |     
 35 |     
 36 |   
 37 |   
 38 |     
 39 |     
 41 |     
 42 |     
 43 |   
 44 |   
 45 |     
 46 |     
 48 |     
 49 |     
 50 |   
 51 |   
 52 |     
 53 |     
 54 |     
 55 |     
 56 |   
 57 |   
 58 |     
 59 |     
 60 |     
 61 |     
 62 |   
 63 |   
 64 |     
 65 |     
 66 |     
 67 |     
 68 |   
 69 |   
 70 |     
 71 |     
 72 |     
 73 |     
 74 |   
 75 |   
 76 |     
 77 |     
 78 |     
 79 |     
 80 |   
 81 |   
 82 |     
 83 |     
 85 |     
 86 |     
 87 |   
 88 |   
 89 |     
 90 |     
 91 |     
 92 |     
 93 |   
 94 |   
 95 |     
 96 |     
 97 |     
 98 |     
 99 |   
100 |   
101 |     
102 |     
103 |     
104 |     
106 |   
107 |   
108 |     
109 |     
110 |     
111 |     
112 |   
113 |   
114 |     
115 |     
116 |     
117 |     
118 |   
119 |   
120 |     
121 |     
122 |     
123 |     
124 |   
125 |   
126 |     
127 |     
128 |     
129 |     
130 |   
131 |   
132 |     
133 |     
134 |     
135 |     
136 |   
137 |   
138 |     
139 |     
140 |     
141 |     
142 |   
143 |   
144 |     
145 |     
146 |     
147 |     
148 |   
149 |   
150 |     
151 |     
152 |     
153 |     
154 |   
155 |   
156 |     
157 |     
158 |     
159 |     
160 |   
161 |   
162 |     
163 |     
164 |     
165 |     
166 |   
167 |   
168 |     
169 |     
170 |     
171 |     
172 |   
173 |   
174 |     
175 |     
176 |     
177 |     
178 |   
179 |   
180 |     
181 |     
182 |     
183 |     
186 |   
187 |   
188 |     
189 |     
190 |     
191 |     
192 |   
193 |   
194 |     
195 |     
196 |     
197 |     
198 |   
199 |   
200 |     
201 |     
202 |     
203 |     
204 |   
205 |   
206 |     
207 |     
208 |     
209 |     
210 |   
211 |   
212 |     
213 |     
214 |     
215 |     
216 |   
217 |   
218 |     
219 |     
220 |     
221 |     
222 |   
223 |   
224 |     
225 |     
226 |     
227 |     
228 |   
229 |   
230 |     
231 |     
232 |     
233 |     
234 |   
235 |   
236 |     
237 |     
238 |     
239 |     
240 |   
241 |   
242 |     
243 |     
244 |     
245 |     
246 |   
247 |   
248 |     
249 |     
250 |     
251 |     
252 |   
253 |   
254 |     
255 |     
256 |     
257 |     
258 |   
259 |   
260 |     
261 |     
262 |     
263 |     
264 |   
265 |   
266 |     
267 |     
268 |     
269 |     
270 |   
271 |   
272 |     
273 |     
274 |     
275 |     
276 |   
277 |   
278 |     
279 |     
280 |     
281 |     
282 |   
283 |   
284 |     
285 |     
286 |     
287 |     
288 |   
289 |   
290 |     
291 |     
293 |     
294 |     
295 |   
296 |   
297 |     
298 |     
300 |     
301 |     
302 |   
303 |   
304 |     
305 |     
307 |     
308 |     
309 |   
310 |   
311 |     
312 |     
313 |     
314 |     
315 |   
316 |   
317 |     
318 |     
319 |     
320 |     
321 |   
322 |   
323 |     
324 |     
325 |     
326 |     
327 |   
328 |   
329 |     
330 |     
331 |     
332 |     
333 |   
334 |   
335 |   
336 |     
337 |     
338 |     
339 |     
340 |   
341 |   
342 |     
343 |     
344 |     
345 |     
346 |   
347 |   
348 |     
349 |     
350 |     
351 |     
352 |   
353 |   
354 |     
355 |     
356 |     
357 |     
358 |   
359 |   
360 |     
361 |     
362 |     
363 |     
364 |   
365 |   
366 |     
367 |     
368 |     
369 |     
370 |   
371 |   
372 |     
373 |     
374 |     
375 |     
376 |   
377 |   
378 |     
379 |     
380 |     
381 |     
382 |   
383 |   
384 |     
385 |     
386 |     
387 |     
388 |   
389 |   
390 |     
391 |     
392 |     
393 |     
394 |   
395 |   
396 |     
397 |     
398 |     
399 |     
400 |   
401 |   
402 |     
403 |     
404 |     
405 |     
406 |   
407 |   
408 |     
409 |     
410 |     
411 |     
412 |   
413 |   
414 |     
415 |     
416 |     
417 |     
418 |   
419 |   
420 |     
421 |     
422 |     
423 |     
424 |   
425 | 
OwnerLatest versionList notifiedNotes
Andrew WestExamples of Baluda and Triple Baluda usage2015-08-05 
Badral Sanligуруулийн дөрвөн эгшиг2015-09-28 
Badral Sanlig1822 variants2015-10-12 
Badral Sanlig1824/26 with drop2015-10-15 
Greg Eck DS00 Standard Mongolian MVS model2015-07-08previous versions: 2015-06-29, 2015-07-04
Greg Eck DS00 Standard Mongolian NNBSP model2015-07-08previous versions: 2015-06-29, 2015-07-04, 2015-07-15
Greg Eck DS01 Mongolian Head Forms, Positional Forms, & Variant Forms2016-04-10previous versions: 2015-09-12, 2015-08-10
Greg Eck DS04 Mongolian MVS Connected AE2015-07-08previous versions: 2015-07-04
Greg EckDS05 Mongolian NNBSP Connected Suffixes2015-07-08updated 2015-07-15, 2015-07-04
Greg EckExamples of Baluda and Triple Baluda usage2015-08-01 
Greg Eck U+1880-U+1884 in Word2015-08-02 
Greg EckFVS mismatch (.doc)2015-08-02 
Greg EckRules for 4 Overrides2015-08-30
commented on by Jirimutu on 2015-08-25

105 |     
previous versions: 2015-08-14
Greg EckDS11 Mongolian Final GA Test Data2015-08-23 
Greg EckDS12 Mongolian Medial GA Test Data2015-08-23 
Greg EckIsolate comparison between fonts2015-10-03previous versions: 2015-09-28, 2015-09-26
Greg EckMongolian consonant-vowel ligatures2015-10-09 
JirimutuMVS Model discussion2015-07-122015-07-05, 2015-07-07, 2015-07-09
JirimutuNNBSP Model discussion2015-07-07 
JirimutuExamples of Ambiguity in spelling - Mongol, odo2015-08-04 
JirimutuExamples of Ambiguity in spelling - bicig, sayiqan (2x), naima2015-08-04 
Jirimutu Issues in teaching and the usage of the Mongolian I2015-08-04previous versions: 2015-08-04
Jirimutu Mongolian Unicode FVS assignment Basic Principles2015-08-05 
Jirimutu FVS Assignment for QA/GA (.doc)2015-08-08 
Jirimutu FVS Final A E Requirement2015-08-08 
Jirimutu About the Mongolian Diphthong2015-08-10
translation of 关于蒙古文书面语双元音的思考

185 |     
previous versions: 2015-08-09
JirimutuFVS Discussion Frame05-Aug-15 
JirimutuMedial & Final GA exceptions24-Aug-15 
JirimutuGB25914 pages2015-09-13 
JirimutuMongolian alphabet2015-09-29 
JirimutuQqir2015-10-19 
JirimutuSibe/Manchu isolates2015-10-05 
JirimutuInner Mongolian Normal University diphthongs & translation2015-11-17previous versions: 2015-10-27
Jirimutu1867 final2015-11-02 
JirimutuMongolia Educational Publishing House diphthongs2015-11-04previous versions: 2015-11-03
JirimutuProfessor Bateer of Social Academy of Inner Mongolia (内蒙古社会科学院) diphthongs2015-11-17previous versions: 2015-11-12
Kamal MansourNoto Sans handling of  NNBSP/MVS2105-06-10 
Liang Jinbao关于蒙古文书面语双元音的思考2015-08-03 
Martin HeijdraManchu rules2015-11-16 
Martin HeijdraMongolian swashes2015-11-16 
Martin HeijdraTong wen yun tong2015-11-16 
Michel SuignardDS01 Mongolian Base Positional Variant Forms2015-08-28 
Myatav Erdenechimegpictures of bui_j-a, qqir, yabui-a2015-08-03 
Richard IshidaStyling vertical text2015-05-26 
Richard IshidaU+202F NNBSP Impact on Mongolian Options2015-07-29Summary statement to UTC regarding NNBSP situation in Mongolian
Richard IshidaShape index2015-08-07 
SiqinBiligeDS05 Mongolian NNBSP Connected Sufixes Others2015-07-09 
SiqinBiligeUsage of -dag/-deg2015-07-15previous versions: 2015-07-14
SiqinBiligeExplanations of MVS, NNBSP and ZWNJ2015-07-17 
SiqinBiligeNa exceptions2015-08-06 
SiqinBiligeSD GA with dots2015-08-25 
SiqinBiligeGuessing the Spelling Examples2015-08-10 
SiqinBiligeIsolate comparison examples2015-09-29 
SiqinBiligeTodo long vowels2015-10-15 
SiqinBiligeMiddle yi2015-10-15 
SiqinBilige182C initial middle2015-10-19 
SiqinBiligeTodo alphabet2015-10-19 
SiqinBiligeManchu A E2015-10-19 
SiqinBiligeSibe/Manchu isolate I2015-10-19 
SiqinBiligeSibe/Manchu zha, second set2015-10-21, -23 
SiqinBilige1864 final2015-10-26 
SiqinBilige1868/69 examples2015-10-27 
SiqinBiligeGenitive dotted 1824/262015-11-12 
SiqinBiligeManchu MVS A E2015-11-13 

426 | 
Other reference documents

427 | 
428 |   
429 |     
430 |     
431 |     
432 |     
433 |   
434 |   
435 |     
436 |     
438 |     
439 |     
440 |   
441 |   
442 |     
443 |     
444 |     
445 |     
446 |   
447 |   
448 |     
449 |     
450 |     
451 |     
452 |   
453 |   
454 |     
455 |     
456 |     
457 |     
458 |   
459 | 
OwnerLatest versionDateNotes
Prof. Quejingzhabu蒙古文编码2000This version is out of date. Prof. Quejingzhabu is currently working on a 9th edition.
Unicode ConsortiumStandardized Variants2015-05-19This document is problematic and the Mongolian variants discussion aims to provide the information for its update.
Aaron Bell, Greg Eck, Andrew GlassProposal to update the code charts for Mongolian (L2/14-031)2014-01-20This is out of date. See DS001 above.
Asmus FreytagMongolian Unicode Project Home Page2004-11-12Contains a list of additional reference documents.

460 | 
461 | 
462 | 


--------------------------------------------------------------------------------
/index.html:
--------------------------------------------------------------------------------
   1 | 
   2 | 
   3 | 
   4 | 
   5 |   
   6 | 
   7 |   Mongolian Layout Requirements
   8 |   
   9 |   
  43 |   
  44 | 
  45 | 
  46 | 
  47 | 

  48 | 
This document describes or points to requirements for the layout and presentation of text in languages that use the Traditional Mongolian script. The target audience is developers of Web standards and technologies, such as HTML, CSS, Mobile Web, Digital Publications, and Unicode, as well as implementers of web browsers, ebook readers, and other applications that need to render Mongolian text.

  49 | 

  50 | 
  51 | 

  52 | 
This document describes the basic requirements for Mongolian script layout and text support on the Web and in eBooks. These requirements provide information for Web technologies such as CSS, HTML and digital publications about how to support users of Mongolian script languages. Currently the document focuses on the Traditional Mongolian script as used for Mongolian. The information here is developed in conjunction with a document that summarises gaps in support on the Web for Mongolian.

  53 | 
The editor's draft of this document is being developed by the Mongolian Layout Task Force, part of the W3C Internationalization Interest Group. It is published by the Internationalization Working Group. The end target for this document is a Working Group Note.

  54 | 
To make it easier to track comments, please raise separate issues or emails for each comment, and point to the section you are commenting on  using a URL.

  55 | 

  56 | 
  57 | 
  58 | 
  59 | 

  60 | 
Some links on this page point to repositories or pages to which information will be added over time. Initially, the link may produce no results, but as issues, tests, etc. are created they will show up.

  61 | 
  62 | 
Links that have a gray color led to no content the last time this document was updated.  They are still live, however, since relevant content could be added at any time. When the document is updated, links that now point to results will have their live colour restored.

  63 | 

  64 | 
  65 | 
  66 | 
  67 | 
  68 | 
  69 | 
  70 | 
  71 | 
  72 | 
  73 | 
  74 | 
  75 | 

  76 | 
Introduction

  77 | 
  78 | 
  79 | 
  80 | 
  81 | 
  82 | 

  83 | 
Contributors

  84 | 
  85 | 
The original text of this document was prepared by Nasun-urt and Hu Chitu. Richard Ishida reorganised the material and added the script overview.

  86 | 
  87 | 
See also the GitHub contributors list for the Mongolian Language Enablement project, and the discussions related to Traditional Mongolian script.

  88 | 

  89 | 
  90 | 
  91 | 
  92 | 
  93 | 
  94 | 
  95 | 

  96 | 
About this document

  97 | 
  98 | 
The aim of this document is to describe the basic requirements for Traditional Mongolian script layout and text support on the Web and in eBooks. These requirements provide information for Web technologies such as CSS, HTML and digital publications, and for application developers, about how to support users of the Mongolian script. The document currently focuses on texts using the Mongolian language.

  99 | 
 100 | 
 101 | 
The main purpose of this document is to provide standardization and guiding rules for the display and application of traditional Mongolian script in the web. However, the more complex layout requirements such as paper layout are not included in this document. Thus, this document includes the most basic rules of display of page and characters of the traditional Mongolian script, aiming at formulating the corresponding standards of web display and application of Mongolian script for the web application vendors to follow this standard of display and application of Mongolian script in the web.

 102 | 
 103 | 
 104 | 
 105 | 
 106 | 
 107 | 

 108 | 
Terminology

 109 | 
 110 | 
The following terms and definitions apply to this standard.

 111 | 
 112 | 
 113 | 

 114 | 
Composition

 115 | 
The composition in the W3C Standard Format includes Mongolian characters, punctuation marks, and other marks related to the script.

 116 | 
Mongolian Space

 117 | 
Two spaces are used in Mongolian, U+0020 SPACE and the  Mongolian space U+202F NARROW NO-BREAK SPACE.

 118 | 
 119 | 
Mongolian Symbols

 120 | 
This refers to various symbols used in Mongolian text. In formulating the Mongolian coding standard, some of the codes is used in the coding area of the Mongolian standard, while the rest are symbols used in the scripts of other ethnic groups, due to the fact that some symbols are borrowed from other ethnic groups. 

 121 | 
 122 | 
Baseline

 123 | 
Baseline in Mongolian is called “Nirogo”. Mongolian writing is generally aligned to the baseline. 

 124 | 
 125 | 
Writing Direction

 126 | 
It refers to the default direction of writing. For example, English writing direction is horizontal from top to bottom, while the Mongolian writing is vertical from left to right. 

 127 | 
 128 | 
Text Width

 129 | 
Text width indicates the distance from the word at the left start to the word at the right end in a line in Mongolian, in the equivalent of the height of the horizontal  English or Chinese text writing. 

 130 | 
 131 | 
Text Height

 132 | 
Text height refers to the height of a Mongolian word, in equivalent of the width of the horizontal English or Chinese text writing. 

 133 | 
 134 | 
Text Spacing

 135 | 
Text spacing refers to the gap between the Mongolian words.

 136 | 
 137 | 
Leftline and Rightline

 138 | 
As the Mongolian writing is vertical, the right line, the left line and the line through is equivalent to the underline and overline in the horizontal English or Chinese text writing. 

 139 | 

 140 | 

 141 | 

 142 | 
 143 | 
 144 | 
 145 | 
 146 | 
 147 | 
 148 | 

 149 | 
Gap analysis

 150 | 
 151 | 
This document is pointed to by a separate document, Mongolian Gap Analysis, which describes gaps in support for Mongolian on the Web, and prioritises and describes the impact of those gaps on the user.

 152 | 
 153 | 
Wherever an unsupported feature is indentified through the gap analysis process, the requirements for that feature need to be documented. The gap reports will typically point back to this document for more information.

 154 | 
 155 | 
As gaps in support for Mongolian are captured, the gaps can be brought to the attention of the relevant spec developer or the browser implementator community. The progress of such work is tracked in the Gap Analysis Pipeline.

 156 | 
 157 | 
This document should contain no reference to a particular technology. For example, it should not say "CSS does/doesn't do such and such", and it should not describe how a technology, such as CSS, should implement the requirements. It is technology agnostic, so that it will be evergreen, and it simply describes how the script works. The gap analysis document is the appropriate place for all kinds of technology-specific information.

 158 | 

 159 | 
 160 | 
 161 | 
 162 | 
 163 | 
 164 | 
 165 | 
 166 | 

 167 | 
Other related resources

 168 | 
 169 | 
To complement any content authored specifically for this document, the sections in the document also point to related, external information, tests, GitHub discussions, etc.

 170 | 
 171 | 
The document Language enablement index points to this document and others, and provides a central location for developers and implementers to find information related to various scripts.

 172 | 
 173 | 
The W3C also has a repository with discussion threads related to the Mongolian script, including requests from developers to the user community for information about how scripts/languages work, and a notification system that tracks issues in W3C working groups related to the Mongolian script. See a list of unresolved questions for Mongolian experts. Each section below points to related discussions. See also the repository home page.

 174 | 

 175 | 

 176 | 
 177 | 
 178 | 
 179 | 
 180 | 
 181 | 
 182 | 
 183 | 
 184 | 
 185 | 
 186 | 
 187 | 
 188 | 
 189 | 
 190 | 
 191 | 
 192 | 
 193 | 

 194 | 
Mongolian Script Overview

 195 | 
 196 | 
The Mongolian script is an alphabet, ie. a writing system in which both consonants and vowels are indicated.

 197 | 
 198 | 
Modern Mongolian can be written using a subset of the letters available in the Mongolian Unicode block. The remainder are used for writing Todo, Sibe, and Manchu, or for writing foriegn words, especially in Tibetan and Sanskrit.

 199 | 
 200 | 
Mongolian text runs top to bottom in vertical lines and  (unusually) the lines flow left to right.

 201 | 
 202 | 
The script is cursive, ie. letters in a word are joined. All letters join both on the left and right.

 203 | 
 204 | 
Words are separated by spaces, but also contain narrow spaces that precede suffixes and may produce shaping differences to the surrounding letters. These are part of the word, and the parts on either side should not be separated.

 205 | 
 206 | 
 207 | 
Modern  Mongolian uses 16 basic consonant letters and 11 more for representing foreign sounds.

 208 | In the Traditional Mongolian alphabet  vowels are written using 8 vowel letters, including one for foreign sounds.
 209 | 
Mongolian has separate code points for each sound in Mongolian, but many of these look indistinguishable from each other when rendered. This creates difficulties for novices to reproduce Mongolian text without access to the source.

 210 | 
 211 | 
Vowel reduction is a significant feature of Mongolian. Non-initial short vowels are reduced to vestiges or to zero, and non-initial long vowels in the orthography are reduced to short vowel length.

 212 | 
 213 | 
Vowel harmony is another key feature, grouping vowels in a way that indicates a front or back position for the tongue root (ATR).

 214 | 
 215 | 
The script is monocameral.

 216 | 
 217 | 
There is a set of  Mongolian digits.

 218 | 

 219 | 
 220 | 
 221 | 
 222 | 
 223 | 
 224 | 
 225 | 
 226 | 
 227 | 
 228 | 
 229 | 
 230 | 
 231 | 
 232 | 
 233 | 
 234 | 
 235 | 
 236 | 

 237 | 
Text direction

 238 | 
 239 | 
 240 | 

 241 | 
Writing mode

 242 | 
 243 | 
The Mongolian writing direction is shown in .

 244 | 
 245 | 
 246 | 

 247 | 
 

 248 | 
Mongolian writing direction.

 249 | 

 250 | 

 251 | 

 252 | 
 253 | 
 254 | 
 255 | 
 256 | 
 257 | 
 258 | 

 259 | 
Glyph shaping & positioning

 260 | 
 261 | 
 262 | 

 263 | 
Letterform slopes, weights, & italics

 264 | 
 265 | 

 266 |   Traditionally, Mongolian does not have the concept of italics, and it is not used in modern times either. When it becomes necessary to synthesize an italic typeface, the text should tilt downward in a clockwise direction for vertical text and to the right in a clockwise direction for horizontal text.
 267 | 

 268 | 
 269 | 

 270 | 

 271 | 
 272 | 
 273 | 
 274 | 
 275 | 
 276 | 
 277 | 
 278 | 
 279 | 
 280 | 
 281 | 
 282 | 

 283 | 
Typographic units

 284 | 
 285 | 
 286 | 
 287 | 
 288 | 

 289 | 
Grapheme/word segmentation & selection

 290 | 
 291 | 
 292 | 
 293 | 

 294 | 
Display rules for Mongolian space

 295 | 
 296 | 
Mongolian word suffixes are separated from the preceding word using U+202F NARROW NO-BREAK SPACE, rather than U+0020 SPACE. For example, the code points that make up the suffix  “ ᠤᠨ” are: 0x202F  0x1824 0x1828.

 297 | 
 298 | 
 299 | 

 300 | 

 301 | 
The difference between the common space and Mongolian space.

 302 | 

 303 | 
 304 | 
 305 | 
U+202F NARROW NO-BREAK SPACE and a following suffix cannot appear at the beginning of a line. For example,  shows the correct approach and  shows an incorrect approach.

 306 | 

 307 | 
 308 | 
 309 | 

 310 | 

 311 | 
Correct processing.

 312 | 

 313 | 
 314 | 
 315 | 

 316 | 

 317 | 
Incorrect processing.

 318 | 

 319 | 

 320 | 

 321 | 
 322 | 
 323 | 
 324 | 
 325 | 
 326 | 
 327 | 

 328 | 
Selection rules

 329 | 
 330 | 
Inline selected text must overlap the Mongolian baseline, as shown in . Multi-line selection must follow the writing direction of the Mongolian script, i.e., text direction from top to bottom and from left to right, as shown in .

 331 | 
 332 | 
 333 | 

 334 | 
 

 335 | 
The effect of choosing a single-line text.

 336 | 

 337 | 
 338 | 
 339 | 

 340 | 
 

 341 | 
The effect of choosing multi-line text.

 342 | 

 343 | 

 344 | 
 345 | 
 346 | 
 347 | 
 348 | 
 349 | 
 350 | 
 351 | 

 352 | 
Cursor movement rules

 353 | 
 354 | 
Striking cursor movement keys on the keyboard, including “←”, “→”, “↑”, “↓”, “Page Up”, “Page Down”, “Home” and “End”, should produce movement that follows the writing direction of the Mongolian script from top to bottom and from left to right. For example, the cursor moves to the left after striking the “←” key; the cursor moves to the right when striking the “→” key. The cursor moves down after striking the “↓” key. When the cursor reaches the bottom of the current line, and the key “↓” is pressed again, the cursor will move right and to the top of the next line, as shown in . In the case of the  “↑” key, the opposite  occurs.

 355 | 
 356 | 
 357 | 

 358 | 
 

 359 | 
Illustration of cursor movement.

 360 | 

 361 | 

 362 | 
 363 | 
 364 | 
 365 | 
 366 | 
 367 | 
 368 | 

 369 | 
Mouse pointer rules

 370 | 
 371 | 
The mouse pointer in text editing is shown in . 

 372 | 
 373 | 
 374 | 

 375 | 
 

 376 | 
Illustration of the text cursor in Mongolian text.

 377 | 

 378 | 
 379 | 
 380 | 
The scrollbar will scroll left and right when mouse wheel is scrolling, that is, the scrollbar will move left or the text will move right when mouse wheel is scrolling forward; the scrollbar will move right or the text will move left when mouse wheel is scrolling backward.

 381 | 
 382 | 
The cursor shape during text editing  (shown in ) must be aligned at the base on the midpoint of the Mongolian script baseline, that is, the midpoint of the Mongolian script baseline  overlaps the midpoint of the cursor, with the length no longer than the middle line between the two lines of the text, as shown in .

 383 | 
 384 | 
 385 | 

 386 | 
 

 387 | 
Illustration of cursor movement.

 388 | 

 389 | 

 390 | 

 391 | 

 392 | 
 393 | 
 394 | 
 395 | 
 396 | 
 397 | 
 398 | 
 399 | 
 400 | 
 401 | 
 402 | 
 403 | 
 404 | 
 405 | 

 406 | 
Punctuation & inline features

 407 | 
 408 | 
 409 | 
 410 | 
 411 | 
 412 | 
 413 | 
 414 | 
 415 | 
 416 | 
 417 | 

 418 | 
Phrase & section boundaries

 419 | 
 420 | 
 421 | 
 422 | 
 423 | 

 424 | 
Punctuation rules

 425 | 
 426 | 
Mongolian has some specific requirements related to punctuation:

 427 | 
 428 | 
    
 429 | 
  1. Commas, periods, exclamation marks, question marks, or colons cannot be used at the beginning of a line.
    2. 
 430 | 
 431 | 
  2. Opening brackets cannot be used at the end of a line.
    3. 
 432 | 
 433 | 
  3. Closing brackets cannot be used at the beginning of a line.
    4. 
 434 | 
 435 | 
  4. The colon and  "《" of the opening bracket cannot be used separately, which means they must be used together and they are not allowed to be used at the beginning of a line.
    5. 
 436 | 
 437 | 
  5. Dash consists of two long separators, which cannot be separated, i.e. one cannot be used at the beginning of a line and the other is  at the end. However, it is allowed to appear at the beginning of the line when a paragraph begins.
    6. 
 438 | 
 439 | 
  6. Mongolian names of Mongolian punctuation and writing direction are as shown in , namely the writing direction is the same as that in the graph. Need to clarify the meaning of this bullet.
    
 440 | 
 441 | 
    
 442 | 
    
 443 | 
    Mongolian punctuation sample.
    
 444 | 
    
 445 | 
    7. 
 446 | 
 447 | 
  7. 
 448 | 
    Mongolian punctuation should be centered vertically, as shown in .
    
 449 | 
 450 | 
    
 451 | 
    
 452 | 
    Alignment relationship between punctuation and Mongolian script text.
    
 453 | 
    
 454 | 
    8. 
 455 | 

 456 | 

 457 | 

 458 | 
 459 | 
 460 | 
 461 | 
 462 | 
 463 | 
 464 | 

 465 | 
Text decoration & other inline features

 466 | 
 467 | 
 468 | 
 469 | 

 470 | 
Text decoration

 471 | 
 472 | 
The “right line” in Mongolian writing is to the right of the text, and is used similarly to the underline of horizontal English and Chinese text. The “left line” is to the left of the text, and is used similarly to the overline of horizontal English and Chinese text. The strikethrough is a baseline-centered vertical line as shown in .

 473 | 
 474 | 
 475 | 

 476 | 
 

 477 | 
Illustration of the right line, the left line and the strikethrough.

 478 | 

 479 | 
 480 | 
 481 | 
Underline,  overline and  strikethrough in mixed composition with other languages are shown in :

 482 | 
 483 | 
 484 | 

 485 | 
 

 486 | 
Underline,  overline and  strikethrough as mixed with other languages.

 487 | 

 488 | 
 489 | 
 490 | 
Lines alongside the text may break on the spaces between words. When doing so, the gaps introduced before suffixes by U+202F NARROW NO-BREAK SPACE and U+180E MONGOLIAN VOWEL SEPARATOR should not be skipped. Even though there is a gap, suffixes are considered part of the word. See an example in the second word of :

 491 | 
 492 | 
 493 | 

 494 | 
 

 495 | 
When inter-word spaces are skipped, gaps produced by NNBSP or MVS are not.

 496 | 

 497 | 

 498 | 
 499 | 
 500 | 
 501 | 
 502 | 
 503 | 

 504 | 
Mongolian text width, height and spacing

 505 | 
 506 | 
Due to the different height of Mongolian text, in order to ensure that every character is in  fully displayed and the whole word looks beautiful, the height of each letter must keep in balance. The spaces between words must be different from the common gaps before suffixes, whose code point is U+202F NARROW NO-BREAK SPACE. See :

 507 | 
 508 | 
 509 | 

 510 | 
 

 511 | 
The height, width and spacing of Mongolian words.

 512 | 

 513 | 

 514 | 

 515 | 
 516 | 

 517 |   
Emphasis & highlighting

 518 | 
 519 |   

 520 |     In Mongolian, emphasis is typically expressed by either changing the font or drawing a wavy line. For horizontal text, the wavy line is placed beneath the text, while for vertical text, it appears on the right side. Mongolian does not use italics to indicate emphasis.§
 521 |   

 522 |   
 523 |   

 524 | 

 525 | 
 526 | 
 527 | 
 528 | 
 529 | 
 530 | 
 531 | 
 532 | 
 533 | 
 534 | 
 535 | 
 536 | 
 537 | 
 538 | 
 539 | 

 540 | 
Line & paragraph layout

 541 | 
 542 | 
 543 | 
 544 | 

 545 | 
Line breaking & hyphenation

 546 | 
 547 | 
 548 | 
Line-breaking should not split words.  shows  correct line-breaking, without breaking the Mongolian words.  shows incorrect line-breaking for “” and “”.

 549 | 

 550 | 
 551 | 
 552 | 

 553 | 

 554 | 
Correct newline.

 555 | 

 556 | 
 557 | 
 558 | 

 559 | 

 560 | 
Incorrect newline.

 561 | 

 562 | 

 563 | 

 564 | 
 565 | 
 566 | 
 567 | 
 568 | 
 569 | 
 570 | 
 571 | 

 572 | 
Text alignment & justification

 573 | 
 574 | 

 575 | 
First-line indents

 576 | 
Spacing can be added to the first line of a paragraph for indentation. There is no clear standard for how much indentation to use.

 577 | 
 578 | 

 579 | 

 580 | 
First-line indents.

 581 | 

 582 | 

 583 | 
 584 | 

 585 | 
Text alignment

 586 | 
Text alignment includes "left alignment", "horizontal centering", and "right alignment", as well as "top alignment", "vertical centering", "bottom alignment", and "top-bottom alignment".

 587 | 
 588 | 
"Left alignment", "horizontal centering", and "right alignment" are the alignment rules that apply inside a line. "Top alignment", "vertical centering", "bottom alignment", and "top-bottom alignment" are the alignment rules in a page or a paragraph of multi-line text.

 589 | 
 590 | 
Among "left alignment", "horizontal centering", and "right alignment", "horizontal centering" is the default option, which means that the Mongolian text will align based on its baseline axis. "Left alignment" means that the text will be positioned to the left by a certain distance, which shows obvious differences compared with the text after setting "horizontal center". "Right alignment" means that the text will be positioned to the right by a certain distance, which shows obvious differences compared with the text after setting "horizontal center".

 591 | 
 592 | 
Among "top alignment", "vertical centering", "bottom alignment", and "top-bottom alignment", "top-bottom alignment" is the default option, which means that the words at both the upper and lower boundaries of multi-line text in a paragraph or page are all aligned. This alignment method stretches the spaces in the text proportionally. "Top alignment" means that the words at the upper boundary of multi-line text in a paragraph or page are all aligned without considering the alignment of the lower boundary or stretching the space between words. "Vertical center" means the words at the upper and lower boundaries of multi-line text in a paragraph or page do not need to align and leave equal spacing without stretching the space between words.

 593 | 

 594 | 

 595 | 
 596 | 
 597 | 
 598 | 
 599 | 
 600 | 
 601 | 
 602 | 
 603 | 
 604 | 

 605 | 
Baselines, line height, etc.

 606 | 
 607 | 
 608 | 

 609 | 
Baseline position

 610 | 
 611 | 
Mongolian is aligned to a baseline that runs down the center of the writing, and all text is aligned to this baseline  as shown in :

 612 | 
 613 | 
 614 | 

 615 | 
 

 616 | 
The aligning baseline for Mongolian.

 617 | 

 618 | 

 619 | 
 620 | 
 621 | 
 622 | 
 623 | 
 624 | 
 625 | 

 626 | 
Mixed Arrangement Rules with Other Languages

 627 | 
 628 | 
When mixed with other languages,  the text in those languages should also be centre-aligned along the Mongolian baseline. 

 629 | 

 630 | 
 631 | 
 632 | 
 633 | 
 634 | 
 635 | 

 636 | 
Mixed Arrangement Rules with Numbers and Latin 

 637 | 
 638 | 
There is no obvious midcourt line in numbers and Latin. Therefore generally, half of the text height is regarded as a midcourt line position. When Mongolian script is mixed with numbers and Latin, the line of half of the text height should be aligned with Mongolian midcourt line. When  font size of numbers is the same as Mongolian’s, it will be slightly larger, so some handling methods should be taken to avoid the problem, such as the methods listed in .

 639 | 
 640 | 
 641 | 

 642 | 
 

 643 | 
The mixed arrangement of Mongolian, Latin and numbers.

 644 | 

 645 | 

 646 | 
 647 | 
 648 | 
 649 | 
 650 | 
 651 | 

 652 | 
Mixed Arrangement Rules with Chinese and Japanese

 653 | 
 654 | 
For mixed arrangements with Chinese or Japanese, note the following:

 655 | 
 656 | 
    
 657 | 
  1. Chinese and Japanese cannot be displayed in on their side. They must be displayed upright, as in horizontal Chinese or Japanese.
    2. 
 658 | 
 659 | 
  2. The center line of Chinese or Japanese text (the width in this case) needs to be aligned with the centre baseline of the Mongolian text.
    3. 
 660 | 
 661 | 
  3. Pay attention to the top alignment and bottom alignment of the Mongolian text. In the same line, the mixed display of Mongolian and Chinese needs attention to produce a balanced alignment. When displayed, it should stretch space, but empty distance or space should not be added in Chinese text. Does this mean that no inter-character spacing should be applied to the Chinese?
    4. 
 662 | 
 663 | 
  4.  Mongolian is smaller than Chinese or Japanese in the same font size, so some handling methods should be taken to avoid the problem, such as methods listed in .
    5. 
 664 | 

 665 | 
 666 | 
 667 | 

 668 | 
 

 669 | 
The mixed arrangement of Mongolian and Chinese.

 670 | 

 671 | 

 672 | 

 673 | 
 674 | 
 675 | 
 676 | 
 677 | 
 678 | 
 679 | 
 680 | 

 681 | 
Lists, counters, etc.

 682 | 
 683 | 
 684 | 
The display of these controls needs to pay attention to the direction of the output. That is to say, the  primary display of the number 1, 2, 3, etc. is from left to right. The effect of the following code is as  shown in .  Note how the text is centered on the vertical midline. The separator dots for the numbering are not centre-aligned. We should probably mention that. Also, shouldn't the numbers be rotated counter-clockwise?

 685 | 
 686 | 
 687 | 

 688 | 

 689 | 

 690 | 

 691 | 

 692 | 
Lists.

 693 | 

 694 | 

 695 | 

 696 | 
 697 | 
 698 | 
 699 | 
 700 | 
 701 | 
 702 | 
 703 | 
 704 | 
 705 | 
 706 | 
 707 | 
 708 | 
 709 | 
 710 | 
 711 | 
 712 | 
 713 | 
 714 | 
 715 | 

 716 | 
Page & book layout

 717 | 
 718 | 
 719 | 
 720 | 
 721 | 
 722 | 

 723 | 
General page layout & progression

 724 | 
 725 | 
 726 | 
 727 | 

 728 | 
Bookbinding and the Direction of Page Turning

 729 | 
 730 | 
In general, bookbinding is on the left side, as shown in :

 731 | 
 732 | 
 733 | 

 734 | 
 

 735 | 
Bookbinding.

 736 | 

 737 | 
 738 | 
 739 | 
The direction of page turning is to the left, as shown in :

 740 | 
 741 | 
 742 | 

 743 | 
 

 744 | 
The direction of page turning.

 745 | 

 746 | 

 747 | 
 748 | 
 749 | 
 750 | 
 751 | 
 752 | 

 753 | 
Paper direction

 754 | 
 755 | 
Generally,  landscape is the default Mongolian format, as shown in .

 756 | 
 757 | 
 758 | 

 759 | 
 

 760 | 
 Example of landscape paper direction.

 761 | 

 762 | 

 763 | 
 764 | 
 765 | 
 766 | 
 767 | 

 768 | 
Paper scrolling direction

 769 | 
 770 | 
By default, pages should scroll from left to right, as shown in .

 771 | 
 772 | 
 773 | 

 774 | 
 

 775 | 
The direction of page scrolling.

 776 | 

 777 | 

 778 | 
 779 | 
 780 | 
 781 | 
 782 | 
 783 | 

 784 | 
The scrolling direction of scroll bars

 785 | 
 786 | 
When the amount of text exceeds the prescribed space available, a scroll bar needs to be displayed. The default display position of the scroll bar is along the bottom of the corresponding space. (The simultaneous display of both horizontal and vertical scroll bars has not been installed).

 787 | 
 788 | 
 789 | 

 790 | 
 

 791 | 
Position and scrolling direction of scroll bar.

 792 | 

 793 | 

 794 | 
 795 | 
 796 | 
 797 | 
 798 | 
 799 | 

 800 | 
Columns

 801 | 
 802 | 
Columns in Mongolian text should be divided vertically.

 803 | 
 804 | 
 805 | 

 806 | 
 

 807 | 
The effect of 2 columns.

 808 | 

 809 | 

 810 | 
 811 | 
 812 | 
 813 | 
 814 | 
 815 | 

 816 | 
Mixed arrangement of text and illustrations  (or other non-text objects)

 817 | 
 818 | 
The illustrations here include ordinary picture formats, textboxes, charts, media objects and so on, all of which are called illustrations in what follows. There are many ways (as shown in ) of mixing the arrangements of text and illustrations but, no matter which way is used, some principles need to be obeyed.

 819 | 
 820 | 
    
 821 | 
  1. The illustration cannot be rotated, that is, the original illustration is inserted just as it is. The illustration cannot be rotated into the vertical one just because of vertical text.
    2. 
 822 | 
 823 | 
  2. The Mongolian script around the inserted illustrations cannot be broken inside the word. The rules of the beginning and end of lines are the same as the original ones.
    3. 
 824 | 

 825 | 
 826 | 
 827 | 

 828 | 
 

 829 | 
Mixed arrangement of text and illustrations (or other non-text objects).

 830 | 

 831 | 

 832 | 

 833 | 
 834 | 
 835 | 
 836 | 
 837 | 
 838 | 
 839 | 
 840 | 

 841 | 
Grids & tables

 842 | 
 843 | 
When setting writing-mode:tb-lr using CSS (grammar will have a little difference according to various browsers), the table will support vertical display feature of Mongolian script. When setting default options for the text in a table, it will display horizontally centered, that is, the upper and the lower center lines of the table cell will align at the center line of the baseline of the Mongolian text, as shown in .

 844 | 
 845 | 
 846 | 

 847 | 
 

 848 | 
The aligning baseline for Mongolian.

 849 | 

 850 | 

 851 | 
 852 | 
 853 | 
 854 | 
 855 | 
 856 | 
 857 | 
 858 | 

 859 | 
Page headers, footers, etc

 860 | 
 861 | 

 862 | 
Page numbering

 863 | 
 864 | 
In the Mongolian format, page numbers should be displayed on the upper or lower side of the page.

 865 | 
 866 | 

 867 | 
 

 868 | 
Adding the horizontal type and number on the page number .

 869 | 

 870 | 

 871 | 

 872 | 
 873 | 
 874 | 
 875 | 
 876 | 
 877 | 
 878 | 
 879 | 

 880 | 
Forms & user interaction

 881 | 
 882 | 
All input controls need to be adjusted to match the characteristics of the vertically typeset Mongolian text. For example, controls like text fields and buttons need to support vertical input and display of text, and furthermore the cursors in text and passwords need to conform to the cursor style as shown in .

 883 | 
 884 | 
 885 | 

 886 | 
 

 887 | 
The display of input controls and the alignment of Mongolian script.

 888 | 

 889 | 
 890 | 
 891 | 
 892 | 
 893 | 
 894 | 

 895 | 
Select

 896 | 
 897 | 
The select box appearing in the following HTML code should be displayed as shown in . According to the default setting, the scroll bar is at the bottom and starts at the left. To see the contents at the end of the list, it scrolls from left to right. The scrolling of the mouse wheel should be in accordance with  illustration in . While selecting a column, the selected text and the selected background color should conform to the principle of aligning to the Mongolian vertically-centered baseline (see the descriptions in ).

 898 | 
 899 | 
 900 | 

 901 | 

 902 | 

 903 | 
Correct newline.

 904 | 

 905 | 

 906 | 

 907 | 
Mongolian standard  select box.

 908 | 

 909 | 

 910 | 

 911 | 
 912 | 
 913 | 
 914 | 
 915 | 
 916 | 
 917 | 

 918 | 
Textarea

 919 | 
 920 | 
Textarea is an important control, and is required in the text input, edit, and display. Scrollbar movement accords with requirements of the select control in . The display and moving direction of the cursor should be consistent with the standard for cursor movement in . In some browsers, there are functions for stretching the size of the textarea. The stretching icon should be in the lower right corner, and the  textarea scaling accords with the mouse dragging. The rows and cols attribute of textarea are the opposite of those in horizontal text. Its specific attributes are as the following: rows {int} : showing the column number and cols {int} : showing the row number.

 921 | 
 922 | 
 923 | 

 924 | 

 925 | 
Display status of the standard textarea.

 926 | 

 927 | 

 928 | 
 929 | 
 930 | 
 931 | 
 932 | 
 933 | 

 934 | 
Label

 935 | 
 936 | 
The label control mainly considers text midcourt line aligning principles. ( See the descriptions in ). The label display for the following code is shown in .

 937 | 
 938 | 
 939 | 

 940 | 

 941 | 

 942 | 

 943 | 

 944 | 
The display of label controls.

 945 | 

 946 | 

 947 | 
 948 | 
 949 | 
 950 | 
 951 | 
 952 | 

 953 | 
Fieldset

 954 | 
 955 | 
As shown in , which is an example fieldset generation with the following code, the components are aligned along the centred-vertical Mongolian baseline.

 956 | 
 957 | 
 958 | 

 959 | 

 960 | 

 961 | 

 962 | 

 963 | 
Fieldset effect.

 964 | 

 965 | 

 966 | 

 967 | 

 968 | 
 969 | 
 970 | 
 971 | 
 972 | 
 973 | 
 974 | 
 975 | 
 976 | 
 977 | 
 978 | 
 979 | 
 980 | 
 981 | 
 982 | 
 983 | 
 984 | 
 985 | 
 986 | 
 987 | 
 988 | 
 989 | 
 990 | 
 991 | 
 992 | 
 993 | 
1022 | 
1023 | 
1024 | 

1025 |   
Suggestions about Formulating New CSS Standard

1026 | 
1027 | 
    
1028 | 
  1. When Mongolian webpage is created, the page direction should be designated: CSS-MONGOLIAN-LAYOUT:Y. Designating the option means that all page elements should be arranged in accordance with the requirement of vertical column script. Meanwhile, there are the main requirements: script should conform to the habit of Mongolian writing -----arrangement from top to bottom and from left to right (see the descriptions in 2.2.3); textboxes, buttons and list order are all displayed in vertical column; pictures, videos and the other third party controls do not need to accord with the requirement of vertical column.
    2. 
1029 | 
  2. In mixed arrangement with other languages, Mongolian text is X larger than the other texts. Designating the option requires that the size of Mongolian in all control texts should be automatically X larger than the size of the text of other scripts or X smaller under the condition of using minus.
    3. 
1030 | 
  3. When arranged with other languages, Mongolian should follow the midcourt line aligning principles as the following. when the option CSS-MONGOLIAN-MOVE- WAIST:X px is designated, Mongolian text in all control texts should move X px to left or right so that it can be aligned with the midcourt line of other texts. Because the midcourt line cannot be aligned well under the condition, the option needs to be set.
    4. 
1031 | 
  4. When arranged with other languages, Mongolian font should be set as  CSS-MONGOLIAN-FONT:MongolianFontName. When the option is designated, Mongolian font in all control texts should be changed into MongolianFontName, while other languages’ font should accord with default font in the system. Because the change of Mongolian font will affect Chinese font when it is arranged with Chinese or other languages and sometimes, Chinese will be displayed in the way of lying down.
    5. 
1032 | 
  5. Whether Mongolian space (0x202F) is stretched: CSS-MONGOLIAN-SPACE:Stretch|Normal, when the Stretch option is designated, the length of Mogolian space should be stretched as that of normal space. While the option Normal is designated, Mongolian space should not be stretched, and should be displayed in the length of the font library.
    6. 
1033 | 
  6. Whether the Mongolian vowel space mark MVS (0x180E): is displayed: CSS-MONGOLIAN-MVS:Display|Normal, when the option Display is designated, there will be a small hollow rectangular on the screen with the size in the font library, but the rectangular will not be shown when it is printed. When the option Normal is designated, there will be no picture on the screen, but it will occupy a space of the size in the font library.
    7. 
1034 | 

1035 | 

1036 | 
1037 | 
1038 | 
1039 | 

1040 |   
Relative Standards of Currently Used Scripts in the Traditional Mongolian Script

1041 |   
Currently, there are some main characters in applied traditional Mongolian script, including basic Mongolian characters, symbols and Mongolian numbers.

1042 | 

1043 | 
1044 | 
1045 | 
1046 | 
1047 | 
1048 | 
1049 | 
1050 | 
1051 | 
1052 | 
1053 | 
1054 | 

1055 | 
Change log

1056 | 
1057 | 
1060 | 

1061 | 
1062 | 
1063 | 


--------------------------------------------------------------------------------