Ttf-hunky-fonts pkgbuild: bitstream vera with non Eng chars

Saw it, built it, posting it :-)
I admit it - not all characters are perfect. But this is the first version and author promised to repair it soon. Still, if you want to have Bitstream Vera TTF fonts (originally lacking nonEn chars) with additional characters ("Baltic, Central European, South European and other languages, including Maori, Welsh and Esperanto") you can try it. It can co-exist with other ttf fonts (including original Bitstream Vera). Font names are Hunky Serif and Hunky Sans.
ttf-hunky-fonts PKGBUILD
pkgname=ttf-hunky-fonts
pkgver=0.1.0
pkgrel=1
pkgdesc="Bitstream Vera based TTF fonts with non-English characters"
url="http://www.yoper.com/ariszlo/hunky.html"
depends=('x-server')
install=ttf-hunky-fonts.install
source=(http://www.yoper.com/ariszlo/packages/SOURCES/hunkyfonts-$pkgver.tar.gz)
md5sums=('082b8220b2112830f7e418451a2c2f78')
build() {
install -d -m755 $startdir/pkg/usr/X11R6/lib/X11/fonts/TTF
install -m644 $startdir/src/hunkyfonts-$pkgver/TTF/*.ttf
$startdir/pkg/usr/X11R6/lib/X11/fonts/TTF
ttf-hunky-fonts.install
# arg 1: the new package version
post_install() {
echo "Rebuilding font cache..."
/usr/bin/fc-cache
echo "...done."
# arg 1: the new package version
# arg 2: the old package version
post_upgrade() {
echo "Rebuilding font cache..."
/usr/bin/fc-cache
echo "...done."
# arg 1: the old package version
pre_remove() {
/bin/true
# arg 1: the old package version
post_remove() {
echo "Rebuilding font cache..."
/usr/bin/fc-cache
echo "...done."
op=$1
shift
$op $*

Saw it, built it, posting it :-)
I admit it - not all characters are perfect. But this is the first version and author promised to repair it soon. Still, if you want to have Bitstream Vera TTF fonts (originally lacking nonEn chars) with additional characters ("Baltic, Central European, South European and other languages, including Maori, Welsh and Esperanto") you can try it. It can co-exist with other ttf fonts (including original Bitstream Vera). Font names are Hunky Serif and Hunky Sans.
ttf-hunky-fonts PKGBUILD
pkgname=ttf-hunky-fonts
pkgver=0.1.0
pkgrel=1
pkgdesc="Bitstream Vera based TTF fonts with non-English characters"
url="http://www.yoper.com/ariszlo/hunky.html"
depends=('x-server')
install=ttf-hunky-fonts.install
source=(http://www.yoper.com/ariszlo/packages/SOURCES/hunkyfonts-$pkgver.tar.gz)
md5sums=('082b8220b2112830f7e418451a2c2f78')
build() {
install -d -m755 $startdir/pkg/usr/X11R6/lib/X11/fonts/TTF
install -m644 $startdir/src/hunkyfonts-$pkgver/TTF/*.ttf
$startdir/pkg/usr/X11R6/lib/X11/fonts/TTF
ttf-hunky-fonts.install
# arg 1: the new package version
post_install() {
echo "Rebuilding font cache..."
/usr/bin/fc-cache
echo "...done."
# arg 1: the new package version
# arg 2: the old package version
post_upgrade() {
echo "Rebuilding font cache..."
/usr/bin/fc-cache
echo "...done."
# arg 1: the old package version
pre_remove() {
/bin/true
# arg 1: the old package version
post_remove() {
echo "Rebuilding font cache..."
/usr/bin/fc-cache
echo "...done."
op=$1
shift
$op $*

Similar Messages

  • UploadedFile and filenames with non-ascii chars

    Hi
    I'm using an UploadedFile object in my web app, and all works fine. However, when I try to upload a file, with a filename containing non-ascii chars (e.g. Spanish), I see that the getBytes method returns an empty byte array, the filename is not stored correctly (the non-ascii chars are lost, replaced by another representation), and that the content-type is application/octet-stream instead of image/png as supposed to be.
    If I rename that same file to have only ascii chars - everything is back to normal.
    How can I upload files with non-ascii chars in their name?

    Hi, back! Spent a few hours experimenting and found
    that everything is working great (including the creation
    of international non-ASCII foldernames) when I used
    utf-8 encoding in the sieve filters rules for the
    the match strings and the folder names... at least
    so far so good... for your ref and sorry for bothering.

  • [SOLVED!] On USB drives, problems with non-English chars and HAL

    Hello,
    I am having a problem with non-English caracters (áãàçéẽê...) on files stored on my USB drive.
    On Windows they're created with the correct name. But on Linux the files have the non-English characteres replaced by '?' and are not accessible.
    If I manuallly mount the drives using 'mount -o iocharset=utf8 /dev/sdb1 /media/usbdisk' the characters are OK, so I think I just need to get HAL to pass the correct parameters to mount. However I don't know how to do that, and haven't found any good solution.
    I tried to build a custom kernel setting the default charset as UTF-8 and it didn't work.
    Any ideas? I'm using x86-64, HAL 0.5.13-3 and my locale is pt-BR.UTF-8.
    Thanks!
    EDIT: Actually, this is not a HAL problem, but a problem with 'exo'. For the solution, I edited /etc/xdg/xfce4/mount.rc and added iocharset=utf8 to the [vfat] category.
    Last edited by Renan Birck (2009-11-28 20:54:23)

    I don't use Thunar presently, but I looked in the Thunar Volume Manager doc and I didn't find anything to change the mount options of removable drives. I am not quite sure if it's possible or not. Maybe someone using it can tell for sure.
    But if it is not possible to change the mount options, a possible solution is to disable the Thunar Volume Manager plugin and to use something else more configurable to manage the automount function.
    Personally I use the halevt package from AUR which uses configuration files in the xml format.
    It's not so easy to use but is highly configurable.
    But there exists other tools also.
    I can help you with halevt if you choose that way...

  • Problem with  Non English Chars

    OS : Mac OS
    Java : 1.5.0_07
    Hi,
    i have an Swing application that reads data from a database and shows them in a swing GUI. The text returned by the database is in Arabic and saved in a TextField object.
    But once printed, the arabic chars are screwed up.or actually they r not arabic chars at all!!
    For debugging i also write the result of the query in the console and in a log4j log file.
    There, it is printed in the right form.
    here the code:
    System.out.println("D3"+java.nio.charset.Charset.defaultCharset().name());
    System.out.println("singular "+dit.getData().getSingular());
    log4j,debug("singular "+dit.getData().getSingular());
    Font font = Font.decode("Geeza Pro");
    textl.setFont(font);
    textl.setText(dit.getData().getSingular());
    The output in the console is (and log4j) :
    D3MacRoman
    singular صوف
    The output in the Swing Textfield is
    ������
    If i configure log4j to use UTF8 ,then even into log4j log file the same screwed
    chars are written.
    Looks like i've to tell Swing to use MacRoman, which is the default of the OS and
    the used by the console&log4j. but i don't know how to.
    Any clue??
    Thanks,
    Chris.

    convert your strings to unicode:
    example 1
    import java.awt.*;
    import java.awt.event.*;
    public class ApplicationFrame
        extends Frame {
      public ApplicationFrame() { this("ApplicationFrame v1.0"); }
      public ApplicationFrame(String title) {
        super(title);
        createUI();
      protected void createUI() {
        setSize(500, 400);
        center();
        addWindowListener(new WindowAdapter() {
          public void windowClosing(WindowEvent e) {
            dispose();
            System.exit(0);
      public void center() {
        Dimension screenSize = Toolkit.getDefaultToolkit().getScreenSize();
        Dimension frameSize = getSize();
        int x = (screenSize.width - frameSize.width) / 2;
        int y = (screenSize.height - frameSize.height) / 2;
        setLocation(x, y);
    import java.awt.*;
    public class BidirectionalText {
      public static void main(String[] args) {
        Frame f = new ApplicationFrame("BidirectionalText v1.0") {
          public void paint(Graphics g) {
            Graphics2D g2 = (Graphics2D)g;
            g2.setRenderingHint(RenderingHints.KEY_ANTIALIASING,
                RenderingHints.VALUE_ANTIALIAS_ON);
            Font font = new Font("Lucida Sans Regular", Font.PLAIN, 32);
            g2.setFont(font);
            g2.drawString("Please \u062e\u0644\u0639 slowly.", 40, 80);
        f.setVisible(true);
    example2
    Java Internationalization
    By Andy Deitsch, David Czarnecki
    ISBN: 0-596-00019-7
    O'Reilly
    import java.awt.event.*;
    import java.awt.*;
    import java.text.*;
    import javax.swing.*;
    public class ArabicDigits extends JPanel {
      static JFrame frame;
      public ArabicDigits() {
        NumberFormat nf = NumberFormat.getInstance();
        if (nf instanceof DecimalFormat) {
          DecimalFormat df = (DecimalFormat)nf;
          DecimalFormatSymbols dfs = df.getDecimalFormatSymbols();
          // set the beginning of the range to Arabic digits
          dfs.setZeroDigit('\u0660');
          df.setDecimalFormatSymbols(dfs);
        // create a label with the formatted number
        JLabel label = new JLabel(nf.format(1234567.89));
        // set the font with a large enough size so we can easily
        // read the numbers
        label.setFont(new Font("Lucida Sans", Font.PLAIN, 22));
        add(label);
      public static void main(String [] argv) {
        ArabicDigits panel = new ArabicDigits();
        frame = new JFrame("Arabic Digits");
        frame.addWindowListener(new WindowAdapter() {
        public void windowClosing(WindowEvent e) {System.exit(0);}});
        frame.getContentPane().add("Center", panel);
        frame.pack();
        frame.setVisible(true);
    To avoid having to type all the \u... notation manually, use the native2ascii tool (included with the SDK).
    http://java.sun.com/developer/technicalArticles/Intl/HTTPCharset/

  • Can ims5.2p1 do sieve filter searches with non-ASCII chars?

    Particularly, is it possible with the
    Subject header line, which is
    =?xxx?Q?xxxxx?= or =?xxx?B?xxxxx?= encoded
    Resolved the fileinto foldername part, but
    now found that seems like ims's sieve filter
    cannot do non-ASCII matches... Thanks.

    Hi, back! Spent a few hours experimenting and found
    that everything is working great (including the creation
    of international non-ASCII foldernames) when I used
    utf-8 encoding in the sieve filters rules for the
    the match strings and the folder names... at least
    so far so good... for your ref and sorry for bothering.

  • Keyboard input bug with non-english chars

    Hi community, i'm facing a weird problem with the following flex application (something very simple, couldn't be more):
    <?xml version="1.0" encoding="utf-8"?>
    <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute">
         <mx:TextInput/>
    </mx:Application>
    The bug is coming only on Google Chrome (on Mac), when i try to enter french special chars in the input field, let's say i try to enter the following letters: éèçà, instead i'll get ÈËÁ‡ (see the following screenshots respectively for Safari and Chrome)
    I tried these browsers on Mac: Safari, Firefox, Omniweb, Opera. And it works like a charm for them. The bug is only on Google Chrome Mac.
    I also tried on Windows with IE6, IE7, Firefox, Opera, Google Chrome. No bug either for them on Windows.
    I've read on the Internet other people on Linux have the same bug sometimes (again, it's just for a couple of browsers and never all the browsers on their platform). I hope I don't have to tell my users to trick with their OS configuration. It's our job to make our apps to fit the visitor, not theirs!
    Does anyone knows a workaround for it? A special configuration to do (compatibility mode with older Flash version 8, 9, something like that?)...

    I just tested Firefox and Chrome on linux, i doesn't work either, but i get different weird chars: éèça
    However, on both mac and linux, if i copy the chars and paste them in the input field, it passes.

  • 10.6.5 upgrade issue: folders with non-standard chars in names unusable

    Hi all,
    I recently upgraded my XServe (2 x dual-core 2Ghz Xeon; 10Gb RAM) from OSX Server 10.6.4 to 10.6.5 (and applied several other updates: XCode 3.2.5, iTunes 10.1.1, Safari 5.0.3 and Java 10.6u3). Since the upgrade, I have a new problem whereby some folders shared via both SMB and AFS are unusable over the network.
    The problem applies to all folders whose names either (1) contain atypical characters like *, > or /, or (2) begin or end in a space.
    These folders are unusable over the network. Some appear, but others do not. Those that appear do not contain any files, even though they contain files when I browse them locally on the server. I cannot copy files into or out of any of the folders, nor can I rename them (remotely).
    When I browse the local file system on the server, there are no problems whatsoever - the problems occur only when connected remotely. The problems occur with both SMB and AFS access; I have not tried other protocols.
    These folders were heavily used by both Windows and Mac clients prior to the upgrade, and the problems are reliable and reproducible.
    The problems are fixed immediately by renaming the files to have more standard names, and they re-occur if I name the folders back. I will encourage the users here to adopt more standard naming conventions, but this is a fairly serious bug that is requiring some tedious workarounds.
    Any advice on this problem would be much appreciated!
    Regards
    Tim

    Different OS have different naming conventions. As you notices there are characters the macs will let you use; that the PC will not. And there are also characters the pc can use that the macs can not.
    check out
    http://www.portfoliofaq.com/pfaq/FAQ00352.htm
    http://technet.microsoft.com/en-us/library/cc976909.aspx
    http://support.microsoft.com/kb/147438
    One solution I know of is to batch scan/ rename files on a regular basis. Witch you could automate. to keep from generating lots of support requests. And to compliment this tactic you can educate the staff on file naming.
    There are programs that focus on pc/mac compatibility. Basically they try to restrict the mac and pcs from doing any thing that would cause naming convention conflicts. I hear they help reduce the number of naming conflicts.
    the other thing is verify the permissions on the share point. make sure no one can create files that other users can not see.
    If you find a better solution; I'd love to know.
    At least your not on the other side; I have window shares. And mac files can just completely fail to save, or if the file has a resource, the fork might be lost. I like mac shares better; because at least the files will save to the server.

  • Safari Bitstream Vera Sans font not displaying

    Hello,
    I have a font display problem in Safari 4.
    I upgraded to Snow Leopard and Safari 4.0.3, and web pages which specify in the CSS file:
    "font-family: 'Bitstream Vera Sans', Verdana, Arial, Helvetica, sans-serif;"
    are not displaying properly. The entire page, except where a different font is used, is replaced with a character that looks like letter "A" with a square around it.
    If I inspect the text element, then uncheck the font-family line, all characters display readably. What could be happening?
    Thanks!

    I was having this problem, too. I fixed it by I fixed it by downloading the font via the "Download" button at http://www.dafont.com/bitstreamverasans.font, decompressing the downloaded zip file, selecting the four ".ttf" files in the Finder, right-clicking and choosing "Open With.../Font Book.app", clicking "Install Font" on the resulting window. Then, in order to clear the font cache, I did the following in a Terminal window:
    sudo atsutil databases -remove
    sudo atsutil databases -removeUser
    sudo atsutil server -shutdown
    sudo atsutil server -ping

  • Map binary data (PDF) to XML not possible due to non-printable chars

    Hi XI Gurus,
    we have the following issue.
    We send a PDF as binary data (as a hex string '25255044462D3' ) along with some other information from ERP within one RFC to XI , doing a message split 1:n for those two kind of messages (1. the PDF, 2. the XML) an send the split messages to file/ftp receiver adapter.
    The message split and sending of the messages is working well, but we encounter some problems with non-printable chars (hex code below 0x20) in the pdf binary. The PDF data and the dynamic file name is mapped into an XML. But the non printable characters are converted into '#' when mapped into the XML target field.
    (Due to the 1:n multi mapping, we cannot put the filename into dynamic configuration, so we have to map the pdf and the filename into an XML and extract the content with variable substitution in receiver file adapter....)
    My question is: how can binary data with non-printable chars be sent through XI and can be mapped into an XML without beeing replaced by '#' ?
    Any help will be greatly appreciated.
    Thanks and regards
    Holger

    Maybe I didn´t explained it clearly enough.
    We do not have the issue that the RFC puts the '#' into the string. We got from the RFC a hex string containing the pdf as visible hex values like:
    As you can see we have the pdf as hex string. During message mapping XI replaces some non-printable chars like '0x04' or '0x19' with '#'.
    My question is: how can we avoid those char replacement ?
    BTW: I grabbed a pdf with sender file adapter, routed through XI without any mapping and send it with ftp in binary mode. But the pdf contains more chars as the origional file and the pdf content is not visible when opening with a pdf reader like Acrobat. I guess the file adpter has problems with carriage return and linefeed chars. Some CR and LF are replaced inserted somehow.
    Best regards,
    Holger

  • [SOLVED] Non english chars kdemod 4 problem

    Hello, I have a little problem with KDE and the non english charactes.
    If I open a file with non english chars in its name I get something like this:
    (In this case kwrite opens "other" file but in other applications it fails with an error of file not found)
    Other sympton is that in KDE menu my name have bad chars too:
    (It must be López)
    And the third sympton is that if try to rename a file in the desktop, I can't write accented chars (á é í ó ú). At the begining the keyboard in this rename dialog was totally in english but i have got a semi spanish keyboard (i can write ñ letters) with the apropiate /etc/hal/fdi/policy/10-keymap.fdi file.
    But the most strange is that in general, in all Kde and non-kde applications and even in the console, non english chars works ok. I can go to the file->Open menu of the application and open a file with non english chars in its name. The problem seems to reside in the part of kde that passes the name of the file to the application (¿kwin?)
    my locale is es_ES@UTF8 and as I said I have configured correctly the 10-keymap.fdi file.
    I have read in some forums that something like this could be a kde or qt bug, but for me it's not clear as i don't see a general complaining about this.
    Any idea will be apreciated.
    Thanks in advance,
    Christian.
    Last edited by christian (2009-03-27 14:52:17)

    SanskritFritz wrote:
    That should be "es_ES.utf8"
    Sorry, i mispelled it in the post.
    Of course, my locale is es_ES.utf8:
    LANG=es_ES.utf8
    LC_CTYPE="es_ES.utf8"
    LC_NUMERIC="es_ES.utf8"
    LC_TIME="es_ES.utf8"
    LC_COLLATE=C
    LC_MONETARY="es_ES.utf8"
    LC_MESSAGES="es_ES.utf8"
    LC_PAPER="es_ES.utf8"
    LC_NAME="es_ES.utf8"
    LC_ADDRESS="es_ES.utf8"
    LC_TELEPHONE="es_ES.utf8"
    LC_MEASUREMENT="es_ES.utf8"
    LC_IDENTIFICATION="es_ES.utf8"
    LC_ALL=
    I don't think this could be the source of the problem, because, except in the places I said in the firs post, the rest of my system works perfectly.

  • IPhone: sectionIndexTitlesForTableView and non-ASCII chars

    You specify an array of strings for your section titles in your implementation of UITableViewDataSource method sectionIndexTitlesForTableView. However, it seems like if you have a string with non-ASCII characters, it is left blank (for example the Korean string "누리마루"). Anybody else encounter this issue?

    I bump Dr. Chucks thread for a similiar problem with non-ascii chars.
    The chars show up but the sorting is a bit off.
    Example: A, Å, B, ... Z
    Should be: A, B, ... Z, Å, Ä, Ö
    In Swedish Å (the letter Aring;) is one of the last letters and should not be placed after A despite being similiar.
    Any ideas?

  • FILE_DATASTORE and non-ASCII chars

    I have created an interMedia Text index
    with the FILE_DATASTORE option, so that
    interMedia treats table entries as
    filenames and indexes the corresponding
    file on the servers's filesystem.
    But whenever the filename contains characters
    which are not part of the US7ASCII charset (like dv| _), the file is not found. But both Oracle and the operating system support these characters.
    The Oracle instance uses UTF8 as internal
    characterset. The client which stores
    the filenames in the table uses the
    WE8ISO8859P1 charset. The values in the
    database table are stored and shown correctly
    when viewed with Oracle or Java client
    programs.
    So where does the charset conversion fail ?
    The names are stored correctly, they can be
    read correctly by clients, but the indexer
    seems to use a wrong charset to translate
    the filenames stored in the database into
    filenames of the operating system.
    Do I have to apply some additonal configurations to my indexer ?
    Greetings,
    Michael Skusa
    null

    I bump Dr. Chucks thread for a similiar problem with non-ascii chars.
    The chars show up but the sorting is a bit off.
    Example: A, Å, B, ... Z
    Should be: A, B, ... Z, Å, Ä, Ö
    In Swedish Å (the letter Aring;) is one of the last letters and should not be placed after A despite being similiar.
    Any ideas?

  • Bitstream Vera Fonts

    Hello,
    Installed Arch on 5 different computers and planning on world-domination with this awesome distro (!!)
    However, one of the first search-queries I made in the forums was for help installing Bitstream Vera fonts.  Nothing much turned-up.  Being a recovering Windows-aholic, I am very fond of the high-quality, free, Vera fonts(http://www.gnome.org/fonts/).
    Beyond the basic help-file in the src's, can anyone recommend the best way to install in Arch?  My guess follows:
    1.  Get fonts:  http://ftp.gnome.org/pub/GNOME/sources/ … 10.tar.bz2
    2.  Install as prescribed to /usr/X11R6/lib/X11/fonts/TTF/
    3.  Run 'mkfontscale', then 'mkfontdir' in /usr/X11R6/lib/X11/fonts/TTF/
    4.  Copy 'local.conf' into /etc/fonts/
    5.  fc-cache -v
    6.  Now what?
    Is the base Fontconfig in Arch set-up to auto-detect the new fonts and apply the local.conf or does it need some tweak'n?  (we loves tweak'n)
    Thanx.

    Mozilla without XFT should NOT use these fonts.  No-big-deal.  The standard adobe fonts in Mozilla are perfectly usable--however, after viewing some pages in Konqueror with XFT/Vera fonts.....well I'm sure you'll agree it is somewhat easier on the eyes to have a little anti-alais'n occasionally.
    Hmmm.  If I'm not mistaken, having seen these fonts in Red Hat 9/Gnome/OpenOffice 1.1.RC1 from:
    http://www.users.bigpond.net.au/gavindi … noarch.rpm
    I'm wondering if the font setup in RH9 does additional 'tweak'n'(!?)  It seems that either Gnome(alone) or RH9/Gnome(combo) looks even better ???  Or is the KDE in Arch not compiled against XFT ???  Hmmmm.  I'm really try'n, here, to be helpful to those newbie's from across the Windows "Trail-of-Tear's" to not be discouraged by the lack of good, free, non-MS, fonts in LINUX .... especially ARCH-LINUX.  Hope this doesn't seem trivial to the long-time *nix'ers.  I just know how important screen-fonts are to the less-technically-inclined user a.k.a. the new potential LINUX user.   
    Thanx for your time and consideration.

  • Problems with ttf-mac-fonts package from AUR

    Hello,
    I've problems with generate package ttf-mac-fonts:
    $ sudo yaourt -S aur/ttf-mac-fonts
    A Macbuntu-10.04
    A Macbuntu-10.04/install.sh
    A Macbuntu-10.04/panel
    A Macbuntu-10.04/panel/panel.entries
    A Macbuntu-10.04/upgrade.sh
    A Macbuntu-10.04/compiz
    A Macbuntu-10.04/compiz/x64
    A Macbuntu-10.04/compiz/x64/original
    A Macbuntu-10.04/compiz/x64/original/libanimation.la
    A Macbuntu-10.04/compiz/x64/original/libanimation.a
    A Macbuntu-10.04/compiz/x64/original/libanimation.so
    A Macbuntu-10.04/compiz/x64/original/animation.xml
    A Macbuntu-10.04/compiz/x64/libanimation.a
    A Macbuntu-10.04/compiz/x64/libanimation.so
    A Macbuntu-10.04/compiz/x64/animation.xml
    A Macbuntu-10.04/compiz/x32
    A Macbuntu-10.04/compiz/x32/original
    A Macbuntu-10.04/compiz/x32/original/libanimation.la
    A Macbuntu-10.04/compiz/x32/original/libanimation.a
    A Macbuntu-10.04/compiz/x32/original/libanimation.so
    A Macbuntu-10.04/compiz/x32/original/animation.xml
    A Macbuntu-10.04/compiz/x32/libanimation.a
    A Macbuntu-10.04/compiz/x32/libanimation.so
    A Macbuntu-10.04/compiz/x32/animation.xml
    A Macbuntu-10.04/uninstall.sh
    A Macbuntu-10.04/readme
    Checked out revision 134.
    install: cannot stat 'gbk/*.ttf': No such file or directory
    ==> ERROR: A failure occurred in package().
    Aborting...
    ==> ERROR: Makepkg was unable to build ttf-mac-fonts.
    ==> Restart building ttf-mac-fonts ? [y/N]
    ==> --------------------------------------
    ==>
    How can I solve this problem?.
    Regards.

    Crap - sorry, I typed too quick, the upstream source if fine.  But as that PKGBUILD does some odd things, I missed the problem.   The simplest (but far from best) fix is to change the lines in the package function to the following:
    svn co https://macbuntu.svn.sourceforge.net/svnroot/macbuntu/Macbuntu/fonts/ ./
    install -d $pkgdir/usr/share/fonts/{TTF,Type1}
    install -m644 ./Macbuntu/fonts/gbk/*.ttf $pkgdir/usr/share/fonts/TTF
    install -m644 ./Macbuntu/fonts/mac/*.ttf $pkgdir/usr/share/fonts/TTF
    install -m644 ./Macbuntu/fonts/mac/*.pfb $pkgdir/usr/share/fonts/Type1
    That is, add the proper paths to the install commands.
    EDIT: or here is one that is at least a lot closer to the right way - though it's the first svn PKGBUILD I've worked on:
    _svn=ttf-mac-fonts
    pkgname=${_svn}-svn
    pkgver=134
    pkgrel=1
    pkgdesc="Mac fonts including Lucida Grande, Apple Garamond and other fonts from Apple"
    arch=('any')
    url="http://www.apple.com/safari/"
    license=('custom')
    depends=()
    makedepends=('subversion')
    conflicts=('macfonts' 'ttf-mac-fonts-svn')
    source=(
    "${_svn}::svn+http://svn.code.sf.net/p/macbuntu/code/Macbuntu/fonts"
    "http://images.apple.com/legal/sla/docs/SafariWindows.pdf"
    sha256sums=(
    'SKIP'
    'd1c9697ea430a3ddad6548c7b9c961c4b06f9da5a5ba1f1007fe998b3354df4a'
    install='ttf-mac-fonts.install'
    pkgver() {
    cd ${srcdir}/${_svn}
    svnversion | tr -d [A-z]
    package() {
    cd ${srcdir}
    install -d $pkgdir/usr/share/licenses/${_svn}
    install -m644 SafariWindows.pdf $pkgdir/usr/share/licenses/${_svn}/
    cd ${srcdir}/${_svn}
    install -d $pkgdir/usr/share/fonts/{TTF,Type1}
    install -m644 gbk/*.ttf $pkgdir/usr/share/fonts/TTF
    install -m644 mac/*.ttf $pkgdir/usr/share/fonts/TTF
    install -m644 mac/*.pfb $pkgdir/usr/share/fonts/Type1
    Last edited by Trilby (2013-08-21 13:35:55)

  • (Arial) Fonts turn into cyrillic with anti-aliasing 'none' (bug?)

    Hi, I've got this really strange problem here.
    When I'm typing 'ç' in a Photoshop I get a cyrillic 'H'. When I turn the anti-aliasing of the font into 'sharp' instead of 'none' for instance, it's back the ç again. This occurs with every key in the numeric row.
    I'm using an azerty keyboard and the ç is located on the 9-key,  This only happens with the default font 'Arial' (regular). I'm working with Photoshop CS3 (Master Collection) on a Mac OSX 1.5.6 (Leopard).

    You're welcome.   
    Undisclosed recipient wrote:
    Thrashing the preferences did the trick. I should make a habbit of this when things fall apart.
    Absolutely! It's the first thing I try when anything starts acting weird "suddenly".
    Undisclosed recipient wrote:
    I figured it was a russian H because the other letters on the numeric row were russian too (inverted R's and so on).
    Interesting.
    Incidentally, the я is not an inverted or flipped R but a uniquely Cyrillic letter which represents the diphthong YA, and its name in Russian is indeed "Ya".

Maybe you are looking for

  • Who's Up for a Challenge? (or who needs a good Color Picker?)

    Greetings, I got lost in the muck trying to figure out how to make this color-picker code initialize with the last chosen color.... This is an open source project, and I posted my predicament on the blog for it, but it's been a few weeks and no one h

  • Which is better for 3D rendering

    Hello everyone. I build a new computer. I want to work with 3d graphics. Can not decide which graphics card can handle better rendering. Decide between: HP Nvidia Quadro K4000 or GeForce GTX 780 Thank you for your help, Karči

  • Photosmart 5510d wireless connection problem

    Photosmart 5510d  Mac OS 10.7.5 The printer is connected to my network and can access the internet (I can browse the app store). My computer has access to internet on the same network (I can post this message). I cannot see the SSID of the printer Wh

  • How can i get itunes on my surface 32bit

    how can i download itunes on my surface windows 8 32 bit

  • When will Mozilla address and optimize the performance of Firefox?

    We all (unfortunately) can't deny that Chrome is 'faster' than Firefox while Firefox is way more customizable. I heard that Mozilla will concentrate on the performance of Firefox this year, make everything smooth and load web pages faster. Is that tr