I wanted to put his name Japanese seiyuu 都ほのか in page http://www.animecharactersdatabase.com/viewone.php?id=14111 discipline Game and gave me ????
Why did this happen? you can fix it please.
Thank you

Fixed.

Be sure you use UTF-8.

Also, I updated the page so that if you load the page again, you can change the voice again.

Thank again for adding voice actor names.

[ Edited Jan 18, 2009 ]

私は日本語を少し読むと書くをできます。あなたも？

Looking at that seiyuu name, I suddenly remembered something important. See, 都ほのか (Honoka Miyako) is actually an adult game pseudonym for the seiyuu 萩原えみこ (Emiko Hagiwara). She also has other pseudonyms like 井村屋さくら (Honoka Imuraya) and 井村屋さくら (Sakura Imuraya). Of course, Ms Hagiwara is not the only one. Many seiyuu use pseudonyms like these, and you have to decide how your system is going to deal with this.

In my case, I created a separate table for seiyuu aliases, storing simply a name (kanji or otherwise) and a foreign key to the actor table. For Emiko Hagiwara, to extend the example, I could have three entries in the alias table (or six if I wanted to store the romaji, etc). When entering the actor for a part, my system looks up the name in the alias table, and if it is found, automatically links to the actual person instead. This way, of course, I lose the information of what alias was used in the particular game/anime, but in my case I don't care – as long as I have the name of the actual actor/actress.

What do you think, Rei?

Kyareshi Looking at that seiyuu name, I suddenly remembered something important. See, 都ほのか (Honoka Miyako) is actually an adult game pseudonym for the seiyuu 萩原えみこ (Emiko Hagiwara). She also has other pseudonyms like 井村屋さくら (Honoka Imuraya) and 井村屋さくら (Sakura Imuraya). Of course, Ms Hagiwara is not the only one. Many seiyuu use pseudonyms like these, and you have to decide how your system is going to deal with this.

Actually, I didn't know that. The increases the priority of coding a better Seiyu system. ^^

Kyareshi In my case, I created a separate table for seiyuu aliases, storing simply a name (kanji or otherwise) and a foreign key to the actor table. For Emiko Hagiwara, to extend the example, I could have three entries in the alias table (or six if I wanted to store the romaji, etc). When entering the actor for a part, my system looks up the name in the alias table, and if it is found, automatically links to the actual person instead. This way, of course, I lose the information of what alias was used in the particular game/anime, but in my case I don't care – as long as I have the name of the actual actor/actress. What do you think, Rei?

Putting that idea aside for the moment, let's look at the basic idea: Each character can be assigned multiple seiyu, and each seiyu can be assigned multiple details. If we want to get fancy, the details can be keyed to specific works.

If your system achieves that, I think it's a success.

[ Edited Jan 19, 2009 ]

私は日本語を少し読むと書くをできます。あなたも？

Rei Putting that idea aside for the moment, let's look at the basic idea: Each character can be assigned multiple seiyu, and each seiyu can be assigned multiple details. If we want to get fancy, the details can be keyed to specific works. If your system achieves that, I think it's a success.

This is, in fact, exactly what my system does.

You'll basically end up with something like this.



Excuse the double post, I couldn't make an attachment otherwise.

No prob with the double post, I've had the same issue... normally I start a new post to upload the image, preview it so it uploads and gives me the IMAGE code, copy and paste that into the original reply, and cancel the new post. ;-) I'll admit, the forum really shouldn't require such a brutal roundabout way, but it works.


Hmm, hmm, well for the most part it looks good.

To help me figure this out, I took a few random statements, and jotted down who they'd fit into a DB...

None of this is true, just an example.


Aya voiced Konata
vid,cid
Aya is named Aya Hatate
vid,type,text
Aya is named A-ya-ha-ya-te
vid,type,text
Aya was born on Sept 25th
vid,type,text
Aya voiced Ichigo
vid,cid
Aya looks like this
vid,type,text
Aya goes by this name when she worked on Hoshiful characters
vid,type,text



So, I'm looking at three new tables.

voiceactors: id, name
voicedetail: id, vid, dtype, detail
voiceassignments: vid,cid

In `voiceactors` I'll store a unique ID for one human being, and their real name in English.
In `voicedetail` I'll store whatever details people want to add to the person. The dtype flag will alter what's done with the detail. Like, 1 would be their Japanese name and would override the default name on Japanese pages, and show up as an additional detail on English pages with the header Japanese name. 2 would be a recent photo of them to use as an avatar. 3 would be an additional image to go into an image gallery etc etc.
Then `voiceassignments` is a typical way to assign one item to multiple works.

Everything else, I'll handle in PHP.

私は日本語を少し読むと書くをできます。あなたも？

I have to question your practice of making all of your columns soft. Instead of having, for sake of argument, a "birthdate" field and a "bloodtype" in the voiceactor tables, you're having a row for each of these in the voicedetail table. In other words, to make sense of all of these detail rows, an external set of ID's is needed (1=Japanese Name, 2=Photo, etc.). Why do you overcomplicate like this when you could simply store these values in the appropriate fields?

Also, how is your system going to know who is the correct actor/actress to credit? For example, if chiqui1970 enters 都ほのか in the seiyuu field, how will your system know that this is actually Emiko Hagiwara? None of the three new tables you suggested seems to store this kind of information. Refer to the "Seiyuu Alias" entity in my diagram – this is the kind of table you seem to be missing.

Kyareshi I have to question your practice of making all of your columns soft. Instead of having, for sake of argument, a "birthdate" field and a "bloodtype" in the voiceactor tables, you're having a row for each of these in the voicedetail table. In other words, to make sense of all of these detail rows, an external set of ID's is needed (1=Japanese Name, 2=Photo, etc.). Why do you overcomplicate like this when you could simply store these values in the appropriate fields? Also, how is your system going to know who is the correct actor/actress to credit? For example, if chiqui1970 enters 都ほのか in the seiyuu field, how will your system know that this is actually Emiko Hagiwara? None of the three new tables you suggested seems to store this kind of information. Refer to the "Seiyuu Alias" entity in my diagram – this is the kind of table you seem to be missing.

It'll all work out. I haven't actually coded anything yet, so I'm just saying what's on my mind at the moment...

About using appropriate fields. I'm keeping it simple by making only a single piece of info (their name in English) required that'll be stored in the initial table.

Same thing with adding a name. We keep it simple. So when someone type in a name, the system will query the voice actor table test for matching names, then failing that, it will deep query the details table for that name, then backtrace it to the correct ID. Failing that, it'll create a new voice actor and ID with the name given, and toss it into a QC pool where moderators can easily merge duplicate voice actors into single entities.

Maybe it's great, maybe it sucks, but all I know is once I start coding, something good will take shape.

私は日本語を少し読むと書くをできます。あなたも？

Rei Maybe it's great, maybe it sucks, but all I know is once I start coding, something good will take shape.

I admire your confidence.

Well, if you run into any trouble, you know you can always turn to me for advice.