Page MenuHomeDevCentral

Support Grapheme functions for UTF-8 strings
ClosedPublic

Authored by dereckson on Feb 21 2022, 23:04.
Tags
None
Referenced Files
F4006671: D2550.id9264.diff
Wed, Jan 15, 12:26
F4006670: D2550.id9247.diff
Wed, Jan 15, 12:26
F4006669: D2550.id6432.diff
Wed, Jan 15, 12:26
F4006247: D2550.id.diff
Wed, Jan 15, 09:48
F4006068: D2550.diff
Wed, Jan 15, 08:58
Unknown Object (File)
Thu, Jan 9, 13:43
Unknown Object (File)
Wed, Jan 8, 01:07
Unknown Object (File)
Tue, Jan 7, 04:36
Subscribers
None

Details

Summary

The intl extension supports the grapheme concept from Unicode,
while the mbstring extension handle UT8 codepoints.

An emoji like 🏴󠁧󠁢󠁥󠁮󠁧󠁿 has 28 bytes, 7 codepoints (tags E N G L A N D),
1 grapheme. That could affects method like substr or strlen when
we want to manipulate graphemes and not codepoints.

Strategy is to offer bytes/codepoints/graphemes capabilities,
downgrade from graphemes to codepoints for non UTF-8 encoding,
and defaults to grapheme.

Test Plan

Tests added for new methods.

Diff Detail

Repository
rKERUALD Keruald libraries development repository
Lint
No Lint Coverage
Unit
No Test Coverage
Branch
mbstring-to-grapheme
Build Status
Buildable 3987
Build 4239: arc lint + arc unit

Event Timeline

dereckson held this revision as a draft.

We need unit tests for this change.

Spacing issues. Adding tests.

dereckson retitled this revision from WIP: support Grapheme functions for UTF-8 strings to Support Grapheme functions for UTF-8 strings.Nov 11 2024, 23:50
dereckson edited the test plan for this revision. (Show Details)
dereckson published this revision for review.Nov 17 2024, 00:37
dereckson accepted this revision.
This revision is now accepted and ready to land.Nov 17 2024, 00:37
This revision was landed with ongoing or failed builds.Nov 17 2024, 00:38
This revision was automatically updated to reflect the committed changes.