Author |
Message |
Registered: March 13, 2007 | Posts: 21,610 |
| Posted: | | | | Quoting Taro: Quote: Skip, you are trying my patience very, very much:
1. I quote you directly from this very thread.: http://www.invelos.com/Forums.aspx?task=viewtopic&topicID=468923&PageNum=11 I see now that you didn't say it but copy-pasted it from another user. So my apologies for missing that. I retract what I said.
2. You didn't offer any solution to the issue posted by Yves as well, only the usual rant which actually does not solve the issue at hand.
3. I sincerely hope your solution for Asian names never gets signed off by Ken as it as based on a total lack of understand of the issue at hand. I find it rather striking that you seem so convinced you have the perfect solution to the problem when a Japanologist (me) and a Japanese native (my wife) think it does not address the issue at all and in fact makes matters worse.
And finally, no, I will not go away because you demand it. I find it very offensive you even wrote that. Taro: I am so sorry that I am trying your patience. You are trying mine, that's Ok for you but not for me. Ok, I get that...NOT. NO Ttaro, you quoted me as saying something which I did not say. Your link took me to Rho | | | ASSUME NOTHING!!!!!! CBE, MBE, MoA and proud of it. Outta here
Billy Video | | | Last edited: by Winston Smith |
|
Registered: March 13, 2007 | Posts: 21,610 |
| Posted: | | | | Kathy:
Martian has seen it he even referred and yes Ken has said that we are no after correct name. But Ken has ruled on this very issue and here we are going over it again. so obviously someone doesn't believe in following what Ken said so if that's fair, then visiting my solution of using the CA system to accomodate this problem for people like Yves and Taro is also fair.<knocks head against the wall> | | | ASSUME NOTHING!!!!!! CBE, MBE, MoA and proud of it. Outta here
Billy Video |
|
Registered: May 26, 2007 | Reputation: | Posts: 599 |
| |
Registered: March 13, 2007 | Reputation: | Posts: 6,635 |
| Posted: | | | | Quoting T!M: Quote: Quoting hal9g:
Quote: Quoting TheMadMartian:
Quote: Just so we are clear, the solution I am thinking of is "François Truffaut [Francois Truffaut]". This would also be exactly the same as using CA for differences in capitalization, which Ken has specifically said "NO" to. Yet we are supposed to diligently track the lack or presence of a comma preceding a Jr./Sr. suffix, or even more futile: the lack or presence of a SPACE between initials. Is it just me, or is there some serious discrepancy there? And you know perfectly well why. Spaces and commas break linking. Capitalization does not. | | | Hal |
|
Registered: March 13, 2007 | Posts: 2,759 |
| Posted: | | | | Quoting TheMadMartian: Quote: Just so we are clear, the solution I am thinking of is "François Truffaut [Francois Truffaut]". Actually in this case it is the solution for a credit 'Francoit Truffaut' because 'François Truffaut' is the common name for this person. But I guess you are correct, he has suggested this even for the case when there is only a single name variant. IMO this could partially work but would be to complicated. |
|
Registered: March 13, 2007 | Posts: 21,610 |
| Posted: | | | | But capitalization can and does misrepresent the data. He could just as easily set ther cap issue up to function as does the suffix and prefix. Or even vice versa. | | | ASSUME NOTHING!!!!!! CBE, MBE, MoA and proud of it. Outta here
Billy Video |
|
Registered: March 13, 2007 | Posts: 21,610 |
| Posted: | | | | Quoting RHo: Quote: Quoting TheMadMartian:
Quote: Just so we are clear, the solution I am thinking of is "François Truffaut [Francois Truffaut]". Actually in this case it is the solution for a credit 'Francoit Truffaut' because 'François Truffaut' is the common name for this person. But I guess you are correct, he has suggested this even for the case when there is only a single name variant. IMO this could partially work but would be to complicated. Not sure how it could possibly be any more complicated than the existing system but....OK I guess. | | | ASSUME NOTHING!!!!!! CBE, MBE, MoA and proud of it. Outta here
Billy Video |
|
Registered: March 13, 2007 | Posts: 2,759 |
| Posted: | | | | Quoting hal9g: Quote: It also does not address role names or Overviews (in all caps). We need no new solution for those because it is usually easy to assign a language to those texts which has its own proper capitalisation rules including the adaptation of accents. |
|
Registered: March 13, 2007 | Posts: 2,759 |
| Posted: | | | | Quoting T!M: Quote: Yet we are supposed to diligently track the lack or presence of a comma preceding a Jr./Sr. suffix, or even more futile: the lack or presence of a SPACE between initials. Is it just me, or is there some serious discrepancy there? No, I still wonder why this has been decided like this. I would prefer standardisation without credited as in those cases similar to the capitalisation variants that you have mentioned. |
|
Registered: March 15, 2007 | Reputation: | Posts: 5,459 |
| Posted: | | | | Quoting RHo: Quote: Quoting TheMadMartian:
Quote: Just so we are clear, the solution I am thinking of is "François Truffaut [Francois Truffaut]". Actually in this case it is the solution for a credit 'Francoit Truffaut' because 'François Truffaut' is the common name for this person. But I guess you are correct, he has suggested this even for the case when there is only a single name variant. IMO this could partially work but would be to complicated. Fine in theory, but would totally screw up the CLT in practice. A program update that gets the system to see e, è, é, ê and ë all as the same letter would I think work much better and wouldn't require a mass change to profiles. |
|
Registered: March 13, 2007 | Reputation: | Posts: 13,202 |
| Posted: | | | | Quoting Prof. Kingsfield: Quote: But capitalization can and does misrepresent the data. He could just as easily set ther cap issue up to function as does the suffix and prefix. Or even vice versa. Actually, if we are being honest, any time we convert from all uppercase/all lowercase into mixed case, it misrepresents the data. The argument being made is, and it is a valid one, if we are going to misrepresent the data, why not misrepresent it properly? | | | No dictator, no invader can hold an imprisoned population by force of arms forever. There is no greater power in the universe than the need for freedom. Against this power, governments and tyrants and armies cannot stand. The Centauri learned this lesson once. We will teach it to them again. Though it take a thousand years, we will be free. - Citizen G'Kar |
|
Registered: March 13, 2007 | Reputation: | Posts: 6,635 |
| Posted: | | | | Quoting RHo: Quote: Quoting hal9g:
Quote: It also does not address role names or Overviews (in all caps). We need no new solution for those because it is usually easy to assign a language to those texts which has its own proper capitalisation rules including the adaptation of accents. I only mention these because some here have claimed that capitalization rules do not cover the process of converting all caps to mixed case. I tend to agree with that position. | | | Hal |
|
Registered: March 13, 2007 | Reputation: | Posts: 6,635 |
| Posted: | | | | Quoting northbloke: Quote: Quoting RHo:
Quote: Quoting TheMadMartian:
Quote: Just so we are clear, the solution I am thinking of is "François Truffaut [Francois Truffaut]". Actually in this case it is the solution for a credit 'Francoit Truffaut' because 'François Truffaut' is the common name for this person. But I guess you are correct, he has suggested this even for the case when there is only a single name variant. IMO this could partially work but would be to complicated. Fine in theory, but would totally screw up the CLT in practice. A program update that gets the system to see e, è, é, ê and ë all as the same letter would I think work much better and wouldn't require a mass change to profiles. ...or a different linking system! | | | Hal |
|
Registered: March 13, 2007 | Reputation: | Posts: 6,635 |
| Posted: | | | | Quoting TheMadMartian: Quote:
Actually, if we are being honest, any time we convert from all uppercase/all lowercase into mixed case, it misrepresents the data. The argument being made is, and it is a valid one, if we are going to misrepresent the data, why not misrepresent it properly? Precisely! | | | Hal |
|
Registered: March 15, 2007 | Reputation: | Posts: 5,459 |
| Posted: | | | | Quoting hal9g: Quote: ...or a different linking system! That would be bloody marvellous! ...also a bloody miracle! |
|
Registered: March 13, 2007 | Posts: 21,610 |
| Posted: | | | | Quoting TheMadMartian: Quote: Quoting Prof. Kingsfield:
Quote: But capitalization can and does misrepresent the data. He could just as easily set ther cap issue up to function as does the suffix and prefix. Or even vice versa. Actually, if we are being honest, any time we convert from all uppercase/all lowercase into mixed case, it misrepresents the data. The argument being made is, and it is a valid one, if we are going to misrepresent the data, why not misrepresent it properly? But Martian that is a language base argument, not an argument which is based upon the data. Placement of diacriticals which do not actually appear On screen is purely fictitious, plain and simple, particulatly uin view of surfeur's revelations to day that there is no standard that he has printed, which means it is not a Ruleof the language, it is at best a custom and if we are now going to start honoring various customs, well that's going to be a mess even in the states. Is it Bobbi Jo// or Bobbi.Jo, I don't know where is she from Mississippi, well that's probably gonna be Bobbi jo//, whew. Talk about nightmares. | | | ASSUME NOTHING!!!!!! CBE, MBE, MoA and proud of it. Outta here
Billy Video |
|