I want to embed this character into my config string:
http://www.fileformat.info/info/unicode/char/2756/index.htm
$char(2756) doesn't work, and $char(10070) doesn't work. I know the glyph exists with the font I'm using, because I can see it on the character map. I know it's possible, because my last config I used (before I lost it all in a foobar crash), I was able to get the character to show up.
Full Version: special characters in foobar
If I am not mistaken, the U+2756 is hex so when converted to decimal $char(10070) should have worked. Are you absolutely sure that your current font supports this character? Have you tried running foobar under different locales either with AppLocale or by changing your windows regional settings for non-unicode programs?
Where are you trying to display this character? Have you had success displaying other extended characters in the same place?
Where are you trying to display this character? Have you had success displaying other extended characters in the same place?
QUOTE(Yotsuya @ Nov 7 2007, 01:08) 
If I am not mistaken, the U+2756 is hex so when converted to decimal $char(10070) should have worked. Are you absolutely sure that your current font supports this character? Have you tried running foobar under different locales either with AppLocale or by changing your windows regional settings for non-unicode programs?
Where are you trying to display this character? Have you had success displaying other extended characters in the same place?
I'm using wine with ubuntu.
When I do $char(10070) it shows up as a colon. If I try to use the font FreeSans, it'll be a colon. But if I use Bitstream Vera Sans, it'll show up correctly. Both fonts have the glyph according to the character map... Odd.
I have been encountering similar problems with japanese text under wine+ubuntu. I resolved most of my character mapping issues by replacing the fonts in ~/.wine/drive_c/windows/fonts with those found in C:\Windows\Fonts on a separate xp install. I do still occasionally come across a few characters that don't get mapped properly and display as a colon as you have described above. I don't think this is a problem with foobar itself but with wine's international support which is rather dismal IMO (Have you been able to input anything using SCIM with wine?).
Foobar is not designed to work on wine. Don't expect to find much support on these forums for your setup but I would suggest continuing to plug away at different fonts until you can find something you can live with.
When selecting a font there is a pull-down menu for "Script". You may wish to try different scripts for your font. If you are using exotic characters you may need to choose a script other than "Western". You may need to explore using WineLoc to reveal additional script types.
Foobar is not designed to work on wine. Don't expect to find much support on these forums for your setup but I would suggest continuing to plug away at different fonts until you can find something you can live with.
When selecting a font there is a pull-down menu for "Script". You may wish to try different scripts for your font. If you are using exotic characters you may need to choose a script other than "Western". You may need to explore using WineLoc to reveal additional script types.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.