https://bugs.documentfoundation.org/show_bug.cgi?id=35538
--- Comment #64 from Eyal Rozenberg <eyalr...@gmx.com> --- (In reply to خالد حسني from comment #63) > even if we switch to something else, we will need > to emulate the old naming scheme otherwise existing documents using it will > be broken. We will only need to do that for documents created before the switch to proper recognition of fonts within a family. But in the UI, and new documents, that should not be a problem. I may be wrong about ODF support, though, since I don't know the ODF spec, so if there are issues there, please mention them. > Adding more options is dodging the issue (by exposing the internal to the > user) not fixing it. It is fixing the issue, because it will allow proper handling of multiple variants of font families. Whenever we have a feature which MS Office doesn't - we can either let our files always break in MS-Office (bad), or drop that feature (also bad - features should not be dictated by Microsoft, especially whe they get things wrong), or distinguish somehow between whether we need to save with or without MS compatibility. But actually... perhaps it _is_ possible to save both kinds of information at the same time. i.e. save the MSO-compatible font info we do today, but also save some meta-data that MS doesn't use, but we can use, which tells us what the real font variants are. What do you think? > It isn’t only MS Office, but versions of LibreOffice on > Windows before the fix, and probably other Windows office suites. Yes, these may all need a compatibility mode when saving in MSO-targeting formats. If it's ODF files - it's no different than saving in a newer version of ODF which is unsupported by older versions of LO. > My inclination is to keep things simple and do it the MS way. But, again, > that is not my call. This is a significant missing feature in LO, and was recognized as NEW, so the question IMNSHO is how to best do this, rather than if it should be done. Actually, it goes beyond just that: The choice of some SW makers, in the 1980s or early 1990s, to arbitrarily force the 2x2 style space, is a historic blunder. It needs to be fixed in all personal computing applications. Our not fixing this is holding back others as well, and is mis-educating users about fonts. -- You are receiving this mail because: You are the assignee for the bug.
