[Libreoffice-bugs] [Bug 101889] Using OpenSymbol font with proper codepage in Linux

2020-11-08 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=101889

--- Comment #12 from V Stuart Foote  ---
remains an issue

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 101889] Using OpenSymbol font with proper codepage in Linux

2020-07-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=101889

Timur  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=13
   ||4214

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 101889] Using OpenSymbol font with proper codepage in Linux

2020-07-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=101889

--- Comment #11 from QA Administrators  ---
Dear Aron Budea,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 101889] Using OpenSymbol font with proper codepage in Linux

2018-07-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=101889

--- Comment #10 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 101889] Using OpenSymbol font with proper codepage in Linux

2017-07-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=101889

Xisco FaulĂ­  changed:

   What|Removed |Added

 CC||xiscofa...@libreoffice.org
   Assignee|mikekagan...@hotmail.com|libreoffice-b...@lists.free
   ||desktop.org

--- Comment #9 from Xisco FaulĂ­  ---
Setting Assignee back to default. Please assign it back to yourself if you're
still working on this issue

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 101889] Using OpenSymbol font with proper codepage in Linux

2016-09-06 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=101889

Mike Kaganski  changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |mikekagan...@hotmail.com
   |desktop.org |

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 101889] Using OpenSymbol font with proper codepage in Linux

2016-09-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=101889

--- Comment #4 from Mike Kaganski  ---
Posted a patch to gerrit: https://gerrit.libreoffice.org/28677

I managed to avoid using external fonts as source of absent glyphs, using and
modifying OpenSymbol's own glyphs.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 101889] Using OpenSymbol font with proper codepage in Linux

2016-09-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=101889

--- Comment #3 from Mike Kaganski  ---
It's not that straightforward to fix the font substitution.
The actual used font is selected in ImplFontCache::GetFontInstance() and
PhysicalFontCollection::FindFontFamily(). The latter performs several steps,
and on my system, it finds OpenSymbol as Symbol's replacement at
rFontSubst.getSubstInfo( aSearchName ). There, it searches for exact match of
searched name in sorted list. If it wouldn't find OpenSymbol here, e.g. by
explicit break for Symbol search, then PhysicalFontCollection::FindFontFamily()
will use next method: for symbol fonts, it uses LO configuration
org.openoffice.VCL:LocalizedDefaultFonts['lang'].SYMBOL, that is a list of
fonts: on my system, it is StarSymbol;OpenSymbol;Arial Unicode MS;StarBats;Zapf
Dingbats;WingDings;Symbol. If I add e.g. Standard Symbols L to the head of the
list, then "it works".

To fix it properly, I think, two things are necessary:
1. To update OpenSymbol (that is LO native font, and so it must support the
necessary glyphs itself, instead of hoping that some system font will happen to
have those). I wonder if just copying those glyphs from Standard Symbols L is
OK? According to https://en.wikipedia.org/wiki/Ghostscript, the font is either
GPL or AFPL.
2. The first step alone if not a proper fix: if user installs a font with a
name that will intercept the search in the above-mentioned algorithm, then
OpenSymbol won't be selected. So, some hardcoding may be necessary.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 101889] Using OpenSymbol font with proper codepage in Linux

2016-09-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=101889

Mike Kaganski  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=39
   ||256

--- Comment #2 from Mike Kaganski  ---
This problem is described as #6 in bug 39256.
As that bug looks more like a meta-bug for tracking WMF-related problems, I add
it as "See Also" and will work on it here.

Further analysis shows that my previous statements need correction.
1. Always using 1252 doesn't work for Windows; I must had been dreaming when
wrote that it worked under Win10. So, the only way to fix this by selecting
encoding is conditional compilation (symbol charset for Windows, 1252 for
Linux).
2. OpenSymbol doesn't contain necessary glyphs for brackets/braces/parentheses.
Standard Symbols L actually does. When Symbol font encoding is set to 1252,
Standard Symbols L is used by LO, while for symbol encoding, OpenSymbol is
used, with recoding using utilities from unotools/source/misc/fontcvt.cxx. I
see preferable way to fix this by enabling LO to substitute Standard Symbols L
for Symbol font when symbol charset is used.
3. MT Extra problem mentioned above (and in bug 39256 #6) is fixed by using
symbol encoding, works both for Windows and Linux (MacOS isn't tested).

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 101889] Using OpenSymbol font with proper codepage in Linux

2016-09-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=101889

Aron Budea  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 CC||mikekagan...@hotmail.com
 Depends on||99402
 Ever confirmed|0   |1
 OS|All |Linux (All)

--- Comment #1 from Aron Budea  ---
Mike, thanks for your analysis in bug 99402, here's the new bug report as
requested. Please adjust component if a different one is more suitable.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=99402
[Bug 99402] FORMATTING_Black question mark for Mathtype symbols (Brackets)
-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs