Apparently, it's supposed to be possible to convert a RISC OS Font to a
TTF using Dr Fonty.

Could some kind person run me through the process as I can't get it to
work with my Dr Fonty version 1.46

Thanks
Dave

--

Dave Triffid

In article <5b39c3fc0fdave@triffid.co.uk>,
Dave <dave@triffid.co.uk> wrote:
> Apparently, it's supposed to be possible to convert a RISC OS Font to a
> TTF using Dr Fonty.

> Could some kind person run me through the process as I can't get it to
> work with my Dr Fonty version 1.46

> Thanks
> Dave

Mnnn!
I have looked at the Stardot posting of a few years ago, but there's no
details, just that Gerald Holdsworth had managed to do it.

Dave

--

Dave Triffid

In message <5b39f0baf1dave@triffid.co.uk>
Dave <dave@triffid.co.uk> wrote:

> In article <5b39c3fc0fdave@triffid.co.uk>,
> Dave <dave@triffid.co.uk> wrote:
>> Apparently, it's supposed to be possible to convert a RISC OS Font to a
>> TTF using Dr Fonty.

>> Could some kind person run me through the process as I can't get it to
>> work with my Dr Fonty version 1.46

>> Thanks
>> Dave

> Mnnn!
> I have looked at the Stardot posting of a few years ago, but there's no
> details, just that Gerald Holdsworth had managed to do it.

> Dave

Looking at that Stardot posting. The last update from Gerald Holdsworth
was that he exported / saved the font from Dr Fonty as Postscript and then
converted the Postcript file online to ttf. He gives a link to an online
converter.

Not familiar with Dr Fonty, so I don't know if this is easy or not.
Load the font - Save as Postcript ???

I'm probably not being much help - sorry

--
John Crane

In article <e4896f3b5b.john@john.johnandtina.force9.co.uk>,
John Crane <john@johnandtina.force9.co.uk> wrote:
> In message <5b39f0baf1dave@triffid.co.uk>
> Dave <dave@triffid.co.uk> wrote:

> > In article <5b39c3fc0fdave@triffid.co.uk>,
> > Dave <dave@triffid.co.uk> wrote:
> >> Apparently, it's supposed to be possible to convert a RISC OS Font to a
> >> TTF using Dr Fonty.

> >> Could some kind person run me through the process as I can't get it to
> >> work with my Dr Fonty version 1.46

> >> Thanks
> >> Dave

> > Mnnn!
> > I have looked at the Stardot posting of a few years ago, but there's no
> > details, just that Gerald Holdsworth had managed to do it.

> > Dave

> Looking at that Stardot posting. The last update from Gerald Holdsworth
> was that he exported / saved the font from Dr Fonty as Postscript and
> then converted the Postcript file online to ttf. He gives a link to an
> online converter.

> Not familiar with Dr Fonty, so I don't know if this is easy or not. Load
> the font - Save as Postcript ???

> I'm probably not being much help - sorry

Thanks for your thoughts anyway John. :-)

There's never been a problem loading the font into Dr Fonty, the problem
is being able to actually get anything usable out of the (Expletive) app.

Dave

--

Dave Triffid

[Snip]

> > I'm probably not being much help - sorry

> Thanks for your thoughts anyway John. :-)

> There's never been a problem loading the font into Dr Fonty, the problem
> is being able to actually get anything usable out of the (Expletive) app.

> Dave

I'll try a different ask. :-)

At http://www.triffid.co.uk/dstuff/Fontimage.jpg is a Jpeg image of a
Font, which in RISC OS is "Visage (Hollow)".

I've searched around but can't find a match Windows side, so I'm wondering
if anyone in their travels has seen it?

Thanks
Dave

--

Dave Triffid

In message <5b3c00f626dave@triffid.co.uk>
Dave <dave@triffid.co.uk> wrote:

[snip]

> At http://www.triffid.co.uk/dstuff/Fontimage.jpg is a Jpeg image of a
> Font, which in RISC OS is "Visage (Hollow)".

