Bug 2689

i think that drakfont have a pb with your file because there is a space.

can you do 2 things ?  

1- add this file on the bugreport
2- rename it to remove the space and try to import again.

CC: (none) => dmorganec

the file link is 

http://fonts.qurancomplex-dev.com/wp-content/uploads/2011/04/UthmanicHafs1-Ver08.zip

the results after rename

===========================

    Wide character in print at /usr/sbin/drakfont line 457.

    before install any font be sure  you have the rights to use it and installing it at your system

    you can install the fonts with by manual way , some fake fonts can freez x server

    Install Specifics Fonts...........
    Wide character in print at /usr/sbin/drakfont line 461.
    Font to install: /home/mageia/Downloads/ÙجÙداتÙ/UthmanicHafs1-Ver08.otf
    ghostscript is not installed on your system...
    sh: /usr/sbin/ttmkfdir: No such file or directory
    type1inst Version 0.6.1 (11th February 1998)
    Copyright (C) 1996-1998 James Macnicol (james.macnicol@mailexcite.com)

    There are no PostScript fonts in this directory

    The End...........................

===========================

no more

===========================

    There are no PostScript fonts in this directory
    mv: cannot stat `UthmanicHafs1': No such file or directory
    mv: cannot stat `Ver08.otf': No such file or directory

===========================

lik at the previous message

i reproduce this bug.

i work on it.

Assignee: bugsquad => dmorganec

(In reply to comment #3)
> i reproduce this bug.
> 
> i work on it.

Pinging, because nothing has happened with this report for more than 3 months, it still has the status NEW or REOPENED.

@ DMorgan

Please set status to ASSIGNED (FIXED is fine too, of course :))

CC: (none) => marja11

yes the problem has been fixed since two months ago

but i forgot to reply here about it

thanks D Morgan for your help

@ salim

Glad to hear that D Morgan helped you so well :)

However, the package didn't get fixed yet, there has been no update for Mageia 1.

Besides, Manuel just reproduced the bug in updated Mageia 1

(In reply to comment #5)
> yes the problem has been fixed since two months ago
> 
> but i forgot to reply here about it
> 
> thanks D Morgan for your help

how have you resolve it ?

a ... aaa ....

i am a little bit confused

i dont know how did that happened in that time

but now nothing changes 

the problem is still in drakfont

will sorry .... to report that this problem has been solved

while its not

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

the problem still remain in mageia 2

Fixed in git

Status: NEW => ASSIGNED
CC: (none) => thierry.vignaud
Assignee: dmorganec => thierry.vignaud

and in svn ? :)

CC: (none) => nicolas.lecureuil

In SVN too and in cauldron too

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED