Comment #3 on issue 6816 by x...@chromium.org: Header/footer placement when printing RTL pages http://code.google.com/p/chromium/issues/detail?id=6816
From Idan: I am not sure what the right option is here. It is a little strange to flip the header/footer when the user prints an English page (http://www.cnn.com for instance) from within the Hebrew version of Chrome (or not flipping them when a Hebrew page is printed from the English version of Chrome). I noticed that the Hebrew version of IE7 doesn't change the header/footer (in fact, the "Page 1 of 1" string is not even translated). So we will surely do better than IE if we flip based on the browser UI language. From Jeremy: Agreed, doesn't make much to print English pages with the header and footer flipped, regardless of UI language. WDYT about flipping if both the page's language and Chrome UI are RTL? IMHO, not doing anything would be fine, but flipping in the right conditions is one of those nice touches that would delight users, and considering the current state of the bidi web in non-IE browsers, we could do with more of that :) From Idan: Flipping if both the page's language and the Chrome UI are RTL is certainly a good start and it is probably a good idea to implement things this way initially. However, if you print http://www.ynet.co.il from within the English version of Chrome, wouldn't you prefer that the head/footer are flipped? Not sure what the answer is. I think we should do what you suggested initially because there are some tricky issues with BiDi text handling when the browser's UI language is not RTL. For example, it is not safe to mark a string with an LRE/PDF pair if the browser UI is not RTL because if the user doesn't have the RTL fonts installed, then we'll show squares around the text in question. Thus, I think it is much safer to apply the heuristic only if the browser UI is RTL. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
