| Age | Commit message (Collapse) | Author |
|---|
|
Adding a API not to drop CBDT/CBLC tables. OTS doesn't recognize the tables
for now, but trusts users of this API, assuming users exactly know the risks.
BUG=324187
R=ksakamoto@chromium.org
Review URL: https://codereview.chromium.org/341983012
git-svn-id: http://ots.googlecode.com/svn/trunk@114 a4e77c2c-9104-11de-800e-5b313e0d2bf3
|
|
on QNX, "#include <cstring>" doesn't put memcpy in the global namespace
Patch from efidler@blackberry.com.
BUG=312446
Review URL:https://codereview.chromium.org/49933002/
git-svn-id: http://ots.googlecode.com/svn/trunk@105 a4e77c2c-9104-11de-800e-5b313e0d2bf3
|
|
Add woff2.h and woff2.cc from the WOFF 2.0 reference implementation
(https://code.google.com/p/font-compression-reference/).
WOFF2 support is disabled by default and is enabled by ots::EnableWOFF2().
Patch originally by bashi@chromium.org.
BUG=122603
R=yusukes@chromium.org
Review URL: https://codereview.chromium.org/13918002
git-svn-id: http://ots.googlecode.com/svn/trunk@100 a4e77c2c-9104-11de-800e-5b313e0d2bf3
|
|
Use intrinsics for byte order conversion, per suggestion by maruel.
Are there any other opentype tests to verify functionality? Wiki page
says I need security team access to get the malicious fonts.
Patch-by: dcurtis
BUG=115477
TEST=No longer crashes with new ffmpeg.
git-svn-id: http://ots.googlecode.com/svn/trunk@82 a4e77c2c-9104-11de-800e-5b313e0d2bf3
|
|
(This is the approach suggested by the standard.
Modern compilers inline memcpy anyway.)
Patch-by: evan
http://codereview.chromium.org/9117014/
git-svn-id: http://ots.googlecode.com/svn/trunk@80 a4e77c2c-9104-11de-800e-5b313e0d2bf3
|
|
Patch-by: rsleevi
http://codereview.chromium.org/7113001/
git-svn-id: http://ots.googlecode.com/svn/trunk@68 a4e77c2c-9104-11de-800e-5b313e0d2bf3
|
|
When ots is built as a part of Chromium, 'NOMINMAX' macro will be provided by
command-line arguments. This involves macro redefinition when we define
'NOMINMAX' in source code. To avoid this, we define it in gyp file.
BUG=73805
TEST=built ots as a part of Chromium on local windows machine.
git-svn-id: http://ots.googlecode.com/svn/trunk@56 a4e77c2c-9104-11de-800e-5b313e0d2bf3
|
|
Separated gyp file for chromium build and stand-alone build.
A test tool (idempotent) would be able to build on Windows by applying this CL.
BUG=72546
TEST=Executed idempotent.exe with some malformed/unmalformed fonts and ensured the results.
git-svn-id: http://ots.googlecode.com/svn/trunk@53 a4e77c2c-9104-11de-800e-5b313e0d2bf3
|
|
Added Script table, Featre table, Lookup table, and Device table support. This is a part of adding GPOS/GSUB table support. The CL also contains unittests for layout common tables. Some fix for bugs which detected by the unittests also included.
Review: http://codereview.chromium.org/6410047/
BUG=27131
TEST=test/layout_common_table_test.cc
git-svn-id: http://ots.googlecode.com/svn/trunk@51 a4e77c2c-9104-11de-800e-5b313e0d2bf3
|
|
Patch by: cjacek
http://codereview.chromium.org/6024011
git-svn-id: http://ots.googlecode.com/svn/trunk@45 a4e77c2c-9104-11de-800e-5b313e0d2bf3
|
|
Adds parsing/sanitising features for cmap subtable format 14 to support
UVSes in OTS. This change also changes the way to output cmap table.
0-3-4 table is no longer written as a 3-1-4 table since some fonts which
include 0-5-14 table seems to require 0-3-4 table.
Following fonts were used to test UBSes support:
- IPAex fonts
http://ossipedia.ipa.go.jp/ipafont/index.html
- Mozilla's test font for UVSes
http://mxr.mozilla.org/mozilla-central/source/layout/reftests/fonts/gw432047.ttf
BUG=66778
TEST=Ran ots/test/test_{un,}malicious_fonts.sh on Linux with various fonts and checked any errors are reported.
git-svn-id: http://ots.googlecode.com/svn/trunk@44 a4e77c2c-9104-11de-800e-5b313e0d2bf3
|
|
git-svn-id: http://ots.googlecode.com/svn/trunk@39 a4e77c2c-9104-11de-800e-5b313e0d2bf3
|
|
(a) Trailing commas in enumerations at src/cff.cc (enum DICT_OPERAND_TYPE and enum DICT_DATA_TYPE) and src/cff_type2_charstring.h (enum Type2CharStringOperator). These are not strictly correct, and lead to compiler warnings or errors, depending on the specific compiler version and options being used.
(b) Some common headers, at least in a Windows environment, appear to #define macros for "min" and "max", leading to compilation failures in include/opentype-sanitiser.h where these names are used with the explicit std:: namespace prefix. This seems to me like a flaw in the headers I'm using, which should not define such macros in a C++ environment, but a simple workaround is to #undef the names after including the windows headers.
Review URL: http://code.google.com/p/chromium/issues/detail?id=53821
Patch from Jonathan Kew (Mozilla)
git-svn-id: http://ots.googlecode.com/svn/trunk@36 a4e77c2c-9104-11de-800e-5b313e0d2bf3
|
|
Not all the test utilities will work with WOFF fonts since they tend
to get a lot larger after transcoding. I've updated |idempotent|, but
none of the others as our test suites of fonts are still in TTF format.
http://codereview.appspot.com/946044
git-svn-id: http://ots.googlecode.com/svn/trunk@29 a4e77c2c-9104-11de-800e-5b313e0d2bf3
|
|
Review URL: http://go/mair
(reviewed by Jungshik Shin. r3 is also reviewed by him.)
BUG=17818
git-svn-id: http://ots.googlecode.com/svn/trunk@10 a4e77c2c-9104-11de-800e-5b313e0d2bf3
|
|
git-svn-id: http://ots.googlecode.com/svn/trunk@2 a4e77c2c-9104-11de-800e-5b313e0d2bf3
|
