Add your ANDROIDXML file
Drop one or more .androidxml files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
ANDROIDXML to QTS
Converting a .androidxml font to .qts repackages the same glyphs and metrics for a different delivery target. Free, private, and validated — the file never leaves your browser.
Private for supported formats — processed in your browser
Runs on your deviceConvert supported files
Drop ANDROIDXML files here
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.About converting Android string resources to Qt Linguist TS
Converting a .androidxml font to .qts repackages the same glyphs and metrics for a different delivery target. An Android string resource file — catalogued here as .androidxml — is the res/values/strings.xml of an Android application: a <resources> element containing <string name=…> entries, plus optional <plurals> and <string-array> groups. Because every Android project names the file strings.xml, there is no real extension to key on, so Novus Convert recognises these by the .android.xml suffix and files them under .androidxml to keep them distinct from generic XML.
A Qt Linguist translation source — catalogued here as .qts — is the XML file a Qt application is translated in: a <TS> document holding <context> groups, each containing <message> elements that pair a <source> string with its <translation>. Qt names these files .ts, which collides with TypeScript, so Novus Convert recognises them by the .qt.ts suffix and files them under .qts to keep the two apart. For this route the practical draw is context grouping gives translators genuine information about where a string appears and review state and obsolete strings are typed attributes, not conventions — balanced against the .ts extension collides with TypeScript, which breaks naive tooling constantly, which is worth knowing before you commit a large batch.
Why convert ANDROIDXML to QTS?
The practical trigger for this conversion is usually a mismatch: with .androidxml, escaping rules are a common source of subtly broken translations. Switching to .qts buys you context grouping gives translators genuine information about where a string appears, which is why it is the better fit for translating a Qt or KDE desktop application. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
ANDROIDXML vs QTS at a glance
| Aspect | Android string resources (.androidxml) | Qt Linguist TS (.qts) |
|---|---|---|
| Format type | Text-based — characters and structure, so there is no visual quality loss | Text-based — characters and structure, so there is no visual quality loss |
| How it stores data | entries are <string name=…> with the translatable text as element content; the name is the R.string identifier the code references | the root <TS> element carries a version and the target language; <context> groups messages under a <name>, conventionally the class that contains them |
| Strongest at | localising an Android application | translating a Qt or KDE desktop application |
| Weak spot | escaping rules are a common source of subtly broken translations | the .ts extension collides with TypeScript, which breaks naive tooling constantly |
| Metadata | string names and their text are preserved. Plural groups, string arrays, the translatable attribute and the directory-derived locale are not represented in flat catalog targets | source strings and translations are preserved, keyed on the source text. Context grouping, source locations, the unfinished/vanished state attribute and numerus plural forms are not represented in flat catalog targets |
Pick QTS as the output
Select .qts in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if QTS is selectable, the route is real and validated.
Convert on your device
Press Convert. The font tables are parsed and rewritten locally with fonteditor-core; glyph outlines, hinting, and kerning survive the trip.
Verify and download
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid QTS file. Outputs keep the original filename with the .qts extension.
ANDROIDXML to QTS questions, answered
Will converting ANDROIDXML to QTS lose quality?
There is no visual quality to lose — androidxml is text-oriented and qts is text-oriented, so the question is structural fidelity. Text, ordering, and basic structure are preserved; complex layout, embedded objects, and styling beyond the target's model are simplified.
Is it private to convert ANDROIDXML files here?
Yes — the .androidxml file is processed inside your browser tab and never uploaded. The font tables are parsed and rewritten locally with fonteditor-core; glyph outlines, hinting, and kerning survive the trip. Close the tab and the file is gone from memory.
Where will the QTS file work?
Qt Linguist, Qt Creator and KDE's Lokalize read .ts natively, and the larger translation platforms support it. Elsewhere it is rarely recognised — and the extension collision means generic tools frequently mistake it for TypeScript. Novus Convert keys entries on the source text, rejects documents with a doctype or custom entities, and converts to and from the other localization formats.
Will the QTS file be bigger or smaller than my ANDROIDXML?
It depends on the content: the root <TS> element carries a version and the target language; <context> groups messages under a <name>, conventionally the class that contains them. Convert one representative file first and compare before batch-processing a large set.
What happens to the metadata in my ANDROIDXML file?
In .androidxml, string names and their text are preserved. Plural groups, string arrays, the translatable attribute and the directory-derived locale are not represented in flat catalog targets. Re-encoding through the browser pipeline does not carry embedded metadata into the output, which doubles as a privacy scrub — check the exported file if you specifically need tags preserved.
Can I convert QTS back to ANDROIDXML?
Yes — the reverse route exists as a separate tool. Bear in mind that round-tripping .androidxml → .qts → .androidxml is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.