Quoting northbloke:

Quote:
Quoting 8ballMax:

Quote:
Where did you get that from? The first "written language" was discovered by a German archaeologist found at the tomb of King Scorpion the First in Abydos, near Luxor, in Egypt.

Admittedly I am stretching it a bit, but...

Just a bit   .

Ummm because he wants it his way?

Skip

Quoting 8ballMax:

Quote:
I just don't get it.

The rules state to use "credited as" when the credited name differs from the actor's name. If it can be documented that Gong is a surname then what is wrong with submitting a profile change of Li Gong [Gong Li]? Why the need for a total revamp of the program to accomodate Asian names when it can be accomplished simply by using "credited as"?    

Because you double the work of those who actually add Asian cast and crew.  You make us reverse the names to a wrong format, then reverse them back again in the Credited As field!  By just entering the credited way the first time, you get it right.  The only people trying to be accomadated are the ones who want the surname in the 2nd field.  As Skip as pointed out, that is only useful for searching, something that is done locally.  The extra work should be on those who want that for their own private databases.

Quoting synner_man:

Quote:
Quoting 8ballMax:

Quote:
I just don't get it.

The rules state to use "credited as" when the credited name differs from the actor's name. If it can be documented that Gong is a surname then what is wrong with submitting a profile change of Li Gong [Gong Li]? Why the need for a total revamp of the program to accomodate Asian names when it can be accomplished simply by using "credited as"?    

Because you double the work of those who actually add Asian cast and crew.  You make us reverse the names to a wrong format, then reverse them back again in the Credited As field!  By just entering the credited way the first time, you get it right.  The only people trying to be accomadated are the ones who want the surname in the 2nd field.  As Skip as pointed out, that is only useful for searching, something that is done locally.  The extra work should be on those who want that for their own private databases.

OHHH...soooooo much work to type a name in the "credited as" field. I'm so sorry you have to do so much heavy lifting . BTW, I don't make you do anything .

Quoting 8ballMax:

Quote:
I just don't get it.

The rules state to use "credited as" when the credited name differs from the actor's name. If it can be documented that Gong is a surname then what is wrong with submitting a profile change of Li Gong [Gong Li]? Why the need for a total revamp of the program to accommodate Asian names when it can be accomplished simply by using "credited as"?    

Except that the "credited as" field is to be populated with what's on screen in addition to the "Name" field which is to be populated with the most commonly credited name according to the CLT.

You would not find Li Gong as the most commonly credited name, therefore, it cannot be used in the "Name" field regardless of any documentation that it is the "correct" name.

As has been stated over and over, the "Name" field is not to be used for the "correct" name but the most commonly credited name.

I have the answer for you, north. You have finally turned me totally off with your attitude and behavior. Follow the rules and use th substring filter, that will do what you want, end of subject.

Skip

Quoting Unicus69:

Quote:
synner_man illustrates the basic problem with this request.  It assumes that everyone who owns DVDs, with an Asian cast, want it this way.  If you guys don't all agree, how can we expect Ken to pick a side?  Whichever way he goes, someone is going to be unhappy.

But that's the same for all feature requests - not just this one. I remember there were people unhappy with some of the changes between ver 2.x and ver 3. It's highly unlikely there will ever be 100% support for a feature request, all we can do is say what we think could be changed and how it would affect the data or program and let Ken decide the best way to go forward if at all.

Edit: I don't remember every one agreeing about how to deal with accented characters but Ken still managed to "pick a side" there. (I've quoted that as I don't believe that's what Ken does - he has his own "side").

Going fron 3 fields to 2 doesn't solve anything.  Unless I am missing something, we will still have to deal with the issue of parsing double surnames.