On Aug 3, 2013, at 15:03 , Peng Yu <[email protected]> wrote:
>> Let me see if I follow you here. In essence, you're arguing that because
>> many websites do something stupid and incorrect with BibTeX, BibDesk
>> should follow suit? Sounds great! :)
>
> No. You didn't follow what I mean. For an end user, as long as he can
> get the title capitalized, he doesn't have to care how it is done
> (whether by the way you mentioned or by add {}). However, the way you
> suggest does require more effort in the user end (and every users have
> to do the same thing to fix it as this is not the default).
Yes, I did follow what you meant. You want to inflict this on all users,
and that's not going to happen as long as I have commit privileges on
this project. I gave you a workaround, since you don't care about a
correct solution.
> This cause
> a huge burden to users. I can not speak for other websites who choose
> to add '{}'. But the fact that many of them do this, means that adding
> '{}' don't cause much trouble (otherwise, it is already be fixed by
> now). Therefore, for the convenience of users, it is better to add
> such a feature (even you consider this feature is wrong to be added).
Do you have any idea how much work we've had to do in order to import
so-called BibTeX from websites, including commercial providers who
should know better? This type of half-assed solution is a huge problem
with bibliographic data, but I assume it's borne of incompetence
rather than laziness.
Suppose BibDesk does this. How are users going to react when the items
they add manually don't have this behavior? That's more of a debugging
hassle, because some entries will print as-shown, and others won't.
You'll have the same debugging hassle, because you've allowed users to
shoot themselves in the foot with incorrect behavior.
--
Adam
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Bibdesk-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bibdesk-develop
