Browsing Pennsylvania German translation

261.

textual representation (short name) of the type of error. On sub-typed error types you may want to prepend the error_name that belongs to the main number to make the name complete.

262.

one of node/way/relation

263.

an OSM node_id, way_id or relation_id

264.

one of new, reopened, ignore_temporarily, ignore. You won't see any 'cleared' errors because the dump contains active errors only. Temporarily ignored errors are issues fixed by a user who really hopes to have fixed it. Temporarily ignored errors will jump back in the 'new' state with the next update if the error isn't really fixed. Ignored errors are issues that are simply false positives and should never come back just because KeepRight is wrong and this exception cannot be included in the ruleset.

265.

Errors that were once cleared and come back at some point in time later are put in the <em>reopened</em> state. Please note that this may happen due to runtime-errors in the scripts. So you may just consider <em>new</em> and <em>reopened</em> the same.

266.

The verbose error message that comes out of the checking routine in English language. For translating the messages use the next columns

267.

This is the scaffold for the error description where placeholders ("$i") stand in place of the actual values inserted by the concrete error instance. You may put this scaffold inside a GNU gettext() function to have it translated. GNU gettext requires a .po file that holds original and translated strings. You may use existing .po files from here:

268.

find the GNU gettext template file here:

269.

These bits of text are the contents that have to be inserted in the error message after translation. txt1 will replace $1, etc.

270.

Timestamp (MESZ) of when this error was found the first time