Skip to content

fontconfig: handle when lang is string and not langset - #14853

Merged
mitchellh merged 1 commit into
mainfrom
pluie/jj-tyurmpmrlnzn
Oct 26, 2026
Merged

mitchellh merged 1 commit into
mainfrom
pluie/jj-tyurmpmrlnzn

Conversation

@pluiedev

@pluiedev pluiedev commented Oct 26, 2026 •

Copy link
Copy Markdown
Member

Fontconfig accepts strings when a langset is expected. This by itself is not a problem. But for some ungodly reason it can also return a string in place of a langset, for example when a FcPattern doesn't match any language and it falls back to "en". Just why would you do this? What reason can there ever be to do this??????

@pluiedev
pluiedev requested a review from a team as a code owner October 26, 2026 09:44
Fontconfig accepts strings when a langset is expected. This by itself is
not a problem. But for some ungodly reason it can also *return* a string
in place of a langset, for example when a `FcPattern` doesn't match any
language and it falls back to `"en"`. Just why would you do this? What
reason can there ever be to do this??????
@pluiedev
pluiedev force-pushed the pluie/jj-tyurmpmrlnzn branch from f28954c to f63124c Compare October 26, 2026 09:45
@mitchellh
mitchellh merged commit 8112f76 into main Oct 26, 2026
210 of 214 checks passed
@mitchellh
mitchellh deleted the pluie/jj-tyurmpmrlnzn branch October 26, 2026 12:16
@github-actions github-actions Bot added this to the 1.5.0 milestone Oct 26, 2026
@pluiedev

Copy link
Copy Markdown
Member Author

I think this should be part of the 1.4 milestone? Doesn't make sense to put it in 1.5 I think

@mitchellh mitchellh modified the milestones: 1.5.0, 1.4.0 Oct 26, 2026
@mitchellh

Copy link
Copy Markdown
Contributor

Yes, automation error

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants