Bug 294236 - Non-NLS markers flag not set on many projects in .genmodel
Summary: Non-NLS markers flag not set on many projects in .genmodel
Status: ASSIGNED
Alias: None
Product: STEM
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Stefan Edlund CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-04 13:43 EST by Stefan Edlund CLA
Modified: 2010-01-14 21:00 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Edlund CLA 2009-11-04 13:43:17 EST 
We need to set the Non-NLS markers flag to true in the root node of the .genmodel files so that the //$NON-NLS-X$ are put into the generated code. This way we avoid getting warnings on strings that don't need to be translated and making it easier to find strings that actually needs to be translated.

Only 7 .genmodel files have the flag set to true right now

One thing we noticed is that you might need to delete the generated file before you regenerate to make the markers how up.
Comment 1 Daniel Ford CLA 2009-11-04 17:39:04 EST 
Any suggestion who to assign it to?
Comment 2 James Kaufman CLA 2009-11-23 16:46:43 EST 
Stefan is looking at all of NLS. We should probably combine into 1 NLS master bug as this will be a longer term effort
Comment 3 James Kaufman CLA 2010-01-14 21:00:07 EST 
NLS