# DSDL string type support **URL:** \ **Category:** Development & Maintenance\ **Created:** [April 23, 2023, 3:29pm UTC](https://forum.opencyphal.org/t/dsdl-string-type-support/1873 "2023-04-23T15:29:55Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![pavel.kirienko](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/pavel.kirienko/32/9_2.png) [@pavel.kirienko](https://forum.opencyphal.org/u/pavel.kirienko)\ **Post date:** [April 23, 2023, 3:29pm UTC](https://forum.opencyphal.org/t/dsdl-string-type-support/1873/1 "2023-04-23T15:29:55Z")
I would like to point out that the support for string types in DSDL is currently marked for inclusion in the v1.0 release. The technical proposal is outlined here: > > > We will need native support for strings in UAVCAN v1.1 or later to avoid ambigui…ty like: > > \`\`\`python > uint8\[\<=100\] text > \`\`\` The implementation can be carried out easily without affecting the existing deployments. The lack of native string support is known to affect certain applications dealing with registers and file transfers (such as bootloaders). Here is one example: [yakut reg produces wrong format on output for natural8 with option -d · Issue #65 · OpenCyphal/yakut · GitHub](https://github.com/OpenCyphal/yakut/issues/65) The full list of issues scheduled for v1.0 is available here: [Issues · OpenCyphal/specification · GitHub](https://github.com/OpenCyphal/specification/issues?q=is%3Aopen+is%3Aissue+milestone%3Av1.0) ---
**Author:** ![pavel.kirienko](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/pavel.kirienko/32/9_2.png) [@pavel.kirienko](https://forum.opencyphal.org/u/pavel.kirienko)\ **Post date:** [April 24, 2023, 6:10pm UTC](https://forum.opencyphal.org/t/dsdl-string-type-support/1873/2 "2023-04-24T18:10:20Z")
_Poll ([view on site](https://forum.opencyphal.org/t/dsdl-string-type-support/1873/2))_