Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
Thanks to Loreia, User Defined Language version 2 (UDL2) is available in Notepad++ 6.2.
Here you can find Notepad++ 6.2 Release Candidate:
The key features in UDL2 are:
1. More groups are added: 3 folder groups, 8 keyword groups and 8 delimiter sets.
2. Multipart keywords (for exemple: "else if" can be defined as single keyword) is supported.
3. Whitespace is no longer mandatory as keyword separator: Operators and folding keywords can be recognized with or without whitespace separators.
4. Operators and delimiters can be longer that one character now.
5. Numbers recognition support is greatly improved(prefix, suffix, range and extra symbols supported).
6. The same characters can be used as comments AND operators.
7. Comments and delimiters support nesting (even within each other).
There are a lot more new feature in UDL2, you can have the tutorial (done by Loreia) here:
The official release will come out in one week, if there's no critical bug found.
I am trying to use the Multipart Keywords feature but cannot seem to get it to work properly. I am putting quotes around the phrase, such as "AAA BBB". The ignore case is checked. The phrase is being highlighted together, but when I toggle the ignore case box off and on, AAA and BBB, which are also independently on separate lines, are getting highlighted.
Also, lower case "aaa bbb" is not being recognised when the keyword phrase is defined in caps "AAA BBB".
Any help would be greatly appreciated.
Great! I'm looking forward to test the UDL2 features.
Thanks a lot, great work!
There seems to be a minor regression, however: In the View menu, localized strings are not correctly applied for submenus.
Basically, this looks like the problem discussed here, but it is puzzling because the program reads the new localization format. It is just the Project and Collapse Level submenus that don't show correctly.
I notice the html api has been updated but it has a few typos: <KeyWord name="datails" /> should be <KeyWord name="details" /> and <KeyWord name="prpgress" /> should be <KeyWord name="progress" /> There may be more errors, but I found them comparing the diff.
Can you fix this for next version?
Indeed, it's a regression. I will fix it and provide fixed 6.2 RC tonight.
"prpgress" has been fixed.
"datails" will be fixed.
Feel free to let me know the other errors if you find any.
I scanned through the file and found the following errors:
<KeyWord name="onmpusewheel" /> should be <KeyWord name="onmousewheel" />
<KeyWord name="caption" />" /> should be <KeyWord name="caption" />
Can you publish your changes more often to the online repository? It is then possible to report problems in source code before release.
I don't know whether this has been discussed elsewhere, or whether this is an old issue, but in Settings / Style Configurator… it is not always possible to change the Bold, Italic or Underline settings for built-in languages. For example if I try to set the comment styles for MATLAB and FORTRAN to italic, I can't tick the box.
As I promised, a fixed RC is available:
Note that one of attribute in nativeLang.xml has been changed from:
I updated German translation with your latest update. All you need to do is synchronize your local translation with the fixed one:
Thank you for the alert.
Thank you for the tipo fix.
The updated version is on SVN now:
Excellent, thank you!
I have a few questions regarding the Localization of the new Styler Dialog.
How does this dialog start and end? (Tags please). And where in the language file should the strings be located?
Styler dialog strings were not added to localization file as of yet. It will be done by the time v6.2. is released.
@Loreia & joergenr
I'm working on Localization of the new Styler Dialog.
It'll be available in v6.2 release.
try to use single quotes for this purpose.
'AAA BBB' <-- highlighted only on the same line
"AAA BBB" <-- highlighted even if separted by new line characters
Thank you very much, this will be a big help.
Using the single quotes ('AAA BBB' and ignore case on), the following occurs:
AAA BBB <-- highlighted
aaa bbb <-- not highlighted
aaa BBB <-- highlighted
AAA bbb <-- not highlighted
Not sure if it is intended to work in this manner.