Integrations & reuse

Integrations and advanced settings

Filename patterns

Filename pattern defines the order of the parts. {project} is the project name chosen here, or otherwise the last part of its GlotPress path. {locale} is the exported language code, including its variant. {path} uses the full project path with hyphens instead of slashes; it ignores names chosen for {project}. {set} adds the translation set’s short name. Keep {locale}; never type .po or another extension into the pattern. Names allow A–Z, a–z, 0–9, underscores and hyphens, up to 160 characters. Optional direct entries use full/project/path = desired-name; the easiest route is the project search.

Preview

Choose Preview in a project’s result row, or enter its full GlotPress path under Check filenames before saving. No website address is needed. Examples include unsaved edits, list every translation set and use .po. The actual export supplies the selected format extension, including compound extensions such as .l10n.php. Each row explains the parts actually used. Read the status: if GlotPress or another naming plugin is responsible, these rules are illustrative only. A --set- number distinguishes otherwise identical names within one project. When a rule cannot produce a valid name, the original GlotPress name is retained.

Project search

Under Find projects and choose their filenames, search by project name or path. Up to 20 projects are shown per page. Edit Project name in filenames and choose Apply this name to the draft; then Save Changes. The field supplies {project}; a pattern using only {path} will keep the full path instead. Preview opens the selected project’s translation sets. Optional direct entry above supports multiple lines. Warnings identify missing saved project paths, invalid names and duplicate names within a project. Different projects may deliberately share filenames; those are not renamed globally.

Responsibility

Leave Automatic selected unless a different choice is needed. It uses this plugin when no recognized competitor is active; it defers to GP Download Name or GP Use Slug for Downloads when detected. Use GP Project Export Name explicitly selects these rules. Use GlotPress or another naming plugin disables this plugin’s naming changes. No plugin is deactivated. Other, unrecognized naming plugins can still affect exports; their settings may need checking separately.

External bulk downloads

Exports made by GP Bulk Download Translations also use these naming rules when this plugin is responsible. That separate plugin is optional and handles the actual bulk download. GP Project Export Name does not add its own ZIP download. Distinct filenames within a project help prevent one translation set overwriting another; this does not fix unrelated behavior in the external plugin.

Fixed language code

Advanced configuration only: an existing GP_PROJECT_EXPORT_LOCALE constant can force a fixed language code. Normally, no constant is needed because the exported translation supplies the language. Formal and custom variants stay distinct. A custom language/set entry overrides the full code for that nondefault set, even when the constant exists. Duplicate names get --set- numbers within their project. This does not install any language.

Backup and import

Under Back up or restore your settings, choose Download settings backup (.json). The file contains this website’s saved filename settings, not translations, user accounts or unsaved edits. Keep it before making larger changes.

To restore or transfer settings, open Import settings and choose that file (up to 64 KB). Alternatively, paste its JSON text. Review import lists everything that will be added, replaced or removed. Confirm these changes replaces the website’s saved filename settings; it does not merge them. A dash means that an entry is removed.

Project paths and language/set identifiers must suit the destination website. Missing projects are reported and their entries are retained. The initial rule check covers the first 20 projects; the project search checks further pages. If someone saves different settings while the review is open, confirmation is rejected so that those edits are not overwritten. Import requires GlotPress and administrator permission. Pasted-JSON import also works without JavaScript.

Reset

Open Reset filename settings and select the part to reset: the pattern, project names, language codes, the naming plugin choice or all filename settings. A single project name or custom language code can also be removed. Supply its exact saved project path or language/set identifier in that case.

Choose Review reset, check the old and new values, then Confirm these changes. Cancel returns without applying the reset. Translation content and Library preferences are unaffected.

Updates and privacy

The updater contacts api.github.com for public release metadata and GitHub for update packages; standard HTTP metadata such as the server IP is transmitted. No telemetry or credentials are required. Metadata is cached by the updater. The optional Library online catalog defaults off; its UI explains activation and installation. Only validated release packages with matching identity, offered version and compatible requirements are accepted. Prereleases are not advertised as stable updates.

Stored data

Deactivating or deleting the plugin keeps the filename settings. They belong to the current website, even with network activation. No translation text is copied or stored by this plugin. Reset filename settings offers deliberate removal of selected rules after review. Library preferences remain separate and are preserved by default; temporary Library data is cleared only when no installed deckerweb host plugin still needs it. The updater’s temporary metadata for this repository is cleared on uninstall.

Imported from the published release 2.0.0. Original source · Deutsch