4e30468e9b
ICU72 release note https://icu.unicode.org/download/72 CLDR42 release note https://cldr.unicode.org/index/downloads/cldr-42 Unicode15 release note https://blog.unicode.org/2022/09/announcing-unicode-standard-version-150.html Changing test expectation: 1. Use THIN SPACE (U+202F) for the space before "AM/PM" in date formatting. 2. Bidi control code around some dash in date format output. Change the space around – \u2013 U+2013 "En Dash" from ASCII SPACE to \u2009 "Thin Space" 3. @ is now consider part of a word. ICU 72 migration diary https://docs.google.com/document/d/1bzme4zR_swaqMoJIYLL9wwk-rsjdAdjGrU073h0TJbo Ref about 2009 https://www.compart.com/en/unicode/U+2009 Ref about 202f https://www.compart.com/en/unicode/U+202f Size Impact due to increase of more unicode characters and localized patterns: - Fuchsia web_engine +16384 bytes compressed - Fuchsia chrome_fuchsia +24576 bytes compressed - Android Normalized APK Size: +107854 bytes Bug: 1371208 Binary-Size: Size increase is unavoidable (see above). Fuchsia-Binary-Size: Size increase is unavoidable. Change-Id: Ic8dccaceecbf348e74880286d903320ab6983541 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3995549 Reviewed-by: Orin Jaworski <orinj@chromium.org> Reviewed-by: Daniel Libby <dlibby@microsoft.com> Reviewed-by: Luca Hunkeler <hluca@google.com> Reviewed-by: Kent Tamura <tkent@chromium.org> Reviewed-by: Peter Marshall <petermarshall@chromium.org> Commit-Queue: Frank Tang <ftang@chromium.org> Reviewed-by: Pavol Marko <pmarko@chromium.org> Reviewed-by: Jungshik Shin <jshin@chromium.org> Reviewed-by: Thanh Nguyen <thanhdng@chromium.org> Reviewed-by: Richard Chui <richui@chromium.org> Reviewed-by: Toni Barzic <tbarzic@chromium.org> Reviewed-by: Lei Zhang <thestig@chromium.org> Auto-Submit: Frank Tang <ftang@chromium.org> Reviewed-by: Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/main@{#1073687}
//pdf contains the PDF plugin, its Blink-based replacement, as well as PDF
utility functions that leverage PDFium. It can use low-level components that
live below the content layer, as well as other foundational code like
//printing. It should not use //content or anything in //components that
lives above the content layer. Code that lives above the content layer should
live in //components/pdf, or in the embedder. All the code here should run in
sandboxed child processes.
TODO(crbug.com/1220865): Remove existing //content dependencies.