https://bugzilla.redhat.com/show_bug.cgi?id=1382428
Cheng-Chia Tseng <pswo10680(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(pswo10680(a)gmail.c |
|om) |
--- Comment #16 from Cheng-Chia Tseng <pswo10680(a)gmail.com> ---
I finally figured it out.
Blender only picks the compressed font archives in its own data structure, that
means you must place those font archives into
/usr/share/blender/2.78/datafiles/fonts directory, and everything works well.
Trying to separate those font archives and place them at /usr/share/fonts makes
blender cannot use those fonts made for international usage.
Furthermore, those fonts are derived works of droid sans (which means it use
the same name as droid sans, but contains more glyphs from other international
fonts besides western fonts). So users will receive unpredictable font display
because the repeating font name will make fontconfig confuse.
So the new packages you built does not improve the issue. Blender keeps
complaining not finding those font archives in the place it expects, so those
Chinese translations are STILL squares (tofus) even with your latest build.
Even worse the blender-fonts package break the default font selection for
Chinese environment.
Before installation of the latest blender-fonts package you built, the default
CJK font of Chinese is SourceHanSansTW-Regular.otf: "思源黑體 TW"
"Regular". But
after the installation, the default font changed to droidsans.ttf: "DejaVu
Sans" "Book" (which blender provides). That introduces an regression. (you
can
use 'fc-match -s sans-serif' to check this in zh_TW locale)
So what I suggest is not to uncompressed those font archives and see them as a
part of blender because they are not designed to be used globally, but only as
a fallback internatinoal font to display those translations internally in
blender itself. If we must separate the font packaging, just intall them in
/usr/share/blender/2.78/datafiles/fonts directory, then everything will works
as fine as it should be.
--
You are receiving this mail because:
You are on the CC list for the bug.