Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: LuaTeX: no bugs in rendering Linear B

Table of Contents
Version 1.0.3,

...

25 February 2022

Version history:

1.0, 17 February 2022

1.01, 21 February 2022

1.02, 22 February 2022

1.03, 25 February 2022

About the script

...

Many typesetters use Adobe InDesign to perform page layout for PDF production. It has been observed that Adobe InDesign CC 2022 fails (v. 17.1) as well as CC 2021 and CC 2020 fail to render a few distinct group of Linear B characters, although the character codes remain present in the text: they are 𐀀 (Noto_Sans_Linear_B_u10000.pdfU+10000) and 𐀍 (Noto_Sans_Linear_B_u1000D.pdfU+1000D), but until the whole character set has been investigated we will not know how many more, if any(U+10000), 𐀈 (U+10008), 𐀉 (U+10009), 𐀊 (U+1000A), and 𐀍 (U+1000D). The problem seems to be connected with Adobe’s ‘World-Ready Paragraph Composers’, which are the default in Brill publications.used by default by typesetters producing PDF of Brill publications. The oldertwo Adobe Paragraph Composers: Adobe Paragraph Composer and the Adobe Single-line Paragraph Composer render all Linear B characters correctly.

Furthermore, when importing text from either .docx or .txt (UTF-8) formats, 𐄐 (U+10110, AEGEAN NUMBER TEN) and 𐄒 (U+10112, AEGEAN NUMBER THIRTY) needed a manual application of the Noto Sans Linear B font (the underlying character codes are and remain correct).

These software issues have so far not been found to occur This software issue has not been observed in any other applications including MS Word 365 and web browsers, suggesting that they are connected with the Adobe InDesign software and not with the Noto Sans Linear B font. When another font – Aegean v. 8.91 – is used to render Linear B, the exact same problems occur when one of Adobe’s World-Ready Paragraph Composers is active and not when one of the older Adobe Paragraph Composers is used; the fonts are not to blame. Without a doubt, therefore, there is a bug in both of Adobe’s World-Ready Paragraph Composers. And there are probably file import filter bugs as well.

Instruction to typesetters dealing with Linear B text

  • Adobe InDesign users must switch the paragraph composer applied to all paragraphs containing text in the Linear B script, even if there is just one Linear B character, to either of the older Adobe Paragraph Composers: Adobe Paragraph Composer or the Adobe Single-line Paragraph Composer.
  • If

...

  • a paragraph containing Linear B characters also contains complex-script text (this includes any bidirectional script such as Phoenician, Hebrew, Syriac, Arabic, etc., but also many others!),

...

  • only switching to an older Adobe Paragraph Composer is very likely to cause new problems elsewhere.

In such an event, Brill personnel must always contact scripts@brill.com.

...

A typesetting program other than Adobe InDesign

...

, such as LuaTeX as used by TAT Zetwerk

...

, does not exhibit this bug.

  • Typesetters must also check that 𐄐 (U+10110, AEGEAN NUMBER TEN) and 𐄒 (U+10112, AEGEAN NUMBER THIRTY) are rendered correctly with the Noto Sans Linear B font as well – if these characters occur, of course.

All Brill personnel sending textual material containing Linear B text to typesetting service providers who use Adobe InDesign must send along the above instruction with each batch containing Linear B material.

...