Project Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Boost Json Translation (zh_Hans) 100% 1
Boost Unordered Translation (zh_Hans) 100% 86

Summary

Language code en
Aliased language codes base, en_en, en_us, eng, enp, source
English name of the language English
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 1,728,473,503
Plural: Default plural 85 translations
Number of plurals 2
Plural type One/other
Plurals Singular 1
Plural 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, …
Plural formula n != 1
Plural: Qt Linguist plural 0 translations
Number of plurals 2
Plural type One/other
Plurals Singular 1
Plural 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, …
Plural formula (n != 1)
05/14/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 7,193 95,795 750,967
Approved 0% 0 0% 0 0% 0
Waiting for review 0% 0 0% 0 0% 0
Translated 100% 7,193 100% 95,795 100% 750,967
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 7,193 100% 95,795 100% 750,967
Failing checks 1% 87 2% 2,776 3% 22,855
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
MayJunJulAugSepOctNovDecJanFebMarApr

Quick numbers

0
Hosted words
0
Hosted strings
0%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
—
—
Hosted strings
—
—
Translated
—
—
Contributors
—
User avatar admin

Resource updated
File “doc/pages/allocators/background.adoc” was added. 05/13/2026
User avatar admin

String added in the repository
Boost.JSON solves this problem by introducing a new smart pointer called <<ref_storage_ptr>> which builds upon {cpp}17's memory allocation interfaces, accomplishing the goals above. As a result, libraries which use this type compose more easily and enjoy faster compilation, as member functions for containers which use the type can be defined out-of-line.
Boost.JSON solves this problem by introducing a new smart pointer called <<ref_storage_ptr>> which builds upon {cpp}17's memory allocation interfaces, accomplishing the goals above. As a result, libraries which use this type compose more easily and enjoy faster compilation, as member functions for containers which use the type can be defined out-of-line.
05/13/2026
User avatar admin

String added in the repository
`T` interoperates with code already using `std::pmr`
`T` interoperates with code already using `std::pmr`
05/13/2026
User avatar admin

String added in the repository
`T` supports both reference semantics or shared ownership
`T` supports both reference semantics or shared ownership
05/13/2026
User avatar admin

String added in the repository
`T` references a {ref_memory_resource}
`T` references a {ref_memory_resource}
05/13/2026
User avatar admin

String added in the repository
`T` is not a class template
`T` is not a class template
05/13/2026
User avatar admin

String added in the repository
We would like an allocator model using a single type `T` with the following properties:
We would like an allocator model using a single type `T` with the following properties:
05/13/2026
User avatar admin

String added in the repository
Problem Statement
Problem Statement
05/13/2026
User avatar admin

String added in the repository
Workarounds for this problem are worse than the problem itself. The library could return a pair with the vector and `std::unique_ptr<std::pmr::memory_resource>` which the caller must manage. Or the library could change its function signatures to accept a {ref_memory_resource}``*`` provided by the caller, where the library also makes public the desired memory resources (`my_resource` above).
Workarounds for this problem are worse than the problem itself. The library could return a pair with the vector and `std::unique_ptr<std::pmr::memory_resource>` which the caller must manage. Or the library could change its function signatures to accept a {ref_memory_resource}``*`` provided by the caller, where the library also makes public the desired memory resources (`my_resource` above).
05/13/2026
User avatar admin

String added in the repository
This can be worked around by declaring the container to use a custom allocator (perhaps using a `std::shared_ptr< std::pmr::memory_resource >` as a data member). This hinders library composition; every library now exports unique, incompatible container types. A raw memory resource pointer is also easy to misuse:
This can be worked around by declaring the container to use a custom allocator (perhaps using a `std::shared_ptr< std::pmr::memory_resource >` as a data member). This hinders library composition; every library now exports unique, incompatible container types. A raw memory resource pointer is also easy to misuse:
05/13/2026
Browse all changes for this language