On 7/21/2008 1:17 AM, Hussein Shafie wrote: > Andy Black wrote: >> >> Does this mean that XXE v4 will have the CSS font-family restrictions >> removed? > > No. > >> These restrictions are in listed the CSS documentation as >> --- >> >> font-family is expected to contain serif, sans-serif or monospace. >> Example: "|font-family: Helvetica, Arial, sans-serif;|". >> >> However a few well-know font families are mapped to the corresponding >> generic font families. Example: "|font-family: verdana;|" is >> understood to be sans-serif. >> >> All other cases will cause the serif font family to be used. Example: >> "|font-family: 'Nimbus Sans';|". >> >> --- >> >> That would be wonderful if so. > > This restriction has no technical reasons, only ``philosophical > reasons''. It is there to stress the fact that XMLmind XML Editor is a > pure content editor. > > If you give us a good reason explaining why you need more than 3 fonts > (serif, sans-serif, monospace) when rendering an XML document on > screen, may be we'll remove this restriction.
Many of our users are writing linguistic papers using very specialized orthographies. A number of them need to use Unicode characters in the Private Use Area because the symbols are not in standard Unicode. We have fonts that correctly render these PUA characters (e.g. Charis SIL, see http://www.sil.org/computing/catalog/show_software.asp?id=112), but XXE ignores them (at least as far as I can tell...) due to this CSS restriction. This means that these users only see square boxes instead of their specialized characters. Obviously this is not a good situation for an author. He/she must check the formatted output to see if he/she keyed the correct character. He/she cannot merely look at the screen. --Andy
