I'm not able to dedicate as much time to developing and maintaining this module as I'd like: please get in touch if you'd like to help out as a co-maintainer.

Allows users to set custom submit messages for different node types via the Drupal UI. So, rather than being stuck with "Page title has been saved", "Page title has been updated" and "Page title has been deleted" the user can set custom submit messages. In addition to this, CSM allows you to change the title of the node creation page. CSM allows both of these things to be set separately for each language your Drupal site is running in.

Depends on the Token module and the Status Messages Alter module. The Drupal 7 version of the module includes a version of Status Messages Alter. Kudos to Michael Barton for his work on Status Messages Alter; see #1209450: Drupal 7?
for some background on why it is included with CSM.

CSM is currently in beta: please post any issues in the issue queue. For a discussion on the future of the module, see #2019885: Future additions
.

Instructions

1. Download, install and enable the Token module. If you're using Drupal 6, do the same for Status Messages Alter.
2. Download, install and enable the CSM module as usual.
3. When CSM has been enabled, follow the instructions that are displayed with regards to updating Status Messages Alter.
4. Go to http://yoursite.com/admin/content/node-type/[node-type].
5. Make the necessary changes in the "Submit message settings" and "Node creation page title" sections, using standard HTML tags and token replacements as and when you like.
6. Click Save!

Roadmap towards a 1.0 release for Drupal 6 and Drupal 7 - please help out where you can!

1. Fix the open issues in the issue queue (apart from those specifically mentioned below)
2. Release a beta version of the module, and allow this to be in the wild for three weeks to allow for testing
3. While the module is in beta, check that it works with non-English Drupal installations #1524912: Check whether csm_variables() works as intended for non-English Drupal installations
4. Drupal 6 release of a 1.0 version of the module
5. Create a Drupal 7 branch from the 1.0 version of the Drupal 6 code
6. Aim to develop the Drupal 7 branch as follows: alpha1, alpha2, beta1, beta2, RC, 1.0, with alpha1 including an upgrade path as per #1528930: Once the module is in beta, build in an upgrade path

Notes

It is possible to achieve some of the intended functionality of this module with the String Overrides module. However, String Overrides requires the end user to dig around in core code to find the pattern of any non-fixed string that is to be translated, which is not ideal from a usability point of view. Furthermore, as node.module provides only one string for all node types, it is not possible to set different submit messages for different node types using String Overrides.