| Summary: | quick fix: offer marking strings as non-nls [quick fix] | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Adam Kiezun <akiezun> |
| Component: | UI | Assignee: | Martin Aeschlimann <martinae> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | daniel_megert |
| Version: | 2.0 | ||
| Target Milestone: | 2.1 M3 | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
|
Description
Adam Kiezun
can you help me on this one (maybe refactor the method that evaluates position and text for a nls-string to an edit?!) workaround define a non-nls macro Adam, I would also like NON-NLS to code assist for single line comments and therefore support Martin's wish for getting access (internal API) to the NLS scanner e.g. getNonNlsString(int offset, int length) or getNonNlsString(String line) *** Bug 20201 has been marked as a duplicate of this bug. *** added NLSScanner.scanCurrentLine(ICompilationUnit, int) it gives you back an obhect that has the information that you need to create a 'non-nls' string and position it correctly Could I have util method? TextEdit getNonNlsString(int strigStart, int stringLength) returns null if string is NLS'd already or the edit that appends a NON-NLS string see NLSUtil.createNLSEdit(ICompilationUnit cu, int position) new quick fix added > 20021022 |