1. wxEuphoria v16 spellings
- Posted by ArthurCrump Jul 27, 2013
- 1568 views
There appears to be a mix of British and American spellings in wxEuphoria version 16. For example:
wxALIGN_CENTER (American), but not wxALIGN_CENTRE (British)
wxColour (British), but not wxColor (American)
I think that either British or American spelling should be standardized for all routines and constants. Where the contrary spelling exists it must be left in for existing usage but should they be marked as degraded?
There are already some constants with both British and American spellings
2. Re: wxEuphoria v16 spellings
- Posted by jimcbrown (admin) Jul 27, 2013
- 1564 views
There appears to be a mix of British and American spellings in wxEuphoria version 16. For example:
wxALIGN_CENTER (American), but not wxALIGN_CENTRE (British)
wxColour (British), but not wxColor (American)
I think that either British or American spelling should be standardized for all routines and constants. Where the contrary spelling exists it must be left in for existing usage but should they be marked as degraded?
There are already some constants with both British and American spellings
Why not go the extra mile and have dual constants for all cases where spelling differs? (And maybe we can even add Canadian/New Zealand/Australian specific spellings as they are discovered also.)
3. Re: wxEuphoria v16 spellings
- Posted by DerekParnell (admin) Jul 27, 2013
- 1543 views
Why not go the extra mile and have dual constants for all cases where spelling differs? (And maybe we can even add Canadian/New Zealand/Australian specific spellings as they are discovered also.)
Not helping, Jim.
4. Re: wxEuphoria v16 spellings
- Posted by jimcbrown (admin) Jul 28, 2013
- 1557 views
Why not go the extra mile and have dual constants for all cases where spelling differs? (And maybe we can even add Canadian/New Zealand/Australian specific spellings as they are discovered also.)
Not helping, Jim.
Why is this a bad idea? There aren't even all that many differences ( http://homepage.ntlworld.com/vivian.c/SpellingVarieties/British&American.htm ) and both Americans and Brits will sometimes switch to the other's standard when writing informally.
5. Re: wxEuphoria v16 spellings
- Posted by ArthurCrump Jul 28, 2013
- 1518 views
Why not go the extra mile and have dual constants for all cases where spelling differs? (And maybe we can even add Canadian/New Zealand/Australian specific spellings as they are discovered also.)
Not helping, Jim.
Why is this a bad idea? There aren't even all that many differences ( http://homepage.ntlworld.com/vivian.c/SpellingVarieties/British&American.htm ) and both Americans and Brits will sometimes switch to the other's standard when writing informally.
I agree that there are not all that many differences. I have only seen centre/center and colour/color in wxEuphoria.
wxWidgets appears to use the British spelling colour in the routines and constants, with color appearing only in a couple of descriptions. Not surprising as it was developed in Edinbugh.
Arthur
6. Re: wxEuphoria v16 spellings
- Posted by jimcbrown (admin) Jul 28, 2013
- 1492 views
wxWidgets appears to use the British spelling colour in the routines and constants, with color appearing only in a couple of descriptions. Not surprising as it was developed in Edinbugh.
Hmm.. if wxWidgets has standarized based on British spellings, then it probably makes sense for wxEuphoria to follow suit.
7. Re: wxEuphoria v16 spellings
- Posted by jaygade Jul 28, 2013
- 1427 views
- Last edited Jul 29, 2013
Why not go the extra mile and have dual constants for all cases where spelling differs? (And maybe we can even add Canadian/New Zealand/Australian specific spellings as they are discovered also.)
Not helping, Jim.
Why is this a bad idea? There aren't even all that many differences ( http://homepage.ntlworld.com/vivian.c/SpellingVarieties/British&American.htm ) and both Americans and Brits will sometimes switch to the other's standard when writing informally.
Because your reply (online) seemed sarcastic, as if a dozen variations on the spelling of one variable would have to be accepted, and then applied to all variables.
That's the way that I took it anyway.
Whereas you don't have to make a separate variable for Canada and Australia and New Zealand dialects -- just US and UK English.
EDIT: Stupid double dash.
8. Re: wxEuphoria v16 spellings
- Posted by jimcbrown (admin) Jul 29, 2013
- 1387 views
Because your reply (online) seemed sarcastic, as if a dozen variations on the spelling of one variable would have to be accepted, and then applied to all variables.
That's the way that I took it anyway.
I get it now. This is really my own fault, for never using <sarcasm></sarcasm> or <joke></joke> tags.
Whereas you don't have to make a separate variable for Canada and Australia and New Zealand dialects just US and UK English.
No one else had a Noah Webster, but I would have figured at least some differences would have crept in over time. Go figure.
9. Re: wxEuphoria v16 spellings
- Posted by DerekParnell (admin) Jul 29, 2013
- 1376 views
Why not go the extra mile and have dual constants for all cases where spelling differs? (And maybe we can even add Canadian/New Zealand/Australian specific spellings as they are discovered also.)
Not helping, Jim.
Why is this a bad idea? There aren't even all that many differences ( http://homepage.ntlworld.com/vivian.c/SpellingVarieties/British&American.htm ) and both Americans and Brits will sometimes switch to the other's standard when writing informally.
I thought you weren't being serious, but as it turns out you are/were then ...
- There are not that many difference variations in English spelling - basically there are two - British and American.
- If one includes all the spelling differences, do we extend that to the variations due to abbreviations too?
- Having multiple constants with the same meaning makes long-term maintenance more costly. There are just more things to look at when maintaining stuff
- 'grepping' becomes an issue as it is easy to miss references.
Experience shows that the better solution is to stick with one standard and just make it something that readers/writers of the code have to learn. It doesn't matter if one uses British, American or ... Klingon spelling, as consistency is more important in keeping maintenance costs down. We must be careful not to be chauvinistic with our own language.
10. Re: wxEuphoria v16 spellings
- Posted by jimcbrown (admin) Jul 29, 2013
- 1384 views
- There are not that many difference variations in English spelling - basically there are two - British and American.
- If one includes all the spelling differences, do we extend that to the variations due to abbreviations too?
- Having multiple constants with the same meaning makes long-term maintenance more costly. There are just more things to look at when maintaining stuff
- 'grepping' becomes an issue as it is easy to miss references.
Experience shows that the better solution is to stick with one standard and just make it something that readers/writers of the code have to learn. It doesn't matter if one uses British, American or ... Klingon spelling, as consistency is more important in keeping maintenance costs down. We must be careful not to be chauvinistic with our own language.
You're right. In that case, since wxWidgets already uses the British standard, I think wxEuphoria should follow suit - otherwise, we'd get all these headaches (from not picking a standard but trying to support both) anyways (if wxEuphoria picked the American standard, contradicting its parent library).
I thought you weren't being serious,
This is my fault. My apologies.
11. Re: wxEuphoria v16 spellings
- Posted by ArthurCrump Jul 30, 2013
- 1305 views
Hmm.. if wxWidgets has standarized based on British spellings, then it probably makes sense for wxEuphoria to follow suit.
Any American spellings already in the include file must stay there because they may have been used. However, I think they should be removed from the documentation or at least marked as degraded.
Arthur
12. Re: wxEuphoria v16 spellings
- Posted by mattlewis (admin) Aug 07, 2013
- 1213 views
Hmm.. if wxWidgets has standarized based on British spellings, then it probably makes sense for wxEuphoria to follow suit.
Any American spellings already in the include file must stay there because they may have been used. However, I think they should be removed from the documentation or at least marked as degraded.
In general, these things have followed whatever wxWidgets has, which I don't think are always consistent. Typically, I've copied and pasted. It's possible that some were changed. I think consistency with wxWidgets naming is the most important criteria for spelling, and I won't swear that I've always been faithful.
Matt
