Standard Options: -Dfile.encoding=UTF-8 -Xmx512M -DSHOW_FILES plus your choice of source/target directories.

Options for each pass:

1. First change draft="true" to draft="unconfirmed" with Search&Replace // run on ALL of common *.xml
   
2. <none> - do it with nothing but standard options first.
   1. This will regularize the structure, so that's not mixed in with later changes
   2. If any WARNING occurs, fix it manually (this is when two items have the same path when reading in the file).
      
3. -fp : do the input processing (normally done by Survey Tool, but this catches manual insertions)
   
4. -ff : fix NFC
5. -f_ : remove superfluous compound language translations (like "Portuguese (Brazilian)")
   
6. -fn - fix the number formats to be uniform
   1. Sanity-check this one over carefully, since sometimes a vetter will put in a localized decimal point or thousands separator instead of the neutral, pattern one!
7. -fw : change problematic alt="proposed" cases.
8. -fi : fix identical children (this copies up items that are the same in all child locales)
   JCE: The -fi option has some significant problems and needs to be reworked.  Recommend not to use it in most BRS situations.
   
9. Optional - review the following and see if any apply. Most require code changes to work!!
   
1. -fx: This lets you remove paths that match a pattern. Only use this if you are making a structural change
2. -fv: only do this if ConsoleCheckCLDR fails with lots of attribute errors. And if you do, you'll have to look at the code and maybe make some fixes, since it is old. Diff the results carefully!
3. -fy: remove deprecated. Only use this pass if the structure needs to be changed. You'll need to modify the code to make the changes that you want.
4. There were also one-time fixes, that you only have to apply in special cases.
   

1. -r minimalize data
   JCE: Be SURE to diff these carefully.  You may choose to keep certain data, especially in places where the stuff being minimized is part of a larger group ( such as date/time formats, available formats, or month names.
   
2. -fw : Run again to make sure that no unconfirmed valued got orphaned during minimilization.
   

Sanity Check

1. The console will list changes made, such as:
• Creating File: {cldrdata}/dropbox\gen\main\zh_Hant.xml
  *Renaming old {cldrdata}/dropbox\gen\main\zh_Hant.xml
  %zh_Hant_HK    -    Replacing: <yy'年'M'月'd'日'>    by <yy年M月d日>     at: //ldml/dates/calendars/calendar[@type="gregorian"]/dateFormats/dateFormatLength[@type="short"]/dateFormat[@type="standard"]/pattern[@type="standard"]
2. The diff folder in the output has CompareIt! bat files for each change, or you can use CVS diff after moving to the CVS folder by doing the Copy and then checking.

Copy Files

• Copy from the target directory (eg {cldrdata}/dropbox\gen\main) to the cvs directory (eg {cldrdata}/common\main)
  • skip the file log.txt, and the files _unchanged_.....xml
• Run CLDRModify again, with nothing but standard options. This will verify that there are no xml errors.
  • There should be no change in the output; thus you should not see anything but _unchanged_.....xml files in the target directory.

Now ready to check in

• Refresh (F5), then click "Show committable only" icon (red)
• Diff the changed files (red) as a sanity check.
• Select main; Modify>Create tag> (eg pre-NFC1-4)
• Check in
• Select main; Modify>Create tag> (eg post-NFC1-4)

If someone checks in a change in the middle of one of your passes, it is generally easier to check in the rest of the changes, check out a clean copy of that file, and return the pass with only that file. The -m(uk) option can be used to restrict the pass to only uk.xml, for example.

CLDRModify Configuration File

The CLDRModify tool can be used to make changes to a number of files, based on a configuration tool. 

1. Use the -fk option
2. Either put your changes into cldr/tool/modify_config.txt, or use -k config_file to specify a different file. The path is relative to cldr/tool/
3. Run CLDRModify, and as usual, diff your changes.