[i18n] [Bug 490004] Some translations are not used
https://bugs.kde.org/show_bug.cgi?id=490004 --- Comment #1 from Shinjo Park --- Given that the plasma_applet_org.kde.plasma.digitalclock.po is fully translated and this problem did not existed in Plasma 5, I think that this is the problem of Qt 6's missing translation. -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 424024] Main window doesn't repaint correctly on Wayland
https://bugs.kde.org/show_bug.cgi?id=424024 Shinjo Park changed: What|Removed |Added CC||k...@peremen.name --- Comment #32 from Shinjo Park --- I just found that on Kubuntu 22.10 the XCB workaround is also completely broken, just making the file tab all black. Wayland problem is still present. (In reply to David Edmundson from comment #5) > I'm debugging blind a bit, but it seems we have multiple TMTab objects that > (indirectly) inherit from KMainWindow despite being children. I think you are right, see https://invent.kde.org/sdk/lokalize/-/blob/master/DESIGN: > Tabs are KMainWindows + KXmlGuiCleints. Given that workarounds are not really working, I guess the application code should be modified. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 463848] KDE Text Encoding for Korean (applies to KWrite and SubtitleComposer in Flatpaks)
https://bugs.kde.org/show_bug.cgi?id=463848 --- Comment #2 from Shinjo Park --- As I didn't stored any Korean text in CP949 and made everything UTF-8 since decades ago, even I was not fully aware of the situation... > This price was worth it to ensure that a typo character (`낥` instead of `날`) > would not be lost. Not only for typo or character in composition, but also for some proper names and newly invented words. > It only knows "ms949", "windows-949", and "windows-949-2000", which seem to > all refer to the same codec? According to https://icu4c-demos.unicode.org/icu-bin/convexp?conv=windows-949 it seems true. To make thing more worse, one of the alias (KSC_5601) is shared between CP949 and EUC-KR internally in ICU (see https://icu4c-demos.unicode.org/icu-bin/convexp?conv=euc-kr). As CP949 is a superset of EUC-KR, most Korean implementations interchangeably use them, this is somewhat reflected even in the WHATWG (https://encoding.spec.whatwg.org/#names-and-labels). So I think it is just a matter of naming. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 453705] self signed certificate SMTP
https://bugs.kde.org/show_bug.cgi?id=453705 Shinjo Park changed: What|Removed |Added CC||k...@peremen.name --- Comment #1 from Shinjo Park --- Can confirm this. At least Thunderbird allows accepting this use case. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 387618] words less than 3 letters are ignored
https://bugs.kde.org/show_bug.cgi?id=387618 Shinjo Park changed: What|Removed |Added CC||pikakolend...@gmail.com --- Comment #15 from Shinjo Park --- *** Bug 454696 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 454696] Two Chinese characters will be ignored in searching box
https://bugs.kde.org/show_bug.cgi?id=454696 Shinjo Park changed: What|Removed |Added Status|REPORTED|RESOLVED CC||k...@peremen.name Resolution|--- |DUPLICATE --- Comment #1 from Shinjo Park --- *** This bug has been marked as a duplicate of bug 387618 *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 432699] Effects list's filter field does not work for CJK characters
https://bugs.kde.org/show_bug.cgi?id=432699 Shinjo Park changed: What|Removed |Added CC||k...@peremen.name --- Comment #9 from Shinjo Park --- Can confirm also in Korean language too. Some effect names are translated as of 21.12.3, but searching using translation does not work. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 452330] appstreamcli validate complains about ksame's appstream file (klickety)(edit)
https://bugs.kde.org/show_bug.cgi?id=452330 --- Comment #2 from Shinjo Park --- Trailing dot is now gone, please reopen if problem persists. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 445534] New: Code blocks on website are not visible in dark mode theme
https://bugs.kde.org/show_bug.cgi?id=445534 Bug ID: 445534 Summary: Code blocks on website are not visible in dark mode theme Product: www.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-...@kde.org Reporter: k...@peremen.name Target Milestone: --- SUMMARY When a dark mode theme is enabled in mobile web browser, it is not possible to read code blocks embedded in https://plasma-bigscreen.org/ko/faq/ page. Might be applicable also in other websites. STEPS TO REPRODUCE 1. Set the browser or system to use dark mode. 2. Browse https://plasma-bigscreen.org/faq/ 3. See the code blocks. OBSERVED RESULT Code blocks are not readable as the texts are in white. EXPECTED RESULT Code blocks should be readable. SOFTWARE/OS VERSIONS Tested with Safari on iOS, Firefox on Android. Not sure about desktop browsers. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 443767] [Request] Add new functionality to make the (sub)title spread vertically
https://bugs.kde.org/show_bug.cgi?id=443767 Shinjo Park changed: What|Removed |Added CC||k...@peremen.name --- Comment #1 from Shinjo Park --- Just FYI: when it comes to video subtitles Korean is mostly written in horizontal. Just grab some YouTube videos and you will never see anything written in vertical. Subtitles in cinema is probably the last thing written in vertical, which is also moving to horizontal nowadays. I am not objecting in this feature request as vertical writing could be also used for retro theming for Korean language, but it is not frequently used as Chinese and Japanese. The linked two videos are Chinese (not sure about simplified or traditional) and Japanese respectively. -- You are receiving this mail because: You are watching all bug changes.
[Spam] [Bug 445313] preethi
https://bugs.kde.org/show_bug.cgi?id=445313 Shinjo Park changed: What|Removed |Added CC||k...@peremen.name Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 444032] Ark zstd tarball compress failed due to non-ascii character in filenames
https://bugs.kde.org/show_bug.cgi?id=444032 Shinjo Park changed: What|Removed |Added CC||k...@peremen.name --- Comment #2 from Shinjo Park --- Works for me in Korean. Could you please provide more details on your system? You haven't provided any of the "Software/OS Versions". -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 442572] Chinese l10n problem in check printing
https://bugs.kde.org/show_bug.cgi?id=442572 --- Comment #4 from Shinjo Park --- (In reply to Alvin Wong from comment #3) > I believe the numbering rules between Chinese, Japanese and Korean are quite > similar, but there may be some subtle differences with the handling of zeros > and ones. True, we don't explicitly mention zero and one in colloquial speech but ones are expllicitly mentioned in financial speech in Korean. That's why I only suppress zeroes at https://websvn.kde.org/trunk/l10n-kf5/ko/scripts/kmymoney/kmymoney.js?view=markup (line 19 to 28) and explicitly include ones. > Side note: In Hong Kong it is rather common for us to write cheques with the > amount in English, so I would hope that KMyMoney will not force the use of > Chinese numbers when the interface language is set to Chinese Traditional > (zh_TW). (But to clarify, I don't use KMyMoney so I may be missing some > context.) That's another good point... Do we support issuing cheques in different language from the current $LANG? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 442572] Chinese l10n problem in check printing
https://bugs.kde.org/show_bug.cgi?id=442572 Shinjo Park changed: What|Removed |Added CC||k...@peremen.name --- Comment #2 from Shinjo Park --- We had a similar problem in Korean too, so that's why this exist: https://invent.kde.org/office/kmymoney/-/blob/2257a1e2f9837fa23b3ac4550fb422307cada5a6/kmymoney/plugins/checkprinting/numbertowords.cpp#L79 Instead of coding numerals for every language, it is possible to write a Javascript logic for translating them. The JS function should take numbers as input and should produce a proper translation. See also: https://techbase.kde.org/Localization/Concepts/Transcript and bug 420321 -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 439343] New: "Make Confidential" blurs extra area in non-rectangular selection
https://bugs.kde.org/show_bug.cgi?id=439343 Bug ID: 439343 Summary: "Make Confidential" blurs extra area in non-rectangular selection Product: kolourpaint Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kolourpaint-supp...@lists.sourceforge.net Reporter: k...@peremen.name Target Milestone: --- Created attachment 139764 --> https://bugs.kde.org/attachment.cgi?id=139764&action=edit Circular selection of profile images on KDE Community Twitter and performed "Make Confidential". The blur is not limited to the circular area, but extends to the bounding rectangle. SUMMARY If I make a circular selection and perform "Make Confidential" action, it adds a blur not only inside a circular selection, but also along to the inner borders of a circular selection. I tried to use this feature to blur out the circular profile pictures and names from the screenshot of e.g. Facebook and Twitter, but I am also seeing the blur outside of the circle which is not quite optimal. STEPS TO REPRODUCE 1. Make a circular or freehand selection. 2. Apply "Make Confidential". OBSERVED RESULT Blur applied also outside of the circular/freehand area of selection, extending to the bounding rectangle of circle/freeform. EXPECTED RESULT Blur only applied within the circular/freehand area of selection. Attached image is KDE Community Twitter capture, and tried to blur out profile pictures by making a circular selection and "Make Confidential". Note that the original profile picture is circular, after "Make Confidential" a rectangular area around the circle got blurred. SOFTWARE/OS VERSIONS Kolourpaint from git master KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 432882] Improve Font settings for CJK users under Windows
https://bugs.kde.org/show_bug.cgi?id=432882 --- Comment #11 from Shinjo Park --- (In reply to Shinjo Park from comment #10) > Created attachment 139545 [details] > Korean default font Not mentioned in comment #7 is Korean font, which is also different from Chinese/Japanese. Krita is using Gulim/굴림 for all UI elements on Windows, which used to be default up till Windows XP, replaced by Malgun Gothic/맑은 고딕 starting from Windows Vista. The desktop and taskbar contains text in Malgun Gothic, looking differently from what is inside Krita. The glyph inside the menu bar is coming from the bitmap of Gulim 8pt, which is considered smaller than what Korean users expected even back then (Gulim 9pt). Docker texts are even smaller than that. I don't have Mac by myself, so I am not 100% sure of the font situation there. (In reply to Tyson Tan from comment #8) > 4) Let the translator to assign a default font list and font sizes. As far as I know Qt's default fonts are suboptimal for CJK. In fact, Telegram Desktop had the similar problem regarding font selection. They maintain their own patches for Qt 5.12/5.15. Github issue: https://github.com/telegramdesktop/tdesktop/issues/7773 Patch itself: https://github.com/desktop-app/patches/blob/master/qtbase_5_15_2/0005-fix-cjk-font-fallback.patch -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 432882] Improve Font settings for CJK users under Windows
https://bugs.kde.org/show_bug.cgi?id=432882 Shinjo Park changed: What|Removed |Added CC||k...@peremen.name --- Comment #10 from Shinjo Park --- Created attachment 139545 --> https://bugs.kde.org/attachment.cgi?id=139545&action=edit Korean default font -- You are receiving this mail because: You are watching all bug changes.
[Mangonel] [Bug 438166] New: Mangonel fails to launch under Wayland
https://bugs.kde.org/show_bug.cgi?id=438166 Bug ID: 438166 Summary: Mangonel fails to launch under Wayland Product: Mangonel Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: mangonel Assignee: martin.sandsm...@kde.org Reporter: k...@peremen.name Target Milestone: --- SUMMARY Mangonel will segfault when launched in Plasma/Wayland. STEPS TO REPRODUCE 1. Start Plasma/Wayland 2. Launch Mangonel 3. Segfault OBSERVED RESULT Application: Mangonel (mangonel), signal: Segmentation fault [KCrash Handler] #4 0x7f8ebaa6d6f4 in XkbUseExtension (dpy=0x5595d65e03b0, major_rtrn=0x0, minor_rtrn=0x0) at xkb/../../../src/xkb/XKBUse.c:653 #5 0x7f8ebaa65fdc in _XkbLoadDpy (dpy=0x5595d65e03b0) at xkb/../../../src/xkb/XKBBind.c:527 #6 XKeysymToKeycode (dpy=0x5595d65e03b0, ks=32) at xkb/../../../src/xkb/XKBBind.c:157 #7 0x5595d5f0e90c in QGlobalShortcut::toNativeKeycode (k=Qt::Key_Space) at /home/psj/dev/kde-devel/src/mangonel/globalshortcut/qglobalshortcut_x11.cpp:110 #8 0x5595d5f0cfa1 in QGlobalShortcut::calcId (keyseq=...) at /home/psj/dev/kde-devel/src/mangonel/globalshortcut/qglobalshortcut.cpp:76 #9 0x5595d5f0ccd8 in QGlobalShortcut::setKey (this=0x5595d6600150, keyseq=...) at /home/psj/dev/kde-devel/src/mangonel/globalshortcut/qglobalshortcut.cpp:44 #10 0x5595d5f0cb55 in QGlobalShortcut::QGlobalShortcut (this=0x5595d6600150, keyseq=..., parent=0x5595d5f4a240 ) at /home/psj/dev/kde-devel/src/mangonel/globalshortcut/qglobalshortcut.cpp:19 #11 0x5595d5e60279 in Mangonel::Mangonel (this=0x5595d5f4a240 ) at /home/psj/dev/kde-devel/src/mangonel/Mangonel.cpp:127 #12 0x5595d5e617ac in Mangonel::instance () at /home/psj/dev/kde-devel/src/mangonel/Mangonel.cpp:192 #13 0x5595d5e69ce1 in main (argc=1, argv=0x7ffcd30f9b98) at /home/psj/dev/kde-devel/src/mangonel/main.cpp:57 [Inferior 1 (process 478864) detached] Setting QT_QPA_PLATFORM=xcb makes Mangonel to at least launch but the global shortcut does not work. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.21.4 KDE Frameworks Version: git master Qt Version: 5.15.2 on Kubuntu 21.04 ADDITIONAL INFORMATION Mangonel built using kdesrc-build. -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 404918] Hangul is not input.
https://bugs.kde.org/show_bug.cgi?id=404918 Shinjo Park changed: What|Removed |Added CC||k...@peremen.name --- Comment #1 from Shinjo Park --- I would suggest to prioritize this bug as WISHLIST at this moment, as 1) current KTouch seems not aware of any QT_IM_MODULE and 2) proper support of Korean layout will require certain amount of work which requires Korean speakers. I can come up with Korean keyboard layouts, but that will be just a starting point. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408662] Proper time formatting for locales where AMPM is going in front of time value
https://bugs.kde.org/show_bug.cgi?id=408662 --- Comment #2 from Shinjo Park --- (In reply to momo from comment #1) > Hello Shinjo. Do you know if there's a resource that lists locales that show > AM/PM this way? I've been looking at CLDR > (http://cldr.unicode.org/translation/date-time-1/date-time-patterns) but I > cannot find data about the AM/PM order. "hour minute" of the CLDR Date/Time Chart [1] or "hm"/"hms" formatting of "Date & Time" should be suffice. [1] https://unicode-org.github.io/cldr-staging/charts/latest/verify/dates/ko.html [2] https://st.unicode.org/cldr-apps/v#/ko/Gregorian/6cdad6946fa0fe82 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433297] Locale-aware/romanized alphabetic categories for when using a language with a non-Latin alphabet
https://bugs.kde.org/show_bug.cgi?id=433297 Shinjo Park changed: What|Removed |Added CC||k...@peremen.name --- Comment #7 from Shinjo Park --- Okay, confirmed the same issue for Korean. However we have DIFFERENT requirement from Chinese. What I am seeing currently: 도 * 도움말 (Help Center) 둘 * 둘러보기 (Discover) 시 * 시스템 모니터 (System Monitor) * 시스템 설정 (System Settings) 에 * 에모지 선택기 (Emoji Selector) 와 * 와콤 태블릿 찾기 (Find Wacom Tablets) 정 * 정보 센터 (Information Center) What I would expect: ㄷ * 도움말 * 둘러보기 ㅅ * 시스템 모니터 * 시스템 설정 ㅇ * 에모지 선택기 * 와콤 태블릿 찾기 ㅈ * 정보 센터 Difference is it is grouped by the initial of each Hangul character. As far as I know the contact grid of Sailfish OS does the right job for Korean: Decompose the composed letters in NFD, categorize with the first character of decomposed unicode code point sequence. See also: https://git.sailfishos.org/mer-core/nemo-qml-plugin-contacts/blob/master/src/seasidefilteredmodel.cpp#L133 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdoctools] [Bug 407037] meinproc5 is not honoring Korean naming order (reversed surname/firstname)
https://bugs.kde.org/show_bug.cgi?id=407037 --- Comment #3 from Shinjo Park --- (In reply to Luigi Toscano from comment #2) > Does it work if you add a file called > /kf5/kdoctools/customization/xsl/ko.xsl with the > following content? > > http://docbook.sourceforge.net/xmlns/l10n/1.0";> > > > > > > > I tried that, but nope. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 426600] Hangul is not written in the title clip.
https://bugs.kde.org/show_bug.cgi?id=426600 --- Comment #6 from Shinjo Park --- If it is installed via AppImage then the root cause might be the same as #415420. Otherwise it would be different. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 426600] Hangul is not written in the title clip.
https://bugs.kde.org/show_bug.cgi?id=426600 Shinjo Park changed: What|Removed |Added CC||k...@peremen.name --- Comment #5 from Shinjo Park --- (In reply to 이야기 from comment #4) > (In reply to 2wxsy58236r3 from comment #3) > > Do you mean the user interface is no longer in Korean now? > > Hangul is not written in the title clip. How did you installed Kdenlive? AppImage or distro specific package? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 407386] Action shortcut default to "Alt+关" if not specified
https://bugs.kde.org/show_bug.cgi?id=407386 --- Comment #13 from Shinjo Park --- (In reply to Marco Martin from comment #9) > it also chooses the first available letter for those which don't have an &, > which is the same thing happening in qwidget applications when are running > under plasma This does not work at all in some languages, this is basically what the bug report is about. (In reply to Marco Martin from comment #6) > would be ok to restrict automatic shortcuts to standard latin? (then having > to explicitly set one with a non latin string which can have a shortcut) Yes please. Also when if translators need to manually set an accelerator or shortcut key, please clearly mark that cases so translators can take care of that. Currently in QWidget application, no accelerator key will be assigned if the translated string contains no latin-1 character. This is also far from ideal. I also wrote a report about that too: https://marc.info/?l=kde-frameworks-devel&m=158782004706664&w=2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 234407] systemsettings iconview wordwrapping cause narrow icon in zhcn locale
https://bugs.kde.org/show_bug.cgi?id=234407 Shinjo Park changed: What|Removed |Added CC||k...@peremen.name --- Comment #10 from Shinjo Park --- Is this bug still relevant? At least for Korean locale, the text width in System Settings' icon view is adequate in Plasma 5.18. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 420683] New: Inaccurate decimal precision of South Korean Won (KRW)
https://bugs.kde.org/show_bug.cgi?id=420683
Bug ID: 420683
Summary: Inaccurate decimal precision of South Korean Won (KRW)
Product: kmymoney
Version: git (master)
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kmymoney-de...@kde.org
Reporter: k...@peremen.name
Target Milestone: ---
SUMMARY
Currently in KMyMoney's currency setting, both "Smallest cash unit" and
"Smallest money unit" is set to KRW 0.01. However, in every Korean bank
statements and stock price tickers the price is always presented in the unit of
KRW 1 (no decimal points). Only in foreign exchange markets rates are announced
in the precision of KRW 0.01, and it is usually rounded down when it becomes to
accounting.
At kmymoney/kmymoney/mymoney/mymoneyfile.cpp:
currencyList.append(MyMoneySecurity("KRW", i18n("South Korean Won"),
QChar(0x20A9)));
This should be:
currencyList.append(MyMoneySecurity("KRW", i18n("South Korean Won"),
QChar(0x20A9), 1));
--
You are receiving this mail because:
You are watching all bug changes.
[kdenlive] [Bug 420494] Opening the archived project crashes
https://bugs.kde.org/show_bug.cgi?id=420494 --- Comment #2 from Shinjo Park --- Update: Could you please try opening the same file using Kdenlive 20.04? In 20.04 it says "Project file is corrupted (no tracks). Try to find a backup file?" and if I click on the Cancel nothing happens. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420494] Opening the archived project crashes
https://bugs.kde.org/show_bug.cgi?id=420494 Shinjo Park changed: What|Removed |Added CC||k...@peremen.name --- Comment #1 from Shinjo Park --- Some useful backtraces upon opening archived.kdenlive (in the attachment): #0 0x77403eac in QDomNamedNodeMapPrivate::clearMap() (this=0x5a0a2690) at /usr/include/c++/9/bits/atomic_base.h:326 #1 0x774041b3 in QDomNamedNodeMapPrivate::~QDomNamedNodeMapPrivate() (this=0x5a0a2690, __in_chrg=) at dom/qdom.cpp:3044 #2 QDomElementPrivate::~QDomElementPrivate() (this=0x5a094bb0, __in_chrg=) at dom/qdom.cpp:4423 #3 0x7740421d in QDomElementPrivate::~QDomElementPrivate() (this=0x5a094bb0, __in_chrg=) at dom/qdom.cpp:4420 #4 0x55b1b56f in QDomElement::~QDomElement() (this=0x7fffbfb8, __in_chrg=) at /usr/include/x86_64-linux-gnu/qt5/QtXml/qdom.h:471 #5 Xml::addXmlProperties(QDomElement&, QMap const&) (element=..., properties=...) at ./src/xml/xml.cpp:98 #6 0x55b1d4c0 in Xml::setXmlProperty(QDomElement, QString const&, QString const&) (element=..., propertyName=..., value=...) at ./src/xml/xml.cpp:133 #7 0x55b3e015 in DocumentValidator::upgrade(double, double) (this=this@entry=0x7fffc6d0, version=version@entry=0, currentVersion=currentVersion@entry=0.98999) at ./src/doc/documentvalidator.cpp:1941 #8 0x55b474e6 in DocumentValidator::validate(double) (this=this@entry=0x7fffc6d0, currentVersion=currentVersion@entry=0.98999) at ./src/doc/documentvalidator.cpp:226 #9 0x55870783 in KdenliveDoc::KdenliveDoc(QUrl const&, QString, QUndoGroup*, QString const&, QMap const&, QMap const&, QPoint const&, bool*, MainWindow*) (this=0x58d0f990, url=..., projectFolder=..., undoGroup=, profileName=..., properties=..., metadata=..., tracks=..., openBackup=0x7fffc86f, parent=0x561bcfb0) at ./src/doc/kdenlivedoc.cpp:221 The result of mainplaylist.toElement() is null, leading to this error. I can confirm this on Ubuntu 20.04 / Kdenlive 19.12.3. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 420488] New: Wrong accelerator and shortcut keys specified in Kirigami-based apps
https://bugs.kde.org/show_bug.cgi?id=420488 Bug ID: 420488 Summary: Wrong accelerator and shortcut keys specified in Kirigami-based apps Product: frameworks-kirigami Version: 5.68.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: k...@peremen.name Target Milestone: Not decided Created attachment 127813 --> https://bugs.kde.org/attachment.cgi?id=127813&action=edit Discover's Korean screenshot, where accelerator keys are misallocated SUMMARY While this bug do not exist in QWidgets based applications, but Kirigami based applications seems to have the accelerator bug. Attached here is configuration dialog of Dolphin and update dialog of Discover, using QWidgets and Kirigami respectively. In Dolphin's dialog, only the translated message of "Switch between split views panes with tab key" has its accelerator key assigned, as only that item of the configuration dialog has alphabet. All other texts are using 100% Hangul, so no accelerator keys were added. That actually hurts usability (no accelerator keys available for Korean users) but I think this should be discussed in another bug. On the other hand, in Discover's update dialog, accelerator keys are allocated to composed Hangul which could not be used as an accelerator key. Only the translated message of "Plasma Addons" has alphabets in this case. All others are using 100% Hangul, but accelerator keys are nevertheless allocated. This is clearly a bug. Note that I checked the behavior of KHangMan's settings dialog which is using Qt Quick but not Kirigami, and the said accelerator key problem is not present there. STEPS TO REPRODUCE 1. Launch any app using Kirigami and translated into Korean with LANG=ko_KR.UTF-8 2. Press Alt key to see the accelerator key OBSERVED RESULT When pressing Alt key, there is also underlines in Hangul characters. This is unacceptable as there is basically no way to press such accelerator key. Also in case of Plasma Discovery, there are shortcut keys with Hangul such as "Alt+설" displayed, but there is basically no way to press short cut key either. EXPECTED RESULT No Hangul characters should be underlined and used as an accelerator key. Usually translations will specifiy the accelerators separate from the main text. Kirigami should pick up accelerators only from [A-Za-z]. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 58647] Wrong accelerators specified in Info pages
https://bugs.kde.org/show_bug.cgi?id=58647 Shinjo Park changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|CONFIRMED |RESOLVED --- Comment #13 from Shinjo Park --- Given that the kdelibs is discontinued, I am going to report a new bug. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 420321] New: 1000 based number to words grouping is not suitable for Korean language
https://bugs.kde.org/show_bug.cgi?id=420321 Bug ID: 420321 Summary: 1000 based number to words grouping is not suitable for Korean language Product: kmymoney Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: k...@peremen.name Target Milestone: --- SUMMARY According to plugins/checkprinting/numbertowords.cpp, the grouping of numbers for conversion into human readable form is hard-coded into groups of 1000: Thousand, Million, Billion. However this scale does not fit into numbers used in Korean language, as numbers are grouped by 1 (instead of 1000) and more than billion (short scale) is often discussed as a monetary unit in Korean language. Let me give some example: * 10,000 KRW should be converted into "일만원". We have a separate noun for 10,000, not calling them as an equivalent of "ten thousand". * 3,000,000 KRW should be converted into "삼백만원", literally meaning 300 * 1. There is no equivalent word of "million", and we don't call them in "three million". * 200,000,000 KRW should be converted into "이억원". We have a separate noun for 100,000,000, not calling them as an equivalent of "two hundred million". * When it comes to the budget of small to medium sized companies, more than hundred billion KRW is not unheard of. At least numerals for 10^12 and 10^16 is not unheard of in newspapers. I don't know where and how to address this situation. The same 1 base grouping is also used in Chinese/Japanese language too. See also: https://en.wikipedia.org/wiki/Chinese_numerals#Large_numbers -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415420] cjk input of apt install and flatpak (appimage)
https://bugs.kde.org/show_bug.cgi?id=415420 Shinjo Park changed: What|Removed |Added CC||k...@peremen.name --- Comment #5 from Shinjo Park --- I suggest closing this bug as RESOLVED/NOT A BUG as the root cause of the problem is not in Kdenlive, but "Qt/KDE Flatpak Runtime". Also current KDE Flatpak Runtime contains ibus and fcitx plugin, but my setup with fcitx was not properly working (Kubuntu 19.10) and this should be discussed elsewhere. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 416888] Cities of North and South Korea needs to be separated
https://bugs.kde.org/show_bug.cgi?id=416888 --- Comment #2 from Shinjo Park --- Created attachment 127013 --> https://bugs.kde.org/attachment.cgi?id=127013&action=edit Modified citydb.sqlite, now listing North and South Korea separately. Data source for latitude/longitude is Wikidata, as of today. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 58647] Wrong accelerators specified in Info pages
https://bugs.kde.org/show_bug.cgi?id=58647 --- Comment #12 from Shinjo Park --- Created attachment 126656 --> https://bugs.kde.org/attachment.cgi?id=126656&action=edit Dolphin's Korean screenshot, only one accelerator key is allocated but there is no incorrect accelerator keys. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 58647] Wrong accelerators specified in Info pages
https://bugs.kde.org/show_bug.cgi?id=58647 --- Comment #11 from Shinjo Park --- Created attachment 126655 --> https://bugs.kde.org/attachment.cgi?id=126655&action=edit Discover's Korean screenshot, where accelerator keys are misallocated -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 58647] Wrong accelerators specified in Info pages
https://bugs.kde.org/show_bug.cgi?id=58647 Shinjo Park changed: What|Removed |Added CC||k...@peremen.name --- Comment #10 from Shinjo Park --- Although the original bug is 17 years old, it is still relevant. The bug seems to be at least fixed in the QWidgets based applications, but QML based applications seems to have the bug. Attached here is configuration dialog of Dolphin and update dialog of Discover, using QWidgets and QML respectively. In Dolphin's dialog, only the translated message of "Switch between split views panes with tab key" has its accelerator key assigned, as only that item of the configuration dialog has alphabet. All other texts are using 100% Hangul, so no accelerator keys were added. That actually hurts usability but I think this should be discussed in another bug. On the other hand, in Discover's update dialog, accelerator keys are allocated to composed Hangul which could not be used as an accelerator key. Only the translated message of "Plasma Addons" has alphabets in this case. All others are using 100% Hangul, but accelerator keys are nevertheless allocated. This is clearly a bug. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 131336] Perfomance: Wikimedia pages are rendered too slow
https://bugs.kde.org/show_bug.cgi?id=131336 Shinjo Park changed: What|Removed |Added CC||k...@peremen.name --- Comment #10 from Shinjo Park --- Hello, Is this bug still exist in the recent version of KHTML? We can close the bug if this bug is no longer relevant. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 416888] New: Cities of North and South Korea needs to be separated
https://bugs.kde.org/show_bug.cgi?id=416888 Bug ID: 416888 Summary: Cities of North and South Korea needs to be separated Product: kstars Version: git Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: k...@peremen.name Target Milestone: --- SUMMARY The citydb.sqlite from current git lists both North and South Korean cities under the same country "Korea". This is practically incorrect, so we need to separate both Koreas for this moment. STEPS TO REPRODUCE 1. git checkout https://cgit.kde.org/kstars.git/ 2. Open kstars/data/citydb.sqlite 3. Check where country == 'Korea' OBSERVED RESULT Both North and South Korean cities are mixed. EXPECTED RESULT These cities should go to North Korea: id=540, 'Ch''ongjin' id=1334, 'Hungnam' id=1507, 'Kimch''aek' id=1428, 'Kaesong' id=1766, 'Maando' id=2305, 'P''yongyang' id=2804, 'Sinuiju' id=3336, 'Wonsan' id=3383, 'Yupojin' All the rest should go to South Korea. Also there are some errors in South Korean cities too: id=719, 'Daegwallyeong' -> 'Province' should be 'Gangwon' id=797, 'Dokdo' -> 'Province' should be 'Gyeongbuk' id=1089, 'Name' should be 'Geumsan' -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 383682] kstars 2.8.1 crash after click 'Settings-Geographic' and 1 hour error in korea
https://bugs.kde.org/show_bug.cgi?id=383682 Shinjo Park changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #6 from Shinjo Park --- Closed again per bug #291203. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 383682] kstars 2.8.1 crash after click 'Settings-Geographic' and 1 hour error in korea
https://bugs.kde.org/show_bug.cgi?id=383682 Shinjo Park changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED CC||k...@peremen.name Resolution|FIXED |--- --- Comment #5 from Shinjo Park --- Still the DST rule of South Korea is not fixed, which is also a duplicate of Bug #291203. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 291203] KStars should use system time zone and DST data
https://bugs.kde.org/show_bug.cgi?id=291203 Shinjo Park changed: What|Removed |Added CC||k...@peremen.name --- Comment #8 from Shinjo Park --- Although Bug #383682 is currently closed, another problem raised there - DST rule of South Korea is incorrect - is still not fixed. Also there are some external report about wrong time zone [1] too. Is there a reason not using tzdata at all? Maintaining the own database won't make sense unless having a good reason. [1] https://www.indilib.org/forum/ekos/3226-kstars-local-time-offset-wrong.html https://indilib.org/forum/general/2272-kstars-clock-and-utc-offsets.html -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 395148] Double-click text selection
https://bugs.kde.org/show_bug.cgi?id=395148 Shinjo Park changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||k...@peremen.name Status|REPORTED|NEEDSINFO --- Comment #4 from Shinjo Park --- (In reply to 이야기 from comment #0) > When double-clicking, no word is selected. > Where are the settings in the options? Could you explain a bit more on the expected behavior? Let's take in this example: // * 본 메일은 발신전용이므로 메일을 통한 답변이 되지않습니다 If I place the mouse cursor in "일" inside the word "메일을" then that word is selected. This is intended operation, and where exactly do you have problem? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 409151] Typing Hangul with ibus in Konsole doesn’t work properly
https://bugs.kde.org/show_bug.cgi?id=409151 Shinjo Park changed: What|Removed |Added CC||k...@peremen.name --- Comment #1 from Shinjo Park --- This is not a Konsole bug, it is a bug in IBus Qt module. As far as I know patch for this problem is applied in Qt 5.13. See also: * https://github.com/ibus/ibus/issues/2068 * https://bugreports.qt.io/browse/QTBUG-58220 * https://codereview.qt-project.org/c/qt/qtbase/+/212179 * https://codereview.qt-project.org/c/qt/qtbase/+/255587 -- You are receiving this mail because: You are watching all bug changes.
[calligraactive] [Bug 408231] [Enhancement] add Korean Hangul code point range on Calligra
https://bugs.kde.org/show_bug.cgi?id=408231 Shinjo Park changed: What|Removed |Added CC||k...@peremen.name --- Comment #1 from Shinjo Park --- See also: Phabricator item D21553 Also closes #260064 for Korean too. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408662] New: Proper time formatting for locales where AMPM is going in front of time value
https://bugs.kde.org/show_bug.cgi?id=408662 Bug ID: 408662 Summary: Proper time formatting for locales where AMPM is going in front of time value Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: k...@peremen.name Target Milestone: 1.0 SUMMARY On certain locales like Korean, time in 12-hour format has AM/PM indicator prefixed to the time value like AM 12:00. Currently digital clock applet does not support such situation. STEPS TO REPRODUCE 1. Set locale to ko_KR (or other locale where 12-hour time format is AP hh:mm 2. Set digital clock to 12-hour mode 3. See the clock OBSERVED RESULT AM/PM indicator goes after time value (in example for Korean: 12:00 오전) EXPECTED RESULT AM/PM indicator goes in front of time value (in example for Korean: 오전 12:00) SOFTWARE/OS VERSIONS I checked the source code of master, function timeFormatCorrection(timeFormatString) of contents/ui/DigitalClock.qml hardcodes AM/PM indicator after the time value. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdoctools] [Bug 407037] New: meinproc5 is not honoring Korean naming order (reversed surname/firstname)
https://bugs.kde.org/show_bug.cgi?id=407037 Bug ID: 407037 Summary: meinproc5 is not honoring Korean naming order (reversed surname/firstname) Product: frameworks-kdoctools Version: 5.56.0 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-doc-engl...@kde.org Reporter: k...@peremen.name CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY While I was testing generation of DocBook file and HTML files based on Korean translation for docmessages (not in SVN yet), I found that surname, firstname is not correctly ordered in Korean even if I specified lang="ko" attribute to the tag. Because Korean names in Hangul (FirstnameSurname display) and names in Latin alphabet (Surname Firstname display) can appear on the single document, I think the lang attribute of not only the document but also the individual credit should be honored. Note that order reversing is implemented in DocBook's DSSSL since version 1.59. STEPS TO REPRODUCE 1. Add translator information to ROLES_OF_TRANSLATORS such as: 박신조 Note that lang="ko" attribute. 2. Run scripts/update.xml from l10n-kf5 directory, check whether those attributes are preserved. 3. Run meinproc5 --check index.docbook for the generated docbook and check the generated HTML. OBSERVED RESULT Generated HTML document shows: : 신조 박 EXPECTED RESULT This should be: : 박신조 Note that there is no space between surname and firstname, and surname goes first. While the part is empty, but looks like it is mentioned in TODO. SOFTWARE/OS VERSIONS KDE Frameworks Version: 5.56 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 400435] New: Incorrect unzipping of ZIP files with backslash('\') in filenames
https://bugs.kde.org/show_bug.cgi?id=400435
Bug ID: 400435
Summary: Incorrect unzipping of ZIP files with backslash('\')
in filenames
Product: ark
Version: 18.04.3
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: elvis.angelac...@kde.org
Reporter: k...@peremen.name
CC: rthoms...@gmail.com
Target Milestone: ---
SUMMARY
When viewing/extracting ZIP files using backslash('\') characters as path
delimiter, Ark fails to create folder structure and unzips all files in a
single folder.
STEPS TO REPRODUCE
1. Get a ZIP file containing a filename with backslash (possibly created on
Windows).
2. Open the ZIP file with Ark.
3. Extract the file using Ark directly or via Dolphin's context menu.
OBSERVED RESULT
Ark lists all files in a single folder, ignoring the backslash as path
delimiter. All files are extracted in the single path.
EXPECTED RESULT
Folders should be created.
SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.13.5
KDE Frameworks Version: 5.50.0
Qt Version: 5.11.1
ADDITIONAL INFORMATION
I used the ZIP file at:
http://org.downloadcenter.samsung.com/downloadfile/ContentsFile.aspx?CDSite=UNI_SEC&CttFileID=5352082&CDCttType=SW&ModelType=N&ModelName=SHW-M250K&VPath=SW/201302/20130208104403376/M250K_Data_JB.zip&OriginYN=N
(27.85 MiB)
--
You are receiving this mail because:
You are watching all bug changes.
[kdeconnect] [Bug 395854] New: Unable to enter Korean text with remote keyboard
https://bugs.kde.org/show_bug.cgi?id=395854 Bug ID: 395854 Summary: Unable to enter Korean text with remote keyboard Product: kdeconnect Version: 1.8 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: k...@peremen.name Target Milestone: --- Trying to input Korean text via any input method (I'm using fcitx here) for remote keyboard input is not working at all. I doubt any language via IM module is not appearing at all. Steps to reproduce: 1. Open any Android app and set Android's IM to "KDE Connect Remote Keyboard". 2. Launch KDE Connect Plasma applet and enter any Korean text. 3. The entered text is not appearing on the Android. Workaround: enter the text elsewhere and copy-paste it. Version: Android: 1.8.4 from Google Play Desktop: kdeconnect 1.3.0 from Ubuntu 18.04 I think it is possibly related to the bug #365305. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 387619] Some of Mailsploit test patterns are incorrectly decoded
https://bugs.kde.org/show_bug.cgi?id=387619 --- Comment #1 from Shinjo Park --- Created attachment 109217 --> https://bugs.kde.org/attachment.cgi?id=109217&action=edit Message list showing incorrectly parsed sender (2nd) field -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 387619] New: Some of Mailsploit test patterns are incorrectly decoded
https://bugs.kde.org/show_bug.cgi?id=387619 Bug ID: 387619 Summary: Some of Mailsploit test patterns are incorrectly decoded Product: kmail2 Version: 5.5.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: k...@peremen.name Target Milestone: --- The email address parsing problem, as discovered by the Mailsploit, persists in various mail clients. Looks like KMail is not tested, I am filing a bug to improve the current status. Test the email at: https://www.mailsploit.com/index#demo As of my KMail version 5.5.3, bugs are existing in both message list and message viewer. For message list, the following messages from Mailsploit shows incorrect sender values: - Mailsploit: Mozilla-Thunderbird ≤ 52.5.0-like (via spoof\n\0 ) - Mailsploit: Variation #3 (via "spoof" \n\0\0\0 ) - Mailsploit: Variation #3.2 (via "spoof" \n\0\0\0 ) - Mailsploit: Variation #3.2 (via "spoof" \n\0\0\0 ) For message viewer, I have Enterprise, Fancy, Standard, Brief headers and KMail 5.2. From my testing, only "Enterprise headers" shows incorrect sender values for the following messages: - Mailsploit: Variation #5 (via spoof ) - Mailsploit: Mozilla-Thunderbird ≤ 52.5.0-like (via spoof\n\0 ) -- You are receiving this mail because: You are watching all bug changes.
