Package Details: ttf-ms-win8-thai 6.3.9600.17238-1

Git Clone URL: https://aur.archlinux.org/ttf-ms-win8.git (read-only, click to copy)
Package Base: ttf-ms-win8
Description: Microsoft Windows 8.1 Latin and International TrueType fonts
Upstream URL: http://www.microsoft.com/typography/fonts/product.aspx?PID=161
Licenses: custom
Conflicts: ttf-ms-fonts, ttf-tahoma, ttf-vista-fonts, ttf-win7-fonts, ttf-win7-fonts-autodownload
Provides: ttf-font, ttf-ms-fonts, ttf-tahoma, ttf-vista-fonts, ttf-win7-fonts
Submitter: reflexing
Maintainer: severach
Last Packager: severach
Votes: 62
Popularity: 0.000000
First Submitted: 2012-06-08 06:11 (UTC)
Last Updated: 2017-07-13 07:10 (UTC)

Required by (287)

Sources (8)

Pinned Comments

severach commented on 2018-03-01 20:05 (UTC)

Package is not broken. You can't build this with yaourt or pamac. It must be built with makepkg after obtaining the fonts manually.

Latest Comments

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 .. 34 Next › Last »

reflexing commented on 2014-07-29 17:46 (UTC)

@sl1pkn07 I took a look at ttf-wps-symbol-fonts. It installs copyrighted Microsoft fonts, freely. LOL. No way I will add it to conflicts array. Because this package provides complete checksums for Microsoft Windows 8.1 fonts, all of them, including Symbol and Webdings, etc. If you want to use this package, remove ttf-wps-symbol-fonts. That package is WRONG by it's nature and ILLEGAL.

reflexing commented on 2014-07-29 17:35 (UTC)

@sl1pkn07 > /home/sl1pkn07/aplicaciones/ttf-ms-win8/PKGBUILD: line 324: 32551 Segmentation fault fontforge -lang=ff -c "$ff_script" $* ==> ERROR: A failure occurred in package_ttf-ms-win8-korean(). fontforge's bug. I will report it. > change from /usr/share/fonts/ttf-ms-win8/ to /usr/share/fonts/ broken ttf-wps-symbol-fonts and other custom font packages > is possible back to /usr/share/fonts/ttf-ms-win8/? I don't understand your problem. Can you elaborate? AFAIK this package fonts was never installed to /usr/share/fonts/ttf-ms-win8/. I think it's cool, to have fonts in distinctive directories, but it caused problems before.

MacNuke commented on 2014-07-29 16:36 (UTC)

I have the same problem, sl1pkn07

sl1pkn07 commented on 2014-07-29 15:59 (UTC)

change from /usr/share/fonts/ttf-ms-win8/ to /usr/share/fonts/ broken ttf-wps-symbol-fonts and other custom font packages is possible back to /usr/share/fonts/ttf-ms-win8/? greetings

sl1pkn07 commented on 2014-07-29 15:52 (UTC)

/home/sl1pkn07/aplicaciones/ttf-ms-win8/PKGBUILD: line 324: 32551 Segmentation fault fontforge -lang=ff -c "$ff_script" $* ==> ERROR: A failure occurred in package_ttf-ms-win8-korean().

wzyboy commented on 2014-07-27 03:47 (UTC)

@reflexing Great! Thanks! I finally managed to write a small python script to determine which fonts embed bitmaps. Here is the list: calibrib.ttf calibrii.ttf calibri.ttf calibriz.ttf cambriab.ttf cour.ttf lucon.ttf batang.ttc (korean) cambria.ttc gulim.ttc (korean) mingliu.ttc (zh_tw) msgothic.ttc (japanese) msmincho.ttc (japanese) simsun.ttc (zh_cn) Only bitmaps in CJK fonts should be taken care of. So I suggest shipping four seperate conf files. I wrote them for you: https://gist.github.com/wzyboy/16337c3c29f769f96ecb :-)

reflexing commented on 2014-07-26 19:16 (UTC)

@wzyboy can you test it? config will be only with zh_cn and uncommented. https://reflexing.ru/ttf-ms-win8-6.3.9600.16384-4.src.tar.gz

wzyboy commented on 2014-07-26 10:07 (UTC)

@reflexing As far as zh_cn fonts are concerned, the only file with embedded bitmap fonts is "simsun.ttc". Modern Chinese fonts like msyh.ttc and Adobe Source Han Sans does not use (old, ugly) bitmaps any more. Other CJK fonts may contain embedded bitmap fonts as well. When I opened a font file with embedded bitmaps with fontforge, it will ask me whether to load bitmaps. But I cannot find a way to inspect whether they embed bitmaps in batch with scripts ...

reflexing commented on 2014-07-26 09:49 (UTC)

@wzyboy What font families should I mention there?

wzyboy commented on 2014-07-26 09:48 (UTC)

@reflexing Sorry I made a typo. I was to mean "/etc/fonts/conf.avail/" instead of "/etc/fonts/conf.d/". The prior direcotry is to store "available configuration templates", and users can decide whether to symlink them to "conf.d" directory. This is the usage of recommendation according to "/etc/fonts/conf.d/README". That way everyone would be satifised :-)

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 .. 34 Next › Last »