AnsiString vs Utf8String properly declared, Delphi: we no longer force AnsiString to UTF-8
( This announcement is a bit non-exciting small improvement around the engine codebase. For something more exciting, that I was working on through September, see the screenshot attached here :), and stay…
( This announcement is a bit non-exciting small improvement around the engine codebase. For something more exciting, that I was working on through September, see the screenshot attached here :), and stay…
AnsiString vs Utf8String properly declared, Delphi: we no longer force AnsiString to UTF-8
( This announcement is a bit non-exciting small improvement around the engine codebase. For something more exciting, that I was working on through September, see the screenshot attached here :), and stay tuned for more news soon. ) Previously, our engine did SetMultiByteConversionCodePage(CP_UTF8) forcing all AnsiStrings (with both FPC and Delphi) to have UTF-8 encoding. This is also consistent with what Lazarus LCL was (and still is) doing.
castle-engine.io
September 30, 2026 at 8:09 PM
AnsiString vs Utf8String properly declared, Delphi: we no longer force AnsiString to UTF-8
( This announcement is a bit non-exciting small improvement around the engine codebase. For something more exciting, that I was working on through September, see the screenshot attached here :), and stay…
( This announcement is a bit non-exciting small improvement around the engine codebase. For something more exciting, that I was working on through September, see the screenshot attached here :), and stay…
Next we DER encode it as a UTF8String so it can be 'digitally signed'
November 5, 2025 at 11:00 PM
Next we DER encode it as a UTF8String so it can be 'digitally signed'
Episode 241 - Artisanal Enums
@Codemobileuk #AirPower #Facebook #AWS #newsplus @ColorWare #Swift5 #UTF8String #Samsung trade ins, #PowerbeatsPro #SwiftStyle. @ericasadun
https://mtjc.fireside.fm/241
@Codemobileuk #AirPower #Facebook #AWS #newsplus @ColorWare #Swift5 #UTF8String #Samsung trade ins, #PowerbeatsPro #SwiftStyle. @ericasadun
https://mtjc.fireside.fm/241
November 19, 2024 at 4:31 PM
Episode 241 - Artisanal Enums
@Codemobileuk #AirPower #Facebook #AWS #newsplus @ColorWare #Swift5 #UTF8String #Samsung trade ins, #PowerbeatsPro #SwiftStyle. @ericasadun
https://mtjc.fireside.fm/241
@Codemobileuk #AirPower #Facebook #AWS #newsplus @ColorWare #Swift5 #UTF8String #Samsung trade ins, #PowerbeatsPro #SwiftStyle. @ericasadun
https://mtjc.fireside.fm/241
is a Utf8String coming to .NET? or do we stick to Span<byte> and alike for it?
May 20, 2025 at 2:34 AM
is a Utf8String coming to .NET? or do we stick to Span<byte> and alike for it?
@mackuba.eu who thought objc++ was a good idea?
// main.mm
#include
#import
int main(void)
{
std::cout << [@"Hello, World\n" UTF8String];
return 0;
}
// main.mm
#include
#import
int main(void)
{
std::cout << [@"Hello, World\n" UTF8String];
return 0;
}
July 5, 2025 at 3:24 AM
@mackuba.eu who thought objc++ was a good idea?
// main.mm
#include
#import
int main(void)
{
std::cout << [@"Hello, World\n" UTF8String];
return 0;
}
// main.mm
#include
#import
int main(void)
{
std::cout << [@"Hello, World\n" UTF8String];
return 0;
}
CVE-2026-9265 - Crypt::OpenSSL::PKCS12 versions before 1.96 for Perl permits a heap OOB read in print_attribute UTF8STRING path
CVE ID : CVE-2026-9265
Published : June 20, 2026, 12:46 a.m. | 2 hours, 57 minutes ago
Description : Crypt::OpenSSL::PKCS12 versions before 1.9...
CVE ID : CVE-2026-9265
Published : June 20, 2026, 12:46 a.m. | 2 hours, 57 minutes ago
Description : Crypt::OpenSSL::PKCS12 versions before 1.9...
CVE-2026-9265 - Crypt::OpenSSL::PKCS12 versions before 1.96 for Perl permits a heap OOB read in print_attribute UTF8STRING path
Crypt::OpenSSL::PKCS12 versions before 1.96 for Perl permits a heap OOB read in print_attribute UTF8STRING path. print_attribute() copies a UTF8STRING ASN.1 attribute value into a heap buffer sized exactly to its declared length via strncpy, leaving no NUL terminator. Downstream callers run strlen() on the result and pass the inflated length …
cvefeed.io
June 20, 2026 at 5:49 AM
CVE-2026-9265 - Crypt::OpenSSL::PKCS12 versions before 1.96 for Perl permits a heap OOB read in print_attribute UTF8STRING path
CVE ID : CVE-2026-9265
Published : June 20, 2026, 12:46 a.m. | 2 hours, 57 minutes ago
Description : Crypt::OpenSSL::PKCS12 versions before 1.9...
CVE ID : CVE-2026-9265
Published : June 20, 2026, 12:46 a.m. | 2 hours, 57 minutes ago
Description : Crypt::OpenSSL::PKCS12 versions before 1.9...
TC39/JavaScript Idea: Utf8String()
JS strings are UTF-16 but most langs/tools use UTF-8 which makes interop hard sometimes
Uint8String() would actually just be a new TypedArray/ArrayBuffer view (not a new String type)
It would provide familiar string APIs on raw UTF-8 bytes making interop easier
JS strings are UTF-16 but most langs/tools use UTF-8 which makes interop hard sometimes
Uint8String() would actually just be a new TypedArray/ArrayBuffer view (not a new String type)
It would provide familiar string APIs on raw UTF-8 bytes making interop easier
![// JS strings are represented as UTF-16, but most langs/tools
// have preferred using UTF-8 for many years, which complicates interop
//
// We can never change the underlying representation of JavaScript strings, but
// still many tools need to operate on raw utf-8 bytes.
//
// It would be nice if we could do use some familiar string APIs but operating
// on UTF-8 bytes
// The body returned by fetching example.com will return UTF-8 bytes.
// We can access those bytes directly in an ArrayBuffer.
let response = await fetch("https://example.com/")
let buffer = await response.arrayBuffer()
// You can then construct a Uint8Array from that buffer and each element
// will represent one UTF-8 code unit.
let bytes = new Uint8Array(buffer)
// However, now you're just working with numbers
console.log(bytes) // >> Uint8Array(1256) [60, 33, 100, 111, 99, 116, ...]
// If you want to do any string-like operations on these arrays, you basically
// need to do everything yourself
// Proposal:
// What if we had a new TypedArray class that had string-ish methods?
let utf8 = new Utf8String(buffer)
// This is still just a Uint8Array/ArrayBuffer under the hood
utf8 instanceof Uint8Array // true
utf8.buffer === buffer // true
// Indices would still just be numbers
// (They wouldn't automatically convert to UTF-16 strings)
utf8[0] // >> 60
// But accessing malformed data would return U+FFFD (�) the "Replacement Char"
utf8[malformedCharIndex] // >> 65533
// Then we can start getting into the fun bits: Now you can have familiar
// String-like APIs that operate on UTF-8 encoded bytes rather than UTF-16
utf8.trim() // >> Utf8String
utf8.padEnd(5) // >> Utf8String
// For operations that need another string, you'd use other Utf8Strings
let other = Utf8String.from("<h1>Example Domain</h1>")
utf8.includes(other)
utf8.localeCompare(other, { sensitivity: "base" })
// Maybe even regex operations could still work
utf8.match(/Example/)
utf8.replace(/Example/, Utf8String.from("Paragon"))](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:mlm5fumlu4k7emxlveklmp4z/bafkreifaj4xneiwoeyricso3ihgdhlnpf7fxsmftxmlno6xjvhvrpbyrwi)
November 18, 2024 at 9:50 PM
TC39/JavaScript Idea: Utf8String()
JS strings are UTF-16 but most langs/tools use UTF-8 which makes interop hard sometimes
Uint8String() would actually just be a new TypedArray/ArrayBuffer view (not a new String type)
It would provide familiar string APIs on raw UTF-8 bytes making interop easier
JS strings are UTF-16 but most langs/tools use UTF-8 which makes interop hard sometimes
Uint8String() would actually just be a new TypedArray/ArrayBuffer view (not a new String type)
It would provide familiar string APIs on raw UTF-8 bytes making interop easier
This is why it's prerelease :)
And why I keep bugging the clr folks for a Utf8String class.
And why I keep bugging the clr folks for a Utf8String class.
December 20, 2024 at 1:41 PM
This is why it's prerelease :)
And why I keep bugging the clr folks for a Utf8String class.
And why I keep bugging the clr folks for a Utf8String class.
🚨 EUVD-2026-38103
📊 n/a
🏢 JONASBN
📝 Crypt::OpenSSL::PKCS12 versions before 1.96 for Perl permits a heap OOB read in print_attribute UTF8STRING path.
print_attribute() copies a UTF8STRING ASN.1...
🔗 https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-38103
#cybersecurity #infosec #cve #euvd
📊 n/a
🏢 JONASBN
📝 Crypt::OpenSSL::PKCS12 versions before 1.96 for Perl permits a heap OOB read in print_attribute UTF8STRING path.
print_attribute() copies a UTF8STRING ASN.1...
🔗 https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-38103
#cybersecurity #infosec #cve #euvd
June 20, 2026 at 3:00 AM
🚨 EUVD-2026-38103
📊 n/a
🏢 JONASBN
📝 Crypt::OpenSSL::PKCS12 versions before 1.96 for Perl permits a heap OOB read in print_attribute UTF8STRING path.
print_attribute() copies a UTF8STRING ASN.1...
🔗 https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-38103
#cybersecurity #infosec #cve #euvd
📊 n/a
🏢 JONASBN
📝 Crypt::OpenSSL::PKCS12 versions before 1.96 for Perl permits a heap OOB read in print_attribute UTF8STRING path.
print_attribute() copies a UTF8STRING ASN.1...
🔗 https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-38103
#cybersecurity #infosec #cve #euvd
NSString에서 꺼낸 UTF8String을 const char* 로 집어서 strlen에 집어넣으면, 자세한 이유는 모르겠지만 0x0을 읽으려 들면서 접근위반으로 뒈짖함. lengthOfBytesUsingEncoding 을 써서 읽었어야 했다.
November 4, 2024 at 12:02 PM
NSString에서 꺼낸 UTF8String을 const char* 로 집어서 strlen에 집어넣으면, 자세한 이유는 모르겠지만 0x0을 읽으려 들면서 접근위반으로 뒈짖함. lengthOfBytesUsingEncoding 을 써서 읽었어야 했다.
string :=utf8string だと合成文字が合成されちゃう？
April 5, 2025 at 10:11 PM
string :=utf8string だと合成文字が合成されちゃう？
There’s a long issue here github.com/dotnet/runti...
We built a version of this in our experimental repo at one point.
We built a version of this in our experimental repo at one point.
Introduce a Utf8String type · Issue #933 · dotnet/runtime
AB#1117209 This is the API proposal for Utf8String, an immutable, heap-allocated representation of UTF-8 string data. See dotnet/corefxlab#2368 for the scenarios and design philosophy behind this p...
github.com
December 6, 2024 at 4:44 AM
There’s a long issue here github.com/dotnet/runti...
We built a version of this in our experimental repo at one point.
We built a version of this in our experimental repo at one point.
KMP 라고 해서 Kotlin에서 iOS 개발도 가능한 뭐 그런건데 iOS 라이브러리도 kotlin으로 작성할수 있다길래 해봤는데 그냥 완전 다른 코드짜기….
이게 swift 코드
let doc = try QRCode.Document(utf8String: input)
그리고 이게 kotlin 코드 겨우 찾은거
val document = QRCodeDocument()
document.setUtf8String(input)
이건 걍 쓰지 말란 수준의 문서를 보고도 추측으로 짜야함. 따로 만들고 말지…
이게 swift 코드
let doc = try QRCode.Document(utf8String: input)
그리고 이게 kotlin 코드 겨우 찾은거
val document = QRCodeDocument()
document.setUtf8String(input)
이건 걍 쓰지 말란 수준의 문서를 보고도 추측으로 짜야함. 따로 만들고 말지…
February 26, 2025 at 1:48 PM
KMP 라고 해서 Kotlin에서 iOS 개발도 가능한 뭐 그런건데 iOS 라이브러리도 kotlin으로 작성할수 있다길래 해봤는데 그냥 완전 다른 코드짜기….
이게 swift 코드
let doc = try QRCode.Document(utf8String: input)
그리고 이게 kotlin 코드 겨우 찾은거
val document = QRCodeDocument()
document.setUtf8String(input)
이건 걍 쓰지 말란 수준의 문서를 보고도 추측으로 짜야함. 따로 만들고 말지…
이게 swift 코드
let doc = try QRCode.Document(utf8String: input)
그리고 이게 kotlin 코드 겨우 찾은거
val document = QRCodeDocument()
document.setUtf8String(input)
이건 걍 쓰지 말란 수준의 문서를 보고도 추측으로 짜야함. 따로 만들고 말지…
how does one encode couchette with proper bedsheets in UIC 918... placeDescription UTF8String it is...
October 29, 2025 at 7:49 PM
how does one encode couchette with proper bedsheets in UIC 918... placeDescription UTF8String it is...
The nicer syntax can be a bit of a trap, though. Like, `ByteSlice` should not be something usable on a `string` unless you're explicit that (e.g.) it's a `utf8String` and the resulting byte sequence isn't necessarily usable as text. It may be more readable but that can give devs false confidence.
October 4, 2025 at 2:13 AM
The nicer syntax can be a bit of a trap, though. Like, `ByteSlice` should not be something usable on a `string` unless you're explicit that (e.g.) it's a `utf8String` and the resulting byte sequence isn't necessarily usable as text. It may be more readable but that can give devs false confidence.
It’s been a really long time since I’ve said I hate computers, but this got me.
An HSM signs a certificate using its own cert, but uses a mix of UTF8String and PrintableString when ASN.1 encoding the Issuer in the new cert. The Subject of its own cert is encoded only with PrintableString.
The […]
An HSM signs a certificate using its own cert, but uses a mix of UTF8String and PrintableString when ASN.1 encoding the Issuer in the new cert. The Subject of its own cert is encoded only with PrintableString.
The […]
Original post on mastodon.me.uk
mastodon.me.uk
February 4, 2026 at 11:01 PM
It’s been a really long time since I’ve said I hate computers, but this got me.
An HSM signs a certificate using its own cert, but uses a mix of UTF8String and PrintableString when ASN.1 encoding the Issuer in the new cert. The Subject of its own cert is encoded only with PrintableString.
The […]
An HSM signs a certificate using its own cert, but uses a mix of UTF8String and PrintableString when ASN.1 encoding the Issuer in the new cert. The Subject of its own cert is encoded only with PrintableString.
The […]