Fixes and changes to Lokalize, request for feedback
Łukasz Wojniłowicz
lukasz.wojnilowicz at gmail.com
Sat Aug 3 20:18:21 BST 2024
On Fri, 2 Aug 2024 13:57:02 +0300
Emir SARI <emir_sari at icloud.com> wrote:
>Greetings,
>
>I have a long list of feature requests that have been waiting in a
>text file, maybe it’s a good time to dump them here. Besides this, I
>am incredibly happy that Lokalize is getting some love, as it needs a
>lot of improvements in the text editing department.
>
>1. Easier in-(HTML)-tag text editing. It is very tedious to find the
>text to edit inside of a huge block of HTML tags, and make sure that
>it correct. 2. HTML preview. As most of you might relate, each time I
>see a huge block of HTML tags, I need to open a HTML previewer website
>to make sure I don’t mess up anything. 3. Actually readable HTMl tag
>colour. That purple is unreadable, and outright irritating while
>translating documentation where there are a lot of predefined tags. 4.
>Fixed width font by default. 5. 80 column indicator line. 6. Option to
>disable automatic completion. Never use it. Slows me a lot. 7. You
>need to actually close the glossary window in order to prompt a save.
>The window itself can be made more friendly. 8. Session restore is
>janky. Every once in a while all the panel layout gets messed up and
>you need to set an initial one then save it in order to restore it for
>new files. 9. Option to ignore HTML tags for text search. I don’t see
>how it is useful to search in HTML tags.
>
>Below suggestions will help a lot with professional looking texts, a
>la Apple-level professional text. The new HIG also includes these: 10.
>Automatic smart single and double quotes 11. Automatic en, em dash
>formatting. Two for en, three for em. 12. Unicode character
>suggestions. If there is a ASCII ligature, offer to replace it with
>Unicode characters, for instance for arrows, ellipsis’, dashes etc.
>13. Smart character suggestion. For instance offer to change 1 x 1
>into multiplication sign, offer to change hyphen into minus sign when
>used with mathematical operations etc. Greater sign, less than sign
>etc. etc.
>
>14. macOS support. Improved Windows support. Windows support is very
>glitchy at the moment. 15. Invent integration to open files directly.
>16. SVN integration to pull languages directly and set them up.
>17. Settings panel has layout issues. Maybe port to QML?
>
>Thanks for reading, and thanks again for the renewed interest.
>
>Best regards,
>Emir (𐰽𐰺𐰍)
>
>** E-mail needs to stay simple
>** Use plain text e-mail
>
>
For 3rd point I reported something similar for Qt Linguist
at https://bugreports.qt.io/browse/QTBUG-120508
Cheers,
Łukasz
More information about the kde-i18n-doc
mailing list