10 Replies Latest reply on Jan 5, 2012 10:42 AM by roustabout

    Unicode / Non-Latin Font Support: WHEN?

      I am studying both Japanese and Chinese in college. Obviously, I would like to use my Nook Color to read e-books containing Japanese and Chinese characters -- but I can't.

       

      It makes no sense at all that the Nook Color can display such characters in its web browser, but not in its e-book reader -- and it makes even less sense that Barnes & Noble sells "Nook Books" that contain such characters, when they can't even be read on a Nook.

       

      Please fix it: ADD UNICODE FONT SUPPORT.

       

      And while you're fixing that, please also give us some more fonts to choose from for the reader. The fonts built into it currently are not Unicode fonts, and they're not particularly attractive, either.

        • Re: Unicode / Non-Latin Font Support: WHEN?

          I believe the best solution for you is to return you Nook color and buy something more to your taste.  Too bad you didn't take time to look into all the NC faults before you purchased.

          • Re: Unicode / Non-Latin Font Support: WHEN?

            NookColor can read pdf files with other character sets, but not epub as yet. If your book is available in pdf format, you should try that.

            • Re: Unicode / Non-Latin Font Support: WHEN?

              Here is what works for my Chinese ePub books. I know very little about ePub and CSS. Not sure how much of this depends on the way ePub files constructed.

               1. In Calibre, right-click on the book, select  <Tweak ePub>
               2. Click "Explode ePub", Windows Explorer opens
               3. Go into OEBPS folder, replace stylesheet.css file with shown below
               4. Close Windows Explorer, click <Rebuild ePub>
               5. Send it to Nook Color, do not convert
               6. On NookColor, open the book, turn on <Publisher Defaults>

              @font-face {
                font-family: "DroidFont", serif, sans, sans-serif, monospace;
                font-weight: normal;
                font-style: normal;
                src: url(res:///system/fonts/DroidSansFallback.ttf);
              }
              @font-face {
                font-family: "DroidFont", serif, sans, sans-serif, monospace;
                font-weight: bold;
                font-style: normal;
                src: url(res:///system/fonts/DroidSansFallback.ttf);
              }
              @font-face {
                font-family: "DroidFont", serif, sans, sans-serif, monospace;
                font-weight: normal;
                font-style: italic;
                src: url(res:///system/fonts/DroidSansFallback.ttf);
              }
              @font-face {
                font-family: "DroidFont", serif, sans, sans-serif, monospace;
                font-weight: bold;
                font-style: italic;
                src: url(res:///system/fonts/DroidSansFallback.ttf);
              }
              
              body {
                margin-left: 5%; margin-right: 5%; margin-top: 5%; margin-bottom: 5%;
                font-family: "DroidFont", serif, sans, sans-serif, monospace;
                font-size: medium;
              }
              
              p {
                font-family: "DroidFont", serif, sans, sans-serif, monospace;
              }
              
              div {
                font-family: "DroidFont", serif, sans, sans-serif, monospace;
              }
              
              h1 {
                font-family: "DroidFont", serif, sans, sans-serif, monospace;
                text-align: center;
              }
              
              h2 {
                font-family: "DroidFont", serif, sans, sans-serif, monospace;
                text-align: center;
              }
              
              h3 {
                font-family: "DroidFont", serif, sans, sans-serif, monospace;
                text-align: center;
              }
              
              h4 {
                font-family: "DroidFont", serif, sans, sans-serif, monospace;
                text-align: center;
              }
              
              h5 {
                font-family: "DroidFont", serif, sans, sans-serif, monospace;
                text-align: center;
              }
              
              h6 {
                font-family: "DroidFont", serif, sans, sans-serif, monospace;
                text-align: center;
              }
              
              .CI {
                  text-align:center;
                  margin-top:0px;
                  margin-bottom:0px;
                  padding:0px;
                  }
              .center   {text-align: center;}
              .smcap    {font-variant: small-caps;}
              .u        {text-decoration: underline;}
              .bold     {font-weight: bold;}

               

              The last step, turning on <Publisher Defaults> is very critical.

              Unfortunately, NookColor seems quite forgettable about it. Every time I open another book with the setting OFF, it will switch the setting back globally.

              Hope this helps. Let us know how it works out for you.

               

               

              • Re: Unicode / Non-Latin Font Support: WHEN?
                Would the upcoming update fix this problem ?!!!
                • Re: Unicode / Non-Latin Font Support: WHEN?
                  Irishelf

                  I wish they would have unicode support as well.  Not because I wish to read books in another language, but because I want to learn another language.  From what I'm reading in the forum, even though B&N sells ebooks for learning other languages, the non latin languages show up as nonintelligible symbols.  Why sell ebooks that will not display properly on the technology it's being downloaded on?!  They should either refrain from selling these ebooks, have unicode support on the device, or provide a workaround (and put the workaround in the guide so that those of us with visual impairments don't have to search to find it).  I want to learn Arabic and maybe Chinese, but I need books in large print.  DTB large print versions do not exist, and the characters don't display properly on the NC.  Unicode support would elleviate this problem.  Does anyone know if calibre can be used to fix this (say for example can you use Calibre to convert  Arabic For Dummies with non latin font)?

                  • Re: Unicode / Non-Latin Font Support: WHEN?

                    The absence of Unicode support in epubs is obscene! We're not living in the 20th century anymore! I need to search my books in a variety of languages, including Hebrew, Cyrilic, German, etc. The present limitation is absolutely outrageous and nonsensical. Fire your programmers!

                      • Re: Unicode / Non-Latin Font Support: WHEN?
                        roustabout

                        There is a proposed solution to this problem, iirc the author of the solution was Tom51.

                         

                        There is a proposed solution in this  very thread.  

                         

                        I'll try to find the link to Tom's, but would someone please let us know if the solutions work?   I'd love to know if these work for people.  I've suggested a few folks try it, at which point... nothing more is heard on the topic.