View Single Post
Old 01-20-2010, 06:13 PM   #3
rogue_ronin
Banned
rogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-booksrogue_ronin has learned how to read e-books
 
Posts: 475
Karma: 796
Join Date: Sep 2008
Location: Honolulu
Device: Nokia 770 (fbreader)
Quote:
Originally Posted by Jellby View Post
In general, one would use the original name of the author in his/her own language, of course, but sometimes the "translated" names have a too strong tradition to ignore them, or there is no "own language". As a second choice, I'd use the language the book is written in. The problem is I would have "Homer" for an English book and "Omero" for an Italian book, and these would be sorted as different authors, when they are actually one and the same. Or there could be different languages in the same book.
If you're using ePub, there is a "file-as" attribute. You could put the author name as appropriate to language in the "creator" element for each book, and use the "file-as" attribute to store a sort-of master name -- whatever you want to use as that author's core identity in your database.

In terms of something like Dublin Core, you may be out of luck. As it exists right now, there is no such "file-as" attribute. There is an "Attributed name" MARC Relator Code, though -- and a "Creator" code, and an "Originator" code. I haven't found clear definitions for these codes, but one may be appropriate.

m a r

EDIT: Whoops, found the definitions here...

Last edited by rogue_ronin; 01-20-2010 at 06:18 PM.
rogue_ronin is offline   Reply With Quote