Comment 6 for bug 759882

I'm sorry to be late. I put together a our view.

First, we analyze evince's source code, but that has huge complexity,
that needs major surgery.

If we erase DejaVu from fontconfig lists, that caused:

- It will cause a some change, Latin-1 characters will be render
  using "Takao" fonts.
- "Takao" include Latin-1 glyphs that has enough legibility.
- DejaVu is *very good* for Latin-1, but Takao is *good* too.
- We had not encountered any regression, but we can not negate
  unknown side-effects.

Our pros/cons lists are below:

fontconfig approach:
(pros) : Fix the evince's problem.
(pros) : And fix the any other applications's problems (such as old Adobe Flash[1]).
(pros) : Fix also fontconfig's "mixed" behavior, see attached "gedit-mixed-sample.png" [2]
(cons) : Latin-1 characters render with "Takao" fonts. ; its trivial changes.

Evince fixing approach:
(pros) : straight eye for solving.
(pros) : Fix the evince's problem.
(cons) : Need major surgery.

[1] Adobe Flash ( < 10.2 ) has same bug, that cannot display Kanji characters in current fontconfig.

[2] When I input "a0" on gedit, these are shown with DejaVu.
However, I input "00", these are with Takao. It follows that DejaVu
Latin characters and Takao Latin characters are mixed in one document.
Yes, this is an another bug, but i dont know that is filed(may be not yet).

------------------------------------------------------------
And, we consult jkbys(He is Japanese LoCo leader && cjk-testers admin),
he has the same opinion.
# cjk-testers has not brisk exchange, but he is expert of such problems.

In conclusion,
- The workaround(by fontconfig) has enough/many pros, and small cons.
- Natty will be releases at soon, now in a last phase.
- We can not prognosis the impact of this changes (we could not test
 *all* cases of ubuntu applications), we must prevent from unpredictable
  side effects at releng.
- If we provide some statement in release notes(in Japanese), user
  can avoid this root problem.

------------------------------------------------------------
So, in our opinion, its too late for Natty.
Natty is in Release Quality Iteration, that patch are too risky.
We shoud provide only "how to" at release notes, its provide
enough environment for Japanese PDFs.

On the other hand, In Oneiric, we believe that fontconfig patching
is acceptable, that have validity for development phase, isn't it?