Oregami
Repositories/oxedyne/fe2o3

fe2o3_austenite/examples/svg_pages.rs

2 operations, oldest first

created by r1870400018:73201, which is this file's identity for as long as the history lasts, whatever it is later renamed to

read the file · who wrote it · compare two states

An operation carries no clock of its own. Each row is therefore dated by the first mark written after it by the same replica, which is one copy of the repository, and that mark is where the command that wrote the operation ended.

+ signed and verified, ? signed by a key this forge does not carry, - unsigned

OperationAuthorWhatWhen
+r1870400018:73201replica 1870400018created fe2o3_austenite/examples/svg_pages.rs40 days ago under "fe2o3_austenite svg: each glyph outline is written once per page, as a <path id> in the page's <defs>, and every occurrence is a <use href x y fill> of it -- a text page wrote every outline in full at every occurrence, so the Hematite guide's page 3 was 2,686,735 bytes and is now 932,388 (defs 70 KB, uses 352 KB, the .tsel text layer 498 KB, now the largest part). The id is 'ag' and a 64-bit hash of the outline's own path data, so one id names one shape on every page and in every font: Daimond inlines several pages into one DOM, where a repeated id must resolve to the same outline whichever copy the browser finds. Defs are per page, not per document, because Daimond's delta caches and drops pages independently. The emit memo caches the body's GlyphDefs with its ink, so a memo render and a whole-frame render write the same bytes; Pearl's SvgSink shares GlyphDefs through a new PageDevice::glyph (default: fill in place, so fe2o3_pearlite's pixmap sink is unchanged) and the one assemble_sized shell, so the Pearl round trip stays byte-identical. Pixels (headless Chrome, inline, 2x): identical or at most 3/255 on a few dozen anti-aliased pixels from float order, zero differing at 1% fuzz. Run-level <g fill> grouping was tried and made page 3 larger (972 KB), the runs being short. Test a_repeated_glyph_is_defined_once_and_used_at_each_occurrence (SZ1)"
+r1870400018:73202replica 1870400018inserted 2.1 KiB40 days ago under "fe2o3_austenite svg: each glyph outline is written once per page, as a <path id> in the page's <defs>, and every occurrence is a <use href x y fill> of it -- a text page wrote every outline in full at every occurrence, so the Hematite guide's page 3 was 2,686,735 bytes and is now 932,388 (defs 70 KB, uses 352 KB, the .tsel text layer 498 KB, now the largest part). The id is 'ag' and a 64-bit hash of the outline's own path data, so one id names one shape on every page and in every font: Daimond inlines several pages into one DOM, where a repeated id must resolve to the same outline whichever copy the browser finds. Defs are per page, not per document, because Daimond's delta caches and drops pages independently. The emit memo caches the body's GlyphDefs with its ink, so a memo render and a whole-frame render write the same bytes; Pearl's SvgSink shares GlyphDefs through a new PageDevice::glyph (default: fill in place, so fe2o3_pearlite's pixmap sink is unchanged) and the one assemble_sized shell, so the Pearl round trip stays byte-identical. Pixels (headless Chrome, inline, 2x): identical or at most 3/255 on a few dozen anti-aliased pixels from float order, zero differing at 1% fuzz. Run-level <g fill> grouping was tried and made page 3 larger (972 KB), the runs being short. Test a_repeated_glyph_is_defined_once_and_used_at_each_occurrence (SZ1)"