Re: [docbook-apps] Odd Characters in UTF-8, Docbook 5.1

[stimits]

Hi,
 
Thank you everyone! With the info on that fop configuration for custom setup I 
was able to get fop to actually use the xconf fileso much trouble because I 
had thought fop had been using the standard system configuration file by 
default, but it does not. Edits to use the required font mentioned in earlier 
replies now works...it just goes to show...be careful what you edit, it might 
not be the file being used! Fonts now work as they should and include the 
previously missing glyphs.
 
The quick workaround is to add the "-c /usr/share/fop/conf/fop.xconf". That 
custom font script though adds a lot to making sure doc builds are more 
predictable.
 
I think I do need to ask the fop people why the dump of current configuration 
details fails. If this had been working I might have seen earlier that the 
expected xconf file was not used...I'm still curious as to where its 
configuration is really from. The base-14 fonts are standard so perhaps no 
config file was used at all and these are just built in...fop just doesn't want 
to tell me about its configuration.
 
Thanks!
 
- Original Message -From: DeanNelson@aol.comTo: stim...@comcast.net, 
docbook-apps@lists.oasis-open.orgSent: Fri, 03 Feb 2017 01:38:19 - 
(UTC)Subject: Re: [docbook-apps] Odd Characters in UTF-8, Docbook 5.1


I use DejaVu fonts with FOP on both Windows and Linux.
 
I use my own config file via "-c configFile.xml" switch with FOPs command line 
to override the standard config. The integration with DejaVu fonts is pretty 
straight forward.
 
This may help you - attached is part of the script that I use on Linux to call 
FOP and also the configuration file.
 
You should be able to comment out the DejaVu parts of the config file and see 
your fonts return to default. If not, I would check the fop script that starts 
FOP.  (using 'which fop' to locate it)
 
Good luck.
 
Dean Nelson
 
 

In a message dated 2/2/2017 2:19:16 P.M. Pacific Standard Time, 
stim...@comcast.net writes:

This is turning out to be odd...I have to conclude that fop is not  reading any 
configuration files...especially none named "fop.xconf". The short  story is 
that I can intentionally introduce errors in fop.xconf (all  occurrences on the 
computer as verified by updatedb and locate .xconf),  introduce 
"true", and  no mention of 
anything different occurs. I can run this under strace, and I  see no calls at 
all referring to opening any xconf file (nor any attempt to do  so). Somehow I 
need to figure out how fop is configured since the installed  xconf files are 
ignored.
 
Here's a summary of how I go there:
 
The DejaVuSans fonts do contain the character glyphs, and this is what  I've 
been trying to switch to instead of Helvetica for the sans-serif.
 
It was determined that param.xsl picks between serif and sans-serif by  naming 
one of these:
serif
sans-serif
 
When changing between serif and sans-serif vi param.xsl edits, it is  verified 
that that either Times or Helvetica are used upon switch. This works  as 
expected.
 
I added the fop option "-d" to debug...this did not indicate any error,  though 
it was more explicit about not finding glyphs. After that I tried the  
strict-configuration modification. No change. I looked for any possible  
occurrence of fop.xconf, these two exist (I don't know how they differ), I  
intentionally tried to break both for warning information:
/usr/share/fop/conf/fop.xconf/usr/share/publican/fop/fop.xconf 
This had no effect, so this is when I tried strace. It seems fop does not  use 
external configuration file searches, and I don't know why...so I can't  
actually add DejaVuSans. I'm currently trying to figure out where there is a  
mailing list or other support for fop. Incidentally, the "fop -x" command to  
dump configuration fails...it wants an input file or it won't tell me anything  
about configuration.
 
Thanks everyone for the help!
 
- Original Message -From: Dave Pawson  To: 
Richard Hamilton 

Cc: stim...@comcast.net, Docbook  
Sent: Thu, 02 Feb 2017 06:37:36  - 
(UTC)Subject: Re: [docbook-apps] Odd Characters in UTF-8, Docbook  5.1

Perhaps start where the problem is. Look for a font which containsthe  glyphs 
for the Unicode code points you want to use. Check thecode points  produce the 
glyphs you want.Find out how the app (fop and any others you  use in your tool 
chain)selects fonts.Run the app knowing that the font  has what you want and 
your codepoints are correct.

HTH

On 1 February 2017 at 23:44, Richard Hamilton   wrote:> 
Im getting out of my depth on  fop, so maybe someone else on the list 
can help here.>> However,  diving in deeper than I should:-)I suspect the 
problem is number  1.>> I suggest running fop with the -d (debug) mode, and you 
 might also try -x, which will dump the configuration; that way you can see if  
the configuration fop uses is what you 

Re: [docbook-apps] Odd Characters in UTF-8, Docbook 5.1

[Dave Pawson]

