[Bf-committers] Possible fix for bug #1483 (Internat. font path badly constructed)

[Stefan Gartner]

--Boundary-02=_f13EB6L7z7xYUx6
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Friday 06 August 2004 13:56, Rob Haarsma wrote:
> Stefan Gartner wrote:
> >* Why is the full path to the font file stored in U.fontname?
>
> Blame me ! Must be a side effect of my coding inexperience.
> You're welcome to make whatever changes to retrieve something more
> appropriate.

I didn't want to blame you explicitly :)
Actually, I thought it's just a leftover from an earlier incarnation of the=
=20
i18n code, as I seem to remember that the user once had to enter the font=20
path manually in a text field. Thinking of it, there can beseveral cases=20
where U.fontname has to contain the full path (e.g. when the user hasn't=20
specified a fontpath).

>
> Greetings Sgefant !
> Rob

cheers,
sgefant

--Boundary-02=_f13EB6L7z7xYUx6
Content-Type: application/pgp-signature
Content-Description: signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBBE31f+200iUD+EwYRAo4QAJ94+i98MWz9j07Ms0EVyiUaD9HQKQCdEDAH
KbhGojmPIARGA29WUTtQShA=
=z4Bc
-----END PGP SIGNATURE-----

--Boundary-02=_f13EB6L7z7xYUx6--