- fix #| (previous untranslated string)
- fix hexadecimal entity
- fix html tag in a < b
- use <keyword> rather than <RegExpr/StringDetect> for auto-completion
- string without " at the end of the line is an error
- # followed by something other than " |:.," is an extension
Details
Details
- Reviewers
dhaumann cullmann - Group Reviewers
Framework: Syntax Highlighting - Commits
- R216:b65c28ceda6c: Gettext: fix "previous untranslated string" and other improvements/fixes
Diff Detail
Diff Detail
- Repository
- R216 Syntax Highlighting
- Branch
- gettext (branched from master)
- Lint
No Linters Available - Unit
No Unit Test Coverage - Build Status
Buildable 15067 Build 15085: arc lint + arc unit
Comment Actions
If it is better not to have a hard-coded color, wouldn't it be better to remove them once and for all? Without necessarily incrementing the version.
Comment Actions
If the highlighting still is OK after removing them, sure, but it looks like the language wanted explicitly have different colors for stuff using the same default style. Perhaps one could use some of the new default styles in some places.
And I would always update the version, to allow people to update properly.