| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0001613 | PacketFence | captive portal | public | 2012-12-02 07:17 | 2015-02-18 10:59 |
|
| Reporter | muhlig | |
| Assigned To | | |
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | open | |
| Platform | | OS | | OS Version | |
| Product Version | 3.6.0 | |
| Target Version | | Fixed in Version | | |
|
| Summary | 0001613: no proper i18n support in some parts of captive portal |
| Description | I did Polish translation of PacketFence captive portal. All is done in UTF-8. /captive-portal renders well formatted translated page. However /signup produces translated page, but all UTF-8 encoded Polish diacritic marks are malformed (replaced by "?"). So there is a difference before formatting in /captive-portal and /signup web pages. |
| Additional Information | I found there are two render_template functions in pf code and pf::web::admin::render_template is the one which works well. Instead, pf::web::render_template (imported by pf::web::guest) damages diacritic marks. Then I found https://github.com/inverse-inc/packetfence/pull/60 [^] and I thought these findings are related to each other.
Looks like you use in admin page code some functions which are not used in other pages although they should be. Namely, these functions are: web_get_locale {} and _init_i18n {}. So, basically, i18n works correctly only for languages without diacritic marks.
Because of this issue I'm not able to start deploying of PacketFence solution in my network and I'm afraid I'm not able to fix it myself so I'd like to know if you're going to change captive program code further any soon to make it behave correctly like the admin part of it. |
| Tags | No tags attached. |
|
| fixed in git revision | |
| fixed in mtn revision | |
|
| Attached Files | |
|
Relationships 
Relationships 