Created attachment 22651 [details]
Part of the screenshot exhibiting the effect of SMallCaps instead of roman

reassigned to US.

norbusan, could you pls. provide a pointer where to get the "expert font set".
Thanks in advance.

Set target milestone to 'OO.o 2.0.1'.

Getting `free' expert font sets is difficult, because they have to be bought
from Adobe, Bitstream, or some other font source. The only option I see is the
following to prepare `free' fonts: I (or you) take the free ScOSF fonts
FreePalladio (from CTAN), rewrite the FontName in the afm and pfb file (with
fontforge) and then you use these fonts instead of the original Adobe ones.
Other options I don't see ATM.
If you need more information, help, I hope I can provide it.

Hacking the freely available substitutes is not my preferred approach for
various reasons.

Let's determin what this issue is about:
I guess you selected "Palatino", expecting "Palatino Roman" and get "Palatino
Small Caps", right? 
Or what are the real font family names stated in the AFMs, respective what are
the font fammily names OO.o displays?

Additionally, you probably are allowed to attach at least one AFM, as this was
the idea behind dividing a font into a metrics file and the font file itself.

The following fonts are installed:
pplr8a:
FontName Palatino-Roman
FullName Palatino Roman
FamilyName Palatino

and pplrc8a:
FontName Palatino-SC
FullName Palatino Small Caps & Old Style Figures
FamilyName Palatino

I select "Palatino" in OOo and get for Roman (no BOld/Italic button pressed) the
small caps font, for italic and bold italic and bold I get the right fonts. When
I export the file into a pdf, I get the SmallCaps font and not the standard roman.

Concerning the afm: Can I send it wiht PM, I am not sure wether this is allowed
and I don't want to post them in a public forum, sorry. You can contact me unter
preining@logic.at

US:->HDU: Palatino-SC probably gets stripped to Palatino which results in mixing
it up with Palatino-Roman which presumably also got stripped to Palatino.

Can you perhaps provide a workaround for the time being until we have a fix? Thanks.

Hm, thought of this again and came to the conclusion that font family name
stripping is probably not the root cause. 
The issue is probably more related to the fontconfig api we use and the family
name and attributes we parse from there or not.

After adding pplrc8a.pfb and pplrc8a.afm:

fc-list | grep Palatino
Palatino:style=Small Caps & Old Style Figures
This is shown as "Palatino" in OO.o Writer m78.8875.

Hence the problem is that we currently don't parse the additional style info
provided by fontconfig which leads to the situation that we can not distinguish
between Palatino SC and Palatino Roman.

