Comment 32 for bug 659280

Revision history for this message
Aron Xu (happyaron) wrote :

@poloshiao, Thanks for you hard work on translating the messages, :)

@xenomorph0525,
You've tried to predict what I'll reply to your comments, and it seems to be you'd like ask me a question: correctly displaying Chinese characters by a workaround or waiting for fixing the buggy software - which is more important?

From your point of view, correctly displaying the characters is more important - I know your opinion very clearly. Please don't doubt I've misunderstood you anymore.

But why such a problem being so critical in your mind? I guess the answer is the problem exists in the application that renders PDF files - which you must use to finish your work or study. So it's critical for you, and for some people who have similar situations - but fixing a problem should not influence other common people who don't care about your problem, their right (to have these three lines in fontconfig configuration) should be respected first.

If there are any problem on preference of fonts, that's another issue and you should convince people your choice is more suitable for a common taste. And you should really be clear that working around a bug in another application should never be your reason to push such a change, because font configuration matters for people who care that, then maybe you are break their things by this way (if you don't influence them, it'll be okay). Also, you can't say after such a change, people still have the freedom to add whatever they like back - then you have your freedom now to do whatever, too.

So I think you have wasted a lot of time here on arguing whether we would change fontconfig to adopt a dirty work around. Why not go and find a fix for poppler(-data)? That's the universal way which make everyone happy. (I think you agree it is able to be fixed.)

There is another issue which has very similar problem:
Many MP3 files have Big5/GBK tags, but no media player accept any work around such as detect Big5/GBK before assuming they are UTF-8 (even placing a locale hack is never accepted) - because such a detection has problems, and people who are using UTF-8 files might suffer problems they should never need.

Now, applying your proposal on working around PDF rendering problem will do harm to people who care their font settings, so it's not acceptable. Please, put all your efforts to make poppler(-data), that is a much more effective (and maybe correct) way to solve your problem, but not keep arguing or asking me "which is more important".