app-text/acroread-8.1.2 is the only version in portage, however the latest asian fontpack for it is 7.0.8. PDF files such as http://tyan.com/datasheets/d_ta26b2932-E_100.pdf require the current asian fontpack. Reproducible: Always
Created attachment 147452 [details] Proposed ebuild for media-fonts/acroread-asianfonts-8.1.2
Created attachment 147462 [details] Fix for installing LICREAD.TXT to /opt instead of the Adobe subdirectory
Seeing that there is the "extended" font package for hebrew, arabic, eastern european and greek fonts, wouldn't it be reasonable to change the name of the package to something like acroread-extrafonts and add installation support to the ebuild? Currently the extended font package can't be installed from portage at all.
Based on the proposed patch in comment #2 and my own problems, I decided to attempt a fix at the situation. The issues: 1. acroread has stuck as a name for quite some time; now the software is called "Adobe Reader" to be distinguished from Adobe Acrobat 2. To view some PDFs, special additions are needed, which have nothing to do with the interface language (e.g. I'd like to have Japanese interface, but be able to view Korean documents without embedded fonts); portage currently cannot handle this in any standard way, so people have been trying to use LINGUAS 3. IMHO, the fontpacks are additions to Adobe Reader, but can be used on its own possibly; So the only dependency is Adobe Reader depends on fontpacks if some USE flag is set So my solution can be found in my pkalin overlay[1]... [1] https://svn.tar.bz/repos/pkalin/trunk/README.txt 1. I have renamed the ebuilds to app-text/Adobe_Reader and media-fonts/Adobe_fontpack 2. TODO: Add proper support for the Extended languages (Arabic, Thai...) 3. I have tested them for LINGUAS=ja, please test for the languages you know. As bug #212625 suggests, it may be a good idea to merge these two ebuilds, but it may not be necessary.
sorry for delay. acroread-asianfonts-8.1.2 in cvs
