The Flatpak/OCI migration left update_flatpak_app and the refusal to replace a
repository-managed Flatpak without tests. A stand-in flatpak on PATH, in child
processes so the environment stays private, covers every scope flag, both
command shapes, a successful update and Flatpak's error text; the guard test
asserts the refusal happens before anything is downloaded.
* Expose supported BMP header recognition
Port the BMP routing check from LightCraft commit 304180a500d1b3f87c8c841f269d305161d6c8b9, preserving minimum length and DIB allowlist.
* Test BMP routing boundaries and unsupported DIB sizes
---------
Co-authored-by: Brandon Thomas <echelon@gmail.com>
flow_table made a table's first row a header row whenever its look had
header_row set, and the look defaults to Word's (header row on). The look
is an option of the table's style (w:tblLook/@w:firstRow), so a table
with no style, or a style the document doesn't have, got a header row
Word never shows: RTF bolded it and marked it \trhdr (repeat on each
page), HTML made it th, and ODT repeated it. Only Repeat as header row
(RowProps::header) makes such a row a header now; styled tables are
unchanged.
Building a paragraph through insert_text/insert_object at its end walked
every run (and insert_object counted every object before the offset) on
each call, so n appends cost O(n^2): one paragraph of 64k runs took
8.5 minutes. push_text and push_object extend the last run or start a
new one, giving the same paragraph as inserting at len().
The README's glTF "Not read" line was doubled and listed sparse
accessors and tangents, which are read.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A primitive's morph targets are not read, and only one scene becomes the
roots. Both now add a warning: a count of the primitives drawn in their
base shape, and which scene of how many was read.
Closes#1938.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A base64 body with `%2B`, `%2F` or `%3D` escapes was refused as bad
base64, and a plain body lost every escaped byte that was not UTF-8 to
U+FFFD. Escapes are now decoded to bytes first, then base64 when the URI
says so. `uri_decode` is unchanged for file names.
Closes#1936
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
sniff_delimiter reads the first 64 KiB of the text and leaves out a
record cut off at that point (#1209). When the first record is longer
than the sample, no record is counted and the function returns comma,
so a semicolon or tab file with a very wide first row opens as one
column.
When no candidate delimiter finds coherent complete records with a
delimiter in each, a candidate that finds no complete record now
counts the delimiters read so far in the first record. Delimiters
inside quoted fields are not counted. A quote inside a field that does
not start with one makes that record incoherent, and the coherent
candidate is picked. When one of those candidates ends the sample
inside a quoted field, each of them counts only up to that field's
opening quote. The per-candidate loop moved into a scan_delimiter
helper, which runs a second scan over the text before that quote.
TeX skips the blanks after a control space, `\ ` or `\` and a tab, as it
does after `\` at a line end. The lexer left them to the whitespace branch,
which added a second space, so text taken as written, such as a reference
or an `\item` label, read `one two`. The control-space branch now skips
them the way the line-end branch does, and a blank line after one still
ends the paragraph.
Three ways the lexer lost a blank line, so two paragraphs ran together:
- A comment took its line end with it, so a blank line right after it
read as a single line end (wordcraft#6350).
- A control word took the spaces and one line end after it, so a blank
line right after `\relax` at a line end read as a single line end
(wordcraft#6366).
- Only LF was a line end. TeX ends a line at LF, CR or CRLF. With CR line
ends every paragraph break was lost, and a comment or a verbatim
environment ran to the end of the file and dropped the rest of it; with
CR or CRLF a control word kept the line end after it as a space
(wordcraft#6365, #6373, #6374, #6375). The lexer now reads every line
end as LF.
Each symptom has its own test. The CR fix needs the control-word fix
before it: CRLF files read a blank line after a control word correctly
only because the CR stopped the control word from taking the line end.
Port of storytold/wordcraft#6387, whose files moved here with the LaTeX
reader.
The control symbol branch took the line end or tab after a `\` as the
symbol's name, and the parser drops unknown commands, so `mid\` at a line
end followed by `line` read as `midline`, and a blank line after it no
longer ended the paragraph. TeX reads `\` before a line end or a tab as a
control space, as for `\ `.
- lex.rs: `\` before a line end (LF or CRLF) or a tab gives `Tok::Cmd(" ")`
and leaves the line end in place, so a following blank line still ends
the paragraph and the line end adds no second space.
- parser.rs: an optional argument such as an `\item` label reads a
control space as a space instead of writing `\ ` back as text.
This also keeps apart, on reopening, a paragraph that ends in two spaces:
export writes its last space as a control space at the line end.
Port of storytold/wordcraft#6298, whose files moved here with the LaTeX
reader.
`\\*` is a line break that also forbids a page break after it. The lexer
read `\\` as the control symbol and left the `*` as text, so `a\\*b`
showed `a`, a line break, then `*b`, `\\*[3pt]` showed `*[3pt]`, and in
a tabular the next row's first cell started with `*`.
The lexer now takes the star with `\\`, so the parser and the tabular
reader see the line break they already handle, with its optional
spacing argument.
* svg: floor declared() name window to a character boundary
If the MAX_NAME+1 cut split a UTF-8 character, get(..bound).unwrap_or(rest)
fell back to scanning the entire suffix. Floor the window instead, and
when recording an overlong name extend to the next character boundary so
the key is still longer than MAX_NAME.
* test(svg): assert declared() keys stay bounded after a multibyte cut
The overlong-name refusal alone also passed on the old unwrap_or(rest)
fallback, which recorded the whole suffix. Bound recorded keys to
MAX_NAME+4 so the test fails if the suffix is stored again.