https://bugzilla.redhat.com/show_bug.cgi?id=683472
Jekyll Wu adaptee@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|adaptee@gmail.com |
--- Comment #13 from Jekyll Wu adaptee@gmail.com ---
(In reply to comment #10)
I have no account on bugs.kde.org
Then create one. That is one minute's work.
I have no idea what is the process there.
Neither do I when I created my very first bug report there. Nobody knows it before doing it. No need to scare yourself.
Actually it is easy, just go to https://bugs.kde.org/enter_bug.cgi?product=konsole&format=guided
I have no idea whether it is fixed in upstream or not - and I have no way to test it.
You are worrying too much. I don't expect average users to confirm my fix after I provide and apply a patch. But without receiving a bug report, nothing will happen.
But I expect that Fedora KDE maintainers can do that very easily.
Sure I believe they know how to do it. But I don't think they have the time/energy to forward all reports to whatever upstream. That simply won't scale.
(In reply to comment #12)
I thought that I will make world better and will notice their developers, that > there is something called IDN, which they probably never heard before and that > their code/program does not support it.
That is really nice.
But that is all. I find my time to report it, but I have no time to persuade it further.
You are scaring yourself, again. Reporting it to bugs.kde.org won't take you more time than reporting it here.
I always thought that package maintainer should *maintian* the package in distribution. And one of his task is to *be* bridge between distribution users and upstream. But if you think you are just packaging new version of upstream code and nothing else, then please close this bug as CLOSED-I-DO-NOT-CARE, because I do not care either - and I do not mean it bad - I do own or use IDN domain, and it does not block me in my work.
I think this report is a typical example of that bridge: identify the problem is not due to fedora's packaging mistake, then ask reporter to report it to the upstream. That is how a community works. If all work goes to the maintainer, then the end result is likely to be no reports being forwarded at all.
Resolution|--- |WONTFIX
Great, problem solved.
Just in case someone misunderstands, that "WONTIX" can mean anything except "KDE WONTFIX IT"
Actually, it turns out I have fixed it in a private branch a few months ago, and then unsurprisingly just forgotten it. Why have I forgot? Because there is no report on bugs.kde.org reminding me of this "not-bothering-myself" issue.
There is another reason I insist a report created on bugs.kde.org beside reminding of developers: we need a central place to record all known and fixed issues. A report on fedora tracker is clearly useless for that purpose.
So it is not up to me to decide when this will be fixed. I just wait for a report on bugs.kde.org.
Remove myself from CC list. I really have forgot this report, again.
i18n-bugs@lists.fedoraproject.org