=>Enhancement (we had on our list anyway, dont't we PL?)

pl->us: The style names are now delivered to vcl; but please check if that
actually fixes the problem. The user could now select the additional style in
Format->Character, but still the small caps font should not be used initially.

fixed in CWS vcl39

Sorry, maybe I am too stupid, but how can I check this? I guess there are no
builds available up to now for the fixed version?!

Thanks a lot and all the best

norbusan: sorry, but you can't at all at the moment; the fix currently just
exists in the CWS vcl39, install sets of which are not currently available. US
will check the issue as soon as install sets exist. If you want to check now you
would have to check out and compile the changes yourself. Alternatively i could
send you libraries containing the change which you could copy into an existing
680m87 installation.

@pl: If you want I could try, but I cannot find 680m87 on the web. The latest
snapshot build is m84 (according to
http://download.openoffice.org/680/index.html). So if you want me to try, send
me the libs to preining@logic.at and tell me where I can find 680m87.
Thanks and all the best
Norbert

Hi pl!
I installed 680m84 and the new libraries and get the same effect: If I do *not*
select any style, then I get small caps.
Interestingly I cannot select the normal "Medium" or "Roman" style from the
Format->Character. Asking my fontconfig I get the following styles for Palatino:
Palatino:style=Light Italic
Palatino:style=Bold Italic
Palatino:style=Medium Italic
Palatino:style=Bold
Palatino:style=Black Italic
Palatino:style=Small Caps & Old Style Figures
Palatino:style=Italic
Palatino:style=Black
Palatino:style=Roman
Palatino:style=Medium
Palatino:style=Light

But in OOo the following are missing:
Roman, Medium, Medium Italic.

I suppose that Medium Italic is subsumed under Italic.
But The problem persists that I cannot select a Medium/Roman font without
getting SmallCaps. In fact if I only select Palatino from the drop down list,
type in some text, and then select the text, Format->Char I see that it is
selected as Small Caps & Old Style Figures Style.

So we are now at a level where it is working more or less, i.e. the Expert fonts
are recognized, but the problem persists, because no Roman/Normal font is found!

All the best

Norbert

I'm not that surprised. Adding the style names wouldn't change the default
behaviour.

pl->hdu: i think that's an ImplFontCache::Get problem. Could you please have a
look ?

HDU->HDU reminder: For a font request with an emtpy style name the available
font with "medium" style style should win...

Hi all!
Some new stuff, or better report on the current milestone m91. I have tested m91
with my fonts and found, that it is getting worse ;-)
First some explanation: There are three (maybe more) types of professional font
sets: 
class 1a: SmallCaps&OsF, example: Palatino:style=Small Caps & Old Style Figures,
these fonts contain the Capitals at the right places, old-style numerals with
afm names "one" "two" ... at the position of the numbers, and SmallCaps with afm
names "a" "b" etc at the positions of the lower case letters

class 1b: OsF, example: Palatino:style=Italic Old Style Figures, these fonts
contain the Capitals at the right places, old-style numerals with afm names
"one" "two" ... at the position of the numbers, and normal lower case letters at
the right positions (difference to 1a: no small caps!)

Class 2: Expert sets, example: Minion:style=Regular Expert, but also
Utopia:style=Expert Regular, these fonts contain old style numerals with afm
names "oneoldstyle" "twooldstyle" .. at the positions of the numbers, Small Caps
with afm names "Asmall" "Bsmall" etc at the position of the lower case letters,
but now upper case letters.

So, I made tests with M91 and these three types:
class 1a and 1b now are shown correct on screen, are printed correctly, but NOT
correctly exported to pdf (interestingly! but true). The Expert font can not be
selected to get real caps or oldstyle numerals.

For class 2 I got very mixed results: None of it goes correctly to the printer
nor into the pdf files, so all of them just are not right. But Minion and Adobe
Garamond are displayed correct, while Utopia completely collapses and is
displayed in fixed font (in 2pt or something, unreadable). Here the expert fonts
can be selected for AGaramond and Minion, and correctly show caps/oldstyle nums.

So you are partly on the way to fixing it, but the there are still several problems:
- Parsing of the font names is still very problematic. Some fontnames just make
the parser go havoc (Expert Utopia).
- Printing/PDF making still is a real problem, definitely not usable
- Usage of class 1 variant fonts is not possible, while those of class 2
variants is usable.

Best wishes, and I hope I can help you a bit!

Norbert

retargeting

retargeted due to resource constraints

i don't see how you can ever succeed trying to map an arbitrary set of styles
into regular/italic/bold/bolditalic.

i think the proper solution to this problem is a 2-stage selection, where one
pull-down menu selects the font family, and a second pull-down menu then
displays all the styles available for that family. in this case, there are 14 of
them. Adobe InDesign on PC/Pac does exactly this. a more cumbersome alternative,
but still superior to the current situation, is to enumerate all family/style
combinations in one pull-down menu. Scribus on Linux does this.

at present, many, many high-quality, professional fonts are simply unusable with
OOo Writer. IMHO, fixing this should be a high priority.

Very similar, if not a dupe of issue #79878

Good point, this is indeed duplicate to the infamous issue 79878. That issue is more up to date and assigned to the 
right team, so it is best to resolve this one as the duplicate one.

*** This issue has been marked as a duplicate of 79878 ***

Closing resolved issue.