Issue 303: LOCALIZATION: Create build tool that scans the source for strings without "Not L10N"

issues
Status:closed
Assigned To:Guest
Type:Localization
Area:Skyline
Priority:3
Milestone:2.6
Opened:2014-02-05 by Brendan MacLean
Changed:2014-08-28 by Brendan MacLean
Resolved:2014-08-28 by Brendan MacLean
Resolution:Fixed
Closed:2014-08-28 by Brendan MacLean
2014-02-05 Brendan MacLean
Title»LOCALIZATION: Create build tool that scans the source for strings without "Not L10N"
Assigned To»Yuval
Notify»donmarsh
Type»Localization
Area»Skyline
Priority»3
Milestone»2.6
We have generally been using comments like // Not L10N to mark strings that we do not want to localize. We need to formalize this in our build, so that we are scanning the source directories the build the project UI, and not the test directories (which we should probably remove all "Not L10N" usage from). And we should fail the build when we encounter these.

We will need to add some form of block comment too for places where we have a lot of strings and putting // Not L10N on every line would be cumbersome.

// Start not L10N

[...lots of strings...]

// End not L10N

Or something like that.

2014-08-28 Brendan MacLean
resolve as Fixed
Statusopen»resolved
Assigned ToYuval»Brendan MacLean

2014-08-28 Brendan MacLean
close
Statusresolved»closed
Assigned ToBrendan MacLean»Guest