Quoting hal9g:

Quote:
It just complicates the programming, but I'm sure he would be up to it if he chose to go this route.

Like you, I have an extreme amount of faith in Ken's capabilities, so I agree with your assessment. Essentially, it's all possible. But is it all likely? All in all, it seems like a HUGE overhaul of the program - surely the biggest we'd have ever seen. Maybe it will happen someday - sometime after that iPhone version is done, I suppose - or maybe not, but I'm not holding my breath. In the meantime, I'll be trying to make the best of what we've got right now.

Quoting Closed:

Quote:

I am following the standard cap rukles, but diacrits are not part of capitalization,(...)

Yes, they are in many languages.

Quoting Closed:

Quote:
BTW Martian, if you are suggesting that we ditch "standard caps", while i don't like it aesthetically, that would be preferable to using fictional or imaginary data.

But we are already using fictional and imaginary data.  The problem is, you prefer one type of fictional and imaginary data, while others prefer a differnet type.

While I haven't suggested that we ditch standard caps, it would certainly end a lot of debate and would be 100% as credited.

Quoting T!M:

Quote:
One gripe with this scenario is that whereas all linking information is currently stored local, it would then be in that illustrious "linking file" and we'd only store the actual "as credited" data in our profiles. Sounds lovely, but what if I'm absolutely certain that two name variants need to link together, but somehow I can't get it approved? Then it won't be part of the "linkfile", and they won't link in my local database? I'd have to contribute and get everything accepted to be able to have my local database reflect my own work?

I'm sure a lock-system could be created. So that if you have created a link in the linking file you have downloaded locally, that would not be overwritten when downloading an updated file, if you have locked that particular link? I'm no programmer, but shouldn't be impossible(?)

edit: wow, so many replies here in between. I guess mine is already dated 

Quoting Closed:

Quote:
Quoting hal9g:

Quote:
Quoting Closed:

Quote:
Hal:

I have a suggestion for you, if you are going to try and impose intent, then i suggest you ASK what that was to begin with. I know that galls you and Martian, but you aren't talking about what the designed intent was. Trust me.

You seem to be unaware of the fact that "capitalization" rules only deal with whether to capitalize the first letter of each word.

If you disagree, please provide a link to an authoritative source for "capitalization" rules which describes how to convert all caps to mixed case.

DUH! I am not the one trying to arguue for imaginary data, Hal. You are, the Rules are what they are and what they have been and what we have operated under for FIVE years. You want to scrap it ALL, you want to play with fiction not fact, you want o use "correct" as defined by HAL,. not by the filmmaker's data, after all Hal knows moer than do the filmmakers and if he doesn't then all we have to do isd ask surfeur and Taro betweemn the three of you...you have all the answers, and martian can fill in what's left. That's a plan....NOT.

In other words, you cannot provide a source for how to convert all caps to mixed case? 

Is it difficult to add characters (such as the en dash) to a program?

Someone had a suggestion that I would also like to bring up; should invelos implement the utilization of the locks? For example, many DVDs are correctly entered in the database. Why shouldn't the online database be locked so that erroneous data can not be entered.

After hearing that, I thought that maybe a committee or the screeners could make a final assessment and then implement the locks.

I do understand that this is premature as far as this thread is concerned but would be implemented once the final decision is made.

Edit: I see Draxen suggested the locks idea first. 

Quoting hal9g:

Quote:

As long as the new "linking" file contained an entry telling the program that Rene Bond=Paula Schnall, then when you double click on Paula Schnall in the cast list, it would display all films where she's credited as either Rene Bond or Paula Schnall.

OK I got it, but I continue to hope I will be able to do it as I do actually in my personal database (if only for the good reason that many of the adult films I own are pay to download version and not dvd, so impossible to contribute).

Quoting hal9g:

Quote:
Quoting No_Name_Needed:

Quote:
It's possible and this is maybe something I've missinterpreted since the first time you had talked about this. So here an exemple with Rene Bond:

Credit screencap from Mary! Mary!

She is credited here under the Paula Schnall alias (wich of course I've confirm on screen)

Presently as I do it in my database this credit is entered like this :

Rene Bond (Paula Schnall) as Policewoman

Will it rest the same with your propose system or it will become :

Rene Bond (no credited as) as Policewoman
Paula Schnall as Policewoman (this is the 2.X way)

It would be entered Paula Schnall as Policewoman

As long as the new "linking" file contained an entry telling the program that Rene Bond=Paula Schnall, then when you double click on Paula Schnall in the cast list, it would display all films where she's credited as either Rene Bond or Paula Schnall.  Additional entries in the "linking" file would be used to link profiles where any other aliases may have been used.  But you would not have to edit any of the cast lists at all.  Just enter the on-screen credit.

Hal.... I always said I thought your suggestion sounded better... but out of curiosity... I know there isn't many like it. But how would handle a credit like Smithee where more then one person may have used the credit?