Closed
Bug 548732
Opened 16 years ago
Closed 16 years ago
Fix the encoding of *properties.strings files in the project
Categories
(Camino Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: alqahira, Assigned: alqahira)
References
()
Details
(Whiteboard: [camino-2.0.3])
Attachments
(1 file)
|
17.09 KB,
patch
|
stuart.morgan+bugzilla
:
superreview+
|
Details | Diff | Splinter Review |
philippe put up a build log tonight of a 10.5sdk-on-10.6 build and I filtered it on warnings. One of the warnings that comes up is that the Gecko strings files are listed in the project as having UTF-8 encoding when they are in fact UTF-16.
Some time when we aren't juggling project patches I need to make sure they have the correct encoding specified in the project (should be 10, not 4).
|
Assignee | |
Comment 1•16 years ago
|
||
Ta-da!
This doesn't apply elsewhere because of context, but I see no reason not to land it elsewhere and it's easy enough to fix up.
Attachment #440584 -
Flags: superreview?(stuart.morgan+bugzilla)
|
||
Updated•16 years ago
|
Attachment #440584 -
Flags: superreview?(stuart.morgan+bugzilla) → superreview+
|
|
||
Comment 2•16 years ago
|
||
Comment on attachment 440584 [details] [diff] [review]
Twiddle the encoding bits
sr=smorgan
|
|
Assignee | |
Comment 3•16 years ago
|
||
http://hg.mozilla.org/camino/rev/ff109a46aa55
and landed on cvs trunk and CAMINO_2_0_BRANCH (fewer warnings, less divergence).
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Whiteboard: [camino-2.0.3]
You need to log in
before you can comment on or make changes to this bug.
Description
•