On 2014-02-18 04:06, Dominik Haumann wrote:
> Ok, next round. The current list looks as follows:
> [snip]

Since I think it's useful, besides commenting directly (which I did in 
my other mail), I'd like to do a hypothetical exercise of making use of 
these in some of the more troublesome HL's with less obvious mappings...

diff.xml:
   Normal Text -> dsNormal
   File -> dsCommentVar / dsVariable
   Header -> dsAnnotation
   Removed line -> dsWarning
   Added line -> dsInformation
   Changed line (old) -> dsWarning + bold
   Changed line (new) -> dsInformation + bold

rest.xml:
   Normal -> dsNormal
   Bold -> dsNormal ^ bold
   Italic -> dsNormal ^ italic

   InlineLiteral -> dsVerbatimString

   FootnoteReference -> dsAnnotation
   HyperlinkReference -> dsAnnotation

   SubstitutionReference -> dsOperator
   SubstitutionDefinition -> dsConstant

   Footnote -> dsInformation
   Citation -> dsInformation

   InlineInternalTarget -> dsFunction
   HyperlinkTarget -> dsFunction

   Field -> dsCommentVar
   FieldBold -> dsCommentVar ^ bold
   FieldItalic -> dsCommentVar ^ italic

   Role -> dsKeyword
   InterpretedText -> dsVariable

   Directive -> dsExtension

   CMakeCode -> dsOther
   CppCode -> dsOther
   PythonCode -> dsOther
   Code -> dsOther

   Comment -> dsComment

(Aside: it would be useful if the bold/italic attributes could be 
toggled from their otherwise-value; note the '^' used above.)

In the above, I do still feel like a dsReference (or dsLink) would be 
useful.

The point isn't to bikeshed the above, rather to use it as an example of 
trying to come up with a sensible semantic mapping in order to see how 
well we're doing with the proposed default attributes at covering a 
real-world HL.

-- 
Matthew

_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel