On Tue, Feb 7, 2012 at 1:04 PM, Sebastian Karcher <[email protected]> wrote: >> Just to be clear, the idea I was presenting here would never enter the >> schema or spec. It would instead be used for a) maybe the primer, as a >> suggestion, and b) for the GUI editor. > OK, that's important. I haven't thought hard enough about the GUI > editor, but for the primer I'm with Frank - if we give coding > advice/conventions in the primer they should be to avoid punctuation > (and with a couple of exceptions such as date-parts - spacing) in > affixes altogether and use groups and delimiters instead. > Having punctuation only in prefixes is preferable to having the mix of > prefixes and suffixes, doubling up punctuation etc. that many existing > styles have, so I understand what you're saying, but it still has a > lot of issues with optional fields and will make code needlessly messy > as opposed to clean grouping and delimiters.
For the GUI, are there any obvious rules one could apply to figuring out what macro calls to group, and therefore where to put punctuation, without user input? For sake of illustration/argument: top-level macro calls get paired, with the intervening punctuation applied to the group delimiter? Or is that simply not possible/practical? Bruce ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ xbiblio-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