> I've searched around but can't find a match Windows side, so I'm wondering
> if anyone in their travels has seen it?

Senator Pro

nk

--
SIGNWORK Signwriting & Design
Mobile: 07866 738825
www.signwork.plus.com

In article <d7d26e3c5b.signwork@riscube.signwork.plus.com>,
Nick K <nk@signwrk.plus.com> wrote:
> In message <5b3c00f626dave@triffid.co.uk>
> Dave <dave@triffid.co.uk> wrote:

> [snip]

> > At http://www.triffid.co.uk/dstuff/Fontimage.jpg is a Jpeg image of a
> > Font, which in RISC OS is "Visage (Hollow)".

> > I've searched around but can't find a match Windows side, so I'm
> > wondering if anyone in their travels has seen it?

> Senator Pro

> nk

Thanks for that bit o' info, appreciated.

It is indeed a match,

Dave

--

Dave Triffid

In article <5b3d055f1bdave@triffid.co.uk>,
Dave <dave@triffid.co.uk> wrote:
> In article <d7d26e3c5b.signwork@riscube.signwork.plus.com>,
> Nick K <nk@signwrk.plus.com> wrote:
> > In message <5b3c00f626dave@triffid.co.uk>
> > Dave <dave@triffid.co.uk> wrote:

> > [snip]

> > > At http://www.triffid.co.uk/dstuff/Fontimage.jpg is a Jpeg image of a
> > > Font, which in RISC OS is "Visage (Hollow)".

> > > I've searched around but can't find a match Windows side, so I'm
> > > wondering if anyone in their travels has seen it?

> > Senator Pro

> > nk

> Thanks for that bit o' info, appreciated.

> It is indeed a match,

I can only find a paid for version. Unless you know better.

--
Chris

In article <5b3d11198dmec@npost.uk>,
Chris Newman <mec@npost.uk> wrote:
> In article <5b3d055f1bdave@triffid.co.uk>,
> Dave <dave@triffid.co.uk> wrote:
> > In article <d7d26e3c5b.signwork@riscube.signwork.plus.com>,
> > Nick K <nk@signwrk.plus.com> wrote:
> > > In message <5b3c00f626dave@triffid.co.uk>
> > > Dave <dave@triffid.co.uk> wrote:

> > > [snip]

> > > > At http://www.triffid.co.uk/dstuff/Fontimage.jpg is a Jpeg image
> > > > of a Font, which in RISC OS is "Visage (Hollow)".

> > > > I've searched around but can't find a match Windows side, so I'm
> > > > wondering if anyone in their travels has seen it?

> > > Senator Pro

> > > nk

> > Thanks for that bit o' info, appreciated.

> > It is indeed a match,

> I can only find a paid for version. Unless you know better.

Yes indeed Chris, I've also searched and can only find a paid for version.

There is another font from someone else, that's the same, called
"Serapine" but that's also a paid for font.

Dave

--

Dave Triffid

So as a kind of footnote question before I go and GAL (Get A Life)...

Aside from one possible case, has anyone here ever ever managed to get any
useful data out of Dr Fonty, Save Postscript wise?

Thanks
Dave

--

Dave Triffid

On 6 Mar 2024 as I do recall,
Dave wrote:

