This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Previously the xWidthAvg metric was calculated based on the character frequency as measured from English text only.
This resulted in the xWidthAvg metric being incorrect for languages that use a different unicode subset range, e.g. Thai.
Supporting Thai now enables adding support for other unicode ranges in the future.
What's changed?
@capsizecss/metrics
The subsets field has been added to the metrics object, providing the xWidthAvg metric for each subset — calculated against the relevant character frequency data.
Previously the xWidthAvg metric was calculated based on the character frequency as measured from English text only.
This resulted in the xWidthAvg metric being incorrect for languages that use a different unicode subset range, e.g. Thai.
Supporting Thai now enables adding support for other unicode ranges in the future.
What's changed?
@capsizecss/metrics
The subsets field has been added to the metrics object, providing the xWidthAvg metric for each subset — calculated against the relevant character frequency data.
Previously the xWidthAvg metric was calculated based on the character frequency as measured from English text only.
This resulted in the xWidthAvg metric being incorrect for languages that use a different unicode subset range, e.g. Thai.
Supporting Thai now enables adding support for other unicode ranges in the future.
What's changed?
@capsizecss/metrics
The subsets field has been added to the metrics object, providing the xWidthAvg metric for each subset — calculated against the relevant character frequency data.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
@capsizecss/core@4.1.0
Minor Changes
#177
879208b
Thanks @michaeltaranto! - xWidthAvg: Addsubset
support for non-latin character setsPreviously the
xWidthAvg
metric was calculated based on the character frequency as measured from English text only. This resulted in thexWidthAvg
metric being incorrect for languages that use a different unicode subset range, e.g. Thai.Supporting Thai now enables adding support for other unicode ranges in the future.
What's changed?
@capsizecss/metrics
The
subsets
field has been added to the metrics object, providing thexWidthAvg
metric for each subset — calculated against the relevant character frequency data.There are no changes to any of the other existing metrics.
@capsizecss/core
Fallback font stacks can now be generated per subset, allowing the correct
xWidthAvg
metric to be used for the relevant subset.The
createFontStack
API now acceptssubset
as an option:@capsizecss/metrics@2.2.0
Minor Changes
#177
879208b
Thanks @michaeltaranto! - xWidthAvg: Addsubset
support for non-latin character setsPreviously the
xWidthAvg
metric was calculated based on the character frequency as measured from English text only. This resulted in thexWidthAvg
metric being incorrect for languages that use a different unicode subset range, e.g. Thai.Supporting Thai now enables adding support for other unicode ranges in the future.
What's changed?
@capsizecss/metrics
The
subsets
field has been added to the metrics object, providing thexWidthAvg
metric for each subset — calculated against the relevant character frequency data.There are no changes to any of the other existing metrics.
@capsizecss/core
Fallback font stacks can now be generated per subset, allowing the correct
xWidthAvg
metric to be used for the relevant subset.The
createFontStack
API now acceptssubset
as an option:@capsizecss/unpack@2.1.0
Minor Changes
#177
879208b
Thanks @michaeltaranto! - xWidthAvg: Addsubset
support for non-latin character setsPreviously the
xWidthAvg
metric was calculated based on the character frequency as measured from English text only. This resulted in thexWidthAvg
metric being incorrect for languages that use a different unicode subset range, e.g. Thai.Supporting Thai now enables adding support for other unicode ranges in the future.
What's changed?
@capsizecss/metrics
The
subsets
field has been added to the metrics object, providing thexWidthAvg
metric for each subset — calculated against the relevant character frequency data.There are no changes to any of the other existing metrics.
@capsizecss/core
Fallback font stacks can now be generated per subset, allowing the correct
xWidthAvg
metric to be used for the relevant subset.The
createFontStack
API now acceptssubset
as an option: