Quoting paulb_99:

Quote:
...
My problem with this is you still expect people to know which name is the first name (Zhang (first name field) Ziyi (last anem field) vs Zhang (last name filed) Ziyi (first name field) (in reverse order).

So you'll still end up with different name variants with different parsing. So mu yopninio remains that a single name field crediting exactly as on screen is the best  and easiest solution.

Paul

solution for that could be not to get forced by the profiler linking an "as credited"-entry (because thats exactly what you what from your "single name"-field) to a 3-parted--"common name"-entry in the database, if you don't know the person at all.

Quoting northbloke:

Quote:
...Although I agree a single name field would be better! 

we have such a field ("as credited"-field), but can't use it as we need

Quoting surfeur51:

Quote:

I think you are missing two things:

- As rules are written, I know many people that will vote no on a contribution like Yun-Fat//Chow [Chow Yun-Fat] arguing that CLT says the contrary.

How will a 'local only' check box change this?  Those same people will vote no because you will still be entering the name in reverse order.

Quote:
- When you have actors that play in many films, you change in a few seconds Chow//Yun-Fat to Yun-Fat//Chow with checked tick-box, and have much more work to take all movies and edit credited as at each time.

So you want to reverse your data, on a local level, then use a check so that it displays properly?  Basically a 'credited as' system where you don't have to type in the 'credited as' name?  Is that what you are asking for?

Quote:
What I cannot understand  is that some users who are not interested in some request that will change nothing for them feel obliged to criticize it, not trying to see that it is important for others. For example, there is a request for option to view last contribution notes prior to accepting an updated profile. I do not even find the smallest interest in that request, but  I said nothing on this thread. If it is good for somebody else, I find normal that they ask it and Ken will decide.

If all Ken wanted were feature requests, he would have implimented a 'feature request FORM'.  The fact that he made it a forum, one where users can express their opinions on them, tells me that he wants more than just suggestions.  He also wants to guage whether or not the community likes or dislikes the request.

Quote:
If you do not want to use the tick box, nothing will change for you.  But for me, it is  very important, much more than bold and italics in overviews or reasons for ratings, or other requests for such futilities against which I never said anything...

This is where you are wrong.  What will change is that some people will want to enter 'Chow Yun-Fat' as 'Yun-Fat/ /Chow' because they have a check box.  That changes things for me.

Quote:
I'm sure that on those forums we can find more than one hundred pages about asian names. There is a problem, and some people try to find solutions and suggest them to Ken via a forum that is made for that.  Those who prefer wrong information to correct one should not try to sabotage their efforts.

This is not a solution as you will still need to have the rules changed for this to work.  Unless, as I noted above, you only want to reverse the names in your local db.

Quoting Unicus69:

Quote:
Quoting surfeur51:

Quote:
I already answered this in a previous page. For people who don't know which is the first name, they act exactly as now, and get the same result. But other users that want a correct display for asian names would be able to get it, which is not the case presently.

= no change for  users who are happy with present situation
= a major improvement for those who want a correct display for asian names.

But you can get it now...it just requires a bit of work and you lose the color coded parsing in the display.  Not sure why the color coding matters when looking at the name, but that is besides the point.

It's not the color coding. It's the correctness of the data. With the example of Mr. Chow his given name=first name is "Yun-Fat" and NOT "Chow".
If this community isn't willing or able to be interested in this difference (and some hardliners here seems to do btw. not you unicus) all this discussions of parsing names etc. are real no-brainers, but with that also becomes the program/database itself. Fact: there is lots of incorrect data out there. Therefore I need not the ProfilerDB.

Quoting Unicus69:

Quote:

For surfeur, it seems to be.  On the last page he said...
Quoting surfeur51:

Quote:

The credited as field works just on one movie profile and shows names in black, with the impossibity to see parsing. A check box works on all occurrences of the concerned  actor and preserve parsing colors.

Colors are important by their meaning. With colors you immediately see the parsing and where is the family name. With credited as feature, you just have black words with no signification attached. That is why I quite never use credited as feature, except for extreme cases, as "Alejandra Flores" credited as "Ivette Gonzalez".

All your long answer to my previous post shows that your reasoning is always with the view of online database, which is a mess that I learned, with regrets, to ignore totally.

My reasoning is about the capacity of the program to allow all users to manage their local database as they wish, and not as other users would love to dictate how they should do.

Quoting surfeur51:

Quote:

Colors are important by their meaning. With colors you immediately see the parsing and where is the family name. With credited as feature, you just have black words with no signification attached. That is why I quite never use credited as feature, except for extreme cases, as "Alejandra Flores" credited as "Ivette Gonzalez".

All your long answer to my previous post shows that your reasoning is always with the view of online database, which is a mess that I learned, with regrets, to ignore totally.

My reasoning is about the capacity of the program to allow all users to manage their local database as they wish, and not as other users would love to dictate how they should do.

I always try and look at things based on how it will impact the on-line db.  That is where most users get their data so having that data correct will affect the most people.  I have not reached the point where I am ready to abandon them.

As to the rest, all users can manage their local database "as they wish".  Yes, you will lose the parsing colors in the display, but I still don't understand why that is such a big deal.

Quoting Unicus69:

Quote:

I always try and look at things based on how it will impact the on-line db. That is where most users get their data so having that data correct will affect the most people. 

This request is to have correct data for asian names. If you wanted correct data, you would support my request rather than  sabotaging it.

Quoting Unicus69:

Quote:
Quoting surfeur51:

Quote:
Quoting Unicus69:

Quote:

I always try and look at things based on how it will impact the on-line db. That is where most users get their data so having that data correct will affect the most people. 

This request is to have correct data for asian names. If you wanted correct data, you would support my request rather than  sabotaging it.

No, this is a request to add a check box for the name field.  The purpose of that check box is to allow people, those that enter asian names in reverse order, to have the names displayed in the correct order without using the 'credited as' field.

Bottom line, this is a request designed to make your life easier..and there is nothing wrong with that...but I would rather Ken address the actual problem.  You may not agree, but this is a forum and I am allowed to express my opinion...just as you are allowed to express yours.