Dear Alex (cc oxygen-user list), Thank you for the quick response. I wonder whether it might be possible to use checkboxes instead of a single selection, so that users could combine profiles selectively according to their specific needs. I also wonder, though, about the possibility of associating a CSS profile in <oXygen/> with a specific CSS stylesheet document, that is, at finer granularity than is available through project-level or global preferences. I have a project that uses multiple stylesheets, some that contain just HTML5 selectors and some that mix HTML5 selectors with SVG selectors. I can put those stylesheets in different projects and specify different CSS profiles that way, but they really belong in the same project for other reasons, and in the non-SVG CSS files I'd want to raise an error if, for example, I specify a "width" value as a non-zero number without a unit of measurement, although that wouldn't be an error in an SVG context. This organization would be analogous to having different schemas for different XML documents in the project; here there would be different CSS profiles for different CSS documents in the project. I realize that there are other complications (e.g., validating inline or otherwise embedded CSS within an XML document), though, so I'm not sure how practical this idea would turn out to be. Best, David
Currently there is no solution to this problem. I will ad an issue to find a solution to such a situation. Perhaps a new entry in the profile combo that will state "All known profiles".
I have an HTML5 document (XML syntax) with inline SVG and I'd like to associate a single external stylesheet with it that specifies both CSS3 and SVG properties. The <oXygen/> documentation at
http://www.oxygenxml.com/doc/versions/17.0/ug-author/index.html#topics/prefe... ,
which matches what I see in my configuration options, seems willing to allow me to select CSS3 or SVG, but not both simultaneously. Is there a way to obtain the sort of validation I'm looking for? I can choose CSS3 in the option menu and ignore the error messages for the SVG properties, but I'd rather have the benefit of validating both.
Hi Alex, If I understand what David is asking for correctly, I’d want to endorse his request. One of the quarrels some people have with DITA is getting tight control of output appearance, layout, etc. If this can be done a different levels of granularity, i.e., if people can have access to very tight control of the output without having to further into coding than doing a CSS stylesheet, this will go a long way toward “taming” DITA output. Coupling this to a more sophisticated publishing product such as Webworks or Antenna House might also provide a lot of interesting possibilities. Ray Business Process Improvement through Communication +33-6 72 40 37 60 Central European Summer Time (GMT +2) Follow me on: Twitter <http://twitter.com/RayGallon> Google Plus <https://plus.google.com/100012946767116683119/posts/p/pub> LinkedIn <http://www.linkedin.com/in/rgallon>
On 26 May 2015, at 11:09 , David Birnbaum <djbpitt@gmail.com> wrote:
Dear Alex (cc oxygen-user list),
Thank you for the quick response. I wonder whether it might be possible to use checkboxes instead of a single selection, so that users could combine profiles selectively according to their specific needs.
I also wonder, though, about the possibility of associating a CSS profile in <oXygen/> with a specific CSS stylesheet document, that is, at finer granularity than is available through project-level or global preferences. I have a project that uses multiple stylesheets, some that contain just HTML5 selectors and some that mix HTML5 selectors with SVG selectors. I can put those stylesheets in different projects and specify different CSS profiles that way, but they really belong in the same project for other reasons, and in the non-SVG CSS files I'd want to raise an error if, for example, I specify a "width" value as a non-zero number without a unit of measurement, although that wouldn't be an error in an SVG context. This organization would be analogous to having different schemas for different XML documents in the project; here there would be different CSS profiles for different CSS documents in the project. I realize that there are other complications (e.g., validating inline or otherwise embedded CSS within an XML document), though, so I'm not sure how practical this idea would turn out to be.
Best,
David
Currently there is no solution to this problem. I will ad an issue to find a solution to such a situation. Perhaps a new entry in the profile combo that will state "All known profiles".
I have an HTML5 document (XML syntax) with inline SVG and I'd like to associate a single external stylesheet with it that specifies both CSS3 and SVG properties. The <oXygen/> documentation at http://www.oxygenxml.com/doc/versions/17.0/ug-author/index.html#topics/prefe... <http://www.oxygenxml.com/doc/versions/17.0/ug-author/index.html#topics/preferences-css-validator.html>, which matches what I see in my configuration options, seems willing to allow me to select CSS3 or SVG, but not both simultaneously. Is there a way to obtain the sort of validation I'm looking for? I can choose CSS3 in the option menu and ignore the error messages for the SVG properties, but I'd rather have the benefit of validating both.
oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Hi Ray, David wants to be able to specify different CSS profiles for CSS validation and be able to do that for each CSS file, right now oXygen allows to set CSS validation options globally or per project, but you cannot have different CSS validation options for multiple files within the same project. Back to your requirement, oXygen supports CSS based PDF output using the DITA-CSS DITA-OT plugin and in version 17 we integrated that with the CSS selection from the Author, so you can easily get output just by using CSS to style the content. I covered this in the overview of oXygen 17 webinar here https://www.youtube.com/watch?v=B52kBMcqKhg&feature=youtu.be&t=43m20s and Radu will probably go into some more details on the DITA specific webinar that we plan for June 10 http://www.oxygenxml.com/events/2015/webinar_oxygen_17_dita_support.html Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 26/05/15 17:39, Culturecom (Ray Gallon) wrote:
Hi Alex, If I understand what David is asking for correctly, I’d want to endorse his request.
One of the quarrels some people have with DITA is getting tight control of output appearance, layout, etc. If this can be done a different levels of granularity, i.e., if people can have access to very tight control of the output without having to further into coding than doing a CSS stylesheet, this will go a long way toward “taming” DITA output.
Coupling this to a more sophisticated publishing product such as Webworks or Antenna House might also provide a lot of interesting possibilities.
Ray
Business Process Improvement through Communication +33-6 72 40 37 60 Central European Summer Time (GMT +2)
Follow me on: Twitter <http://twitter.com/RayGallon> Google Plus <https://plus.google.com/100012946767116683119/posts/p/pub> LinkedIn <http://www.linkedin.com/in/rgallon>
On 26 May 2015, at 11:09 , David Birnbaum <djbpitt@gmail.com <mailto:djbpitt@gmail.com>> wrote:
Dear Alex (cc oxygen-user list),
Thank you for the quick response. I wonder whether it might be possible to use checkboxes instead of a single selection, so that users could combine profiles selectively according to their specific needs.
I also wonder, though, about the possibility of associating a CSS profile in <oXygen/> with a specific CSS stylesheet document, that is, at finer granularity than is available through project-level or global preferences. I have a project that uses multiple stylesheets, some that contain just HTML5 selectors and some that mix HTML5 selectors with SVG selectors. I can put those stylesheets in different projects and specify different CSS profiles that way, but they really belong in the same project for other reasons, and in the non-SVG CSS files I'd want to raise an error if, for example, I specify a "width" value as a non-zero number without a unit of measurement, although that wouldn't be an error in an SVG context. This organization would be analogous to having different schemas for different XML documents in the project; here there would be different CSS profiles for different CSS documents in the project. I realize that there are other complications (e.g., validating inline or otherwise embedded CSS within an XML document), though, so I'm not sure how practical this idea would turn out to be.
Best,
David
Currently there is no solution to this problem. I will ad an issue to find a solution to such a situation. Perhaps a new entry in the profile combo that will state "All known profiles".
> I have an HTML5 document (XML syntax) with inline SVG and I'd like to > associate a single external stylesheet with it that specifies both > CSS3 and SVG properties. The <oXygen/> documentation at > http://www.oxygenxml.com/doc/versions/17.0/ug-author/index.html#topics/prefe..., > which matches what I see in my configuration options, seems willing to > allow me to select CSS3 or SVG, but not both simultaneously. Is there > a way to obtain the sort of validation I'm looking for? I can choose > CSS3 in the option menu and ignore the error messages for the SVG > properties, but I'd rather have the benefit of validating both.
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com <mailto:oXygen-user@oxygenxml.com> http://www.oxygenxml.com/mailman/listinfo/oxygen-user
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Hi all, Being able to select which CSS profiles apply will definitely bring more flexibility. If you want to associate specific profiles with specific files, then I think the feature to help is "Validation scenarios" for CSS files. With this feature you will be able to create a CSS validation scenario, specify in it the profiles to use and associate it with a given file. I will record this feature request. Best regards, Alex -- Alex Jitianu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 5/26/2015 9:50 PM, George Bina wrote:
Hi Ray,
David wants to be able to specify different CSS profiles for CSS validation and be able to do that for each CSS file, right now oXygen allows to set CSS validation options globally or per project, but you cannot have different CSS validation options for multiple files within the same project.
Back to your requirement, oXygen supports CSS based PDF output using the DITA-CSS DITA-OT plugin and in version 17 we integrated that with the CSS selection from the Author, so you can easily get output just by using CSS to style the content. I covered this in the overview of oXygen 17 webinar here https://www.youtube.com/watch?v=B52kBMcqKhg&feature=youtu.be&t=43m20s and Radu will probably go into some more details on the DITA specific webinar that we plan for June 10 http://www.oxygenxml.com/events/2015/webinar_oxygen_17_dita_support.html
Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com
On 26/05/15 17:39, Culturecom (Ray Gallon) wrote:
Hi Alex, If I understand what David is asking for correctly, I’d want to endorse his request.
One of the quarrels some people have with DITA is getting tight control of output appearance, layout, etc. If this can be done a different levels of granularity, i.e., if people can have access to very tight control of the output without having to further into coding than doing a CSS stylesheet, this will go a long way toward “taming” DITA output.
Coupling this to a more sophisticated publishing product such as Webworks or Antenna House might also provide a lot of interesting possibilities.
Ray
Business Process Improvement through Communication +33-6 72 40 37 60 Central European Summer Time (GMT +2)
Follow me on: Twitter <http://twitter.com/RayGallon> Google Plus <https://plus.google.com/100012946767116683119/posts/p/pub> LinkedIn <http://www.linkedin.com/in/rgallon>
On 26 May 2015, at 11:09 , David Birnbaum <djbpitt@gmail.com <mailto:djbpitt@gmail.com>> wrote:
Dear Alex (cc oxygen-user list),
Thank you for the quick response. I wonder whether it might be possible to use checkboxes instead of a single selection, so that users could combine profiles selectively according to their specific needs.
I also wonder, though, about the possibility of associating a CSS profile in <oXygen/> with a specific CSS stylesheet document, that is, at finer granularity than is available through project-level or global preferences. I have a project that uses multiple stylesheets, some that contain just HTML5 selectors and some that mix HTML5 selectors with SVG selectors. I can put those stylesheets in different projects and specify different CSS profiles that way, but they really belong in the same project for other reasons, and in the non-SVG CSS files I'd want to raise an error if, for example, I specify a "width" value as a non-zero number without a unit of measurement, although that wouldn't be an error in an SVG context. This organization would be analogous to having different schemas for different XML documents in the project; here there would be different CSS profiles for different CSS documents in the project. I realize that there are other complications (e.g., validating inline or otherwise embedded CSS within an XML document), though, so I'm not sure how practical this idea would turn out to be.
Best,
David
Currently there is no solution to this problem. I will ad an issue to find a solution to such a situation. Perhaps a new entry in the profile combo that will state "All known profiles".
> I have an HTML5 document (XML syntax) with inline SVG and I'd like to > associate a single external stylesheet with it that specifies both > CSS3 and SVG properties. The <oXygen/> documentation at > http://www.oxygenxml.com/doc/versions/17.0/ug-author/index.html#topics/prefe..., > which matches what I see in my configuration options, seems willing to > allow me to select CSS3 or SVG, but not both simultaneously. Is there > a way to obtain the sort of validation I'm looking for? I can choose > CSS3 in the option menu and ignore the error messages for the SVG > properties, but I'd rather have the benefit of validating both.
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com <mailto:oXygen-user@oxygenxml.com> http://www.oxygenxml.com/mailman/listinfo/oxygen-user
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
participants (4)
-
Alex Jitianu -
Culturecom (Ray Gallon) -
David Birnbaum -
George Bina