Question about CDATA export in format android-strings
complete
D
David Walter
Hello
Earlier this year (around June) I think, we had every Android string wrapped in CDATA if it contained any HTML when exporting android-strings which we then adjusted with a script on our side.
We now checked the export again, and it looks like now only HTML elements that are not natively supported by Android (This list: https://developer.android.com/guide/topics/resources/string-resource#StylingWithHTML
) are wrapped in CDATA. In our use case sometimes <a> links are in texts that should be wrapped in CDATA.
This is the correct behaviour for our use case and how the export works currently.
We just wanted to confirm with you:
- Is that the criteria that are applied when wrapping in CDATA during export in android-strings?
- And how long this behaviour is like this and if it will stay stable in the foreseeable future?
Greeting David

Jakub Pomykała
updated the status to
complete

Jakub Pomykała
Hi David,
Sorry for the slow reply. Yes, that's exactly how the android-strings export works: values that contain only tags Android supports natively (b, i, u, em, br, span, p, etc., as listed in the Android docs) are exported as-is. Values with any other tag, such as <a>, or with malformed markup are wrapped in CDATA.
It has worked this way since late August 2026. Before that, any HTML was wrapped in CDATA. We made the change so the export follows the Android documentation more closely. We knew it would change the output in some cases. We're very careful that exports never change over time without a good reason, but we didn't expect this one to cause trouble, and we're sorry for the extra work it caused on your side. We plan to keep this behaviour, and it's covered by our tests. We're also looking into a way to notify users in advance before we change an export format.
Also, feel free to email us directly at contact@simplelocalize.io with any questions or issues!