Quoting Vittra:

Quote:
Quoting kdh1949:

Quote:
I'm asking this since I don't have the film in question.  Is she the ONLY actor who's first name is in all caps?

If I recall correctly, the entire cast is completely capitalized other than the name in question which has the last name all in lower case. I agree with Martian and Hal. Credited As feature should only be used if the name differs from the Most Credited name, not just due to Capitalization inconsistencies.

You recall correctly.

Quoting TheMadMartian:

Quote:
We already use 'standard capitalization rules' when the credits are in all caps.

No we don't - as this thread clearly shows. For role names, yes, but not for cast and crew names.

Quoting TheMadMartian:

Quote:
If we were to enter them all the same way, regardless of formatting, this thread would be moot.

Indeed it would. But that goal won't be achieved by telling the users to enter the names using "standard capitalization rules" that simply don't apply to names. Besides: which "standard capitalization rules" would you have in mind? One for each "country of origin" of the person we're profiling? I just see a huge mess...

Remember that as of yet, Invelos is consistently VERY hung up on copying formatting as close as we possibly can: for instance, we track the lack or presence of a comma in suffixed names, we even track the lack or presence of a space between someone's initials. I don't see why we'd go the opposite route here - seems entirely inconsistent with those earlier decisions.

It's also worth noting that, contrary to what some people like to declare, the program DOES distinguish between cases:

Quoting Ken Cole:

Quote:
The DBISAM database engine does distinguish cases.

The CLT doesn't, but that doesn't mean anything - for instance, the CLT also doesn't deal with birth years, or with the aforementioned ruling on suffixed names. Instead, the program is specifically set up to always "protect" the value in your local database, to keep it from being accidentally overwritten when you download an update:

Quoting Ken Cole:

Quote:
For actor names, this operates that way intentionally so that if a profile update comes down it won't automatically change the actor name case.

That's great, but it certainly shouldn't be confused with "the program doesn't care about capitalization". It does.

Quoting T!M:

Quote:
Quoting TheMadMartian:

Quote:
If we were to enter them all the same way, regardless of formatting, this thread would be moot.

Indeed it would. But that goal won't be achieved by telling the users to enter the names using "standard capitalization rules" that simply don't apply to names. Besides: which "standard capitalization rules" would you have in mind? One for each "country of origin" of the person we're profiling? I just see a huge mess...

For my proposed rule change, I went with wording similar to what is used in the TITLE section of the rules:  "Enter names, and roles, using standard capitalization rules.  For non-English titles, use capitalization rules common to the language of the feature."

Now that is just a first draft and I am happy to tweak the wording as needed.

Quote:
Remember that as of yet, Invelos is consistently VERY hung up on copying formatting as close as we possibly can: for instance, we track the lack or presence of a comma in suffixed names, we even track the lack or presence of a space between someone's initials. I don't see why we'd go the opposite route here.

Apples and oranges, in my opinion.  While they are hung up on the use, or lack, of characters, they have gone out of their way to ignore capitalization.  In fact, the only capitalization that the program cares about is the first word in each name field.  For all others, the program treats them as the same character.  'JADAGRACE' = 'Jadagrace' = JaDaGrAce' = 'JADAgrace' = 'JadaGRACE', ad infinitum.

Since the program doesn't care about capitalization, I don't see why we should.  Again, JMHO.

Quoting T!M:

Quote:
Quoting TheMadMartian:

Quote:
If we were to enter them all the same way, regardless of formatting, this thread would be moot.

Indeed it would. But that goal won't be achieved by telling the users to enter the names using "standard capitalization rules" that simply don't apply to names. Besides: which "standard capitalization rules" would you have in mind? One for each "country of origin" of the person we're profiling? I just see a huge mess...

Remember that as of yet, Invelos is consistently VERY hung up on copying formatting as close as we possibly can: for instance, we track the lack or presence of a comma in suffixed names, we even track the lack or presence of a space between someone's initials. I don't see why we'd go the opposite route here - seems entirely inconsistent with those earlier decisions.

As you very well know, commas and spaces will break the linking of actors.  Capitalization will not.  That is the essential and critical difference.

Commas and spacing are not "formatting" they are additional ascii characters in the name.  We have no current Rule that tells us to ignore them.  We do currently have a Rule that tells us to utilize standard capitalization when names are in all caps.  So far, we have had very, very few issues with people being able to figure this out.  We have one user who wants to apply the "entirely capitalized" rule to each individual part of the name instead of to the whole name as most of the rest of us would.  The fact that we have one user who just loves to go his own way (upstream, so to speak) does not mean we have a problem with the "standard capitalization" rule.

In actual point of fact, Hal, relative to , Jr. and other such suffizes, we have an experss comment from Ken on how Profiler handles such data and our STANDARD is , Jr. Which does not interfere with capturing the data within CA as necessary.

Skip

That is correct to PROFILER's standard...not Hal's.

Skip

Quoting Woola:

Quote:
That is CORRECT Hal. I used CA to capture the data for berry, and followed the Rules for Jadagrace using standard caps. I was not twisting an interpretation of the Rules, I followed the Rules and the data, and my notes were a detailed explanation of the same and it was accepted. Use iof CA for this kind of odditiy is the only way we can capture the data accurately.

I don't go running around, hal, trying to twist the Rules into a pretzel, There are ALWAYS going to be oddballs such as this one that crop "outside" of the express Rule because of experience orlack thereof in terms of having seen or not seen. It is a simple process, hal as I explained JADAGRACE is consistent with every other credit on the cast list, like CHRISTIAN BALE, it is berry that is both inconsistent with every other name in the list AND cannot be handled directly within our system but there is a way, in this case,to capture the CA data properly and that does not mean JADAGRACE because that name is consistent with all others and is handled under standard caps.

Skip

Skip

The fact that you cannot see that applying standard capitalization rules to the first name but not to the second name within the same credit is totally bizarre, says everything that needs to be said.

Or put another way, the fact that you cannot see that applying the "exactly as credited" rule to the last name but not to the first name within the same credit is totally bizarre, says everything that needs to be said