summaryrefslogtreecommitdiff
path: root/sc/qa
diff options
context:
space:
mode:
authorKhaled Hosny <khaledhosny@eglug.org>2013-12-22 01:02:19 +0200
committerKhaled Hosny <khaledhosny@eglug.org>2013-12-22 01:16:24 +0200
commit4dba6f5837539746293ef6808ea39a764ab7654d (patch)
tree252c7facf89bea38bf61d42b533004d36763f6ca /sc/qa
parent0591a98155348ea640a82c1dfb69931464ae2076 (diff)
fdo#67370: Hyphens are not visible in tagged PDF
One requirement of tagged PDF is to represent automatically inserted hyphens using the soft hyphen (U+00AD) character, so we were doing this by simply passing that character to text layout code when exporting a tagged PDF (which is the literal suggestion of old PDF specification). This is wrong, though, since the soft hyphen is a control character and should not have a visible output by itself (and fonts might not even have a visible glyph there), but this happened to work because non of the layout engines we are using treated soft hyphen specially and was just showing whatever glyph the font had there. This broke with the switch to HarfBuzz since it will not show any visible glyph for Unicode control characters (by default), which is the right thing to do. Latest versions of PDF spec suggest using either ToUnicode mapping or an ActualText text entry to encode the soft hyphen instead, I found it easier to use ActualText since we already have code that handles non-standard hyphenation using it already. Change-Id: I88deadf3a806f69775b2e0ccff2f9b2f61a0f2e2
Diffstat (limited to 'sc/qa')
0 files changed, 0 insertions, 0 deletions