Ubuntu

Lohit Punjabi Regular font is broken (Can't enter text into textboxes)

Reported by lucasvo on 2006-05-19
18
Affects Status Importance Assigned to Milestone
ttf-indic-fonts (Ubuntu)
Medium
Unassigned

Bug Description

  $ scribus
  Font /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType/Racotf04.ttf is broken, discarding it
  $ readlink /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType/Racotf04.ttf
  /usr/share/fonts/truetype/ttf-malayalam-fonts/Racotf04.ttf
  $ dpkg -S /usr/share/fonts/truetype/ttf-malayalam-fonts/Racotf04.ttf
  ttf-malayalam-fonts: /usr/share/fonts/truetype/ttf-malayalam-fonts/Racotf04.ttf
  $ apt-cache show ttf-malayalam-fonts | grep Source:
  Source: ttf-indic-fonts

lucasvo (lucasvo) wrote : version

lucasvo@supernova:~$ scribus --version
Scribus Version 1.2.4.1

If one choose another font, it works, it is a problem of the default font "Lohit Punjabi Regular". It only occurs in Edubuntu. maybe Kubuntu as wel.

KarlGoetz (kgoetz) wrote :

This does not happen on Ubuntu (gnome) dapper.
Any of the fonts available in an ubuntu install are ok (9 of them), the extras that are edubuntu 'only' failed

Changed in scribus:
status: Unconfirmed → Confirmed
Richard Kleeman (kleeman) wrote :

Standard Dapper ubuntu install has this problem on my system. It is a font issue and the "Lohit Punjabi Regular" is the default font for some obscure reason. If you edit text the font cannot change which seems like a bug but if you go to properties and select the text button you can change the font that way and then everything works fine. That is a workaround but this problem will be annoying to users of this popular piece of software.

Craig Ringer (ringerc) wrote :

Is the font free? If so, is there anywhere I can download the version used in Ubuntu to test against recent Scribus 1.3.x CVS?

1.3.x is much fussier about broken fonts, rejecting them rather than sometimes staggering blindly onward. There are LOTS of fonts that look just fine until you try to use them for DTP - Scribus uses lots of features from fonts that other apps just don't, so we run into lots of fonts that're subtly broken.

A good 95% of font-specific issues, when investigated, turn out to be buggy and broken fonts.

--
Craig Ringer

Barry deFreese (bddebian) wrote :

Running from a terminal window I do get an error about a broken font, Racotf04.ttf. So this could be the cause? Thanks.

Barry deFreese (bddebian) wrote :

For us, the package is ttf-punjabi-fonts binary from ttf-indic-fonts source package. I'm looking. Thanks.

Jim Tarvid (tarvid) wrote :

A truly irritating and idiotic bug. Counld we at least have a different default font? These sorts of errors drive potential users away or cost support people a lot of time. A default style wouldn't hurt either.

Jim Tarvid wrote:
> A truly irritating and idiotic bug. Counld we at least have a different
> default font? These sorts of errors drive potential users away or cost
> support people a lot of time. A default style wouldn't hurt either.
>
>
It almost drove me away.... I think it's a good suggestion and probably
a minor change with a huge effect.

Well if it is such an easy fix tell me how. I have looked at the source and can't quite determine how scribus determines it's default font. I'm certainly open for suggestions. Thanks.

Manuel Duran Moyano (mduran) wrote :

I cant change the font size (only 0.5 pt) with any fonts

versions :
* 1.2.4.1.dfsg-1ubuntu4 (dapper)
and
* 1.3.3.2.dfsg-1 (download from http://debian.scribus.net)

ugly bug

Manuel Duran Moyano (mduran) wrote :

I solve this (font size) with the wheel of mouse.

Mathias Strasser (larrrry) wrote :

The easiest way to get around this bug is to simply uninstall the punjabi font package. That did for me. Of course, this is just a workaround, not a solution.

Rocco Stanzione (trappist) wrote :

The racotf04.ttf is definitely bad. ttmkfdir in a dir with this font (and many others) in it returns:
Warning: Can't initialize Face : racotf04.ttf(2)

Rocco Stanzione (trappist) wrote :

According to debian's changelog:
http://packages.debian.org/changelogs/pool/main/t/ttf-indic-fonts/ttf-indic-fonts_0.4.7.1/changelog
this font replaced RachanaMedium.ttf. Should be safe to revert to this. Attached for convenience.

Craig Ringer (ringerc) wrote :

The default font is determined via the app prefs. You'll find the initial setting (for when no prefs yet exist) in the prefs loading code. Search for "scribus*.rc" . (This is certainly correct for Scribus 1.3.x, and I think it should be right for 1.2.x; I don't have 1.2.x code on hand to check and I'm on a shockingly expensive 'net connection at Uni so I have no desire to download it right now).

It's probably not a bad idea to define a font or set of fonts to prefer for the default font if no preferences already exist. Of course, it's much better not to ship broken fonts with the OS.

Matt Zimmerman (mdz) on 2006-08-23
Changed in scribus:
importance: Critical → Medium
Paul Sladen (sladen) wrote :

This source package generates lots of binary font packages, including 'ttf-malayalam-fonts'; is there a way that we can easily check which of these fonts are "broken" according to Scribus?

description: updated

Paul Sladen wrote:
> This source package generates lots of binary font packages, including
> 'ttf-malayalam-fonts'; is there a way that we can easily check which of
> these fonts are "broken" according to Scribus?

Scribus 1.3.x will try to detect fonts that're damaged or incorrect as
it generates its font cache, and will report any problem fonts on
stderr. There are plans to provide GUI for this, but nothing done yet.

In 1.2.x no such scan is performed as there's no font cache. Problems
accessing fonts will be reported when the user first tries to use the
font, again to stderr. It should be possible to just scroll through the
font list and see what ones get complained about (again, to stderr).

--
Craig Ringer

KarlGoetz (kgoetz) wrote :

Whats the status of this? is ubuntu shipping less broken scribus's now? :)

After a Feisty upgrade, the default font was Minya Nouvelle Bold which
"works". The problem was the selection of a default font that did not
work making first use confusing until you selected a working font.

Jim Tarvid
On 4/1/07, KarlGoetz <email address hidden> wrote:
> Whats the status of this? is ubuntu shipping less broken scribus's now?
> :)
>
> --
> Lohit Punjabi Regular font is broken (Can't enter text into textboxes)
> https://launchpad.net/bugs/45565
>

Barry deFreese (bddebian) wrote :

Jim. I'm not sure I understand your comment? The latest scribus is supposed to use an entirely different font-searching scheme. Are you saying it works, but still not correctly on initial startup? Thanks!

Jim Tarvid (tarvid) wrote :

I am saying it "works" on Feisty.

The packager's choice of default font could be more universal (a plain
sans serif font would be a good choice) but it least it "works".

On earlier distros the default font was broken and no text was
rendered. Only a bit of debugging would lead one to that conclusion
and workaround.

Jim Tarvid

On 4/28/07, Barry deFreese <email address hidden> wrote:
> Jim. I'm not sure I understand your comment? The latest scribus is
> supposed to use an entirely different font-searching scheme. Are you
> saying it works, but still not correctly on initial startup? Thanks!
>
> --
> Lohit Punjabi Regular font is broken (Can't enter text into textboxes)
> https://bugs.launchpad.net/bugs/45565
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Soumyadip Modak (soumyadip) wrote :

The bug report includes messages regarding the Racotf font, which is in ttf-malayalam-fonts package. This has been replaced with a better font Rachana in the latest package, while the Lohit fonts have been upgraded too (See ttf-indic-fonts 0.4.9 in Debian Unstable).

Barry deFreese (bddebian) wrote :

Is this bug even valid anymore? Thank you!

Changed in ttf-indic-fonts:
status: Confirmed → Incomplete
Soumyadip Modak (soumyadip) wrote :

Probably not. Can anyone test this with the latest ttf-indic-fonts package (1:0.5.0 in Debian unstable) ?

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in ttf-indic-fonts:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers