AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
![]() ![]() ![]() Look at the byte values for each character in the string and find out exactly what character code the problem quote charter is. You can investigate if EAC is writing correct tags by opening up one of the problem FLAC files in a hex editor and looking at the tag strings. Figure out which part is not working right and figure out why. If you want to figure out what is going wrong with your setups you'll need to look at this as a software QA exercise. If you're just automatically pulling in this bad metadata from the internet when encoding your rips just be aware there's a lot of bad data out there which often needs correcting if you want properly tagged files. So, what I'm getting at is that generally in computing the proper character to use is the single-quote in anything other than word processor documents. You'll find many hardware players such as the one in your car probably doesn't support ID3v2.2 and up or doesn't have an font table with extended character sets to display Unicode characters and will just bork Unicode. If U+2019 is saved in ID3 tags encoded with ID3 standard v1.2 or earlier it is a bad encode, before ID3v2.2 tags could only contain ASCII characters. MS Windows often like to futz with everyone by breaking computing standards like this, especially maddening for many of us tech professionals forced to Windows at work. The standard apostrophe or "single quote" in computing is the ASCII character ' not the Unicode character U+2019 that Windows often converts it to. Some replies here obviously are off-point or irrelevant (like asking how I'm encoding the files that happens after the meta info fetch). I'll try the suggestions where the replier understood my original post. I'm not seeing where to replace the apostrophe with single-quote anywhere, and the Character Replacements box doesn't have a setting for "proper" apostrophe. Right now I literally have to edit each field to replace the apostrophe with a single-quote, BEFORE encoding. The issue is coming from CUETools DB Matadata Plugin, which fetches the artist, album, and song info, not from the encoder I know this because the apostrophe shows in the meta info fields before I encode. I'm not trying to be perfect, but I know that I don't need the "proper" apostrophe, because a single-quote solves all issues for me. The normal keyboard single-quote displays fine in my car, and which is what was encoded from previous CD rippers using freedb, but now that I'm ripping FLAC, I want to at least try to get normal keyboard characters in the folder and file names where I can. On previous devices, some of which I still occasionally use a jukebox, certain characters outside of normal keyboard characters would cause some problems in their app players (like a file or folder or tag like Björk or Trentemøller). In my Altima (default dash player), words like "Don't" displays like "Don’ t", which is of course odd to read. ![]() the fact is, some players don't process or display the character properly. I don't think EAC is causing the apostrophe to be the U+2019 (’), and it doesn't matter if it's the preferred glyph for the apostrophe. Is there a way to have EAC or something automatically change this odd "RIGHT SINGLE QUOTATION MARK" to always be the keyboard single-quote? I've already gone into EAC Options > Character Replacements and the apostrophe or single-quote is not on the list of replaceable characters. ![]() September 2016 on Windows 10 Pro, with metadata plugin "CUETools DB Matadata Plugin V2.1.6". I'm not seeing how to fix this other than manually one title at a time myself after fetching metadata. I of course want the keyboard character because it's probably going to be universally recognized among audio players. When I copy and paste the odd apostrophe into - it says "U+2019 : RIGHT SINGLE QUOTATION MARK ". I'm not sure where else to post this but - I noticed that CDs I ripped through EAC to files and then played in my car's USB drive would show titles with apostrophes as malformed, like "Don' t You" (instead of "Don't You") or just missing text after the apostrophe (or quote?), and when I looked at the file and tag closely, it looks like the metadata plugin puts an odd apostrophe character in the titles that is not a typical keyboard character. ![]()
0 Comments
Read More
Leave a Reply. |