> Aside from one possible case, has anyone here ever ever managed to get any
> useful data out of Dr Fonty, Save Postscript wise?
>
I never managed to get it to do anything useful at all past the stage of
importing fonts (I was trying to add scaffolding to some PD fonts), but
then I gave up before the stage of actually trying to re-export my work.
:-(

--
Harriet Bazley == Loyaulte me lie ==

Cole's Law: Thinly sliced cabbage.

In article <389e533d5b.harriet@bazleyfamily.co.uk>,
Harriet Bazley <harriet@bazleyfamily.co.uk> wrote:
> On 6 Mar 2024 as I do recall,
> Dave wrote:

> > Aside from one possible case, has anyone here ever ever managed to get
> > any useful data out of Dr Fonty, Save Postscript wise?
> >
> I never managed to get it to do anything useful at all past the stage of
> importing fonts (I was trying to add scaffolding to some PD fonts), but
> then I gave up before the stage of actually trying to re-export my work.
> :-(

Thanks Harriet.

Dave

--

Dave Triffid

In article <5b3d57d90ddave@triffid.co.uk>,
Dave <dave@triffid.co.uk> wrote:
> In article <389e533d5b.harriet@bazleyfamily.co.uk>,
> Harriet Bazley <harriet@bazleyfamily.co.uk> wrote:
> > On 6 Mar 2024 as I do recall,
> > Dave wrote:

> > > Aside from one possible case, has anyone here ever ever managed to
> > > get any useful data out of Dr Fonty, Save Postscript wise?
> > >
> > I never managed to get it to do anything useful at all past the stage
> > of importing fonts (I was trying to add scaffolding to some PD fonts),
> > but then I gave up before the stage of actually trying to re-export my
> > work.
> > :-(

> Thanks Harriet.

> Dave

FWIW. This is the error thrown up by Dr Fonty, for ever and a day...

This one specifically when a Save-Postscript-Outlines PFB is attempted.

Reporter 2.74x (13 Oct 2023) List Wed 6th Mar 2024 11:49

11:48:32.30 ** Error **
Error : &80000002
Message: Internal error: Abort on data transfer at &03A5427C
11:48:32.32 ** WimpError ** from Dr Fonty
Error : &80000002
Message: Internal error: Abort on data transfer at &03A5427C
11:49:31.92 ** WimpError ** from Dr Fonty
Error : &20202020

Reporter 2.74x (13 Oct 2023)

Obviously I have no idea what that means. :-)

Dave

--

Dave Triffid

In message <5b3d5da7b1dave@triffid.co.uk>
Dave <dave@triffid.co.uk> wrote:

> In article <5b3d57d90ddave@triffid.co.uk>,
> Dave <dave@triffid.co.uk> wrote:
>> In article <389e533d5b.harriet@bazleyfamily.co.uk>,
>> Harriet Bazley <harriet@bazleyfamily.co.uk> wrote:
>>> On 6 Mar 2024 as I do recall,
>>> Dave wrote:

>>>> Aside from one possible case, has anyone here ever ever managed to
>>>> get any useful data out of Dr Fonty, Save Postscript wise?
>>>>
>>> I never managed to get it to do anything useful at all past the stage
>>> of importing fonts (I was trying to add scaffolding to some PD fonts),
>>> but then I gave up before the stage of actually trying to re-export my
>>> work.
>>> :-(

>> Thanks Harriet.

>> Dave

> FWIW. This is the error thrown up by Dr Fonty, for ever and a day...

> This one specifically when a Save-Postscript-Outlines PFB is attempted.

> Reporter 2.74x (13 Oct 2023) List Wed 6th Mar 2024 11:49

> 11:48:32.30 ** Error **
> Error : &80000002
> Message: Internal error: Abort on data transfer at &03A5427C
> 11:48:32.32 ** WimpError ** from Dr Fonty
> Error : &80000002
> Message: Internal error: Abort on data transfer at &03A5427C
> 11:49:31.92 ** WimpError ** from Dr Fonty
> Error : &20202020

> Reporter 2.74x (13 Oct 2023)

> Obviously I have no idea what that means. :-)

> Dave

Bonsoir,
Je n'ai pas Dr Fonty
I don't have Dr Fonty, but you can try Xp1FontED.
https://clive.semmens.org.uk/RISCOS/XP1FontEd.html

--
Jean-Michel

In article <bc94813d5b.jmb@jmc.bruck.orange.fr>,
Jean-Michel <jmc.bruck@orange.fr> wrote:

[Snip]

> Bonsoir,
> Je n'ai pas Dr Fonty
> I don't have Dr Fonty, but you can try Xp1FontED.
> https://clive.semmens.org.uk/RISCOS/XP1FontEd.html

Thank you for the info.

Unfortunately that's not what I need... Nor is FontEd.

I do not want to edit a font, just process it as is, and output as
Postscript.

Thanks
Dave

--

Dave Triffid

On 6 Mar 2024 as I do recall,
Dave wrote:

> I do not want to edit a font, just process it as is, and output as
> Postscript.
>
Well, if I simply use a font in a Drawfile and use the Save...PostScript
option, that embeds the font definition in the top of the resulting
PostScript file, between a %%BeginFont and %%EndFont, looking a bit like
this:

/RO_Circuss 11 dict dup begin
/FontInfo 10 dict dup begin
/Notice (Converted by MakePSFont 1.18) def
/FullName (Circuss) def
/FamilyName (Circuss) def
/Weight () def
/Version (001.001) def
/ItalicAngle 0.00 def
/isFixedPitch false def
/UnderlinePosition 0 def
/UnderlineThickness 0 def
/decode85 11 dict def decode85 begin
/str 0 def /ind 0 def
/getc {str ind dup 1 add /ind exch store get} bind def
/getn {getc 42 sub getc 42 sub 85 mul add 3500 sub} bind def
101 {PaintType 0 eq {eofill} {StrokeWidth setlinewidth stroke} ifelse exit} bind def

etc. etc.

I don't know if that is the basic data you need?

Certainly when I'm trying to get PostScript output from the !PMS music
software, in order to get the resulting files to render properly I have
to physically add the PMS-Music font to the start of the PostScript
generated by the program! But that file doesn't look the same as the
embedded fonts output by Draw above:

%%BeginSetup
%%BeginResource: font PMS-Music

100 dict begin

/Rm/rmoveto load def/Rl/rlineto load def/Mt/moveto load def
/Lt/lineto load def/St/stroke load def/Tr/translate load def
/Slw/setlinewidth load def/Sc/scale load def/Ct/curveto load def
/Rc/rcurveto load def

/At{arcto 4{pop}}def/An/arcn load def
/Pm{transform round exch round exch itransform Mt}def
/Pl{transform round exch round exch itransform Lt}def

/slthick{matrix currentmatrix aload pop pop
pop 4 1 roll mul 3 1 roll mul sub dup 0.00174 le {pop 30}{0.00174 div
sqrt -0.7 mul 2.718 exch exp 40 mul 10 add}ifelse}def

/ellipsedict 4 dict def ellipsedict/mtrx matrix put
/ea{ellipsedict begin/savematrix mtrx currentmatrix def Tr 5 -1
roll rotate Sc 0 0 1 5 -2 roll arc savematrix setmatrix end}def
/ec{ellipsedict begin/savematrix mtrx currentmatrix def Tr 5 -1
roll rotate Sc 0 0 1 5 -2 roll An savematrix setmatrix end}def

--
Harriet Bazley == Loyaulte me lie ==

It is far better to be deceived than to be undeceived by those we love.

In message <5b3d84ae27dave@triffid.co.uk>
Dave <dave@triffid.co.uk> wrote:

> In article <bc94813d5b.jmb@jmc.bruck.orange.fr>,
> Jean-Michel <jmc.bruck@orange.fr> wrote:

> [Snip]

>> Bonsoir,
>> Je n'ai pas Dr Fonty
>> I don't have Dr Fonty, but you can try Xp1FontED.
>> https://clive.semmens.org.uk/RISCOS/XP1FontEd.html

> Thank you for the info.

> Unfortunately that's not what I need... Nor is FontEd.

> I do not want to edit a font, just process it as is, and output as
> Postscript.

It seems I don't understand everything correctly :-(
If you can go through !Draw, Harriet's solution is good, you can also use
menu: select /conver to path., you get the drawing coordinates.

--
Jean-Michel

In article <0600013e5b.jmb@jmc.bruck.orange.fr>,
Jean-Michel <jmc.bruck@orange.fr> wrote:
> In message <5b3d84ae27dave@triffid.co.uk>
> Dave <dave@triffid.co.uk> wrote:

> > In article <bc94813d5b.jmb@jmc.bruck.orange.fr>,
> > Jean-Michel <jmc.bruck@orange.fr> wrote:

> > [Snip]

> >> Bonsoir,
> >> Je n'ai pas Dr Fonty
> >> I don't have Dr Fonty, but you can try Xp1FontED.
> >> https://clive.semmens.org.uk/RISCOS/XP1FontEd.html

> > Thank you for the info.

> > Unfortunately that's not what I need... Nor is FontEd.

> > I do not want to edit a font, just process it as is, and output as
> > Postscript.

> It seems I don't understand everything correctly :-( If you can go
> through !Draw, Harriet's solution is good, you can also use menu:
> select /conver to path., you get the drawing coordinates.

Mmnn! I think we are all in the not understanding camp ATM.

All I want to do, is stick a font in Dr Fonty or similar, immediately go
to Save-Postscript-PFB to which I get a Name.PFB file.

That PFB file can usually be taken Windows side and converted into a .ttf
file.

Job Done.

Dave

--

Dave Triffid

Well here we still are again... This is like picking at a scab:-)

Really! Just for the fun of experiment, and to indicate it can be done,
and how.

I've taken a selection of Fonts I have in RISC OS and attempted to
process them through Dr Fonty.

Interestingly, some will process and Save out as PFB files while others
will not and error out with the usual...

" Error : &80000002
Message: Internal error: Abort on data transfer at &03A5427C
11:48:32.32 ** WimpError ** from Dr Fonty."

Of course, as per a clause in Sod's law, the fonts I really want to
Save/convert won't. and the fonts I don't care about do.
Such is life methinks... :-(

I'll not bore you with all the minutia and tedium of processing through a
load of fonts to see what will and what won't, so I'll take one that
worked....

Assuming you can get a RISC OS font to process through Dr Fonty, then it
can be later processes Win side into a .ttf.

Bog standard RISC OS font Oxford.Roman.
Loaded into Dr Fonty.
Save out as... Postscript- PFB called it Oxford2. Banner headlines
[No Dr Fonty error.]

Took the resulting file Windows side and re-filetyped it as Oxford2.ps

Called up https://convertio.co/

Processed it through, and out the other side, it arrived as requested a
..ttf file.

Installed that in Windows, no problem.

So a RISC OS font to ttf can be done, but for reasons beyond my postage
stamp of knowledge... Some will and some won't, and you'll need to test
the fonts yourself to find out which... :-/

Dave

Footnote:

If you don't have Dr Fonty, but do have Font Fiend the above noted applies
to it as well.

D.

--

Dave Triffid

In article <5b3e51fe49dave@triffid.co.uk>,
Dave <dave@triffid.co.uk> wrote:
[Snippy]

> If you don't have Dr Fonty, but do have Font Fiend the above noted
> applies to it as well.

After the fun and games with Dr Fonty earlier today, I turned my attention
to FontFiend.

After some testing work, I can report that FontFiend is far more reliable
at outputting .pfb files from RISC OS fonts than Dr Fonty.

I've had enough for one day... So off to my pit I shall go. :-)

Dave

--

Dave Triffid

On 8 Mar 2024 as I do recall,
Dave wrote:

> I've taken a selection of Fonts I have in RISC OS and attempted to
> process them through Dr Fonty.
>
> Interestingly, some will process and Save out as PFB files while others
> will not and error out with the usual...

I would guess that the fonts that can't be processed are probably
defective in some way - years ago I went through the entirety of the EFF
"4000 Free Public Domain Fonts" CD in an attempt to catalogue them in
some useful way and eliminate the (numerous) duplicates, and discovered
in the process that while they would all display *on screen*, a
significant proportion of them crashed Impression if you tried to print
them out, or tried to print out some of the more unusual characters. I
would guess that a lot of them were quite possibly sourced from Windows
and run through some kind of converter in the first place; certainly
when I loaded a few into Dr Fonty they didn't have any scaffolding in
them.

So I wouldn't be at all surprised if quite a few of the fonts on your
machine, depending on where you originally got them from, may be missing
bits of vital information that the PFB conversion process is expecting
to be present, or may contain non-obvious errors.

--
Harriet Bazley == Loyaulte me lie ==

Questions are a burden to others, but answers are a prison for oneself.

In article <867a183f5b.harriet@bazleyfamily.co.uk>,
Harriet Bazley <harriet@bazleyfamily.co.uk> wrote:
> On 8 Mar 2024 as I do recall,
> Dave wrote:

> > I've taken a selection of Fonts I have in RISC OS and attempted to
> > process them through Dr Fonty.
> >
> > Interestingly, some will process and Save out as PFB files while others
> > will not and error out with the usual...

> I would guess that the fonts that can't be processed are probably
> defective in some way - years ago I went through the entirety of the EFF
> "4000 Free Public Domain Fonts" CD in an attempt to catalogue them in
> some useful way and eliminate the (numerous) duplicates, and discovered
> in the process that while they would all display *on screen*, a
> significant proportion of them crashed Impression if you tried to print
> them out, or tried to print out some of the more unusual characters. I
> would guess that a lot of them were quite possibly sourced from Windows
> and run through some kind of converter in the first place; certainly
> when I loaded a few into Dr Fonty they didn't have any scaffolding in
> them.

> So I wouldn't be at all surprised if quite a few of the fonts on your
> machine, depending on where you originally got them from, may be missing
> bits of vital information that the PFB conversion process is expecting
> to be present, or may contain non-obvious errors.

Interesting observation Harriet, thanks...

Not that I've ever bothered with the EFF mass of Fonts, but a few years
ago with the fonts I had installed, problems cropped up regularly.

In my case it was first with "Easy Font Pro" or as it was later known
"EasyPro".

Whereby the activation of certain fonts would either cause it to crash or
in lesser cases, stop showing the fonts.

Secondly, occasionally OvPro would throw a wobbly at a font when document
print time arrived.

I created an OvPro document that per paragraph had sets, (A-Z, a-z and
other characters) of all the Fonts in my collection.

As you noted, they would all display on screen, but when it came to the
print out, that was another story...

Eventually, I excised the errant fonts from my collection and the whole
font list then printed okay.

Undoubtedly you are correct in your last paragraph summation...

Interestingly, during my past hours/days of fun with Dr Fonty, I
discovered a number of fonts that crashed Dr Fonty, but would process to
Save PFB without any problems in Font Fiend.

There was only one font in particular that would appear to process, but on
taking Win side to make .ttf would be somewhat malformed.

All the O, Q and other letters with circular holes would have filled black
centres.

Anyway... I've now done the .ttf business on the couple of fonts I needed
most, so FTTB (Dr Who) I'm sorted.

Just one of the little perils that awaits user like me, (And Fay) who use
OvPro in both RISC OS and Windows. :-)

Dave

Nb: Just to be clear for reader of between the lines...
I love OvPro in both version, and it's one of my most used apps in both
universes. :-)

D.

--

Dave Triffid

On 09/03/2024 20:45, Harriet Bazley wrote:
> I would guess that the fonts that can't be processed are probably
> defective in some way - years ago I went through the entirety of the EFF
> "4000 Free Public Domain Fonts" CD in an attempt to catalogue them in
> some useful way and eliminate the (numerous) duplicates, and discovered
> in the process that while they would all display *on screen*, a
> significant proportion of them crashed Impression if you tried to print
> them out, or tried to print out some of the more unusual characters. I
> would guess that a lot of them were quite possibly sourced from Windows
> and run through some kind of converter in the first place; certainly
> when I loaded a few into Dr Fonty they didn't have any scaffolding in
> them.

Yes, I had a RISC OS font catalogue that I created in Impression and
when printed out was as thick as a phone book! I seem to remember I had
to convert a few of them to paths on Draw files to get it all to print.

---druck