1294189 - localization: migrate webconsole.xul to use properties file instead of dtd

Status: RESOLVED DUPLICATE of bug 1381834

(DevTools :: General, defect, P3)

Description

[Julian Descottes [:jdescottes]]

For devtools.html, XHTML files will no longer be able to load entities from external DTD files. All XHTML/XUL files relying on DTDs for localization should move all the DTD entities to properties files.

This bug is about migrating all localization strings defined in webconsole.xul.

Comment 1

[Julian Descottes [:jdescottes]]

As discussed last week, migrating webconsole.xul to HTML is no longer the priority for phase 2.
This bug should no longer be part of the MVP.

The only reason we should actually fix this in the future depends on how we will transition to the new console frontend.
If at some point the new console frontend reimplements the filters toolbar, and the old filter toolbar is still in the codebase, it would be better to migrate the strings to properties files so that they can be used by both implementations.

Comment 2

[Brian Grinstead [:bgrins]]

(In reply to Julian Descottes [:jdescottes] from comment #1)
> As discussed last week, migrating webconsole.xul to HTML is no longer the
> priority for phase 2.
> This bug should no longer be part of the MVP.
> 
> The only reason we should actually fix this in the future depends on how we
> will transition to the new console frontend.
> If at some point the new console frontend reimplements the filters toolbar,
> and the old filter toolbar is still in the codebase, it would be better to
> migrate the strings to properties files so that they can be used by both
> implementations.

And I've been assuming we will just create new strings in a properties file for the filter toolbar in the new UI even if that leads to a couple of duplicate strings (there are less total strings in the new filtering UI)

Comment 3

[Julian Descottes [:jdescottes]]

dtd files are no longer used in the console since Bug 1381834