Translations & multilingual sites (WPML, Polylang) Free

FileDeck stores documents as ordinary WordPress content — a post type and two taxonomies — which is exactly what translation plugins are built to handle. Documents and categories translate like posts and categories do, and every piece of FileDeck’s own interface text is internationalised.

What the bundled configuration does

FileDeck ships a wpml-config.xml, the standard declaration file that WPML, Polylang and compatible plugins all read. It declares:

• the document post type and both taxonomies as translatable;
• file references (the attached file, external URL, size, type) as copied to translations — a French translation of a policy points at the same PDF, it doesn’t demand a second upload;
• lifecycle settings (visibility, expiry, download limits) as copied, so a translation is governed exactly like its original;
• the download counter as ignored — each language’s copy counts its own downloads.

Bundled interface translations

Since 2.94.0 the plugin ships translations of the strings a visitor reads in a library — the search box, the filters and their "All categories" summaries, "No documents match your search", "Download", the per-page dropdown, the document count, the lead-capture and terms prompts, the share menu — for:

Language	Locale
German	de_DE
Spanish	es_ES, es_MX
French	fr_FR
Hungarian	hu_HU
Italian	it_IT
Polish	pl_PL
Portuguese (Brazil)	pt_BR
Slovak	sk_SK
Chinese (Simplified)	zh_CN

There is no installation step: WordPress picks the file that matches Settings → General → Site Language (or the visitor’s language on a multilingual site). A community language pack from translate.wordpress.org, where one exists, takes precedence over the bundled file, so improvements contributed there reach your site first.

These are machine translations checked for placeholders and length, not native copy. If a string reads wrongly in your language, tell us on the support page or correct it at translate.wordpress.org — both routes land in the next release. Admin screens are not covered by the bundled files; a community language pack covers whatever its contributors have translated.

The honest boundary

Translation-ready is a precise claim and we keep it precise: the data model and interface are fully prepared, and the declaration file covers the meta behaviour. What we have not done is certify every workflow inside WPML’s own UI (translation management jobs, string-translation edge cases). If you run FileDeck on a multilingual site and hit anything odd, say so on the support page — multilingual reports get fixed with priority precisely because this surface is hard to test in the lab.