Created attachment 58346 [details] Figure 1 Pro Optical fonts are collections of fonts that include up to 32 optical size variants for the caption, regular, subhead and display character sizes. So, for example, the 'Caption' size would include: '(regular) Caption', 'Light Caption', 'Italic Caption', 'Light Italic Caption', 'Bold Caption', 'Semibold Caption', 'Bold Italic Caption' and 'Semibold Italic Caption'; so on for the other size variants. (I'm using the Jenson font family for this example.) In the attachment (Figure 1), The 'Character' panel shows the 'Adobe Jenson Pro (regular)' font family selected. You can see, also, that below the selection there're more Jenson font variants available, such as 'Pro Capt', 'Pro Disp', etc. The 'typeface' area is however showing the 'caption' option selected when it should be showing the 'regular' option instead. Note that the 'regular' option is not present on this list, nor anywhere else (in the spanish langpack this one would appear as the 'predeterminada' option). So, the content is scrambled. I've noted that something similar occurs when using Libre Office in English, too. This bug doesn't prevent using the font, but prevents using the font correctly in the document; that's the issue.
Bug persists as of LO release v3.5.3
Hello Marcelo Cárdenas, thank you for your report! I'm looking into this issue ... and will comment if I come out with some results. Resetting the 'Version' field back to 3.5.1 release (please note that the 'Version' field should contain the first version in which a bug appears, not the last one).
(In reply to comment #2) > I'm looking into this issue ... and will comment if I come out with some > results. I had no luck in reproducing this issue. But this does not mean that this bug does not exist. Everybody else who has got access to some Adobe Pro Optical Fonts, please try to reproduce this issue so that we can get it confirmed! Thank you very much!
Hi Marcelo, I cannot confirm this bug, since I do not have any of the fonts in question on my system. Can you please provide a test document so this can be tested against and subsequently be confirmed. If that's not an option, did you retry with the latest LO release 4.1.3.2. Does that change anything? Also it might be worth giving the latest nightly a try. http://dev-builds.libreoffice.org/daily/master/MacOSX-x86@49-TDF/current/ Setting to NEEDINFO until more detail is provided. After providing the requested info, please reset this bug to UNCONFIRMED. Thanks :)
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team
@Marcelo: it would be great if your could check out a newer version of LibreOffice and see whether this problem still happens for you. In general, LibreOffice needs to improve its font variant management. See related bug 66792.
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of FDO Message generated on: 2015-02-11