--> Sorry in advance for our rather disappointing answer:
* No, there is no way to specify @media NOT_XMLmind_XML_Editor {}
* No, we currently do not plan to implement more CSS2/CSS3 features.
We generally do that when this is *really* needed to decently support a
new document type. (The last time we did that was to style DITA maps and
bookmaps.)
--> Now, the workaround:
* Turn off option "Ignore <?xml-stylesheet?>" (Options|Preferences, Open
section). By doing this, XMLmind XML Editor will *not* pick
gt_dictionary.css.
See
http://www.xmlmind.com/xmleditor/_distrib/doc/help/com.xmlmind.guiutil.PreferencesEditorDialog.html#openOptions
* Now create a simple configuration for dictionary files. This simple
configuration will contain something like:
<css name="Dictionary" location="gt_dictionary_XXE.css"/>
where "gt_dictionary_XXE.css" is a simplified variant of
gt_dictionary.css. (No need to duplicate things gt_dictionary.css can
import gt_dictionary_XXE.css.)
See http://www.xmlmind.com/xmleditor/_distrib/doc/configure/css.html
* This configuration file allows you to do much more than simply styling
your dictionary files: custom menu, custom toolbar, custom keyboard
bindings, custom commands, etc.
See http://www.xmlmind.com/xmleditor/_distrib/doc/configure/index.html
* Moreover it is easy to package your configuration as an add-on in
order to distribute it over the internet. The persons using XXE will
simply have to select it using "Options|Install Add-ons".
See "How to package an add-on as a .zip archive" --
http://www.xmlmind.com/xmleditor/contribute.html#package_addon
Sjur Moshagen wrote:
>
> We have a set of xml files publicly browsable through our svn repository (it
> is open source), and we want to also make the files easily editable using
> XXE. The files are rather straightforward dictionary files with a simple
> structure. The files are styled using a processing instruction which links a
> CSS stylesheet. This works fine in both all modern browsers, and using XXE.
> Just to have a look, open the following link with your favorite browser:
>
> https://victorio.uit.no/langtech/trunk/words/dicts/smanob/src/cc_smanob.xml
>
> To make the content look ok in modern browsers, we have been using a few CSS3
> construct, which cause a long list of warnings when opening the files in XXE
> (paths are local to my system, but opening the file directly from the
> repository using webdav will of course give the same warnings):
>
> file:/Users/sjur/langtech/main/words/dicts/scripts/gt_dictionary.css:53:35:
> unsupported property "border-bottom"
>
> file:/Users/sjur/langtech/main/words/dicts/scripts/gt_dictionary.css:59:21:
> unsupported property "cursor"
>
> file:/Users/sjur/langtech/main/words/dicts/scripts/gt_dictionary.css:60:18:
> unsupported property "cursor"
>
> file:/Users/sjur/langtech/main/words/dicts/scripts/gt_dictionary.css:71:20:
> unknown pseudo-element or pseudo-class "nth-child"
>
> file:/Users/sjur/langtech/main/words/dicts/scripts/gt_dictionary.css:72:20:
> unknown pseudo-element or pseudo-class "nth-child"
>
> file:/Users/sjur/langtech/main/words/dicts/scripts/gt_dictionary.css:72:33:
> unsupported value for property "border"
>
> file:/Users/sjur/langtech/main/words/dicts/scripts/gt_dictionary.css:99:32:
> unsupported property "text-transform"
>
> file:/Users/sjur/langtech/main/words/dicts/scripts/gt_dictionary.css:171:24:
> unsupported value for property "margin-left"
>
> file:/Users/sjur/langtech/main/words/dicts/scripts/gt_dictionary.css:185:29:
> unknown pseudo-element or pseudo-class "only-of-type"
>
> file:/Users/sjur/langtech/main/words/dicts/scripts/gt_dictionary.css:185:43:
> unsupported value for property "content"
>
> file:/Users/sjur/langtech/main/words/dicts/scripts/gt_dictionary.css:186:22:
> unknown pseudo-element or pseudo-class "only-of-type"
>
> file:/Users/sjur/langtech/main/words/dicts/scripts/gt_dictionary.css:191:27:
> unknown pseudo-element or pseudo-class "only-of-type"
>
> file:/Users/sjur/langtech/main/words/dicts/scripts/gt_dictionary.css:204:29:
> unsupported value for property "margin-left"
>
> file:/Users/sjur/langtech/main/words/dicts/scripts/gt_dictionary.css:229:25:
> unsupported value for property "margin-left"
>
> file:/Users/sjur/langtech/main/words/dicts/scripts/gt_dictionary.css:237:32:
> unsupported property "text-transform"
>
> file:/Users/sjur/langtech/main/words/dicts/scripts/gt_dictionary.css:248:9:
> syntax error: expected ',' or '{', found '~'
>
> file:/Users/sjur/langtech/main/words/dicts/scripts/gt_dictionary.css:253:9:
> syntax error: expected ',' or '{', found '~'
>
> file:/Users/sjur/langtech/main/words/dicts/scripts/gt_dictionary.css:263:24:
> unsupported value for property "margin-left"
>
>
> I know that some of these things are not presently supported in XXE (like
> border specifications for only one side of the box), but are there plans to
> add support for some of the CSS3 features like the nth-child or ~ selectors?
>
> An althernative solution to avoid the warnings would be to hide the CSS
> constructs from XXE, like it is possible to wrap XXE extensions to CSS in an
> @media construct to hide them from other processors. But that isn't possible
> as far as I know (a negative @media construction, like 'do NOT show if media
> is XXE'?).
>
> I have browsed the FAQ, recent mailing list, users wish list, etc., but found
> nothing. What are the current plans for more CSS3 support, esp. those
> concerning the list above?
>
