CLDR-17566 converting development directory

docs/site/development/cldr-development-site.md

@@ -0,0 +1,30 @@
+---
+title: CLDR Development Site
+---
+
+# CLDR Development Site
+
+Some of the key pages for developers are:
+
+1. [New CLDR Developers](https://cldr.unicode.org/development/new-cldr-developers)
+    1. [Maven Setup](https://cldr.unicode.org/development/maven) (for command line & Eclipse)
+        1. Obsolete (but may still contain useful nuggets): [Eclipse Setup](https://cldr.unicode.org/development/eclipse-setup)      
+    2. [Eclipse](https://cldr.unicode.org/development/running-survey-tool/building-and-running-the-survey-tool-on-eclipse) (survey tool)       
+2. [Handling Tickets (bugs/enhancements)](https://cldr.unicode.org/development/development-process)
+3. [Updating DTDs](https://cldr.unicode.org/development/updating-dtds)
+4. [Editing CLDR Spec](https://cldr.unicode.org/development/editing-cldr-spec)
+    1. [CLDR: Big Red Switch](https://cldr.unicode.org/development/cldr-big-red-switch) (checklist for release)
+5. [Adding a new locale to CLDR](https://cldr.unicode.org/development/adding-locales)
+
+
+The subpages listed give more information on internal CLDR development. See also: [Sitemap](https://sites.google.com/site/cldr/system/app/pages/sitemap/hierarchy).
+
+Note: when editing Sites pages it is often useful to clean up HTML in material pasted in from other sources, such as Word or Google Docs. Some useful regexes for that:
+
+\<(font|span|div)\[^>\]+>         <$1>
+
+style="\[^"\]\*"
+
+Also see the [Google Docs to Markdown extension, by edbacher](https://workspace.google.com/marketplace/app/docs_to_markdown/700168918607)
+
+![Unicode copyright](https://www.unicode.org/img/hb_notice.gif)

docs/site/development/development-process/design-proposals.md

@@ -0,0 +1,117 @@
+---
+title: Design Proposals
+---
+
+# Design Proposals
+
+This section contains design proposals, listed as subpages below.
+
+In each proposal, please add a header and a TOC if it is longer than a page. You can cut&paste the structure in [Proposed Collation Additions](https://cldr.unicode.org/development/development-process/design-proposals/proposed-collation-additions) and make the necessary changes.
+
+[Alternate Time Formats](https://cldr.unicode.org/development/development-process/design-proposals/alternate-time-formats)
+
+[BCP 47 Changes (DRAFT)](https://cldr.unicode.org/development/development-process/design-proposals/bcp-47-changes-draft)
+
+[BCP47 Syntax Mapping](https://cldr.unicode.org/development/development-process/design-proposals/bcp47-syntax-mapping)
+
+[BCP47 Validation and Canonicalization](https://cldr.unicode.org/development/development-process/design-proposals/bcp47-validation-and-canonicalization)
+
+[BIDI handling of Structured Text](https://cldr.unicode.org/development/development-process/design-proposals/bidi-handling-of-structured-text)
+
+[Change to Sites?](https://cldr.unicode.org/development/development-process/design-proposals/change-to-sites)
+
+[Chinese (and other) calendar support, intercalary months, year cycles](https://cldr.unicode.org/development/development-process/design-proposals/chinese-and-other-calendar-support-intercalary-months-year-cycles)
+
+[Consistent Casing](https://cldr.unicode.org/development/development-process/design-proposals/consistent-casing)
+
+[Coverage Revision](https://cldr.unicode.org/development/development-process/design-proposals/coverage-revision)
+
+[Currency Code Fallback](https://cldr.unicode.org/development/development-process/design-proposals/currency-code-fallback)
+
+[Day-Period Design](https://cldr.unicode.org/development/development-process/design-proposals/day-period-design)
+
+[Delimiter (Quotation Mark) Proposal](https://cldr.unicode.org/development/development-process/design-proposals/delimiter-quotation-mark-proposal)
+
+[English Inheritance](https://cldr.unicode.org/development/development-process/design-proposals/english-inheritance)
+
+[European Ordering Rules Issues](https://cldr.unicode.org/development/development-process/design-proposals/european-ordering-rules-issues)
+
+[Extended Windows-Olson zid mapping](https://cldr.unicode.org/development/development-process/design-proposals/extended-windows-olson-zid-mapping)
+
+[Fractional Plurals](https://cldr.unicode.org/development/development-process/design-proposals/fractional-plurals)
+
+[Generic calendar data](https://cldr.unicode.org/development/development-process/design-proposals/generic-calendar-data)
+
+[Grammar & capitalization forms for date/time elements and others](https://cldr.unicode.org/development/development-process/design-proposals/grammar-capitalization-forms-for-datetime-elements-and-others)
+
+[Grapheme Usage](https://cldr.unicode.org/development/development-process/design-proposals/grapheme-usage)
+
+[Hebrew Months](https://cldr.unicode.org/development/development-process/design-proposals/hebrew-months)
+
+[Index Characters](https://cldr.unicode.org/development/development-process/design-proposals/index-characters)
+
+[Islamic Calendar Types](https://cldr.unicode.org/development/development-process/design-proposals/islamic-calendar-types)
+
+[ISO 636 Deprecation Requests - DRAFT](https://cldr.unicode.org/development/development-process/design-proposals/iso-636-deprecation-requests-draft)
+
+[JSON Packaging (Approved by the CLDR TC on 2015-03-25)](https://cldr.unicode.org/development/development-process/design-proposals/json-packaging-approved-by-the-cldr-tc-on-2015-03-25)
+
+[Language Data Consistency](https://cldr.unicode.org/development/development-process/design-proposals/language-data-consistency)
+
+[Language Distance Data](https://cldr.unicode.org/development/development-process/design-proposals/language-distance-data)
+
+[List Formatting](https://cldr.unicode.org/development/development-process/design-proposals/list-formatting)
+
+[Locale Format](https://cldr.unicode.org/development/development-process/design-proposals/locale-format)
+
+[Localized GMT Format](https://cldr.unicode.org/development/development-process/design-proposals/localized-gmt-format)
+
+[Math Formula Preferences](https://cldr.unicode.org/development/development-process/design-proposals/math-formula-preferences)
+
+[New BCP47 Extension T Fields](https://cldr.unicode.org/development/development-process/design-proposals/new-bcp47-extension-t-fields)
+
+[New Time Zone Patterns](https://cldr.unicode.org/development/development-process/design-proposals/new-time-zone-patterns)
+
+[Path Filtering](https://cldr.unicode.org/development/development-process/design-proposals/path-filtering)
+
+[Pattern character for “related year”](https://cldr.unicode.org/development/development-process/design-proposals/pattern-character-for-related-year)
+
+[Pinyin Fixes](https://cldr.unicode.org/development/development-process/design-proposals/pinyin-fixes)
+
+[Post Mortem](https://cldr.unicode.org/development/development-process/design-proposals/post-mortem)
+
+[Proposed Collation Additions](https://cldr.unicode.org/development/development-process/design-proposals/proposed-collation-additions)
+
+[Resolution of CLDR files](https://cldr.unicode.org/development/development-process/design-proposals/resolution-of-cldr-files)
+
+[script-metadata](https://cldr.unicode.org/development/development-process/design-proposals/script-metadata)
+
+[Search collators](https://cldr.unicode.org/development/development-process/design-proposals/search-collators)
+
+[Secular/neutral eras](https://cldr.unicode.org/development/development-process/design-proposals/secularneutral-eras)
+
+[Specifying text break variants in locale IDs](https://cldr.unicode.org/development/development-process/design-proposals/specifying-text-break-variants-in-locale-ids)
+
+[Suggested Exemplar Revisions](https://cldr.unicode.org/development/development-process/design-proposals/suggested-exemplar-revisions)
+
+[Supported NumberingSystems](https://cldr.unicode.org/development/development-process/design-proposals/supported-numberingsystems)
+
+[Thoughts on Survey Tool Backend](https://cldr.unicode.org/development/development-process/design-proposals/thoughts-on-survey-tool-backend)
+
+[Time Zone Data Reorganization](https://cldr.unicode.org/development/development-process/design-proposals/time-zone-data-reorganization)
+
+[Transform Fallback](https://cldr.unicode.org/development/development-process/design-proposals/transform-fallback)
+
+[Transform keywords](https://cldr.unicode.org/development/development-process/design-proposals/transform-keywords)
+
+[Unihan Data](https://cldr.unicode.org/development/development-process/design-proposals/unihan-data)
+
+[Units: pixels, ems, display resolution](https://cldr.unicode.org/development/development-process/design-proposals/units-pixels-ems-display-resolution)
+
+[UTS #35 Splitting](https://cldr.unicode.org/development/development-process/design-proposals/uts-35-splitting)
+
+[Voting](https://cldr.unicode.org/development/development-process/design-proposals/voting)
+
+[XMB](https://cldr.unicode.org/development/development-process/design-proposals/xmb)
+
+![Unicode copyright](https://www.unicode.org/img/hb_notice.gif)

docs/site/development/guidance-on-direct-modifications-to-cldr-data.md

@@ -0,0 +1,53 @@
+---
+title: Direct Modifications to CLDR Data
+---
+
+# Direct Modifications to CLDR Data
+
+*See also: Bulk Import of XML Data.*
+
+### 1\. Verifying changes
+
+Please check that your changes don't cause problems. A minimal test is to run ConsoleCheckCLDR with the following parameter:
+
+\-f(en)
+
+This will run the checks on en: you can substitute other locales to check them also (It is a regular expression, so -f(en.\*|fr.\*) will do all English and French locales).
+
+I recommend also using the following options, to show opened files, and increase memory (some tests require that).
+
+\-Dfile.encoding=UTF-8 -DSHOW\_FILES -Xmx512M
+
+An example of where a DTD broke, the invalid XML:
+
+\<!ELEMENT commonlyUsed (true | false ) #IMPLIED \>.
+
+I changed to \<!ELEMENT commonlyUsed EMPTY \> to get it to function; other changes might be necessary.
+
+### 2\. Explicit defaults
+
+Don't use them, since they cause the XML to be fluffed up, and may interfere with the inheritance unless you make other modifications.
+
+\<!ATTLIST fields casing ( titlecase-words | titlecase-firstword |
+
+lowercase-words | mixed ) "mixed" \>
+
+\=>
+
+\<!ATTLIST fields casing ( titlecase-words | titlecase-firstword |
+
+lowercase-words | mixed ) #IMPLIED \>
+
+Instead, the default should be documented in the spec
+
+### 3\. Mixing meanings.
+
+Attribute and element names should be unique, unless they have the same meaning across containing elements, and same substructure. This is a hard-and-fast rule for elements. For attributes, it is better to have unique names (as we've found by bitter experience) where possible. It is \*required\* when the attribute is distinguishing for one element and not for another.
+
+So the following is ok, but would be better if one of the attribute values were changed.
+
+\<!ATTLIST standard casing (verbatim) #IMPLIED \>
+
+\<!ATTLIST fields casing ( titlecase-words | titlecase-firstword | lowercase-words | mixed ) #IMPLIED \>
+
+![Unicode copyright](https://www.unicode.org/img/hb_notice.gif)

docs/site/development/updating-codes.md

@@ -0,0 +1,34 @@
+---
+title: Updating Codes
+---
+
+# Updating Codes
+
+*Note: This is more complicated than it should be: we need to simplify the process. We just haven't gotten there yet with everything else going on!*
+
+### Steps
+
+First read [Running Tools](https://cldr.unicode.org/development/running-tools)
+
+1. Update [Script Metadata](https://cldr.unicode.org/development/updating-codes/updating-script-metadata)    
+2. [Update Population/GDP/Literacy](https://cldr.unicode.org/development/updating-codes/updating-population-gdp-literacy)    
+3. [Update Language/Script/Region Subtags](https://cldr.unicode.org/development/updating-codes/update-languagescriptregion-subtags)    
+4. [Update Subdivision Codes](https://cldr.unicode.org/development/updating-codes/updating-subdivision-codes)    
+5. [Update Subdivision translations](https://cldr.unicode.org/development/updating-codes/updating-subdivision-translations) (new)    
+6. [Update Currency Codes](https://cldr.unicode.org/development/updating-codes/update-currency-codes)    
+7. [Update Time Zone Data for ZoneParser](https://cldr.unicode.org/development/updating-codes/update-time-zone-data-for-zoneparser)    
+8. [Update Validity XML](https://cldr.unicode.org/development/updating-codes/update-validity-xml)    
+    1. [Update Language/Script/Country Information](https://cldr.unicode.org/development/updating-codes/update-language-script-info)        
+    2. [LikelySubtags and Default Content](https://cldr.unicode.org/development/updating-codes/likelysubtags-and-default-content)        
+    3. Update IANA/FIPS Mappings        
+        1. TBD - Describe what to do. The URLs are            
+        2. http://www.iana.org/domain-names.htm            
+        3. http://www.iana.org/root-whois/index.html            
+        4. http://data.iana.org/TLD/tlds-alpha-by-domain.txt            
+9. Reformat plurals/ordinals.xml with GeneratedPluralRules.java. Review carefully before checking in.    
+    1. Regenerate Supplemental Charts: [Generating Charts](https://cldr.unicode.org/development/cldr-big-red-switch/generating-charts)
+
+
+For information about **Version Info** and external metadata, see [Updating External Metadata](https://cldr.unicode.org/development/updating-codes/external-version-metadata)
+
+![Unicode copyright](https://www.unicode.org/img/hb_notice.gif)