<feed xmlns='http://www.w3.org/2005/Atom'>
<title>dcpomatic/src/lib/font_id_allocator.cc, branch make-centre</title>
<subtitle>DCP-o-matic DCP tools</subtitle>
<id>https://git.carlh.net/cgit/dcpomatic/atom?h=make-centre</id>
<link rel='self' href='https://git.carlh.net/cgit/dcpomatic/atom?h=make-centre'/>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/dcpomatic/'/>
<updated>2024-01-15T09:21:59Z</updated>
<entry>
<title>Fix handling of empty font IDs and default DCP fonts (#2721) (part of #2722).</title>
<updated>2024-01-15T09:21:59Z</updated>
<author>
<name>Carl Hetherington</name>
<email>cth@carlh.net</email>
</author>
<published>2024-01-13T22:34:35Z</published>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/dcpomatic/commit/?id=db22f81ccce9e1a5f205e6d8b3c0631fc039a173'/>
<id>urn:sha1:db22f81ccce9e1a5f205e6d8b3c0631fc039a173</id>
<content type='text'>
Previously we used an empty font ID as the default for when a subtitle
has no Font, but in #2721 we saw a DCP with an empty font ID which
raised an assertion (because we'd already added our default font with
the empty ID).

Here we try to fix this (and also make the default font correctly be
that from the first &lt;LoadFont&gt;).
</content>
</entry>
<entry>
<title>Don't try to add fonts from an asset that we don't have.</title>
<updated>2024-01-04T22:35:44Z</updated>
<author>
<name>Carl Hetherington</name>
<email>cth@carlh.net</email>
</author>
<published>2023-12-29T00:30:22Z</published>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/dcpomatic/commit/?id=56cef0046ea0fabc39e1bfa5371fce1c76a259d8'/>
<id>urn:sha1:56cef0046ea0fabc39e1bfa5371fce1c76a259d8</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Always add a font with an empty ID (#2649).</title>
<updated>2023-11-16T23:24:35Z</updated>
<author>
<name>Carl Hetherington</name>
<email>cth@carlh.net</email>
</author>
<published>2023-11-10T22:51:46Z</published>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/dcpomatic/commit/?id=2603a529a05905f133bd52271fb1298e9a4a4aa5'/>
<id>urn:sha1:2603a529a05905f133bd52271fb1298e9a4a4aa5</id>
<content type='text'>
It's not just subtitle files with no &lt;LoadFont&gt; that can have
subtitles without a specified font.  In particular, DoM makes a
single space subtitle with no font spec when it creates filler
subtitles in multi-reel DCPs.
</content>
</entry>
<entry>
<title>Fix DCP content font ID allocation to cope with DCPs that have multiple fonts</title>
<updated>2023-10-15T07:10:18Z</updated>
<author>
<name>Carl Hetherington</name>
<email>cth@carlh.net</email>
</author>
<published>2023-10-14T19:48:25Z</published>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/dcpomatic/commit/?id=3c802dd6d1451c2c8a7e188f8379738d72e907eb'/>
<id>urn:sha1:3c802dd6d1451c2c8a7e188f8379738d72e907eb</id>
<content type='text'>
with the same name in the same reel (#2600).

Previously we had this id_for_font_in_reel() which would give an ID
of N_font-ID.  This means we got duplicate font IDs.

Here we replace that method with FontAllocator, which gives an ID of
N_font-ID for the first font and M_font-ID, where M is a number higher than
the highest reel index.  The idea is to support the required new IDs
without breaking exisiting projects.

There is some documentation of how it works  in doc/design/fonts
</content>
</entry>
</feed>
