- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Nov 11 2024
@ebo @ikloecker Let me explain my thoughts. If you have time, please help me doing some tests in your environment.
Nov 10 2024
Nov 9 2024
This shell script running gpg-connect-agent should run successfully:
Nov 8 2024
gpg4win-Beta-75:
German tooltip translations are all complete
For Beta-75 it looks similar judging from my first tries.
Gpg4win-Beta-75:
Looks good, I see no "EXCEPTION_ACCESS_VIOLATION" after quitting any more.
Instead only: "process started at 14:11:03.007 has terminated with exit code 0"
Gpg4win-Beta-75: This does not work.
Gpg4win-Beta-75:
Checked the property details of some files in "Progams (X86)" and found several without product name, E.g. libgpg-error-0.dll and other dlls located at C:\Program Files (x86)\GnuPG\bin.
Or gpgolconfig.exe at C:\Program Files (x86)\Gpg4win\bin and the examble from above, libKF5JobWidgets.dll, shows no product name either.
Gpg4win-Beta-75: Symbol is there.
The umlauts are ok again!
Ok with me. setting this to resolved, then.
keep in mind https://dev.gnupg.org/T7217#193778 when tackling this task
I like it better than the very long tool tip.
Testing the removal of the appearance flag from this filter leads to this situation:
Hm, probably I would be for the html-tags, then. Is there an example where one could see how narrow tool tips really get with that option?
We shouldn't have to add explicit line breaks. Explicit line breaks will lead to bad formatting (German: Flattersatz) for people who use huge font sizes (a11y!) and Qt will wrap long tool tips so that they won't become wider than the screen. Alternatively, we wrap the tool tips (in the code that sets the tool tips) into <html> tags. Then (for whatever reason) Qt will make the tool tips much narrower. (Some people think too narrow, but we have to die one death.)