in ChangeAttributeTxn.cpp ChangeAttributeTxn::GetUndoString and ChangeAttributeTxn::GetRedoString have hard-coded strings in them. These will need to be pulled out for L10n efforts.

Also... file methods CreateElementTxn.cpp GetUndoString, GetRedoString DeleteTextTxn.cpp GetUndoString, GetRedoString DeleteElementTxn.cpp GetUndoString, GetRedoString DeleteRangeTxn.cpp GetUndoString, GetRedoString InsertTextTxn.cpp GetUndoString, GetRedoString JoinElementTxn.cpp GetUndoString, GetRedoString SplitElementTxn.cpp GetUndoString, GetRedoString

reassign to myself; cc bobj@netscape.com

I assume these are error messages that you need to resource? Check out: http://www.mozilla.org/projects/intl/string-resources.html Cc'ing Tao and Erik who can help with the strres APIs.

Can wait until M10. We have very few places where we have embedded strings, so I'm not concerned about leaving this until after we've hit full functionality. These are strings that can be made available to the UI to give more meaning to the user about what action will be undone|redone.

Of course, sooner is better. The L10N engineers have already begun creating pseudo-localizations to test localizability where possible.

Of course, sooner is better. The L10N engineers have already begun creating pseudo-localizations to test localizability where possible.

Of course, sooner is better. The L10N engineers have already begun creating pseudo-localizations to test localizability where possible.

changing contact person to tao@netscape.com

moving to M9

M10

m11

infrastructure in place; move to M12 (note: only logging currently uses the hard- coded strings)

setting to M14, this can wait till after dogfood

Beth, this needs to be fixed before M14 because we are localizing M14. Can you set the milestone to M13? I agree it's not dogfood, but early M13 is our deadline for translation. Thanks!

removing whiteboard summary text

Nominating for Beta1 since we are localizing Beta1.

I would like this bug reconsidered and marked PDT- Removing PDT+ on status whiteboard so it will be reconsidered. These strings are only used in the logging system which is a "debug" thing; they don't appear anywhere in the UI. This bug could be fixed in 3 ways: * remove the strings altogether and break logging * create a properties file and write extra code to handle these strings (temporarily) * the "right" way which is dependent on command-dispatching which may not be completely in place for beta1 (bug #18395 I think)

Putting on the PDT- radar for beta1.

moving to M15 (hopefully Simon's / Hyatt's stuff will be done by then)

remove beta1 keyword and PDT- status whiteboard

move to Future for now

adding help wanted keyword

Taking this off of brade's plate.

The GetUndoString() and GetRedoString() methods were ripped out when I landed changes for bug #66308, so this bug is effectively fixed. ;-) The only strings left in the transactions are left for logging/debugging which will never appear in the UI, so they don't need translating.

Kin/Kathy, can you verify this one and mark VERIFIED-FIXED ? thx.

Marking verified.