c7af2db2ec
Initially I just implemented the unit tests, but quickly found that they were failing my expectation of having a size of 256 items. Some of them did contain 256 items and some did not. I looked up various resources and figured that they indeed all need to have 256 items. One of the good resources is https://github.com/davidben/poppler/blob/master/poppler/FontEncodingTables.cc Aside from some missing `notdef` (empty string) entries at the end of the arrays, which I assume causes issues since it may cause out-of-bounds array access which in JavaScript gives `undefined`, there was a `notdef` entry missing in the `MacExpertEncoding`, causing the entries after that to be shifted. This fix for this is similar to the one in #8589. The unit tests verify that, for known encoding names, the return value is not only an array, but that it is also of the right length and contains only strings.
33 lines
713 B
JSON
33 lines
713 B
JSON
{
|
|
"spec_dir": "build/lib/test/unit",
|
|
"spec_files": [
|
|
"annotation_spec.js",
|
|
"api_spec.js",
|
|
"bidi_spec.js",
|
|
"cff_parser_spec.js",
|
|
"cmap_spec.js",
|
|
"colorspace_spec.js",
|
|
"crypto_spec.js",
|
|
"display_svg_spec.js",
|
|
"document_spec.js",
|
|
"dom_utils_spec.js",
|
|
"encodings_spec.js",
|
|
"evaluator_spec.js",
|
|
"fonts_spec.js",
|
|
"function_spec.js",
|
|
"metadata_spec.js",
|
|
"murmurhash3_spec.js",
|
|
"network_utils_spec.js",
|
|
"node_stream_spec.js",
|
|
"parser_spec.js",
|
|
"pdf_history.js",
|
|
"primitives_spec.js",
|
|
"stream_spec.js",
|
|
"type1_parser_spec.js",
|
|
"ui_utils_spec.js",
|
|
"unicode_spec.js",
|
|
"util_spec.js",
|
|
"util_stream_spec.js"
|
|
]
|
|
}
|