Project

General

Profile

Bug #6394

INCORRECT OUTPUT OF TRANSLATION

Added by Luciano Goulart about 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Web Interface
Target version:
2.3.2
Start date:
05/23/2016
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.3.x
Affected Architecture:
All

Description

Hello Development Team,

I want to report a problem with incorrect output on PfSense 2.3.1 when the language are defined to 'Portuguese (Brazil)'. Please take a look on the screenshots attached.

Thank you.

Best Regards,

GUI.zip (463 KB) GUI.zip Screenshots Luciano Goulart, 05/23/2016 12:24 PM

Associated revisions

Revision 6ae99aba (diff)
Added by NewEraCracker about 4 years ago

Fix Bug #6394 - Incorrect Output of Translation

Apparently gettext() does not behave correctly when passed an empty string, this commit ensures gettext() is called only with non-empty strings

Revision 94b5eb1f (diff)
Added by NewEraCracker about 4 years ago

Fix Bug #6394 - Incorrect Output of Translation

Apparently gettext() does not behave correctly when passed an empty string, this commit ensures gettext() is called only with non-empty strings

(cherry picked from commit 6ae99aba5cab12440d88dd9ddaa6535c3b9b5d82)

Revision bb44b41a (diff)
Added by NewEraCracker about 4 years ago

Fix Bug #6394 - Incorrect Output of Translation

Apparently gettext() does not behave correctly when passed an empty string, this commit ensures gettext() is called only with non-empty strings

(cherry picked from commit 6ae99aba5cab12440d88dd9ddaa6535c3b9b5d82)

History

#1 Updated by Jim Pingle about 4 years ago

  • Target version changed from 2.3.1 to 2.3.2
  • Affected Version set to 2.3.1

#2 Updated by Jorge M. Oliveira about 4 years ago

This PR should fix the issue:
https://github.com/pfsense/pfsense/pull/3011

Apparently gettext() does not behave correctly when passed an empty string, this commit ensures gettext() is called only with non-empty strings.

#3 Updated by Chris Buechler about 4 years ago

  • Status changed from New to Resolved
  • Affected Version changed from 2.3.1 to 2.3.x

fixed, thanks NewEraCracker

Also available in: Atom PDF