Menu
▾
▴
[Plplot-devel] Re Help needed to correctly implement underline and overline mode
|
From: Phil R. <phi...@ya...> - 2013-08-25 16:20:31
|
Hi Alan WxWidgets does not implement overline at all. At least not in 2.8. I haven't used 2.9 so not sure there. In this case we would have to manually draw an overline. For underline, what would be the desired outcome? In Word for example if underlined text includes normal and superscript it is all underlined as normal. A text block that only contains superscript is underlined as superscript. Subscript is always underlined as subscript. Changing this would again require manual underlining for wxWidgets as wxWidgets has no concept of sub or superscript and is implemented manually Is this the case for qt and other devices? If this is going to be done manually it would be good to agree formats and distances. Its also not a trivial job when combined with parsing newlines as well. Do we need a plplot text parser to deal with all this consistently across devices? Phil -----Original Message----- From: "plp...@li..." <plp...@li...> Sent: 25/08/2013 00:51 To: "plp...@li..." <plp...@li...> Subject: Plplot-devel Digest, Vol 87, Issue 8 Send Plplot-devel mailing list submissions to plp...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/plplot-devel or, via email, send a message with subject or body 'help' to plp...@li... You can reach the person managing the list at plp...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of Plplot-devel digest..." Today's Topics: 1. Re: Project to replace DocBook backend SGML tools with XML tools (Alan W. Irwin) 2. Help needed to correctly implement underline and overline mode (Alan W. Irwin) 3. Re: Project to replace DocBook backend SGML tools with XML tools (Alan W. Irwin) 4. Time for a release? pen width issues (Orion Poplawski) 5. Re: Time for a release? pen width issues (Alan W. Irwin) 6. Re: Project to replace DocBook backend SGML tools with XML tools (Alan W. Irwin) ---------------------------------------------------------------------- Message: 1 Date: Tue, 20 Aug 2013 10:41:26 -0700 (PDT) From: "Alan W. Irwin" <ir...@be...> Subject: Re: [Plplot-devel] Project to replace DocBook backend SGML tools with XML tools To: Andrew Ross <and...@us...> Cc: Plplot-devel mailing list <plp...@li...> Message-ID: <alpine.DEB.2.02.1308201016470.3402@enira.zlyna.ubzr> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Hi Andrew: On 2013-08-19 20:24-0700 Alan W. Irwin wrote: > Unless there is something you guys dislike about these results that > can be fixed in the short term, I am pretty much finished with it > although there are some obvious issues mentioned in the commit message > for revision 12490 that will need to be addressed in the long term. Well, I am always curious about new stuff so I did take a quick look at http://www.sagehill.net/docbookxsl to see what was possible for customizing the style of the results. And at least the first step in that process (generate meaningful names for the html chunk filenames) turned out (revision 12491) to be trivial. So based on that extremely encouraging result you may see some additional revisions in the next day or so from me as I look at some other customization possibilities. But I plan to test all such revisions before I commit them so please do not wait for customization perfection from me to evaluate what I have done. It's also important that more than one of us understands the customizations so I encourage you to get involved in XSL customizaton yourself (at least by looking up the detailed web references I give in comments included in the new plplotdoc-html.xsl.in file which controls html customization for the default -DDOCBOOK_XML_BACKEND=ON case.) Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ------------------------------ Message: 2 Date: Wed, 21 Aug 2013 11:40:09 -0700 (PDT) From: "Alan W. Irwin" <ir...@be...> Subject: [Plplot-devel] Help needed to correctly implement underline and overline mode To: PLplot development list <Plp...@li...> Message-ID: <alpine.DEB.2.02.1308211111310.3381@enira.zlyna.ubzr> Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII PLplot's underlining and overlining capability is controlled by the #- and #+ escape sequences in text. To see how this works, apply the following patch to example 1. Index: examples/c/x01c.c =================================================================== --- examples/c/x01c.c (revision 12482) +++ examples/c/x01c.c (working copy) @@ -253,7 +253,7 @@ plcol0( 1 ); plenv( xmin, xmax, ymin, ymax, 0, 0 ); plcol0( 2 ); - pllab( "(x)", "(y)", "#frPLplot Example 1 - y=x#u2" ); + pllab( "(x)", "(y)", "#fr#-PLplot#- #+Example 1 - y=x#u2#+" ); // Plot the data points If you run examples/c/x01c -dev xwin the results are not too bad although the underline cuts through the descender part of the "p" in "Plplot" so a smarter algorithm for deciding on the vertical offset of the underline and overline should be implemented. Also, the superscript mode affects the vertical offset of the overline mode just at the superscript and not for the whole overline. Instead the "smart" algorithm should take account of superscripts and subscripts to decide the overall vertical offset for the entire underline or overline. The situation is much worse for modern device drivers such as wxwidgets, qt, and cairo. Underline mode works (with the same limitations as for -dev xwin) for the wxwidgets "basic" device, but overline mode is not implemented for that device. And underline and overline mode do not work at all for the wxwidgets "wxGC" device and the qt and cairo devices. We need volunteers to step forward to make the #- and #+ text escape sequences work correctly for your favorite devices. Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ------------------------------ Message: 3 Date: Wed, 21 Aug 2013 16:24:54 -0700 (PDT) From: "Alan W. Irwin" <ir...@be...> Subject: Re: [Plplot-devel] Project to replace DocBook backend SGML tools with XML tools To: Andrew Ross <and...@us...> Cc: Plplot-devel mailing list <plp...@li...> Message-ID: <alpine.DEB.2.02.1308211526510.3381@enira.zlyna.ubzr> Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed On 2013-08-20 10:41-0700 Alan W. Irwin wrote: > Hi Andrew: > > On 2013-08-19 20:24-0700 Alan W. Irwin wrote: > >> Unless there is something you guys dislike about these results that >> can be fixed in the short term, I am pretty much finished with it >> although there are some obvious issues mentioned in the commit message >> for revision 12490 that will need to be addressed in the long term. > > Well, I am always curious about new stuff so I did take a quick look > at http://www.sagehill.net/docbookxsl to see what was possible for > customizing the style of the results. And at least the first step in > that process (generate meaningful names for the html chunk filenames) > turned out (revision 12491) to be trivial. > > So based on that extremely encouraging result you may see some > additional revisions in the next day or so from me as I look at some > other customization possibilities. But I plan to test all such > revisions before I commit them so please do not wait for customization > perfection from me to evaluate what I have done. It's also important > that more than one of us understands the customizations so I encourage > you to get involved in XSL customizaton yourself (at least by looking > up the detailed web references I give in comments included in the new > plplotdoc-html.xsl.in file which controls html customization for the > default -DDOCBOOK_XML_BACKEND=ON case.) With revision 12494, I think the style for -DDOCBOOK_XML_BACKEND=ON is now looking pretty good both for the html and print (pdf and ps) results. The only issue I am aware of is the ability to represent "S?(f?r?e?q?)" in the html and print results. For the html case, the old DSSSL method converted the special xml fragment <!ENTITY over-under '<anchor id="over-under"/>'> in inline-html.ent to the html fragment <span class="overline">S</span>(<span class="underline">freq</span>) and css rules in stylesheet.css took care of the rest. For the print case, the old method converted the special xml fragment <!ENTITY over-under "Ё"> in inline-print.ent using jadetex (an old SGML backend tool) configuration contained in jadetex.cfg. It is possible something similar to these special techniques to render overlining and underlining for the html and print cases could also be used for the new XML/XSL backend. (In fact, I am fairly close to a special solution for the html case, see comments in plplotdoc-html.xsl.in.) But I think this is a rather low priority since overlining and underlining actually works badly or not at all for modern PLplot devices, see my other post today). So I am going to put off working further on this until the long term (if at all). In any case, in the long term the general utf-8 solution <!ENTITY over-under "S?(f?r?e?q?)"> should just work instead. But PDF generation on Linux currently seems to be limited to just type 1 fonts so those unicode glyphs are not recognized as indicated by the warning messages generated by "xmlto --with-fop" Glyph "?" (0x305, overlinecmb) not available in font "Times-Roman". Glyph "?" (0x332, lowlinecmb) not available in font "Times-Roman". The generated PDF also had a "#" sign in place of each of the missing overlinecmb (just after the "S") and lowlinecmb (just after each of the letters in "freq") glyphs. So this is not a good solution in the short term. In the next day or so I plan to play a bit more with dblatex to see if I can generate dvi results with it, and I am also ready to deal with any issues you find as well, but otherwise I believe I have completed this project. Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ------------------------------ Message: 4 Date: Fri, 23 Aug 2013 15:08:55 -0600 From: Orion Poplawski <or...@co...> Subject: [Plplot-devel] Time for a release? pen width issues To: Plplot-devel mailing list <plp...@li...> Message-ID: <521...@co...> Content-Type: text/plain; charset=ISO-8859-1; format=flowed So, I've updated plplot in (yet to be released) Fedora 20 to svn12479. This contains the change of wid -> width for pen width. This is breaking my gdl build because it is still trying to use wid() which is all of a sudden gone. And now I have nothing like a version number change to key this on. So: - Is it intentional for plstream->wid() to be removed completely already? - Time for a release? - other suggestions? -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nw... Boulder, CO 80301 http://www.nwra.com ------------------------------ Message: 5 Date: Fri, 23 Aug 2013 15:54:48 -0700 (PDT) From: "Alan W. Irwin" <ir...@be...> Subject: Re: [Plplot-devel] Time for a release? pen width issues To: Orion Poplawski <or...@co...> Cc: Plplot-devel mailing list <plp...@li...> Message-ID: <alpine.DEB.2.02.1308231522520.3381@enira.zlyna.ubzr> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed On 2013-08-23 15:08-0600 Orion Poplawski wrote: > So, I've updated plplot in (yet to be released) Fedora 20 to svn12479. This > contains the change of wid -> width for pen width. This is breaking my gdl > build because it is still trying to use wid() which is all of a sudden gone. > And now I have nothing like a version number change to key this on. > > So: > > - Is it intentional for plstream->wid() to be removed completely already? At the C level plwid is still available if the builder specifies -DPL_DEPRECATED=ON, but I suspect nobody has bothered to propagate that deprecated version to other languages. So IIRC we have a gradual change possible from plwid to plwidth for C, but an abrupt change for the bindings. That was not intentional, but it is also not a bad outcome since integer line widths are pretty old-fashioned and the fix is easy (see below). > - Time for a release? My opinion is this is long overdue. We still need to propagate the plcolorbar changes to the OCaml and Ada bindings and examples and document plcolorbar in doc/docbook/src/api.xml, but I think those relatively minor issues are all that is currently blocking us from a release. > - other suggestions? You are probably aware of this already, but the gdl breakage should be trivial to fix. Replace all instances of plstream->wid( integer width) with plstream->plwidth(floating width). One could test plplot to see if plwid or plwidth was available and key the change on that. However, I agree it would make life much easier for you and others to have a PLplot version number to key such a change. Thus, getting out a PLplot release out soon is important not only for this reason but many others. Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ------------------------------ Message: 6 Date: Sat, 24 Aug 2013 16:50:45 -0700 (PDT) From: "Alan W. Irwin" <ir...@be...> Subject: Re: [Plplot-devel] Project to replace DocBook backend SGML tools with XML tools To: Andrew Ross <and...@us...> Cc: Plplot-devel mailing list <plp...@li...> Message-ID: <alpine.DEB.2.02.1308241540500.5020@enira.zlyna.ubzr> Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed On 2013-08-21 16:24-0700 Alan W. Irwin wrote: > In the next day or so I plan to play a bit more with dblatex to see if > I can generate dvi results with it, and I am also ready to deal with > any issues you find as well, but otherwise I believe I have completed > this project. Hi Andrew: It turned out the source of the dvi issue was a dblatex bug (see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720624 for a description of the problem and a patch to fix it). Once I applied that patch, the dblatex command finally started working properly to generate dvi results both when dblatex was invoked directly or indirectly via "xmlto --with-dblatex". Please give the updated documentation build a spin following the (newly updated as of revision 12497) directions in doc/docbook/README.developers. Also, please feel free to update that file if you feel more details about the packages required by xmlto are needed. Revision 12497 is the last commit I plan to do in the near term concerning the DocBook backend tools that we use unless you find some easily fixed issue in the documentation build. In the medium term (i.e., after the next release when we will be using these new backend tools to help generate our website) I plan two more DocBook backend changes. The first of those is to disable use of the deprecated SGML/DSSSL backend tools completely which will allow me to do the second change which is to use UTF-8 directly in our DocBook source. The big advantage of UTF-8 is it allows us to include a potentially enormous range of glyphs in our DocBook source including all of the mathematical and human-language glyphs that appear in our examples. Part of that range allows overlining and underlining so UTF-8 provides a fundamental solution for representing the UTF-8 string "S?(f?r?e?q?)" in our documentation (which is the last outstanding issue of the present approach as far as I know). (I hope your mailer is UTF-8 aware so you can read that UTF-8 string as intended!) The only disadvantage (which I consider to be minor) of UTF-8 is that the dvi format is fundamentally incompatible with it outside the very narrow range of glyphs currently represented in our documentation. The inescapable conclusion is that the dvi format will have to be dropped from our documentation once we extend the range of glyphs in our documentation in the slightest. (In fact, UTF-8 glyphs for overlining and underling are already outside the valid glyph range of the dvi format.) For further comments about how UTF-8 can be implemented for PDF, PostScript, and HTML and the excellent results I have already had with a proof of concept for that implementation please see the updated discussion in doc/docbook/README.developers. Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ------------------------------ ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk ------------------------------ _______________________________________________ Plplot-devel mailing list Plp...@li... https://lists.sourceforge.net/lists/listinfo/plplot-devel End of Plplot-devel Digest, Vol 87, Issue 8 ******************************************* |