https://xmlgraphics.apache.org/fop/maillist.html is the fop mailing list,
if your issue is simply with fop?

regards

On 2 February 2017 at 22:19,   wrote:
> This is turning out to be odd...I have to conclude that fop is not reading
> any configuration files...especially none named "fop.xconf". The short story
> is that I can intentionally introduce errors in fop.xconf (all occurrences
> on the computer as verified by updatedb and locate .xconf), introduce
> "true", and no mention of
> anything different occurs. I can run this under strace, and I see no calls
> at all referring to opening any xconf file (nor any attempt to do so).
> Somehow I need to figure out how fop is configured since the installed xconf
> files are ignored.
>
> Here's a summary of how I go there:
>
> The DejaVuSans fonts do contain the character glyphs, and this is what I've
> been trying to switch to instead of Helvetica for the sans-serif.
>
> It was determined that param.xsl picks between serif and sans-serif by
> naming one of these:
> serif
> sans-serif
>
> When changing between serif and sans-serif vi param.xsl edits, it is
> verified that that either Times or Helvetica are used upon switch. This
> works as expected.
>
> I added the fop option "-d" to debug...this did not indicate any error,
> though it was more explicit about not finding glyphs. After that I tried the
> strict-configuration modification. No change. I looked for any possible
> occurrence of fop.xconf, these two exist (I don't know how they differ), I
> intentionally tried to break both for warning information:
> /usr/share/fop/conf/fop.xconf
> /usr/share/publican/fop/fop.xconf
>
> This had no effect, so this is when I tried strace. It seems fop does not
> use external configuration file searches, and I don't know why...so I can't
> actually add DejaVuSans. I'm currently trying to figure out where there is a
> mailing list or other support for fop. Incidentally, the "fop -x" command to
> dump configuration fails...it wants an input file or it won't tell me
> anything about configuration.
>
> Thanks everyone for the help!
>
> - Original Message -
> From: Dave Pawson 
> To: Richard Hamilton 
> Cc: stim...@comcast.net, Docbook 
> Sent: Thu, 02 Feb 2017 06:37:36 - (UTC)
> Subject: Re: [docbook-apps] Odd Characters in UTF-8, Docbook 5.1
> Perhaps start where the problem is. Look for a font which contains
> the glyphs for the Unicode code points you want to use. Check the
> code points produce the glyphs you want.
> Find out how the app (fop and any others you use in your tool chain)
> selects fonts.
> Run the app knowing that the font has what you want and your code
> points are correct.
> HTH
> On 1 February 2017 at 23:44, Richard Hamilton  wrote:
>> I’m getting out of my depth on fop, so maybe someone else on the list can
>> help here.
>>
>> However, diving in deeper than I should:-)I suspect the problem is number
>> 1.
>>
>> I suggest running fop with the -d (debug) mode, and you might also try -x,
>> which will dump the configuration; that way you can see if the configuration
>> fop uses is what you think it is using.
>>
>> Good luck,
>> Dick
>> ---
>> XML Press
>> XML for Technical Communicators
>> http://xmlpress.net
>> hamil...@xmlpress.net
>>
>>
>>
>>> On Feb 1, 2017, at 15:21, stim...@comcast.net wrote:
>>>
>>> Hi,
>>>
>>> So what my experimenting shows so far for trying to change font is that I
>>> can adjust param.xsl and switch between serif or sans-serif. The result
>>> depends on what is available in fop.xconf which lists Times-Roman for serif,
>>> and Helvetica for sans-serif. I've attempted to add an additional font
>>> definition for DejaVuSans by the following inside the  of fop.xconf:
>>>
>>> 
>>> 
>>> 
>>> 
>>>
>>> I am unable to name "DejaVuSans" instead of "sans-serif" in param.xsl (it
>>> falls back to Symbol). I see three possibilities...
>>> 1. My DejaVuSans declaration is wrong.
>>> 2. I have to remove Helvetica in fop.xconf from the sans-serif listings.
>>> 3. The Docbook parameters you mentioned are somewhere outside of
>>> fop.xconf or param.xsl.
>>>
>>> It seems unlikely I need to remove Helvetica, more likely there is
>>> another configuration elsewhere. However, I don't see any occurrence of
>>> "Helvetica" in any of the other Docbook files under the
>>> "stylesheet/docbook-xsl-ns-1.79.1/" directory tree which are related to this
>>> case (for example, there is a subdirectory for "slides" which would seem to
>>> be unrelated to the "book" being published to pdf). The full path to the ttf
>>> font file is available and readable to everyone; this is verifiable with a
>>> font editor (one reason to choose DejaVu is that the font editor actually
>>> shows the desired box drawing font glyphs at index 0x2500 and on).
>>>
>>> Am I missing another file to edit, or am I simply using the wrong syntax
>>>