The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.If all displayed strings are extracted out of the code and replaced by variables the translation into other languages would be easier. Attached are a modified default (English) autosave.js where all strings are replaced by variables and a localized German version.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | autosave.js_.txt | 5.19 KB | ferrum |
| #4 | autosave.de_.po | 3.7 KB | ferrum |
| #2 | autosave.js_.txt | 4.31 KB | ferrum |
| #1 | autosave.js_.txt | 4.34 KB | ferrum |
| #1 | autosave.de_.js_.txt | 4.46 KB | ferrum |
Comments
Comment #1
ferrum commentedComment #2
ferrum commentednext step: use Drupal's localization mechanism
Now when the language dependent strings are extracted use Drupal's translation function Drupal.t() to add these strings to the normal localization mechanism.
Comment #3
ferrum commentedComment #4
ferrum commentednow here is a German translation for all of the language dependent strings used in autosave
Comment #5
ferrum commentedfor autosave 6.x-2.10 use
Comment #6
ferrum commentedComment #7
liquidcms commentedcan you provide this as a patch file on the latest 6.x-2.x-dev?
Comment #8
quicksketchThe patch over at #1502026: Allow interface translation provides the same thing and looks ready to go to me. The .po files are no longer part of individual projects (they live over at localize.drupal.org now), so there's no reason to keep this issue open.