Hi *, On Sat, Aug 19, 2006 at 12:40:33AM +0900, tora wrote: > > What do you want to discuss first, or something else? > - Listing unknown font names in the font name substitution dialog
That is impossible You cannot even list every known font. There are billions of fonts out there.... > - Disclosing a real font name for rendering a preview text Indicating font-fallback and glyphfallback already has issues filed. But I don't know why you would only do this in a preview text. So maybe I got you wrong. > - Language tuned predefined font name substitution This is already the case. OOo already can do and already does do this. > - Font file discovery procedure ?? more info please. OOo uses fontconfig now, so that should no longer be an issue, should it? > - Virtual font name Again: What is that, what would it be useful for? > - Fake font name for targeting platforms Again: Why would you do that? What would that do/How would you do that? > - Font name replacement in an export filter Not really sure whether this would helpful. At least it would be a pain to set-up. > - Listing unknown font names in the font name substitution dialog > [skipped - see above] > > - Disclosing a real font name for rendering a preview text > [skipped - see above] > > - Language tuned predefined font name substitution > > Current implementation has a predefined list of font substitution, > but the list is generally defined regardless of the language in > which a document is written. No - see VCL.xcu. There are already several language-specific replacement lists. If you want to improve that list, file an issue and provide the fonts that should be used instead. > - Font file discovery procedure > > With current implementation, OOo always finds a font file to render texts. > That would be controversial. Please consider the following two facts: > > 1) Assume that a font name specified in a document is MS Micho and you > computer has a font named Kochi Mincho. You might want OOo to > automatically use Kochi Mincho for MS Mincho to render texts. Use Font-Replacement. This is exactly for things like that. > 2) Manually filling a font name box with a nonexistent font name like a > single letter x or some letters like "Hello World" sounds no sense, > but current OOo chooses a font in any way to render texts. > > In the case 2, some might want OOo not to render texts but to show special > characters such as a rectangle or question mark meaning that no appropriate > glyph is available. No, then you would get that whenever you import a document that was written on another computer, with different fonts set for the characters. > [...] > - Virtual font name > > This is an idea by someone in the Japanese community. Users specify virtual > font names in their document and OOo will automatically choose appropriate > physical font files installed in their computer. The virtual font names do > not depend on users' platform. Exchanging document files between different > computer environments or platforms is being demanded. So, we can try not to > rely on physical font names when authoring documents. > > The virtual font names would be Arial, Courier, Helvetica, Times,... for > Western, > Mincho, Gothic, PMincho (Proportional one), PGothic for CJK,... and so on. Bad idea IMHO. What would that be good for anyway? OOo doesn't ship fonts, so these documents will look different on every computer, depending on the fonts installed. And since you can enter anything in the font-tab (i.e. set a non-installed font for your document) this can already be done. > How does it work? For example, a virtual font Mincho for Japanese document > will be MS Mincho on Windows, Kochi Mincho on Linux. The same font Mincho > for Korean document will be something on Windows, Micho on Linux. No, bad idea. You try to compensate lack of predefined font-replacement tables with that approach. Either you use the font that is installed and set into the document (and have the document look like it was intended) or you have to fall back on another font. Further up you wrote how bad it is to use Korean fonts for japanese documents and the other way round - here you write that you want to set the same font and then depend on the user's system. Sounds like a bad idea for me again. > - Fake font name for targeting platforms > > For interoperability, OOo could provide users with fake font names that > were not available on their computer but available on targeting computers. Again: OOo cannot know what will be installed on another computer. > For example, when a user start to write a document on Linux, she/he should > use the fonts installed in her/his computer. She/He, however, needs to send > the document to their contacts who are using Windows. In such a case, > she/he > might want to use a set of font names that were available on Windows > although she/he used OOo on Linux. Then she has to know what is available and type in that font in the Paragraph-Styles. If OOo chooses a replacement font that she doesn't like, she sets her preferred font in the font-replacement. > - Font name replacement in an export filter > > For interoperability, OOo could have a capability of replacing font names > specified in a document with corresponding font names that are available > on targeting platforms. See above. This again sounds like a bad idea to me. This will again result in documents being formatted differently. Especially when you talk about: > For instance, when saving a document in one of the Microsoft Office file > formats, a font name Kochi Mincho available on Linux could be automatically > replaced with MS Mincho available on Windows. Microsoft Office and not other target-formats such as html or other target-platforms, then I cannot agree. This is again a task for font-replacement. If you want the MS-User to see MS Mincho, then set that font in the document. If you want to make sure that you see Kochi Mincho on your screen, define Font-Replacement (although in that case OOo will most likely choose Kochi Micho by itself) So apart from the "OOo should indicate when it uses a fallback font/glyph fallback and tell what font it uses instead", I don't think that any of the other stuff is necessary. ciao Christian -- NP: Metallica - The Prince --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
