Re: Translator Feedback Request: Which Lokalize actions should be kept, implemented, or removed?
"Josep M. Ferrer" <[email protected]> Sat, 14 Feb 2026 16:55:33 +0100
| Newsgroups | gmane.comp.kde.devel.internationalization-and-documentation |
|---|---|
| Message-ID | <[email protected]> |
El 13/2/26 a les 19:35, Tanish ha escrit: > > Hi translators, > > I’m reviewing a set of Lokalize menu/toolbar actions that are > currently listed in the UI but may not be fully active. > Before deciding whether to implement or remove them, I’d really > appreciate feedback based on your real translation workflows. > > Could you please tell me which actions are useful for you and which > are not? > > Reply format: > > * Must have: > * Nice to have: > * Not useful for my workflow: > * Missing action(s) you want: > > Actions and plain descriptions: > > Editing > > * edit_copy: Copy selected text. > * edit_cut: Cut selected text. > * edit_paste: Paste text from clipboard. > * edit_select_all: Select all text in the current field/view. > * edit_deselect: Clear current selection. > > File/Tab management > > * file_close: Close the current translation tab. > * file_close_all: Close all open translation tabs. > * file_save_all: Save all open files. > * file_revert: Discard unsaved changes in current file and reload > saved version. > * file_revert_all: Revert all open files to their last saved state. > * file_print: Print current file. > * file_print_preview: Show print preview. > * file_mail: Send current file/content by email. > * file_new: Create a new file. > > Translation workflow > > * alttrans_attach: Attach an external file as an alternate > translation source. > * bookmark_edit: Edit/manage bookmarks. > * odf2xliff: Convert OpenDocument content to XLIFF for translation. > > Navigation > > * go_back: Go to previous location in navigation history. > * go_forward: Go to next location in navigation history. > * go_document_back: Go to previous document in document history. > * go_document_forward: Go to next document in document history. > * go_goto: Jump to a specific location/entry. > * go_goto_line: Jump to a specific line. > * go_home: Jump to home/start location. > * go_up: Move one level up. > > Thank you for your help. Your feedback will directly guide what I keep > and improve in Lokalize. > > Best regards, > Tanish Kumar > Season of KDE 2026 Participant > KDE Invent: > https://invent.kde.org/tanishfr<https://invent.kde.org/tanishfr> > > Hi Tanish, these are my options: Must have: edit_copy: Copy selected text. edit_cut: Cut selected text. edit_paste: Paste text from clipboard. edit_select_all: Select all text in the current field/view. file_close: Close the current translation tab. file_revert: Discard unsaved changes in current file and reload saved version. file_new: Create a new file. alttrans_attach: Attach an external file as an alternate translation source. go_back: Go to previous location in navigation history. go_forward: Go to next location in navigation history. go_goto: Jump to a specific location/entry. go_goto_line: Jump to a specific line. go_home: Jump to home/start location. Nice to have: edit_deselect: Clear current selection. file_close_all: Close all open translation tabs. file_save_all: Save all open files. file_revert_all: Revert all open files to their last saved state. go_document_back: Go to previous document in document history. go_document_forward: Go to next document in document history. go_up: Move one level up. Not useful for my workflow: bookmark_edit: Edit/manage bookmarks. odf2xliff: Convert OpenDocument content to XLIFF for translation. file_print: Print current file. file_print_preview: Show print preview. file_mail: Send current file/content by email. Missing action(s) you want: Editing a po file: Action to copy directly all text from the current source message to clipboard (with a shortcut) Editing a po file: Action to copy directly all text from the current target message to clipboard (with a shortcut) Just a comment about odf2xliff. Maybe this option is only useful for people not in this mailing list, so I would recommend some caution before removing this feature. Best regards, Josep M. Ferrer