https://bugs.kde.org/show_bug.cgi?id=500423
--- Comment #9 from Herb Smith ---
It has been almost a month and I thought I would update on how this
issue is impacting me. And because the issue came back
After my initial report for several days I just lived with the
problem. Then Digikam
https://bugs.kde.org/show_bug.cgi?id=158484
Herb Smith changed:
What|Removed |Added
CC||hesmith1...@aol.com
--- Comment #19 from Herb
https://bugs.kde.org/show_bug.cgi?id=500423
--- Comment #8 from Herb Smith ---
I tried all the combinations on that screen, Just In Case. None worked.
I am currently running with the Software OpenGL checked and none of the
others checked. No changes and no relief. This is after several
https://bugs.kde.org/show_bug.cgi?id=500423
--- Comment #6 from Herb Smith ---
Yes, dumb move on my part posting the file with the key. I have gotten
a new one. The new one has the same behavior.
Tried changing the openCL settings. Stopped and restarted Digikam after
each change. No
https://bugs.kde.org/show_bug.cgi?id=500423
--- Comment #4 from Herb Smith ---
The file does not disappear when I stop Digikam. I have attached the file.
When Digikam starts and I go into settings, the API key is there. But
if I just exit without changing it, when I click on any of the
https://bugs.kde.org/show_bug.cgi?id=500423
Bug ID: 500423
Summary: Google Maps API KEY not retained after restart
Classification: Applications
Product: digikam
Version: 8.5.0
Platform: Ubuntu
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=426000
--- Comment #15 from herb ---
Hello Maik,
thanks for your suggestion.
Please be aware that digiKam is the only metadata system (I know) that tries to
follow EXIF-standrad to 100%.
I think it is not necessary to show a special flag for UTF8-strings
https://bugs.kde.org/show_bug.cgi?id=454541
--- Comment #3 from herb ---
Hello Maik,
thanks for your quick reply.
Of course will branches 7.7.0 and 8.0.0. differ.
You wrote: The problem seems to be that the translation is parsed from
git/master.
Could you really do a test, that digiKam 8.0.0
https://bugs.kde.org/show_bug.cgi?id=454541
--- Comment #1 from herb ---
Created attachment 149297
--> https://bugs.kde.org/attachment.cgi?id=149297&action=edit
Screenshot Batch-Queue Manager
Attached please find another screenshot.
--
You are receiving this mail because:
You are w
rmat
#| msgid "A tool to add a border around images"
msgctxt "@info"
msgid "A tool to add a border around images"
msgstr "Ein Werkzeug zum Hinzufügen eines Rahmens"
Sorry for that long post; but to write "something is not translated" will not
help to find the problem.
Thanks in advance for your help.
Best regards
herb
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=426000
--- Comment #13 from herb ---
Dear developers,
please allow UTF-8 strings inside EXIF metadata. I repeat my request from
August 2020.
Also IPTC.org does request this feature. Please read IPTC Photo Metadata
Mapping Guidelines (version 2022.1, 2022-05
https://bugs.kde.org/show_bug.cgi?id=453888
--- Comment #6 from herb ---
Hello,
thanks both for your investigations.
Maik Qualmann wrote:
---
Hmm, the problem is that IntellectualGenre is not output as a list but as 2
separate strings. This will overwrite Genre1 with Genre2 in digiKam. The
https://bugs.kde.org/show_bug.cgi?id=453888
--- Comment #2 from herb ---
Hello Gilles,
thanks for your qucik reply.
Yes I sent it to Maik and after your reply also to you.
Best regards
herb
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370192
--- Comment #1 from herb ---
Dear developers,
I am still convinced that my 2 request (for digiKam 5.2.0) will be great
features for digiKam version 7.7.0 or maybe 8.0.0
To handle > 135 language signs is very annoying and the missing support
testfile to Maik Qualmann.
Thanks in advance
herb
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=435414
--- Comment #5 from herb ---
Hello Maik,
thanks for your reply.
It is really a good news that using Exiftool will solve the "Non standard
format" problem, which occurs in case of re-writing Exif-tags.
But I have an additional question
https://bugs.kde.org/show_bug.cgi?id=435414
--- Comment #3 from herb ---
Dear digiKam developers,
in meantime I started to work with digiKam 7.7.0 (snapshot 13.5.2022) on my
Windows 10 system.
As I wrote in 1st post:
---
Selecting an image e.g. in Albums-view and opening the Edit metadata
not only parts of character E
Best regards
herb
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=446528
--- Comment #7 from herb ---
Hello,
Thanks for this correction.
Best regards
herb
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=446528
--- Comment #5 from herb ---
Hello,
thanks for your comments. But sorry Sir, I do not fully agree:
"No Filter" is all tags to be displayed.
"Photograph" is an internally defined filter.
"Custom" is an user-defined filte
https://bugs.kde.org/show_bug.cgi?id=446528
--- Comment #3 from herb ---
Hello,
thanks for your quick replies.
I think the goal I want to reach is misunderstood.
For me it confuses the user
- when "Custom" filter is selected - but NO tag is assigned in settings
- and ALL metadata are
https://bugs.kde.org/show_bug.cgi?id=446528
Bug ID: 446528
Summary: Metadata filter in metadata tab
Product: digikam
Version: 7.4.0
Platform: Other
OS: Microsoft Windows
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=440012
Bug ID: 440012
Summary: Should digiKam think about Media Topics
Product: digikam
Version: 7.4.0
Platform: Other
OS: Other
Status: REPORTED
Severity: wishlist
https://bugs.kde.org/show_bug.cgi?id=439839
Bug ID: 439839
Summary: GPS-Correlator - not translatabke strings
Product: digikam
Version: 7.3.0
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=439486
--- Comment #15 from herb ---
Hello,
thanks for your comment.
(In reply to Maik Qualmann from comment #14)
> So left sidebar labels or in the DLN album / label selection.
> At the moment I am considering whether
> these strings can also be i
https://bugs.kde.org/show_bug.cgi?id=439486
--- Comment #13 from herb ---
Hello,
Sorry that I come back again with questions, but I need a private lession to
following entries in digikam.po (point 3 in description)
core/libs/album/treeview/albumlabelssearchhandler.cpp
msgctxt "
https://bugs.kde.org/show_bug.cgi?id=439486
--- Comment #12 from herb ---
Hello,
Thanks for your great help.
Things are now much clearer to me.
Best regards
herb
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=439486
--- Comment #9 from herb ---
Hello,
thank you very much for the detailed help. Great!
But in comment 4 Gilles wrote
1) in XMP metadata view through a dedicated ImageMagick namespace.
This made me more curious than I was before.
I never heard about
https://bugs.kde.org/show_bug.cgi?id=439486
--- Comment #2 from herb ---
Hello,
thanks for your comments.
But please allow a curious user to ask for some more details:
(1) I played with ImageMagick identify; but where (in which panel) and when are
these metadata shown to user?
(2) Did I
on.
All these descriptions are translatable.
But for plugin GmicQT I did not find an entry in digikam.po file.
Is this correct?
Thanks in advance for answering all my questions!
Best regards
herb
STEPS TO REPRODUCE
1.
2.
3.
OBSERVED RESULT
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Windows:
ma
https://bugs.kde.org/show_bug.cgi?id=439443
Bug ID: 439443
Summary: Import - DeviceSettings
Product: digikam
Version: 7.3.0
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severity: wish
https://bugs.kde.org/show_bug.cgi?id=439436
Bug ID: 439436
Summary: problems with video-slideschow
Product: digikam
Version: 7.3.0
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severit
https://bugs.kde.org/show_bug.cgi?id=439231
--- Comment #4 from herb ---
Created attachment 139713
--> https://bugs.kde.org/attachment.cgi?id=139713&action=edit
debugview for this problem
Hello,
thanks for your investigations.
I repeated the test with debug-version from 25.6.2021.
A
https://bugs.kde.org/show_bug.cgi?id=439231
Bug ID: 439231
Summary: ExifTool and e.g. *.psd images
Product: digikam
Version: 7.3.0
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severit
https://bugs.kde.org/show_bug.cgi?id=439059
--- Comment #2 from herb ---
Hello,
yes I see; the output in Exiftool tab is grouped.
With mouse hovering over such a header one of the "exiftoollistviewgroup"
strings is displayed.
Thanks for your help.
Best regards
herb
--
You are rece
https://bugs.kde.org/show_bug.cgi?id=439059
Bug ID: 439059
Summary: "exiftoollistviewgroup"
Product: digikam
Version: 7.3.0
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severity: wish
https://bugs.kde.org/show_bug.cgi?id=439057
Bug ID: 439057
Summary: output of Exiftool data
Product: digikam
Version: 7.3.0
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severity: norm
https://bugs.kde.org/show_bug.cgi?id=43
--- Comment #21 from herb ---
(In reply to caulier.gilles from comment #20)
> >I guess option -charset iptc=utf8 is missing in the command you used.
>
> This will work in your case as you know that your IPTC is UFT8 encoded.
>
> B
https://bugs.kde.org/show_bug.cgi?id=43
--- Comment #19 from herb ---
Hello Maik,
Thanks to all for the investigations.
Of course it was tagged with an older version of Exiftool. It was done about 1
year ago. But I never heard that I used a faulty Exiftool.
In your output I see only IPTC
https://bugs.kde.org/show_bug.cgi?id=43
--- Comment #16 from herb ---
Hello,
a comment to your comment 10:
JSON container is generated by ExifTool. So i guest this point is already
handle by ExifTool as well...
That is not always true. Depending on the options/parameters you send to
https://bugs.kde.org/show_bug.cgi?id=43
--- Comment #15 from herb ---
Hello,
@ Gilles:
You wrote: In your test image shared by private email, IPTC miss char encoding
tag as something like that: IPTC:CodedCharacterSet=utf8
As far as I know this tag is not mandatory.
@ Maik:
To write tags
https://bugs.kde.org/show_bug.cgi?id=43
--- Comment #9 from herb ---
Hello,
here a comment to Comment 1:
You wrote:
ExifTool report information by a JSON container to the metadata view.
Typically, data are encoded to UTF8 by default, as we can read in the
documentation.
As all Exif tag
https://bugs.kde.org/show_bug.cgi?id=43
--- Comment #8 from herb ---
Hello,
thanks to all for your investigations.
Please let me answer your question of comment 6 first
with an example of Exiftool output (in German)
Tagunconverted converted
LensID
https://bugs.kde.org/show_bug.cgi?id=43
Bug ID: 43
Summary: Exiftool - non ASCII characters
Product: digikam
Version: 7.3.0
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severi
https://bugs.kde.org/show_bug.cgi?id=438856
Bug ID: 438856
Summary: ShowFoto - DNG-Converter II
Product: digikam
Version: 7.3.0
Platform: Other
OS: Other
Status: REPORTED
Severity: normal
Prior
https://bugs.kde.org/show_bug.cgi?id=438855
Bug ID: 438855
Summary: ShowFoto - DNG-Converter I
Product: digikam
Version: 7.3.0
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severity:
https://bugs.kde.org/show_bug.cgi?id=438466
--- Comment #5 from herb ---
Created attachment 139247
--> https://bugs.kde.org/attachment.cgi?id=139247&action=edit
digikamrc file causes problems with "Color Negativ" tool
Hello,
thanks both for your investigations.
As both
https://bugs.kde.org/show_bug.cgi?id=438466
--- Comment #2 from herb ---
Hello Maik,
thanks for your response.
Yes you are right, the settings for Color Negativ are displayed on the right
side.
Inside the histogram field the "rotating circle" can be seen for short.
Then editor
https://bugs.kde.org/show_bug.cgi?id=438466
Bug ID: 438466
Summary: Image editor - Color Negative closes application
Product: digikam
Version: 7.3.0
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=438465
Bug ID: 438465
Summary: Question to Color Spaces
Product: digikam
Version: 7.3.0
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severity: nor
https://bugs.kde.org/show_bug.cgi?id=438344
Bug ID: 438344
Summary: Questions to Add Border Tool
Product: digikam
Version: 7.3.0
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severity:
https://bugs.kde.org/show_bug.cgi?id=436587
--- Comment #18 from herb ---
Hello Maik,
thanks for this hint.
Best regards
herb
--
You are receiving this mail because:
You are watching all bug changes.
would be - as far as I suggest - a good
solution.
(Maybe you have a better one)
Thanks in advance
herb
STEPS TO REPRODUCE
1.
2.
3.
OBSERVED RESULT
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Vers
https://bugs.kde.org/show_bug.cgi?id=437658
Bug ID: 437658
Summary: crash on windows without OpenGL
Product: digikam
Version: 7.3.0
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severi
https://bugs.kde.org/show_bug.cgi?id=437657
Bug ID: 437657
Summary: size of dialog for database migration
Product: digikam
Version: 7.3.0
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=437655
Bug ID: 437655
Summary: Store fuzzy search without a name
Product: digikam
Version: 7.3.0
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Seve
https://bugs.kde.org/show_bug.cgi?id=436587
--- Comment #16 from herb ---
Hello Maik,
Sorry for my late reply. You asked:
Are you in contact with the German translator team?
Yes, Burkhard Lück asked me to help "translating" digiKam; and I sayed: yes
Best regards
herb
--
You are
https://bugs.kde.org/show_bug.cgi?id=436587
--- Comment #10 from herb ---
Hello Maik,
yes, you are right.
And also a translation of {State} into German is available in digikam.po/.mo
file.
Nevertheless always the Englsh string is displayed.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=436587
--- Comment #8 from herb ---
Hello Maik,
sorry to annoy you again.
But the string(s)
(1) {state} is still not translated inside a German GUI, although it has
a translation in digikam.po file
(2) Interpolate and Match directly cannot be found in
https://bugs.kde.org/show_bug.cgi?id=436299
--- Comment #25 from herb ---
Hello Maik,
thanks again for your investigations and corrections.
I am sorry, but still not all buttons behave as expected.
With digiKam snapshot from 19.5.2021 I did a short test and have seen that with
digikam-language
ata in xmp-video namespace.
I have never heard about this namespace; also Exiftool does not know about.
Can someone help and give some documentation about this namespace and which
fields belong to it.
Thanks in advance
herb
STEPS TO REPRODUCE
1.
2.
3.
OBSERVED RESULT
EXPECTED RESULT
S
https://bugs.kde.org/show_bug.cgi?id=436299
--- Comment #22 from herb ---
Created attachment 138476
--> https://bugs.kde.org/attachment.cgi?id=138476&action=edit
debug output of deigiKam start after language change
Hello Maik,
thanks for your answer.
I am working on Windows 10 sy
https://bugs.kde.org/show_bug.cgi?id=436299
--- Comment #20 from herb ---
Hello,
thanks for your investigations.
But please allow an additional question:
- Is the language of the button-texts the language of the PC-system
(in my case German) or
- is it the language assigned tp digiKam using
https://bugs.kde.org/show_bug.cgi?id=437033
Bug ID: 437033
Summary: HTML tags instead of clickable link
Product: digikam
Version: 7.3.0
Platform: Other
OS: Other
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=436979
--- Comment #5 from herb ---
(In reply to Maik Qualmann from comment #3)
> However, if the tag is a face tag, a Microsoft Photo 1.2 scheme is written.
> We discussed this ...
Yes, that could be ok.
But in my case, NO facetag exists for the
https://bugs.kde.org/show_bug.cgi?id=436977
--- Comment #5 from herb ---
Hello Maik,
thanks for all the details. Very very helpful.
Best regards
herb
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=436979
--- Comment #2 from herb ---
Hello Maik,
thanks for your investigations.
I agree that all regions are written correctly.
I regret, that I was not detailed enough; but I thought it is clear because of
my hint with error 435340.
The problem is the
https://bugs.kde.org/show_bug.cgi?id=436975
--- Comment #3 from herb ---
Created attachment 138368
--> https://bugs.kde.org/attachment.cgi?id=138368&action=edit
Result of advanced search #2
Then I opened again the advanced search dialog.
Without doing any changes I started the searc
https://bugs.kde.org/show_bug.cgi?id=436975
--- Comment #2 from herb ---
Created attachment 138367
--> https://bugs.kde.org/attachment.cgi?id=138367&action=edit
Result of Advanced Saerch #1
Hello,
thanks for your response.
I will show the behaviour with 2 screenshots.
I started an a
https://bugs.kde.org/show_bug.cgi?id=436977
--- Comment #2 from herb ---
Created attachment 138366
--> https://bugs.kde.org/attachment.cgi?id=138366&action=edit
screenshot AdvancedSearch
Hello,
thanks for your response.
I guess the best is to give a screenshot.
For me the "
https://bugs.kde.org/show_bug.cgi?id=436979
Bug ID: 436979
Summary: Empty regions
Product: digikam
Version: 7.3.0
Platform: Other
OS: Other
Status: REPORTED
Severity: normal
Priority: NOR
https://bugs.kde.org/show_bug.cgi?id=436977
Bug ID: 436977
Summary: Field "Options" too small
Product: digikam
Version: 7.3.0
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severity: wi
https://bugs.kde.org/show_bug.cgi?id=436975
herb changed:
What|Removed |Added
Platform|Other |Microsoft Windows
OS|Other
https://bugs.kde.org/show_bug.cgi?id=436975
Bug ID: 436975
Summary: Advanced search - right panel is disabled
Product: digikam
Version: 7.3.0
Platform: Other
OS: Other
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=436261
--- Comment #2 from herb ---
Hello,
This comment is only to inform you that IPTC Genre-Codes have been changed on
28.April 2021.
Please see https://cv.iptc.org/newscodes/genre
Thanks nd best regards
herb
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=436758
Bug ID: 436758
Summary: Question to date-format of import images
Product: digikam
Version: 7.3.0
Platform: Other
OS: Other
Status: REPORTED
Severity: minor
https://bugs.kde.org/show_bug.cgi?id=436587
--- Comment #6 from herb ---
Hello Maik,
thanks for your comments.
When we call right mouse "Add all address elements" a hierarchy of 12
"pseudo-tags" is created.
Most of them can be translated: e.g. {City} --> {Stadt} or {Coun
https://bugs.kde.org/show_bug.cgi?id=436587
herb changed:
What|Removed |Added
Resolution|DUPLICATE |---
Ever confirmed|0 |1
tab Undo/Redo:
They have no entry in digikam.po file (generated on 30.4.2021)
Please help
Thanks in advance
herb
STEPS TO REPRODUCE
1.
2.
3.
OBSERVED RESULT
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
K
https://bugs.kde.org/show_bug.cgi?id=436586
Bug ID: 436586
Summary: Voreinstellung in Settings --> Configure Language
Product: digikam
Version: 7.3.0
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTE
format
msgctxt "@title:tab"
msgid "Behavior"
msgstr "Verhalten"
(2)
#: core/utilities/setup/setupicc.cpp:514
#, kde-format
msgctxt "@title: icc panel tab"
msgid "Behavior"
msgstr "Verhalten"
But in the above mentioned dialog still &q
https://bugs.kde.org/show_bug.cgi?id=436487
--- Comment #3 from herb ---
(In reply to herb from comment #2)
> Hello Maik,
>
> thanks for your comments.
>
> The main goal of the report is to avoid that strings like "4:" or "004:" are
> stored inside the im
https://bugs.kde.org/show_bug.cgi?id=436487
--- Comment #2 from herb ---
Hello Maik,
thanks for your comments.
The main goal of the report is to avoid that strings like "4:" or "004:" are
stored inside the image.
ad:
I don't think it would be common practice to in
splayed
(3) Layout of field Edit IPTC - Properties - Attribute
Please shorten the width of the dropdown box and enlarge the area (on right
side) for the list-elements
Thanks in advance
Best regards
herb
STEPS TO REPRODUCE
1.
2.
3.
OBSERVED RESULT
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Windo
en I open the above
mentioned dialog.
Is this by design, that I have to delete e.g "Friends" and to add "Freunde", in
order to get a German category-name?
Or is it an error?
Thanks in advance for your help
herb
STEPS TO REPRODUCE
1.
2.
3.
OBSERVED RESULT
EXPECTED RESULT
Back - Next - Cancel
Über
I asked on the mailing-list of German translators what must be done in order to
get proper German strings.
The answer was:
- maybe it is a Windows specific problem or
- a problem with installation medium
Thanks for your hel
t;Attribute".
(2) The current IPTC list at http://cv.iptc.org/newscodes/genre contains 47
elements, but digiKam has only 22.
Best regards
herb
STEPS TO REPRODUCE
1.
2.
3.
OBSERVED RESULT
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
(available in Abou
https://bugs.kde.org/show_bug.cgi?id=435884
herb changed:
What|Removed |Added
Summary|"1Vollbildmodus" is used|"Vollbildmodus" is used
s it a not translatable string?
Or what did I wrong?
Best regards
herb
STEPS TO REPRODUCE
1.
2.
3.
OBSERVED RESULT
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDIT
https://bugs.kde.org/show_bug.cgi?id=435879
--- Comment #6 from herb ---
Hello Maik,
again a collision problem.
In case of you cannot change the text of the first context-element,
what about to start the tool itself
Thanks
herb
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=435879
--- Comment #5 from herb ---
Hello Maik,
as we entered our comments at the same time I repeat
- the problem is not the "checkbox" or the "button" in front of the context
element with name of the tool.
- For me the problem is
https://bugs.kde.org/show_bug.cgi?id=435879
herb changed:
What|Removed |Added
Version Fixed In|7.3.0 |
Platform|Other
xt" or
"Show text" should be used.
On the other hand for me it does not make sense to have a mix inside the
toolbar: some (not all) elements with icons only and some with icons and text.
Best regards
herb
STEPS TO REPRODUCE
1.
2.
3.
OBSERVED RESULT
EXPECTED RESULT
SOFTWARE
tart.
But for showFoto I did not find such a menu.
Please make language of showFoto also selectable.
Thanks in advance
herb
STEPS TO REPRODUCE
1.
2.
3.
OBSERVED RESULT
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma V
https://bugs.kde.org/show_bug.cgi?id=435609
--- Comment #2 from herb ---
Hallo,
ich kann nur sagen, dass in allen Bedienungsanleitungen RAW (3 Großbuchstaben)
verwendet wird.
Die Großschreibweise deutet auch darauf hin, dass es sich "etwas, wie einen
Eigennamen" handelt.
Mfg
herb
-
After converting from a RAW image --> Nach Konvertierung des RAW-Formates
(3)
Vielleicht sollte auch der zu übersetzende Originaltext angepasst werden:
- RAW-Camera --> Camera with RAW-File support
Camera with RAW-Image support
Vielen Dank im Voraus
Mfg
herb
STEPS T
https://bugs.kde.org/show_bug.cgi?id=435540
--- Comment #2 from herb ---
Hallo,
vielen Dank für den Kommentar.
Welche Wortwahl ist in den Programmen so üblich:
- Windows 10:
In den Kontextmenüs heißt es "Löschen".
Dann kommt die Frage, ob man die Datei tatsächlich in den
m - in den Papierkorb verschieben - halte ich für die besserer
Übersetzung, die überall verwendet werden sollte.
MfG
herb
STEPS TO REPRODUCE
1.
2.
3.
OBSERVED RESULT
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Ver
hanks in advance and
best regards
herb
STEPS TO REPRODUCE
1.
2.
3.
OBSERVED RESULT
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
--
You are receiving th
https://bugs.kde.org/show_bug.cgi?id=435476
Bug ID: 435476
Summary: Wrong term "Comments" in Edit Metadata dialog
Product: digikam
Version: 7.2.0
Platform: Other
OS: Other
Status: REPORTED
Severity: normal
1 - 100 of 132 matches
Mail list logo
