2017-01-10 01:40:57 +09:00
|
|
|
/* Copyright 2017 Mozilla Foundation
|
|
|
|
*
|
|
|
|
* Licensed under the Apache License, Version 2.0 (the "License");
|
|
|
|
* you may not use this file except in compliance with the License.
|
|
|
|
* You may obtain a copy of the License at
|
|
|
|
*
|
|
|
|
* http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
*
|
|
|
|
* Unless required by applicable law or agreed to in writing, software
|
|
|
|
* distributed under the License is distributed on an "AS IS" BASIS,
|
|
|
|
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
|
|
* See the License for the specific language governing permissions and
|
|
|
|
* limitations under the License.
|
|
|
|
*/
|
|
|
|
|
2017-04-17 05:30:27 +09:00
|
|
|
import {
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
CFFCharset,
|
|
|
|
CFFCompiler,
|
|
|
|
CFFFDSelect,
|
|
|
|
CFFParser,
|
|
|
|
CFFStrings,
|
2020-01-02 20:00:16 +09:00
|
|
|
} from "../../src/core/cff_parser.js";
|
2021-05-02 23:11:01 +09:00
|
|
|
import { SEAC_ANALYSIS_ENABLED } from "../../src/core/fonts_utils.js";
|
2020-01-02 20:00:16 +09:00
|
|
|
import { Stream } from "../../src/core/stream.js";
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
describe("CFFParser", function () {
|
2016-05-03 16:22:22 +09:00
|
|
|
function createWithNullProto(obj) {
|
2020-10-25 23:40:51 +09:00
|
|
|
const result = Object.create(null);
|
|
|
|
for (const i in obj) {
|
2016-05-03 16:22:22 +09:00
|
|
|
result[i] = obj[i];
|
|
|
|
}
|
|
|
|
return result;
|
|
|
|
}
|
|
|
|
|
2017-07-08 05:12:52 +09:00
|
|
|
// Stub that returns `0` for any privateDict key.
|
2020-10-25 23:40:51 +09:00
|
|
|
const privateDictStub = {
|
2017-07-08 05:12:52 +09:00
|
|
|
getByName(name) {
|
|
|
|
return 0;
|
|
|
|
},
|
|
|
|
};
|
|
|
|
|
2020-10-25 23:40:51 +09:00
|
|
|
let fontData, parser, cff;
|
2016-05-03 16:22:22 +09:00
|
|
|
|
2021-04-11 03:21:31 +09:00
|
|
|
beforeAll(function () {
|
2016-05-03 16:22:22 +09:00
|
|
|
// This example font comes from the CFF spec:
|
|
|
|
// http://www.adobe.com/content/dam/Adobe/en/devnet/font/pdfs/5176.CFF.pdf
|
2020-10-25 23:40:51 +09:00
|
|
|
const exampleFont =
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
"0100040100010101134142434445462b" +
|
|
|
|
"54696d65732d526f6d616e000101011f" +
|
|
|
|
"f81b00f81c02f81d03f819041c6f000d" +
|
|
|
|
"fb3cfb6efa7cfa1605e911b8f1120003" +
|
|
|
|
"01010813183030312e30303754696d65" +
|
|
|
|
"7320526f6d616e54696d657300000002" +
|
|
|
|
"010102030e0e7d99f92a99fb7695f773" +
|
|
|
|
"8b06f79a93fc7c8c077d99f85695f75e" +
|
|
|
|
"9908fb6e8cf87393f7108b09a70adf0b" +
|
|
|
|
"f78e14";
|
2020-10-25 23:40:51 +09:00
|
|
|
const fontArr = [];
|
|
|
|
for (let i = 0, ii = exampleFont.length; i < ii; i += 2) {
|
|
|
|
const hex = exampleFont.substring(i, i + 2);
|
2016-05-03 16:22:22 +09:00
|
|
|
fontArr.push(parseInt(hex, 16));
|
|
|
|
}
|
|
|
|
fontData = new Stream(fontArr);
|
2016-10-08 03:51:02 +09:00
|
|
|
});
|
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
afterAll(function () {
|
2016-10-08 03:51:02 +09:00
|
|
|
fontData = null;
|
|
|
|
});
|
2016-05-03 16:22:22 +09:00
|
|
|
|
2021-04-11 03:21:31 +09:00
|
|
|
beforeEach(function () {
|
2016-05-03 16:22:22 +09:00
|
|
|
parser = new CFFParser(fontData, {}, SEAC_ANALYSIS_ENABLED);
|
|
|
|
cff = parser.parse();
|
|
|
|
});
|
|
|
|
|
2021-04-11 03:21:31 +09:00
|
|
|
afterEach(function () {
|
2016-10-08 03:51:02 +09:00
|
|
|
parser = cff = null;
|
2016-05-03 16:22:22 +09:00
|
|
|
});
|
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
it("parses header", function () {
|
2020-10-25 23:40:51 +09:00
|
|
|
const header = cff.header;
|
2016-05-03 16:22:22 +09:00
|
|
|
expect(header.major).toEqual(1);
|
|
|
|
expect(header.minor).toEqual(0);
|
|
|
|
expect(header.hdrSize).toEqual(4);
|
|
|
|
expect(header.offSize).toEqual(1);
|
|
|
|
});
|
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
it("parses name index", function () {
|
2020-10-25 23:40:51 +09:00
|
|
|
const names = cff.names;
|
2016-05-03 16:22:22 +09:00
|
|
|
expect(names.length).toEqual(1);
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
expect(names[0]).toEqual("ABCDEF+Times-Roman");
|
2016-05-03 16:22:22 +09:00
|
|
|
});
|
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
it("parses string index", function () {
|
2020-10-25 23:40:51 +09:00
|
|
|
const strings = cff.strings;
|
2016-05-03 16:22:22 +09:00
|
|
|
expect(strings.count).toEqual(3);
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
expect(strings.get(0)).toEqual(".notdef");
|
|
|
|
expect(strings.get(391)).toEqual("001.007");
|
2016-05-03 16:22:22 +09:00
|
|
|
});
|
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
it("parses top dict", function () {
|
2020-10-25 23:40:51 +09:00
|
|
|
const topDict = cff.topDict;
|
2016-05-03 16:22:22 +09:00
|
|
|
// 391 version 392 FullName 393 FamilyName 389 Weight 28416 UniqueID
|
|
|
|
// -168 -218 1000 898 FontBBox 94 CharStrings 45 102 Private
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
expect(topDict.getByName("version")).toEqual(391);
|
|
|
|
expect(topDict.getByName("FullName")).toEqual(392);
|
|
|
|
expect(topDict.getByName("FamilyName")).toEqual(393);
|
|
|
|
expect(topDict.getByName("Weight")).toEqual(389);
|
|
|
|
expect(topDict.getByName("UniqueID")).toEqual(28416);
|
|
|
|
expect(topDict.getByName("FontBBox")).toEqual([-168, -218, 1000, 898]);
|
|
|
|
expect(topDict.getByName("CharStrings")).toEqual(94);
|
|
|
|
expect(topDict.getByName("Private")).toEqual([45, 102]);
|
2016-05-03 16:22:22 +09:00
|
|
|
});
|
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
it("refuses to add topDict key with invalid value (bug 1068432)", function () {
|
2020-10-25 23:40:51 +09:00
|
|
|
const topDict = cff.topDict;
|
|
|
|
const defaultValue = topDict.getByName("UnderlinePosition");
|
2016-05-08 01:23:47 +09:00
|
|
|
|
|
|
|
topDict.setByKey(/* [12, 3] = */ 3075, [NaN]);
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
expect(topDict.getByName("UnderlinePosition")).toEqual(defaultValue);
|
2016-05-08 01:23:47 +09:00
|
|
|
});
|
|
|
|
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
it(
|
|
|
|
"ignores reserved commands in parseDict, and refuses to add privateDict " +
|
|
|
|
"keys with invalid values (bug 1308536)",
|
2020-04-14 19:28:14 +09:00
|
|
|
function () {
|
2020-10-25 23:40:51 +09:00
|
|
|
const bytes = new Uint8Array([
|
2021-05-19 18:24:38 +09:00
|
|
|
64, 39, 31, 30, 252, 114, 137, 115, 79, 30, 197, 119, 2, 99, 127, 6,
|
|
|
|
]);
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
parser.bytes = bytes;
|
2020-10-25 23:40:51 +09:00
|
|
|
const topDict = cff.topDict;
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
topDict.setByName("Private", [bytes.length, 0]);
|
2016-10-08 03:51:02 +09:00
|
|
|
|
2020-10-25 23:40:51 +09:00
|
|
|
const parsePrivateDict = function () {
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
parser.parsePrivateDict(topDict);
|
|
|
|
};
|
|
|
|
expect(parsePrivateDict).not.toThrow();
|
2016-10-08 03:51:02 +09:00
|
|
|
|
2020-10-25 23:40:51 +09:00
|
|
|
const privateDict = topDict.privateDict;
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
expect(privateDict.getByName("BlueValues")).toBeNull();
|
|
|
|
}
|
|
|
|
);
|
2016-10-08 03:51:02 +09:00
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
it("parses a CharString having cntrmask", function () {
|
2019-12-25 23:54:34 +09:00
|
|
|
// prettier-ignore
|
2020-10-25 23:40:51 +09:00
|
|
|
const bytes = new Uint8Array([0, 1, // count
|
2016-05-03 16:22:22 +09:00
|
|
|
1, // offsetSize
|
|
|
|
0, // offset[0]
|
|
|
|
38, // end
|
|
|
|
149, 149, 149, 149, 149, 149, 149, 149,
|
|
|
|
149, 149, 149, 149, 149, 149, 149, 149,
|
|
|
|
1, // hstem
|
|
|
|
149, 149, 149, 149, 149, 149, 149, 149,
|
|
|
|
149, 149, 149, 149, 149, 149, 149, 149,
|
|
|
|
3, // vstem
|
|
|
|
20, // cntrmask
|
|
|
|
22, 22, // fail if misparsed as hmoveto
|
|
|
|
14 // endchar
|
|
|
|
]);
|
|
|
|
parser.bytes = bytes;
|
2020-10-25 23:40:51 +09:00
|
|
|
const charStringsIndex = parser.parseIndex(0).obj;
|
|
|
|
const charStrings = parser.parseCharStrings({
|
2017-07-08 05:12:52 +09:00
|
|
|
charStrings: charStringsIndex,
|
|
|
|
privateDict: privateDictStub,
|
|
|
|
}).charStrings;
|
2016-05-03 16:22:22 +09:00
|
|
|
expect(charStrings.count).toEqual(1);
|
|
|
|
// shoudn't be sanitized
|
|
|
|
expect(charStrings.get(0).length).toEqual(38);
|
|
|
|
});
|
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
it("parses a CharString endchar with 4 args w/seac enabled", function () {
|
2020-03-24 18:44:17 +09:00
|
|
|
const cffParser = new CFFParser(
|
|
|
|
fontData,
|
|
|
|
{},
|
|
|
|
/* seacAnalysisEnabled = */ true
|
|
|
|
);
|
|
|
|
cffParser.parse(); // cff
|
2016-05-03 16:22:22 +09:00
|
|
|
|
2019-12-25 23:54:34 +09:00
|
|
|
// prettier-ignore
|
2020-10-25 23:40:51 +09:00
|
|
|
const bytes = new Uint8Array([0, 1, // count
|
2016-05-03 16:22:22 +09:00
|
|
|
1, // offsetSize
|
|
|
|
0, // offset[0]
|
|
|
|
237, 247, 22, 247, 72, 204, 247, 86, 14]);
|
2020-03-24 18:44:17 +09:00
|
|
|
cffParser.bytes = bytes;
|
2020-10-25 23:40:51 +09:00
|
|
|
const charStringsIndex = cffParser.parseIndex(0).obj;
|
|
|
|
const result = cffParser.parseCharStrings({
|
2017-07-08 05:12:52 +09:00
|
|
|
charStrings: charStringsIndex,
|
|
|
|
privateDict: privateDictStub,
|
|
|
|
});
|
2016-05-03 16:22:22 +09:00
|
|
|
expect(result.charStrings.count).toEqual(1);
|
|
|
|
expect(result.charStrings.get(0).length).toEqual(1);
|
|
|
|
expect(result.seacs.length).toEqual(1);
|
|
|
|
expect(result.seacs[0].length).toEqual(4);
|
|
|
|
expect(result.seacs[0][0]).toEqual(130);
|
|
|
|
expect(result.seacs[0][1]).toEqual(180);
|
|
|
|
expect(result.seacs[0][2]).toEqual(65);
|
|
|
|
expect(result.seacs[0][3]).toEqual(194);
|
|
|
|
});
|
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
it("parses a CharString endchar with 4 args w/seac disabled", function () {
|
2020-03-24 18:44:17 +09:00
|
|
|
const cffParser = new CFFParser(
|
|
|
|
fontData,
|
|
|
|
{},
|
|
|
|
/* seacAnalysisEnabled = */ false
|
|
|
|
);
|
|
|
|
cffParser.parse(); // cff
|
2016-05-03 16:22:22 +09:00
|
|
|
|
2019-12-25 23:54:34 +09:00
|
|
|
// prettier-ignore
|
2020-10-25 23:40:51 +09:00
|
|
|
const bytes = new Uint8Array([0, 1, // count
|
2016-05-03 16:22:22 +09:00
|
|
|
1, // offsetSize
|
|
|
|
0, // offset[0]
|
|
|
|
237, 247, 22, 247, 72, 204, 247, 86, 14]);
|
2020-03-24 18:44:17 +09:00
|
|
|
cffParser.bytes = bytes;
|
2020-10-25 23:40:51 +09:00
|
|
|
const charStringsIndex = cffParser.parseIndex(0).obj;
|
|
|
|
const result = cffParser.parseCharStrings({
|
2017-07-08 05:12:52 +09:00
|
|
|
charStrings: charStringsIndex,
|
|
|
|
privateDict: privateDictStub,
|
|
|
|
});
|
2016-05-03 16:22:22 +09:00
|
|
|
expect(result.charStrings.count).toEqual(1);
|
|
|
|
expect(result.charStrings.get(0).length).toEqual(9);
|
|
|
|
expect(result.seacs.length).toEqual(0);
|
|
|
|
});
|
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
it("parses a CharString endchar no args", function () {
|
2019-12-25 23:54:34 +09:00
|
|
|
// prettier-ignore
|
2020-10-25 23:40:51 +09:00
|
|
|
const bytes = new Uint8Array([0, 1, // count
|
2016-05-03 16:22:22 +09:00
|
|
|
1, // offsetSize
|
|
|
|
0, // offset[0]
|
|
|
|
14]);
|
|
|
|
parser.bytes = bytes;
|
2020-10-25 23:40:51 +09:00
|
|
|
const charStringsIndex = parser.parseIndex(0).obj;
|
|
|
|
const result = parser.parseCharStrings({
|
2017-07-08 05:12:52 +09:00
|
|
|
charStrings: charStringsIndex,
|
|
|
|
privateDict: privateDictStub,
|
|
|
|
});
|
2016-05-03 16:22:22 +09:00
|
|
|
expect(result.charStrings.count).toEqual(1);
|
|
|
|
expect(result.charStrings.get(0)[0]).toEqual(14);
|
|
|
|
expect(result.seacs.length).toEqual(0);
|
|
|
|
});
|
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
it("parses predefined charsets", function () {
|
2020-10-25 23:40:51 +09:00
|
|
|
const charset = parser.parseCharsets(0, 0, null, true);
|
2016-05-03 16:22:22 +09:00
|
|
|
expect(charset.predefined).toEqual(true);
|
|
|
|
});
|
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
it("parses charset format 0", function () {
|
2016-05-03 16:22:22 +09:00
|
|
|
// The first three bytes make the offset large enough to skip predefined.
|
2019-12-25 23:54:34 +09:00
|
|
|
// prettier-ignore
|
2020-10-25 23:40:51 +09:00
|
|
|
const bytes = new Uint8Array([0x00, 0x00, 0x00,
|
2016-05-03 16:22:22 +09:00
|
|
|
0x00, // format
|
|
|
|
0x00, 0x02 // sid/cid
|
|
|
|
]);
|
|
|
|
parser.bytes = bytes;
|
2020-10-25 23:40:51 +09:00
|
|
|
let charset = parser.parseCharsets(3, 2, new CFFStrings(), false);
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
expect(charset.charset[1]).toEqual("exclam");
|
2016-05-03 16:22:22 +09:00
|
|
|
|
|
|
|
// CID font
|
|
|
|
charset = parser.parseCharsets(3, 2, new CFFStrings(), true);
|
|
|
|
expect(charset.charset[1]).toEqual(2);
|
|
|
|
});
|
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
it("parses charset format 1", function () {
|
2016-05-03 16:22:22 +09:00
|
|
|
// The first three bytes make the offset large enough to skip predefined.
|
2019-12-25 23:54:34 +09:00
|
|
|
// prettier-ignore
|
2020-10-25 23:40:51 +09:00
|
|
|
const bytes = new Uint8Array([0x00, 0x00, 0x00,
|
2016-05-03 16:22:22 +09:00
|
|
|
0x01, // format
|
|
|
|
0x00, 0x08, // sid/cid start
|
|
|
|
0x01 // sid/cid left
|
|
|
|
]);
|
|
|
|
parser.bytes = bytes;
|
2020-10-25 23:40:51 +09:00
|
|
|
let charset = parser.parseCharsets(3, 2, new CFFStrings(), false);
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
expect(charset.charset).toEqual([".notdef", "quoteright", "parenleft"]);
|
2016-05-03 16:22:22 +09:00
|
|
|
|
|
|
|
// CID font
|
|
|
|
charset = parser.parseCharsets(3, 2, new CFFStrings(), true);
|
2020-03-24 22:33:43 +09:00
|
|
|
expect(charset.charset).toEqual([0, 8, 9]);
|
2016-05-03 16:22:22 +09:00
|
|
|
});
|
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
it("parses charset format 2", function () {
|
2016-05-03 16:22:22 +09:00
|
|
|
// format 2 is the same as format 1 but the left is card16
|
|
|
|
// The first three bytes make the offset large enough to skip predefined.
|
2019-12-25 23:54:34 +09:00
|
|
|
// prettier-ignore
|
2020-10-25 23:40:51 +09:00
|
|
|
const bytes = new Uint8Array([0x00, 0x00, 0x00,
|
2016-05-03 16:22:22 +09:00
|
|
|
0x02, // format
|
|
|
|
0x00, 0x08, // sid/cid start
|
|
|
|
0x00, 0x01 // sid/cid left
|
|
|
|
]);
|
|
|
|
parser.bytes = bytes;
|
2020-10-25 23:40:51 +09:00
|
|
|
let charset = parser.parseCharsets(3, 2, new CFFStrings(), false);
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
expect(charset.charset).toEqual([".notdef", "quoteright", "parenleft"]);
|
2016-05-03 16:22:22 +09:00
|
|
|
|
|
|
|
// CID font
|
|
|
|
charset = parser.parseCharsets(3, 2, new CFFStrings(), true);
|
2020-03-24 22:33:43 +09:00
|
|
|
expect(charset.charset).toEqual([0, 8, 9]);
|
2016-05-03 16:22:22 +09:00
|
|
|
});
|
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
it("parses encoding format 0", function () {
|
2016-05-03 16:22:22 +09:00
|
|
|
// The first two bytes make the offset large enough to skip predefined.
|
2019-12-25 23:54:34 +09:00
|
|
|
// prettier-ignore
|
2020-10-25 23:40:51 +09:00
|
|
|
const bytes = new Uint8Array([0x00, 0x00,
|
2016-05-03 16:22:22 +09:00
|
|
|
0x00, // format
|
|
|
|
0x01, // count
|
|
|
|
0x08 // start
|
|
|
|
]);
|
|
|
|
parser.bytes = bytes;
|
2020-10-25 23:40:51 +09:00
|
|
|
const encoding = parser.parseEncoding(2, {}, new CFFStrings(), null);
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
expect(encoding.encoding).toEqual(createWithNullProto({ 0x8: 1 }));
|
2016-05-03 16:22:22 +09:00
|
|
|
});
|
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
it("parses encoding format 1", function () {
|
2016-05-03 16:22:22 +09:00
|
|
|
// The first two bytes make the offset large enough to skip predefined.
|
2019-12-25 23:54:34 +09:00
|
|
|
// prettier-ignore
|
2020-10-25 23:40:51 +09:00
|
|
|
const bytes = new Uint8Array([0x00, 0x00,
|
2016-05-03 16:22:22 +09:00
|
|
|
0x01, // format
|
|
|
|
0x01, // num ranges
|
|
|
|
0x07, // range1 start
|
|
|
|
0x01 // range2 left
|
|
|
|
]);
|
|
|
|
parser.bytes = bytes;
|
2020-10-25 23:40:51 +09:00
|
|
|
const encoding = parser.parseEncoding(2, {}, new CFFStrings(), null);
|
2016-05-03 16:22:22 +09:00
|
|
|
expect(encoding.encoding).toEqual(
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
createWithNullProto({ 0x7: 0x01, 0x08: 0x02 })
|
|
|
|
);
|
2016-05-03 16:22:22 +09:00
|
|
|
});
|
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
it("parses fdselect format 0", function () {
|
2019-12-25 23:54:34 +09:00
|
|
|
// prettier-ignore
|
2020-10-25 23:40:51 +09:00
|
|
|
const bytes = new Uint8Array([0x00, // format
|
2016-05-03 16:22:22 +09:00
|
|
|
0x00, // gid: 0 fd: 0
|
|
|
|
0x01 // gid: 1 fd: 1
|
2016-05-27 00:34:00 +09:00
|
|
|
]);
|
|
|
|
parser.bytes = bytes.slice();
|
2020-10-25 23:40:51 +09:00
|
|
|
const fdSelect = parser.parseFDSelect(0, 2);
|
2016-05-27 00:34:00 +09:00
|
|
|
|
2016-05-03 16:22:22 +09:00
|
|
|
expect(fdSelect.fdSelect).toEqual([0, 1]);
|
2018-01-05 07:43:07 +09:00
|
|
|
expect(fdSelect.format).toEqual(0);
|
2016-05-03 16:22:22 +09:00
|
|
|
});
|
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
it("parses fdselect format 3", function () {
|
2019-12-25 23:54:34 +09:00
|
|
|
// prettier-ignore
|
2020-10-25 23:40:51 +09:00
|
|
|
const bytes = new Uint8Array([0x03, // format
|
2016-05-03 16:22:22 +09:00
|
|
|
0x00, 0x02, // range count
|
|
|
|
0x00, 0x00, // first gid
|
|
|
|
0x09, // font dict 1 id
|
2016-05-27 00:34:00 +09:00
|
|
|
0x00, 0x02, // next gid
|
|
|
|
0x0a, // font dict 2 id
|
2016-05-03 16:22:22 +09:00
|
|
|
0x00, 0x04 // sentinel (last gid)
|
2016-05-27 00:34:00 +09:00
|
|
|
]);
|
|
|
|
parser.bytes = bytes.slice();
|
2020-10-25 23:40:51 +09:00
|
|
|
const fdSelect = parser.parseFDSelect(0, 4);
|
2016-05-27 00:34:00 +09:00
|
|
|
|
|
|
|
expect(fdSelect.fdSelect).toEqual([9, 9, 0xa, 0xa]);
|
2018-01-05 07:43:07 +09:00
|
|
|
expect(fdSelect.format).toEqual(3);
|
2016-05-27 00:34:00 +09:00
|
|
|
});
|
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
it("parses invalid fdselect format 3 (bug 1146106)", function () {
|
2019-12-25 23:54:34 +09:00
|
|
|
// prettier-ignore
|
2020-10-25 23:40:51 +09:00
|
|
|
const bytes = new Uint8Array([0x03, // format
|
2016-05-27 00:34:00 +09:00
|
|
|
0x00, 0x02, // range count
|
|
|
|
0x00, 0x01, // first gid (invalid)
|
|
|
|
0x09, // font dict 1 id
|
|
|
|
0x00, 0x02, // next gid
|
|
|
|
0x0a, // font dict 2 id
|
|
|
|
0x00, 0x04 // sentinel (last gid)
|
|
|
|
]);
|
|
|
|
parser.bytes = bytes.slice();
|
2020-10-25 23:40:51 +09:00
|
|
|
const fdSelect = parser.parseFDSelect(0, 4);
|
2016-05-27 00:34:00 +09:00
|
|
|
|
2016-05-03 16:22:22 +09:00
|
|
|
expect(fdSelect.fdSelect).toEqual([9, 9, 0xa, 0xa]);
|
2018-01-05 07:43:07 +09:00
|
|
|
expect(fdSelect.format).toEqual(3);
|
2016-05-03 16:22:22 +09:00
|
|
|
});
|
|
|
|
|
|
|
|
// TODO fdArray
|
|
|
|
});
|
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
describe("CFFCompiler", function () {
|
2017-10-19 10:33:35 +09:00
|
|
|
function testParser(bytes) {
|
|
|
|
bytes = new Uint8Array(bytes);
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
return new CFFParser(
|
|
|
|
{
|
|
|
|
getBytes: () => {
|
|
|
|
return bytes;
|
|
|
|
},
|
2017-10-19 10:33:35 +09:00
|
|
|
},
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
{},
|
|
|
|
SEAC_ANALYSIS_ENABLED
|
|
|
|
);
|
2017-10-19 10:33:35 +09:00
|
|
|
}
|
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
it("encodes integers", function () {
|
2020-10-25 23:40:51 +09:00
|
|
|
const c = new CFFCompiler();
|
2016-05-03 16:22:22 +09:00
|
|
|
// all the examples from the spec
|
|
|
|
expect(c.encodeInteger(0)).toEqual([0x8b]);
|
|
|
|
expect(c.encodeInteger(100)).toEqual([0xef]);
|
|
|
|
expect(c.encodeInteger(-100)).toEqual([0x27]);
|
|
|
|
expect(c.encodeInteger(1000)).toEqual([0xfa, 0x7c]);
|
|
|
|
expect(c.encodeInteger(-1000)).toEqual([0xfe, 0x7c]);
|
|
|
|
expect(c.encodeInteger(10000)).toEqual([0x1c, 0x27, 0x10]);
|
|
|
|
expect(c.encodeInteger(-10000)).toEqual([0x1c, 0xd8, 0xf0]);
|
|
|
|
expect(c.encodeInteger(100000)).toEqual([0x1d, 0x00, 0x01, 0x86, 0xa0]);
|
|
|
|
expect(c.encodeInteger(-100000)).toEqual([0x1d, 0xff, 0xfe, 0x79, 0x60]);
|
|
|
|
});
|
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
it("encodes floats", function () {
|
2020-10-25 23:40:51 +09:00
|
|
|
const c = new CFFCompiler();
|
2016-05-03 16:22:22 +09:00
|
|
|
expect(c.encodeFloat(-2.25)).toEqual([0x1e, 0xe2, 0xa2, 0x5f]);
|
|
|
|
expect(c.encodeFloat(5e-11)).toEqual([0x1e, 0x5c, 0x11, 0xff]);
|
|
|
|
});
|
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
it("sanitizes name index", function () {
|
2020-10-25 23:40:51 +09:00
|
|
|
const c = new CFFCompiler();
|
|
|
|
let nameIndexCompiled = c.compileNameIndex(["[a"]);
|
|
|
|
let parser = testParser(nameIndexCompiled);
|
|
|
|
let nameIndex = parser.parseIndex(0);
|
|
|
|
let names = parser.parseNameIndex(nameIndex.obj);
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
expect(names).toEqual(["_a"]);
|
2017-10-19 10:33:35 +09:00
|
|
|
|
2020-10-25 23:40:51 +09:00
|
|
|
let longName = "";
|
|
|
|
for (let i = 0; i < 129; i++) {
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
longName += "_";
|
2017-10-19 10:33:35 +09:00
|
|
|
}
|
|
|
|
nameIndexCompiled = c.compileNameIndex([longName]);
|
|
|
|
parser = testParser(nameIndexCompiled);
|
|
|
|
nameIndex = parser.parseIndex(0);
|
|
|
|
names = parser.parseNameIndex(nameIndex.obj);
|
|
|
|
expect(names[0].length).toEqual(127);
|
|
|
|
});
|
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
it("compiles fdselect format 0", function () {
|
2020-10-25 23:40:51 +09:00
|
|
|
const fdSelect = new CFFFDSelect(0, [3, 2, 1]);
|
|
|
|
const c = new CFFCompiler();
|
|
|
|
const out = c.compileFDSelect(fdSelect);
|
2018-01-05 07:43:07 +09:00
|
|
|
expect(out).toEqual([
|
|
|
|
0, // format
|
|
|
|
3, // gid: 0 fd 3
|
|
|
|
2, // gid: 1 fd 3
|
|
|
|
1, // gid: 2 fd 3
|
|
|
|
]);
|
|
|
|
});
|
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
it("compiles fdselect format 3", function () {
|
2020-10-25 23:40:51 +09:00
|
|
|
const fdSelect = new CFFFDSelect(3, [0, 0, 1, 1]);
|
|
|
|
const c = new CFFCompiler();
|
|
|
|
const out = c.compileFDSelect(fdSelect);
|
2018-01-05 07:43:07 +09:00
|
|
|
expect(out).toEqual([
|
|
|
|
3, // format
|
|
|
|
0, // nRanges (high)
|
|
|
|
2, // nRanges (low)
|
|
|
|
0, // range struct 0 - first (high)
|
|
|
|
0, // range struct 0 - first (low)
|
|
|
|
0, // range struct 0 - fd
|
|
|
|
0, // range struct 0 - first (high)
|
|
|
|
2, // range struct 0 - first (low)
|
|
|
|
1, // range struct 0 - fd
|
|
|
|
0, // sentinel (high)
|
|
|
|
4, // sentinel (low)
|
|
|
|
]);
|
|
|
|
});
|
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
it("compiles fdselect format 3, single range", function () {
|
2020-10-25 23:40:51 +09:00
|
|
|
const fdSelect = new CFFFDSelect(3, [0, 0]);
|
|
|
|
const c = new CFFCompiler();
|
|
|
|
const out = c.compileFDSelect(fdSelect);
|
2018-01-05 07:43:07 +09:00
|
|
|
expect(out).toEqual([
|
|
|
|
3, // format
|
|
|
|
0, // nRanges (high)
|
|
|
|
1, // nRanges (low)
|
|
|
|
0, // range struct 0 - first (high)
|
|
|
|
0, // range struct 0 - first (low)
|
|
|
|
0, // range struct 0 - fd
|
|
|
|
0, // sentinel (high)
|
|
|
|
2, // sentinel (low)
|
|
|
|
]);
|
|
|
|
});
|
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
it("compiles charset of CID font", function () {
|
2020-10-25 23:40:51 +09:00
|
|
|
const charset = new CFFCharset();
|
|
|
|
const c = new CFFCompiler();
|
|
|
|
const numGlyphs = 7;
|
|
|
|
const out = c.compileCharset(charset, numGlyphs, new CFFStrings(), true);
|
2019-02-27 08:57:46 +09:00
|
|
|
// All CID charsets get turned into a simple format 2.
|
|
|
|
expect(out).toEqual([
|
|
|
|
2, // format
|
|
|
|
0, // cid (high)
|
|
|
|
0, // cid (low)
|
|
|
|
0, // nLeft (high)
|
|
|
|
numGlyphs - 1, // nLeft (low)
|
|
|
|
]);
|
|
|
|
});
|
|
|
|
|
2020-04-14 19:28:14 +09:00
|
|
|
it("compiles charset of non CID font", function () {
|
2020-10-25 23:40:51 +09:00
|
|
|
const charset = new CFFCharset(false, 0, ["space", "exclam"]);
|
|
|
|
const c = new CFFCompiler();
|
|
|
|
const numGlyphs = 3;
|
|
|
|
const out = c.compileCharset(charset, numGlyphs, new CFFStrings(), false);
|
2019-02-27 08:57:46 +09:00
|
|
|
// All non-CID fonts use a format 0 charset.
|
|
|
|
expect(out).toEqual([
|
|
|
|
0, // format
|
|
|
|
0, // sid of 'space' (high)
|
|
|
|
1, // sid of 'space' (low)
|
|
|
|
0, // sid of 'exclam' (high)
|
|
|
|
2, // sid of 'exclam' (low)
|
|
|
|
]);
|
|
|
|
});
|
|
|
|
|
2016-05-03 16:22:22 +09:00
|
|
|
// TODO a lot more compiler tests
|
|
|
|
});
|