On 9/14/05, Colin Marquardt <colin@...384...> wrote:
My opinion:
#: ../src/jabber_whiteboard/message-utilities.cpp:168 msgid "" "ID for new object is NULL even after generation and lookup attempts: the new " "object will NOT be sent, nor will any of its child objects!"
Certainly not for the user to see. This _may_ be output to the console if you really need it, but (1) mark it not translatable, and (2) make sure it really is an error which happens very unfrequently.
Also:
"Node %p (name %s) is a special node, but it could not be found in the node " "tracker (possible unexpected duplicate?) Generating unique ID anyway." "Could not read next message due to charset conversion error (error: %s)!" "Caught I/O exception (error string: %s) while committing change to session " "file %s. Attempting to commit remaining changes; session file will be " "inconsistent with whiteboard session history." "Caught character set conversion error (error string: %s) while committing " "change to session file %s. Attempting to commit remaining changes; session " "file will be inconsistent with whiteboard session history." msgid "Cannot operate on NULL SessionFile." "Caught I/O error %s while attemping to open file %s for session recording."
-- same as above, I think these all are technical descriptions not for the user. Console only, untranslatable.
"Accepting the invitation in the active document will cause your current " "changes to be lost"
-- what is "current changes"? Changes since last save? Or the entire document content? This is not clear.
"A new desktop could not be opened"
-- "desktop" is our coders jargon, it's not for the user. The user knows these things as "document windows".