The readme file contains the following line: unzip thunderbird-1.0-os2.zip -d c:\thunderbird-1.0 the 1.0 should become something like 2.0, or perhaps even better, XX, with a remark that XX represents the current version number.
Well, it says "i.e." that so... The source is here, if you want to make a patch http://lxr.mozilla.org/seamonkey/source/mail/locales/en-US/os2/README.txt
i.e. means: ‘with other words’, not ‘for example’, that is e.g. So if you want to stick to abbreviations, i.e. should become e.g. I’d prefer a similar remark as in point 1 of the list, though. I’ll make a patch as soon as I am on my other puter once again...
OK, the version number is not a big deal, it should be clear from the above that it is an example, even though it says "i.e." not "e.g.". But that's easily changed. I'll take the chance to change the typical filenames given in that file to what is used now.
Component: Installer → General
Product: Thunderbird → Core
Hardware: Macintosh → PC
Created attachment 243923 [details] [diff] [review] update readmes of all three products Anything else I should change while I am there?
Assignee: mscott → mozilla
Status: NEW → ASSIGNED
I don’t get it, I think it is a good patch, but why do you still keep references to FF 1.0.1? Why not do the x.x.x. trick in the unzip example too?
I don't plan to update the number for every release and if it says x.x.x then the next user will come as ask "There is no x.x.x in the package but 22.214.171.124 instead what should it do?" (Things like that actually do happen!) With 1.0.1 and "e.g." it should now be clear at least that it is an example...
Comment on attachment 243923 [details] [diff] [review] update readmes of all three products r=mkaply
Attachment #243923 - Flags: review?(mozilla) → review+
Checked into trunk.
Status: ASSIGNED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.