Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Font issue Helvetica55Roman
12 views
Skip to first unread message
cortical
Feb 3, 2012, 6:23:01 PM2/3/12
to
Hi
I have a client using Helevtica55Roman for a report, I am re-creating a
replicate report in a new FileMaker file to add to their (eslewhere
developed) solution. The report prints a PDF to desktop.
I have sourced the font from a couple of places and reinstalled (free;
couldn't find a pay for version); but same problem, the 'o' letters do
not print on by Mac OSX.6 FM11Adv ; I haven't heard back from the client
testing yet ( probably will work for them).
There is also a message about license
<<
A font in this document is not licensed for embedding without permission
from the legal owner or font vendor. Depending on the font, blank text
may appear in the output file.
>>
Well, there is only the Helvetica55Roman, and it was supposed to be
free, no indication of licensing requirements.
Thoughts?
Just for your amusement and edification, the solution is a 49 file set,
multiple tables per file; one table I looked at yesterday: 921 fields.
I have a client using Helevtica55Roman for a report, I am re-creating a
replicate report in a new FileMaker file to add to their (eslewhere
developed) solution. The report prints a PDF to desktop.
I have sourced the font from a couple of places and reinstalled (free;
couldn't find a pay for version); but same problem, the 'o' letters do
not print on by Mac OSX.6 FM11Adv ; I haven't heard back from the client
testing yet ( probably will work for them).
There is also a message about license
<<
A font in this document is not licensed for embedding without permission
from the legal owner or font vendor. Depending on the font, blank text
may appear in the output file.
>>
Well, there is only the Helvetica55Roman, and it was supposed to be
free, no indication of licensing requirements.
Thoughts?
Just for your amusement and edification, the solution is a 49 file set,
multiple tables per file; one table I looked at yesterday: 921 fields.
Helpful Harry
Feb 3, 2012, 7:08:19 PM2/3/12
to
In article <jghq8o$d4m$1...@speranza.aioe.org>, cortical
Are you sure it's that font causing the error and not another one? Try
making a new layout that you know uses only that font and make a PDF.
(Fonts embedded in logos for example can cause problems without you even
relaising they're being used.)
If it is that font, then try remove the "Helevtica55Roman" font from the
computer (quit and restart FileMaker, or even reboot the computer to make
sure it's gone). FileMaker will automatically use a close substitute which
may be unnoticeable.
If the automatic substitute doesn't work, then your best option is to
simply use normal Helvetica (I'm almost certain it's still one of the
Mac's default system fonts). You may be able to get away with just using
it on the new report, otherwise you'll have to go through all the Layouts
changing it. If the client is using a Windows computer, FileMaker may well
substitute the font back - not that anyone would notice the difference
anyway.
Helpful Harry :o)
making a new layout that you know uses only that font and make a PDF.
(Fonts embedded in logos for example can cause problems without you even
relaising they're being used.)
If it is that font, then try remove the "Helevtica55Roman" font from the
computer (quit and restart FileMaker, or even reboot the computer to make
sure it's gone). FileMaker will automatically use a close substitute which
may be unnoticeable.
If the automatic substitute doesn't work, then your best option is to
simply use normal Helvetica (I'm almost certain it's still one of the
Mac's default system fonts). You may be able to get away with just using
it on the new report, otherwise you'll have to go through all the Layouts
changing it. If the client is using a Windows computer, FileMaker may well
substitute the font back - not that anyone would notice the difference
anyway.
Helpful Harry :o)
cortical
Feb 4, 2012, 2:43:34 AM2/4/12
to
On 4/02/12 10:38 AM, Helpful Harry wrote:
> In article<jghq8o$d4m$1...@speranza.aioe.org>, cortical
> <c...@corticaldata.com.au> wrote:
>
>> Hi
>>
>> I have a client using Helevtica55Roman for a report, I am re-creating a
>> replicate report in a new FileMaker file to add to their (eslewhere
>> developed) solution. The report prints a PDF to desktop.
>>
>> I have sourced the font from a couple of places and reinstalled (free;
>> couldn't find a pay for version); but same problem, the 'o' letters do
>> not print on by Mac OSX.6 FM11Adv ; I haven't heard back from the client
>> testing yet ( probably will work for them).
>>
>> There is also a message about license
>>
>> <<
>> A font in this document is not licensed for embedding without permission
>> from the legal owner or font vendor. Depending on the font, blank text
>> may appear in the output file.
>> >>
>>
>> Well, there is only the Helvetica55Roman, and it was supposed to be
>> free, no indication of licensing requirements.
>>
>> Thoughts?
>>
>> Just for your amusement and edification, the solution is a 49 file set,
>> multiple tables per file; one table I looked at yesterday: 921 fields.
>
> Are you sure it's that font causing the error and not another one?
Yes
> In article<jghq8o$d4m$1...@speranza.aioe.org>, cortical
> <c...@corticaldata.com.au> wrote:
>
>> Hi
>>
>> I have a client using Helevtica55Roman for a report, I am re-creating a
>> replicate report in a new FileMaker file to add to their (eslewhere
>> developed) solution. The report prints a PDF to desktop.
>>
>> I have sourced the font from a couple of places and reinstalled (free;
>> couldn't find a pay for version); but same problem, the 'o' letters do
>> not print on by Mac OSX.6 FM11Adv ; I haven't heard back from the client
>> testing yet ( probably will work for them).
>>
>> There is also a message about license
>>
>> <<
>> A font in this document is not licensed for embedding without permission
>> from the legal owner or font vendor. Depending on the font, blank text
>> may appear in the output file.
>> >>
>>
>> Well, there is only the Helvetica55Roman, and it was supposed to be
>> free, no indication of licensing requirements.
>>
>> Thoughts?
>>
>> Just for your amusement and edification, the solution is a 49 file set,
>> multiple tables per file; one table I looked at yesterday: 921 fields.
>
> Are you sure it's that font causing the error and not another one?
Try
> making a new layout that you know uses only that font and make a PDF.
> (Fonts embedded in logos for example can cause problems without you even
> relaising they're being used.)
and a report layout. And the initial version of the layout, with
everything working, before I updated it for their corporate
Helvetica55Roman had no problems outputting A PDF.
>
> If it is that font, then try remove the "Helevtica55Roman" font from the
> computer (quit and restart FileMaker, or even reboot the computer to make
> sure it's gone). FileMaker will automatically use a close substitute which
> may be unnoticeable.
is to stick with their corporate image and expensive Agency specified
design parameters. Although FM is incapable of specifying 0.5 font sizes
such as 5.5 or 10.5.
>
> If the automatic substitute doesn't work, then your best option is to
> simply use normal Helvetica (I'm almost certain it's still one of the
> Mac's default system fonts).
You may be able to get away with just using
> it on the new report, otherwise you'll have to go through all the Layouts
> changing it. If the client is using a Windows computer, FileMaker may well
> substitute the font back - not that anyone would notice the difference
> anyway.
>
> Helpful Harry :o)
data entry.
Helpful Harry
Feb 4, 2012, 3:57:21 PM2/4/12
to
In article <jginj6$a0t$1...@speranza.aioe.org>, cortical
normal Helvetica and it should work - any differences between the two
fonts will be extremely minor and unnoticeable anyway.
There could be something on the layout using a different font. You could
try doing a Select All in Layout Mode and changing the font to somthing
else entirely (even a dingbat font), quitting FileMaker, then going back
in and changing the font back again, but I doubt it will make any
difference - it really a font issue and not a FileMaker one.
The only other possbility is to get a copy of the same font file(s) from
their computers, assuming it works there.
Helpful Harry :o)
<c...@corticaldata.com.au> wrote:
>
> There are no logos, this is a file that basically has a search layout
> and a report layout. And the initial version of the layout, with
> everything working, before I updated it for their corporate
> Helvetica55Roman had no problems outputting A PDF.
Which proves the point that particular font is the problem. Just use
>
> There are no logos, this is a file that basically has a search layout
> and a report layout. And the initial version of the layout, with
> everything working, before I updated it for their corporate
> Helvetica55Roman had no problems outputting A PDF.
normal Helvetica and it should work - any differences between the two
fonts will be extremely minor and unnoticeable anyway.
There could be something on the layout using a different font. You could
try doing a Select All in Layout Mode and changing the font to somthing
else entirely (even a dingbat font), quitting FileMaker, then going back
in and changing the font back again, but I doubt it will make any
difference - it really a font issue and not a FileMaker one.
The only other possbility is to get a copy of the same font file(s) from
their computers, assuming it works there.
Helpful Harry :o)
cortical
Feb 4, 2012, 8:16:18 PM2/4/12
to
On 5/02/12 7:27 AM, Helpful Harry wrote:
> In article<jginj6$a0t$1...@speranza.aioe.org>, cortical
> <c...@corticaldata.com.au> wrote:
>>
>> There are no logos, this is a file that basically has a search layout
>> and a report layout. And the initial version of the layout, with
>> everything working, before I updated it for their corporate
>> Helvetica55Roman had no problems outputting A PDF.
>
> Which proves the point that particular font is the problem.
I never had any doubt that it was the font.
> In article<jginj6$a0t$1...@speranza.aioe.org>, cortical
> <c...@corticaldata.com.au> wrote:
>>
>> There are no logos, this is a file that basically has a search layout
>> and a report layout. And the initial version of the layout, with
>> everything working, before I updated it for their corporate
>> Helvetica55Roman had no problems outputting A PDF.
>
> Which proves the point that particular font is the problem.
Just use
> normal Helvetica and it should work - any differences between the two
> fonts will be extremely minor and unnoticeable anyway.
It is a client specification. The client and the agency use the font
without issue.
>
> There could be something on the layout using a different font.
You could
> try doing a Select All in Layout Mode and changing the font to somthing
> else entirely (even a dingbat font), quitting FileMaker, then going back
> in and changing the font back again, but I doubt it will make any
> difference - it really a font issue and not a FileMaker one.
correctly, before redefining the fonts to Helvitac55Roman?
A: I did.
>
> The only other possbility is to get a copy of the same font file(s) from
> their computers, assuming it works there.
presumably got it from somewhere, somewhere that was capable of
supplying a font that works. So not the only other possibility.
This is Oz Harry, not the land of Nod.
End of transmission.
Helpful Harry
Feb 5, 2012, 12:07:05 AM2/5/12
to
In article <jgkl93$n54$1...@speranza.aioe.org>, cortical
This is not a fFileMaker problem - it's a font issue. I've given you a
solution, it's not my problem if you don't want to use it. If you're not
going to accept answers, then don't bother asking questions. I won't be
wasting any more of me own time with you again. :o\
Helpful Harry :o)
solution, it's not my problem if you don't want to use it. If you're not
going to accept answers, then don't bother asking questions. I won't be
wasting any more of me own time with you again. :o\
Helpful Harry :o)
John G
Feb 5, 2012, 12:43:21 AM2/5/12
to
on 5/02/2012, Helpful Harry supposed :
The dark side of OZ where the crows fly backwards to keep the sand out
of their eyes 8-o
--
John G
of their eyes 8-o
>>
>> End of transmission.
>
> This is not a fFileMaker problem - it's a font issue. I've given you a
> solution, it's not my problem if you don't want to use it. If you're not
> going to accept answers, then don't bother asking questions. I won't be
> wasting any more of me own time with you again. :o\
>
> Helpful Harry :o)
Harry I thought you were particularly patient.
>> End of transmission.
>
> This is not a fFileMaker problem - it's a font issue. I've given you a
> solution, it's not my problem if you don't want to use it. If you're not
> going to accept answers, then don't bother asking questions. I won't be
> wasting any more of me own time with you again. :o\
>
> Helpful Harry :o)
--
John G
Message has been deleted
Helpful Harry
Feb 5, 2012, 4:02:12 PM2/5/12
to
In article <slrnjis9aq.1...@ID-685.user.individual.de>,
tr...@gmx.de wrote:
>
> Personally, I agree that this font should be avoided.
> But that's not the answer for the customer.
The "customer" will not be able to tell the difference between
HelveticaXYZ97 and normal Helvetica - and if there's a problem with that
font, then they should be told so. If the font (supposedly) works on the
customer's computers, then why not get a copy of the font from them rather
than download dodgey versions from the Internet??
There's something very peculiar going on that is best to steer well clear
of, as well as some snotty person who won't even listen to answers or try
thing you give them as suggestions.
Helpful Harry :o)
tr...@gmx.de wrote:
>
> Personally, I agree that this font should be avoided.
> But that's not the answer for the customer.
The "customer" will not be able to tell the difference between
HelveticaXYZ97 and normal Helvetica - and if there's a problem with that
font, then they should be told so. If the font (supposedly) works on the
customer's computers, then why not get a copy of the font from them rather
than download dodgey versions from the Internet??
There's something very peculiar going on that is best to steer well clear
of, as well as some snotty person who won't even listen to answers or try
thing you give them as suggestions.
Helpful Harry :o)
Message has been deleted
cortical
Feb 5, 2012, 6:35:21 PM2/5/12
to
On 6/02/12 8:14 AM, Martin Τrautmann wrote:
> that has a very special "5" (Helevtica55Roman?). Maybe this single
> character was changed for a special look. I don't know, since I've never
> seen this font.
>
> It's a clear statement to me that the customer does insist on this very
> special font. I don't mind about the reasons, I just assume that there
> are some.
> that FMP has font issues and I accept that a customer does want a
> certain font.
>
> Personally, I'd argue, as you did, with the client whether another font
> could be ok. But the description sounds as if this discussion has been
> done before.
>
> - Martin
The font is mandated by the client; it is a 'corporate' font, they have
been using it for quite some time, it is part of the corporate style for
which they paid significant money to a PR agency to develop as part of
their corporate image.
The PDF files go to a professional print agency for assembly and
publication. So being a professional print agency they notice deviations
from specification.
To Harry; try reading my requirements.
> On Mon, 06 Feb 2012 10:02:12 +1300, Helpful Harry wrote:
>> In article<slrnjis9aq.1...@ID-685.user.individual.de>,
>> tr...@gmx.de wrote:
>>>
>>> Personally, I agree that this font should be avoided.
>>> But that's not the answer for the customer.
>>
>> The "customer" will not be able to tell the difference between
>> HelveticaXYZ97 and normal Helvetica
>
> How do you know? Maybe it's part of the corporate identity to use a font
>> In article<slrnjis9aq.1...@ID-685.user.individual.de>,
>> tr...@gmx.de wrote:
>>>
>>> Personally, I agree that this font should be avoided.
>>> But that's not the answer for the customer.
>>
>> The "customer" will not be able to tell the difference between
>> HelveticaXYZ97 and normal Helvetica
>
> that has a very special "5" (Helevtica55Roman?). Maybe this single
> character was changed for a special look. I don't know, since I've never
> seen this font.
>
> It's a clear statement to me that the customer does insist on this very
> special font. I don't mind about the reasons, I just assume that there
> are some.
>
>> There's something very peculiar going on that is best to steer well clear
>> of, as well as some snotty person who won't even listen to answers or try
>> thing you give them as suggestions.
>
> Something does go wrong within your communications. Personally, I know
>> There's something very peculiar going on that is best to steer well clear
>> of, as well as some snotty person who won't even listen to answers or try
>> thing you give them as suggestions.
>
> that FMP has font issues and I accept that a customer does want a
> certain font.
>
> Personally, I'd argue, as you did, with the client whether another font
> could be ok. But the description sounds as if this discussion has been
> done before.
>
> - Martin
The font is mandated by the client; it is a 'corporate' font, they have
been using it for quite some time, it is part of the corporate style for
which they paid significant money to a PR agency to develop as part of
their corporate image.
The PDF files go to a professional print agency for assembly and
publication. So being a professional print agency they notice deviations
from specification.
To Harry; try reading my requirements.
cortical
Feb 5, 2012, 6:45:49 PM2/5/12
to
On 5/02/12 5:14 PM, Martin Τrautmann wrote:
>
> I had serious problem myself where FMP created huge PDFs since it did
> include the font definitions again and again.
>
> Another problem is that monospaced font in FMP no longer show as
> monospaced.
>
> Thus there ARE problems with FMP and its font handling.
>
> The named font here is a non-standard font. It's of unclear quality. It
> may work with other applications, but it's broken in FMP. So maybe the
> font is broken, maybe it's FMP.
>
> However, how where the PDFs created? There are at least three different
> ways on Mac to get it done:
>
> 1) let FMP create the PDF
> 2) print and save it as PDF
> 3) use preview
routine save records as pdf form a script
>
> Another choice: do the process on another Platform, Mac vs. PC
It needs to be cross platform. Only tested on a mac on this point
>
> Which way did create the broken PDF? And which other ways where tried by
> now?
>
only option 1 is viable
> On Sun, 05 Feb 2012 18:07:05 +1300, Helpful Harry wrote:
>> This is not a fFileMaker problem - it's a font issue.
>
> It could be very well that this is a FMP problem.
>> This is not a fFileMaker problem - it's a font issue.
>
>
> I had serious problem myself where FMP created huge PDFs since it did
> include the font definitions again and again.
>
> Another problem is that monospaced font in FMP no longer show as
> monospaced.
>
> Thus there ARE problems with FMP and its font handling.
>
> The named font here is a non-standard font. It's of unclear quality. It
> may work with other applications, but it's broken in FMP. So maybe the
> font is broken, maybe it's FMP.
>
> Personally, I agree that this font should be avoided.
> But that's not the answer for the customer.
Quite so.
> Personally, I agree that this font should be avoided.
> But that's not the answer for the customer.
>
> However, how where the PDFs created? There are at least three different
> ways on Mac to get it done:
>
> 1) let FMP create the PDF
> 2) print and save it as PDF
> 3) use preview
routine save records as pdf form a script
>
> Another choice: do the process on another Platform, Mac vs. PC
It needs to be cross platform. Only tested on a mac on this point
>
> Which way did create the broken PDF? And which other ways where tried by
> now?
>
only option 1 is viable
Message has been deleted
cortical
Feb 6, 2012, 5:16:20 PM2/6/12
to
On 6/02/12 5:41 PM, Martin Τrautmann wrote:
> create faulty PDFs on its own and whether there's another choice to
> create proper PDFs at all.
>
> How about other programs on the Mac? Are they ok? Did you make sure that
> it's not the Mac version of the font which is broken?
>
> Either you give up and hope that FileMaker will fix a bug in FMP 12
> (which they won't if they don't know about) or you narrow it down where
> the bug does come from, in order to prevent this bug from happening.
>
> A hardcore solution might be to replace just the single, faulty
> character by another font. I'm afraid this might look more terrible than
> a complete switch of fonts. But I don't know this special Helvetica
> version you refer to.
>
> First step should be to try it on a PC...
>
> - Martin
LibreOffice and TextWrangler have no problem displaying the font, or
Save as PDF from the OS Print menu.
Similarly File>Print>Save as PDF from FileMaker also works without error.
From a clean new test FMP file with a single field, and a single
layout, and a single script with a single default line ( save records as
PDF) , the same error as previously in the client file.
<<
A font in this document is not licensed for embedding without permission
from the legal owner or font vendor. Depending on the font, blank text
may appear in the output file.
>>
So that rather looks like FileMaker issue of some sort.
However, just discovered in Font Book, selecting the Font, right click
contextual menu has a Validate Font option, and this reports a warning
under Warnings or Errors for 'kern' table structure and contents;
and under "No Warnings or Errors another 15 parameters that are ok.
Downloaded the same font (Helvetica_55_Roman.ttf) yet again, from yet
another source ( Fonster), and installed, and this (also free) version,
has no reported warnings in Font Book, and with FM quit and the file
re-opened ( to reset the font to the default Verdana, reapplying the
Helvetica55Roman , save as pdf executes without error.
So, a subtle issue with the particular instance of the font ( from
several different sources ) which the system Print As PDF can deal with
and print without error, but FileMaker has a problem displaying a
character 'o', and also FM scripted Save Records as PDF.
The same truetype font (same filename) form a different source works
without error under the same scenario.
A helpful, and polite individual from another source also pointed out
the licensee source Linotype, as a means of purchasing an original copy
of the font.
> On Mon, 06 Feb 2012 10:15:49 +1030, cortical wrote:
>>> However, how where the PDFs created? There are at least three different
>>> ways on Mac to get it done:
>>>
>>> 1) let FMP create the PDF
>>> 2) print and save it as PDF
>>> 3) use preview
>>
>>
>> routine save records as pdf form a script
>
>>> Another choice: do the process on another Platform, Mac vs. PC
>>
>> It needs to be cross platform. Only tested on a mac on this point
>
>>> Which way did create the broken PDF? And which other ways where tried by
>>> now?
>>
>> only option 1 is viable
>
> You should give the other choices a try, to make sure whether FMP does
>>> However, how where the PDFs created? There are at least three different
>>> ways on Mac to get it done:
>>>
>>> 1) let FMP create the PDF
>>> 2) print and save it as PDF
>>> 3) use preview
>>
>>
>> routine save records as pdf form a script
>
>>> Another choice: do the process on another Platform, Mac vs. PC
>>
>> It needs to be cross platform. Only tested on a mac on this point
>
>>> Which way did create the broken PDF? And which other ways where tried by
>>> now?
>>
>> only option 1 is viable
>
> create faulty PDFs on its own and whether there's another choice to
> create proper PDFs at all.
>
> How about other programs on the Mac? Are they ok? Did you make sure that
> it's not the Mac version of the font which is broken?
>
> Either you give up and hope that FileMaker will fix a bug in FMP 12
> (which they won't if they don't know about) or you narrow it down where
> the bug does come from, in order to prevent this bug from happening.
>
> A hardcore solution might be to replace just the single, faulty
> character by another font. I'm afraid this might look more terrible than
> a complete switch of fonts. But I don't know this special Helvetica
> version you refer to.
>
> First step should be to try it on a PC...
>
> - Martin
LibreOffice and TextWrangler have no problem displaying the font, or
Save as PDF from the OS Print menu.
Similarly File>Print>Save as PDF from FileMaker also works without error.
From a clean new test FMP file with a single field, and a single
layout, and a single script with a single default line ( save records as
PDF) , the same error as previously in the client file.
<<
A font in this document is not licensed for embedding without permission
from the legal owner or font vendor. Depending on the font, blank text
may appear in the output file.
>>
However, just discovered in Font Book, selecting the Font, right click
contextual menu has a Validate Font option, and this reports a warning
under Warnings or Errors for 'kern' table structure and contents;
and under "No Warnings or Errors another 15 parameters that are ok.
Downloaded the same font (Helvetica_55_Roman.ttf) yet again, from yet
another source ( Fonster), and installed, and this (also free) version,
has no reported warnings in Font Book, and with FM quit and the file
re-opened ( to reset the font to the default Verdana, reapplying the
Helvetica55Roman , save as pdf executes without error.
So, a subtle issue with the particular instance of the font ( from
several different sources ) which the system Print As PDF can deal with
and print without error, but FileMaker has a problem displaying a
character 'o', and also FM scripted Save Records as PDF.
The same truetype font (same filename) form a different source works
without error under the same scenario.
A helpful, and polite individual from another source also pointed out
the licensee source Linotype, as a means of purchasing an original copy
of the font.
Message has been deleted
0 new messages