From: Alex R. <sh...@al...> - 2003-07-16 23:52:25
|
Lorenzo, On Tue, Jul 15, 2003 at 03:31:42PM +0200, Lorenzo Cappelletti wrote: > > > Reports->... (all of them): > > > HTML format reports don't handle correctly accented letters > > > > This comes at a surprise. I can see even cyrillic letters just fine. > > Could you provide a test database and the particular report that > > produces the bug? > > Here it is a minimal tarball (I tried to keep it as small as possible to > save bandwidth). [snip] > I created a 1-person database. The individual has an improbable name [snip] > which includes a good heap of accented letters. [snip] > If I display individual_summary.html with a browser (i.e., elinks or > opera), everything works fine. The accented letters are properly > displayed. But here you are: that means that unicode characters are properly written and the HTML is a proper UTF-8 HTML. Why does the pager (less) not show unicode properly is another question, and honestly I don't have an answer, sorry. Maybe some terminal settings? It's hard to argue that the HTML file is having wrong characters, though. > No luck with individual_summary.pdf, though. With xpdf, I see something This is a known problem -- gramps cannot (at least not yet) print non-ascii chars in PS/PDF. This should be addressed sometime, but it's guaranteed not to work right now :-), so no surprise here. > IMHO, it a matter of encoding. I use ISO-8859-15 while the file is in > UTF-8. I don't know why "LANG=UTF-8 less individual_summary.html" > doesn't work, though. Me neither. Maybe someone more competent on how to display non-ascii in text mode can help us here. > Maybe should the user have the opportunity to choose their encoding? I truly think that the UTF-8 is the right encoding, for the following reasons: 1. All strings entered by the user are stored as unicode strings. This is because we should be able to accomodate all the languages. This also follows the overall GNOME approach. 2. All the modern browsers support UTF-8. 3. If the person really wants/needs to get another encoding, (s)he can convert the HTML to the encoding of choice using whatever tools (s)he likes. I assume if the person has the preference (or just knows what encoding means), (s)he should be able to handle the conversion problem. As a summary, I understand that gramps does not have non-ascii chars problems in HTML. Would you agree? Alex -- Alexander Roitman http://ebner.neuroscience.umn.edu/people/alex.html Dept. of Neuroscience, Lions Research Building 2001 6th Street SE, Minneapolis, MN 55455 Tel (612) 625-7566 FAX (612) 626-9201 |