Re: Another load of typos
Florian Zumbiehl [EMAIL PROTECTED] writes: FLTK Please consider this ambiguous (like FAQ), as upstream favors the pronunciation fulltick (and makes a point of noting so on the main http://www.fltk.org/ page because a lot of users nevertheless do spell it out). Thanks. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) Finger [EMAIL PROTECTED] (NOT a valid e-mail address) for more info. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Another load of typos
Steve Langasek [EMAIL PROTECTED] writes: On Thu, Mar 17, 2005 at 09:04:14AM -0800, Thomas Bushnell BSG wrote: Hamish Moffatt [EMAIL PROTECTED] writes: (This might be a topic without a possible conclusion!) Funny, but although I'd say an HTML file or an HTTPS url or similar, I'd say a history achievement. Ah, in a history achievement, you accent the first syllable of history, which provokes you to pronounce the H. In an historic achievement, the first syllable of historic is weak, and so most Americans (at least) do not pronounce the H, and so we use an. The only people I can recall ever hearing say an historic in en_US were idiot politicians, and they *did* pronounce the initial h. For that matter, I can't recall ever hearing anyone drop an initial h just because the syllable was unstressed. On what do you base this claim of most? The ones you speak of, who say an historic where they *are* aspirating the H are not only idiot politicians, but they're in the set. Yes, that's a silly usage for Americans, though it was correct for some dialects in England not to long ago. I can't speak about now. But an historic with no aspirated H, hrm, I hear it all the time. But it's not easy to hear if you start thinking carefully now how do I pronounce this, because people generally have two ways to pronounce words and phrases; one in rapid speech, and one when they are speaking carefully and distinctly. The way to tell is to start listening to people, or better, give them a paragraph of text to read aloud. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Another load of typos
On Thursday 17 March 2005 03:16, Florian Zumbiehl wrote: ... and probably not for (that is, not unless you tell me otherwise): HPGL HTML HTTPS Traditionally I think these would use an. Even if you pronounce h as haich rather than aich as another poster pointed out, many words beginning with h such as historic or horrendous require an in formal writing e.g. an historic achievement. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Another load of typos
On Thu, Mar 17, 2005 at 10:59:34AM +, Will Newton wrote: On Thursday 17 March 2005 03:16, Florian Zumbiehl wrote: ... and probably not for (that is, not unless you tell me otherwise): HPGL HTML HTTPS Traditionally I think these would use an. Even if you pronounce h as haich rather than aich as another poster pointed out, many words beginning with h such as historic or horrendous require an in formal writing e.g. an historic achievement. (This might be a topic without a possible conclusion!) Funny, but although I'd say an HTML file or an HTTPS url or similar, I'd say a history achievement. But then we say aich not haich here. An FAQ, too (not a fack). An SQL server, not a sequel server (my pet hate). Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Another load of typos
On Thu, 2005-03-17 at 23:20 +1100, Hamish Moffatt wrote: On Thu, Mar 17, 2005 at 10:59:34AM +, Will Newton wrote: On Thursday 17 March 2005 03:16, Florian Zumbiehl wrote: [snip] An FAQ, too (not a fack). An SQL server, not a sequel server (my pet hate). Well, you're 1/2 correct: A FAQ. An Ess Que Ell server. Thus I Have Spoken, Thus It Shall Be! ;) -- - Ron Johnson, Jr. Jefferson, LA USA PGP Key ID 8834C06B I prefer encrypted mail. You don't want give people a reason to not invite you to the hot parties. Pat Sajak, on being a Republican in Hollywood signature.asc Description: This is a digitally signed message part
Re: Another load of typos
On Thu, Mar 17, 2005 at 06:47:09AM -0600, Ron Johnson wrote: On Thu, 2005-03-17 at 23:20 +1100, Hamish Moffatt wrote: On Thu, Mar 17, 2005 at 10:59:34AM +, Will Newton wrote: On Thursday 17 March 2005 03:16, Florian Zumbiehl wrote: [snip] An FAQ, too (not a fack). An SQL server, not a sequel server (my pet hate). Well, you're 1/2 correct: A FAQ. That's an eff ay cue. A eff is very awkward to pronounce. An Ess Que Ell server. Thus I Have Spoken, Thus It Shall Be! ;) gee thanks:) Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Another load of typos
On Thu, Mar 17, 2005 at 11:20:12PM +1100, Hamish Moffatt wrote: On Thu, Mar 17, 2005 at 10:59:34AM +, Will Newton wrote: On Thursday 17 March 2005 03:16, Florian Zumbiehl wrote: ... and probably not for (that is, not unless you tell me otherwise): HPGL HTML HTTPS Traditionally I think these would use an. Even if you pronounce h as haich rather than aich as another poster pointed out, many words beginning with h such as historic or horrendous require an in formal writing e.g. an historic achievement. (This might be a topic without a possible conclusion!) Funny, but although I'd say an HTML file or an HTTPS url or similar, I'd say a history achievement. That's right. Usually when you pronounce the letter 'haich', it's silent word-initially. When you pronounce it 'aich', it is audible at the start of the word. Or I _think_ that's the case. And at least for these words, they are all abbreviations, as none of them are pronouncable as acronyms. So they are all governed by the local pronounciation of 'H', not the local pronounciation of 'hotel'. But then we say aich not haich here. I'd say an HP printer or a historic occasion, but if I saw it written a HP printer I'd read it a haich-pee printer without qualm. And for some reason, everytime I try, I get a HTML document. So I'm not even consistent in my own usage. Probably because Australian English seems to be influenced by both British and American pronounciation, in the same way that route is understandable in either pronounciation, although then I know the linguistic background of the speaker's English. ^_^ However, this is a pronounciation rule, not a spelling rule, so it's up to the author to write it by speaking it out loud. So I consider these to the uncorrectable automatically, even from the standpoint of paragraph-internal consistency. ^_^ -- --- Paul TBBle Hampson, MCSE 8th year CompSci/Asian Studies student, ANU The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361) [EMAIL PROTECTED] No survivors? Then where do the stories come from I wonder? -- Capt. Jack Sparrow, Pirates of the Caribbean This email is licensed to the recipient for non-commercial use, duplication and distribution. --- signature.asc Description: Digital signature
Re: Another load of typos
On Fri, 2005-03-18 at 00:41 +1100, Paul Hampson wrote: On Thu, Mar 17, 2005 at 11:20:12PM +1100, Hamish Moffatt wrote: On Thu, Mar 17, 2005 at 10:59:34AM +, Will Newton wrote: On Thursday 17 March 2005 03:16, Florian Zumbiehl wrote: [snip] not even consistent in my own usage. Probably because Australian English Australians speak English?!?! ;) seems to be influenced by both British and American pronounciation, in the same way that route is understandable in either pronounciation, although then I know the linguistic background of the speaker's English. ^_^ Maybe not. I've heard Americans say it both ways. But Then, America is a Really Big Country. However, this is a pronounciation rule, not a spelling rule, so it's up to the author to write it by speaking it out loud. So I consider these to the uncorrectable automatically, even from the standpoint of paragraph-internal consistency. ^_^ -- - Ron Johnson, Jr. Jefferson, LA USA PGP Key ID 8834C06B I prefer encrypted mail. Thanks to the good people in Microsoft, a great deal of the data that flows is dependent on one company. That is not a healthy ecosystem. The issue is that creativity gets filtered through the business plan of one company. Mitchell Baker, Chief Lizard Wrangler at Mozilla signature.asc Description: This is a digitally signed message part
Re: Another load of typos
On Fri, 2005-03-18 at 00:10 +1100, Hamish Moffatt wrote: On Thu, Mar 17, 2005 at 06:47:09AM -0600, Ron Johnson wrote: On Thu, 2005-03-17 at 23:20 +1100, Hamish Moffatt wrote: On Thu, Mar 17, 2005 at 10:59:34AM +, Will Newton wrote: On Thursday 17 March 2005 03:16, Florian Zumbiehl wrote: [snip] An FAQ, too (not a fack). An SQL server, not a sequel server (my pet hate). Well, you're 1/2 correct: A FAQ. That's an eff ay cue. A eff is very awkward to pronounce. All TLAs are wordified if possible. An Ess Que Ell server. Thus I Have Spoken, Thus It Shall Be! ;) gee thanks:) You're welcome. :P -- - Ron Johnson, Jr. Jefferson, LA USA PGP Key ID 8834C06B I prefer encrypted mail. The enemy thinks and plans and strategizes, too. signature.asc Description: This is a digitally signed message part
Re: Another load of typos
Will Newton [EMAIL PROTECTED] writes: On Thursday 17 March 2005 03:16, Florian Zumbiehl wrote: ... and probably not for (that is, not unless you tell me otherwise): HPGL HTML HTTPS Traditionally I think these would use an. Even if you pronounce h as haich rather than aich as another poster pointed out, many words beginning with h such as historic or horrendous require an in formal writing e.g. an historic achievement. Actually, the word historic in the phrase an historic achievement is not pronounced by most speakers with a leading H even though in other contexts it usually does. Correct American English *always* puts an N when there is a consonant, and *never* puts one when there isn't, and the rule is how you actually pronounce the word, not how it happens to be spelled. The best advice for the cases which very by which side of the Atlantic you are on is to consistently pick one or the other. The best advice for the cases which depend on how you pronounce an acronym is to reword the sentence so that no reader will stumble. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Another load of typos
Hamish Moffatt [EMAIL PROTECTED] writes: (This might be a topic without a possible conclusion!) Funny, but although I'd say an HTML file or an HTTPS url or similar, I'd say a history achievement. Ah, in a history achievement, you accent the first syllable of history, which provokes you to pronounce the H. In an historic achievement, the first syllable of historic is weak, and so most Americans (at least) do not pronounce the H, and so we use an. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Another load of typos
Hi Christian, On Wed, Mar 16, 2005 at 06:11:11PM +0100, Christian Perrier wrote: Sigh, I *knew* someone would say this..:-) Well, I may be unlucky enough for the tutorial about i18n/l10n handling for maintainers and translators I proposed at debconf to be accepted. If it is, I *will* have to write something anyway, so I guess that *this* (or an excerpt) could end up in the DR, yes May I suggest reporting your HOWTO mail as a bug in the developers reference? That way it is at least recorded somewhere. I'd do it but I don't want without permission. Greetings Torsten signature.asc Description: Digital signature
Re: Another load of typos
Quoting Torsten Landschoff ([EMAIL PROTECTED]): May I suggest reporting your HOWTO mail as a bug in the developers reference? That way it is at least recorded somewhere. I'd do it but I don't want without permission. Feel free to do so...this will probably be a good motivation for me to write down some other stuff. This should probably go somewhere in the DR after the part of the debconf templates style guide. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Another load of typos
On Thu, Mar 17, 2005 at 09:04:14AM -0800, Thomas Bushnell BSG wrote: Hamish Moffatt [EMAIL PROTECTED] writes: (This might be a topic without a possible conclusion!) Funny, but although I'd say an HTML file or an HTTPS url or similar, I'd say a history achievement. Ah, in a history achievement, you accent the first syllable of history, which provokes you to pronounce the H. In an historic achievement, the first syllable of historic is weak, and so most Americans (at least) do not pronounce the H, and so we use an. The only people I can recall ever hearing say an historic in en_US were idiot politicians, and they *did* pronounce the initial h. For that matter, I can't recall ever hearing anyone drop an initial h just because the syllable was unstressed. On what do you base this claim of most? -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: Another load of typos
On Thu, Mar 17, 2005 at 01:05:02PM -0800, Steve Langasek wrote: On Thu, Mar 17, 2005 at 09:04:14AM -0800, Thomas Bushnell BSG wrote: Hamish Moffatt [EMAIL PROTECTED] writes: (This might be a topic without a possible conclusion!) Funny, but although I'd say an HTML file or an HTTPS url or similar, I'd say a history achievement. Ah, in a history achievement, you accent the first syllable of history, which provokes you to pronounce the H. In an historic achievement, the first syllable of historic is weak, and so most Americans (at least) do not pronounce the H, and so we use an. The only people I can recall ever hearing say an historic in en_US were idiot politicians, and they *did* pronounce the initial h. For that matter, I can't recall ever hearing anyone drop an initial h just because the syllable was unstressed. On what do you base this claim of most? Bill Walsh (copy editor at The Washington Post) has given this topic a reasonable going over [1], and comes out with the answer that American Standard English is a h* but seems to concede that when the second syllable of the h-word is stressed, the first can be weakened and the 'h' may disappear, leaving 'an *' (Which sounds like anistoric event to me). On the other hand... The stylebook of the London Times calls for an hotel, an historic and an heroic. But, remember, that's British English. As to when the second syllable of a h-word is stressed, that's an exercise for the speaker. ^_^ [1] http://www.theslot.com/a-an.html -- --- Paul TBBle Hampson, MCSE 8th year CompSci/Asian Studies student, ANU The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361) [EMAIL PROTECTED] No survivors? Then where do the stories come from I wonder? -- Capt. Jack Sparrow, Pirates of the Caribbean This email is licensed to the recipient for non-commercial use, duplication and distribution. --- signature.asc Description: Digital signature
Re: Another load of typos
On Tue, Mar 15, 2005 at 08:55:05PM +0100, Christian Perrier wrote: (what to do when correcting typos in debconf templatesand want to avoid extra work to translators) Quoting Adeodato Simó ([EMAIL PROTECTED]): * Christian Perrier [Tue, 15 Mar 2005 09:24:57 +0100]: Indeed, typo and spell corrections should not need translation updates and affected translations can certainly be unfuzzied.WHEN ONE KNOWS HOW TO DO THIS CLEANLY...:-) I've never had to to such thing, but I've wondered from time to time. So, if I do a spell correction in a debconf template, what should I take care of doing/not doing? (RTFM welcome if accompanied by a point to the relevant M :). Nothing already written comes to my mind. The following is some of the practice I recommend when discussing with maintainers about such issues. This has to be followed point by point. (...) Is this already in the Developer's Reference? If not, I think it should be added there. Thanks for the info! Regards Javier signature.asc Description: Digital signature
Re: Another load of typos
Is this already in the Developer's Reference? If not, I think it should be added there. Thanks for the info! Sigh, I *knew* someone would say this..:-) Well, I may be unlucky enough for the tutorial about i18n/l10n handling for maintainers and translators I proposed at debconf to be accepted. If it is, I *will* have to write something anyway, so I guess that *this* (or an excerpt) could end up in the DR, yes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Another load of typos
Hi, now that the problems with my last bunch of bug reports on mostly its vs. it's mistakes some months ago seem to be solved, I've found another load of typos of the a vs. an flavor, about 110 in total. please please please...for anything which can be localized (especially debconf templates) add something about translations in the bug reports. [...] So, I really suggest that you separate things between package descriptions and debconf templates. For the latter, plese get in touch with debian-i18n. Well, so far it's package descriptions only; so nothing to worry about, you think? Though debconf templates probably would be a good idea to have a look at :-) Cya, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Another load of typos
Hi, my current plans are now as follows: Submit maint-only bug reports regarding a vs. an for the following words, including a reference to this thread in the mailing list archive: ACPI Adlib AX.25 EsounD FLTK FPU FTP IETF IMAP Internet IP IPv4 IPv6 IR IrDA ISDN ISO-C L2TP LCD LDAP LED LGPL LR (as in parser) LRU MP3 MPEG MRTG MS MTA NDTP NNTP NT NTFS ODBC OO RDBMS RPC RSD X11 X (as in X window system) XML ... not for: FAQ ... and probably not for (that is, not unless you tell me otherwise): HPGL HTML HTTPS Any further comments? Cya, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Another load of typos
Quoting Florian Zumbiehl ([EMAIL PROTECTED]): Hi, now that the problems with my last bunch of bug reports on mostly its vs. it's mistakes some months ago seem to be solved, I've found another load of typos of the a vs. an flavor, about 110 in total. please please please...for anything which can be localized (especially debconf templates) add something about translations in the bug reports. At least pointing the developers to podebconf-report-po for warning translators that their translation needs an update because the original English was changed for instance. All they have to do is installing po-debconf and run this utility from the top of their package's source tree after making the change and run debconf-updatepo. Indeed, typo and spell corrections should not need translation updates and affected translations can certainly be unfuzzied.WHEN ONE KNOWS HOW TO DO THIS CLEANLY...:-) For package descriptions, this is less harmful as indeed there is no real way to handle translations properly (the DDTP does not really implement stuff for that and I'm even not sure it is still working properly). So, I really suggest that you separate things between package descriptions and debconf templates. For the latter, plese get in touch with debian-i18n. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Another load of typos
* Christian Perrier [Tue, 15 Mar 2005 09:24:57 +0100]: Indeed, typo and spell corrections should not need translation updates and affected translations can certainly be unfuzzied.WHEN ONE KNOWS HOW TO DO THIS CLEANLY...:-) I've never had to to such thing, but I've wondered from time to time. So, if I do a spell correction in a debconf template, what should I take care of doing/not doing? (RTFM welcome if accompanied by a point to the relevant M :). -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 The Wright Brothers weren't the first to fly. They were just the first not to crash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Another load of typos
On Monday, 14 March 2005 21:32, Florian Zumbiehl wrote: To verify that what I think to be incorrect really is, here is the list of words I've found to be used with a but which I think should be used with an: FAQ Most people I know pronounce this fack not eff ay kyu. Others probably have the opposite view, but nobody I've spoken with has ever said it out loud. ;) It's probably up to the speaker/writer whether it's a FAQ or an FAQ, depending on how they're intending it to be pronounced. -- Wesley J. Landaker [EMAIL PROTECTED] OpenPGP FP: 4135 2A3B 4726 ACC5 9094 0097 F0A9 8A4C 4CD6 E3D2 pgpVJnOvZFWh9.pgp Description: PGP signature
Re: Another load of typos
(what to do when correcting typos in debconf templatesand want to avoid extra work to translators) Quoting Adeodato Simó ([EMAIL PROTECTED]): * Christian Perrier [Tue, 15 Mar 2005 09:24:57 +0100]: Indeed, typo and spell corrections should not need translation updates and affected translations can certainly be unfuzzied.WHEN ONE KNOWS HOW TO DO THIS CLEANLY...:-) I've never had to to such thing, but I've wondered from time to time. So, if I do a spell correction in a debconf template, what should I take care of doing/not doing? (RTFM welcome if accompanied by a point to the relevant M :). Nothing already written comes to my mind. The following is some of the practice I recommend when discussing with maintainers about such issues. This has to be followed point by point. 0) run debconf-updatepo (to be sure that ALL PO files are up-to-date with regards to your current templates, not yet modified for typos) 1) Put all incomplete PO files out of the way You can check the completeness by using: for i in debian/po/*po ; do msgfmt -o /dev/null --statistics $i ; done move all files which report either fuzzy strings to a temporary place. Files which report no fuzzy strings (only translated and untranslated) will be kept in place 2) NOW AND NOW ONLY, modify the template for the typos AND BE SURE THIS DOES NOT AFFECT THE TRANSLATIONS (typos, spelling errors, sometimes typographical corrections should not affect translations) 3) run debconf-updatepo This will fuzzy all strings you modified in translations. You can see this by running the above again 4) Run: for i in debian/po/*po ; do msgattrib --output-file=$i --clear-fuzzy $i ; done 5) move back files you moved in 1) to debian/po 6) run debconf-updatepo again Doing so, you unfuzzy in 4 all strings fuzzied by the changes in 2+3. Moving incomplete files elsewhere prevents you to clear the fuzzy marker they could have for *legitimate* reasons. Again and again, only do this when you have carefully checked that translations have no reason to be impacted by the change(s) you plan to make. And, do this exactly as I described, in the same order. Messing up with translations is *not* recommended. Doing so with the gettext tools prevents to mess up encodings (emacs can be very good at this as well as several text editors)but you have to be sure of what you're doing, indeed:) There are other ways, more elaborated, to do preventive modification of PO files (for instance by using sed)which allow the unfuzzyfication process to be done even on incomplete filesbut this is gory enough for being left to people who *really* are sure of what they do...:-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Another load of typos
On Tue, Mar 15, 2005 at 05:32:10AM +0100, Florian Zumbiehl wrote: HPGL HTML HTTPS These three vary because the letter H is pronounced starting with either a 'h' (haich) or an 'a' (aich). This is _probably_ a distinction between American and British English, although it was originally a distinction between social class of the speaker of British English. (cf. Pygmalion, I believe) But I don't know which one's which. For me, An aich-pee printer sounds just as good as a haich-pee printer. I just wanted to mention it, and also because this way I can have pee associated with the Debian mailing lists in google. ^_^ -- --- Paul TBBle Hampson, MCSE 8th year CompSci/Asian Studies student, ANU The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361) [EMAIL PROTECTED] No survivors? Then where do the stories come from I wonder? -- Capt. Jack Sparrow, Pirates of the Caribbean This email is licensed to the recipient for non-commercial use, duplication and distribution. --- signature.asc Description: Digital signature
Re: Another load of typos
On Wed, Mar 16, 2005 at 05:11:39PM +1100, Paul Hampson wrote: On Tue, Mar 15, 2005 at 05:32:10AM +0100, Florian Zumbiehl wrote: HPGL HTML HTTPS These three vary because the letter H is pronounced starting with either a 'h' (haich) or an 'a' (aich). This is _probably_ a distinction between American and British English, although it was originally a distinction between social class of the speaker of British English. (cf. Pygmalion, I believe) But I don't know which one's which. For me, An aich-pee printer sounds just as good as a haich-pee printer. I would say that in my experience (in American English, and I'm from the Midwest), one would typically use an in front of a pronounced H, but a in front of words beginning with H. So, an HTML page, a helper page. I don't think that this sort of thing is worth standardizing, given that there might be differences between typical British and American usage. We don't seem to standardize one way or the other on British vs. American spellings, like with color and colour. In fact, believe it or not, the short description for the gimp-dimage-color package uses colour rather than color... I just wanted to mention it, and also because this way I can have pee associated with the Debian mailing lists in google. ^_^ Heh. That'll be funny until we get mail from the first person asking us to remove pee from their computer. (Damn! That probably made it worse.) KEN -- Kenneth J. Pronovici [EMAIL PROTECTED] pgpszcdiWZhiv.pgp Description: PGP signature
Re: Another load of typos
Florian Zumbiehl wrote: - Might it be reasonable to not check for duplicates before sending the reports? I'm using a relatively recent Packages file from unstable - and checking whether it is a duplicate probably is much easier for the maintainer than it is for me (they should know it immediately when they see my bug report, I guess, while I'd have to read through the bug lists of a hundred packages at least). Sounds reasonable to me. To verify that what I think to be incorrect really is, here is the list of words I've found to be used with a but which I think should be used with an: FAQ Would you mind giving a reference to a manual of style or something about these? I always only use an before an acronym if the expansion of the acronym would need an an in front. An FAQ sounds wrong to my ears. -- see shy jo signature.asc Description: Digital signature
Re: Another load of typos
Joey Hess [EMAIL PROTECTED] writes: Would you mind giving a reference to a manual of style or something about these? I always only use an before an acronym if the expansion of the acronym would need an an in front. An FAQ sounds wrong to my ears. It depends on how you expand it. If I pronounce FAQ as fack, then I would write a FAQ. If I pronounce it as eff ay cue, then it starts with a vowel, and I'd write an FAQ. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Another load of typos
On Tue, Mar 15, 2005 at 12:00:30AM -0500, Joey Hess wrote: Florian Zumbiehl wrote: - Might it be reasonable to not check for duplicates before sending the reports? I'm using a relatively recent Packages file from unstable - and checking whether it is a duplicate probably is much easier for the maintainer than it is for me (they should know it immediately when they see my bug report, I guess, while I'd have to read through the bug lists of a hundred packages at least). Sounds reasonable to me. To verify that what I think to be incorrect really is, here is the list of words I've found to be used with a but which I think should be used with an: FAQ Would you mind giving a reference to a manual of style or something about these? I always only use an before an acronym if the expansion of the acronym would need an an in front. An FAQ sounds wrong to my ears. It depends on if the acronym is usually spelled or pronounced. I say a fack, other people say an eff ahy cue. I don't think there's a universally accepted way to handle acronyms. - Matt signature.asc Description: Digital signature
Re: Another load of typos
Hi, To verify that what I think to be incorrect really is, here is the list of words I've found to be used with a but which I think should be used with an: FAQ Would you mind giving a reference to a manual of style or something about these? I always only use an before an acronym if the expansion of the acronym would need an an in front. An FAQ sounds wrong to my ears. Indeed, it doesn't seem to be as undisputable as I thought. Though most of what this google search turns up seems to be in agreement with my assumptions, your rule can be found, too: http://www.google.com/search?q=%22a+vs+an%22+acronyms The rule I am following is that a vs. an is decided by pronounciation only - i.e., it's an eff ey kju, but a FAT file system. After all, that's how the exact letters are most easily read (without expanding acronyms or such). Cya, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Another load of typos
Florian Zumbiehl [EMAIL PROTECTED] writes: The rule I am following is that a vs. an is decided by pronounciation only - i.e., it's an eff ey kju, but a FAT file system. After all, that's how the exact letters are most easily read (without expanding acronyms or such). Your rule is correct: it is determined by pronunciation only. But what you have missed is that many people pronounce FAQ as fack. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Another load of typos
Hi, The rule I am following is that a vs. an is decided by pronounciation only - i.e., it's an eff ey kju, but a FAT file system. After all, that's how the exact letters are most easily read (without expanding acronyms or such). Your rule is correct: it is determined by pronunciation only. But what you have missed is that many people pronounce FAQ as fack. Well, I had the impression that FAQ was picked randomly by Joey - though it might be a bad choice for an example here :-) In the google results, Joey's rule to consider the expanded form, is mentioned as a possibility on this page: http://www.techwr-l.com/techwhirl/archives/9903/techwhirl-9903-00224.html Though, as I wrote, there don't seem to be many people using that rule. Apart from whether determining use of a vs. an by the expanded form of an acronym should be considered correct or not, of course, there might be particular acronyms, such as FAQ, that are pronounced letter-by-letter only by some and due to that fact might be correct with either form. Cya, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
