Back to bug 814599

Who When What Removed Added
David Mason 2012-04-30 05:28:18 UTC CC damason
Sean Flanigan 2012-05-29 00:31:46 UTC Target Release --- 1.7
CC sflaniga
Sean Flanigan 2012-05-29 04:13:52 UTC Summary [Validation Option %x variables] position-explicit printf format string should not produce validation warnings %x validation should support positional printf strings (eg %1$s)
Sean Flanigan 2012-06-01 04:55:17 UTC Summary %x validation should support positional printf strings (eg %1$s) RFE: %x validation should support positional printf strings (eg %1$s)
Patrick Huang 2012-07-02 04:50:50 UTC Status NEW ON_DEV
CC pahuang
Assignee runab pahuang
Patrick Huang 2012-07-02 05:28:51 UTC Status ON_DEV ASSIGNED
Patrick Huang 2012-07-03 01:38:17 UTC Status ASSIGNED ON_QA
Patrick Huang 2012-07-05 03:05:52 UTC Status ON_QA ASSIGNED
Patrick Huang 2012-07-06 01:53:03 UTC Status ASSIGNED ON_QA
Sean Flanigan 2012-07-06 06:36:18 UTC Status ON_QA ASSIGNED
Patrick Huang 2012-07-09 06:06:15 UTC Status ASSIGNED ON_QA
Ding-Yi Chen 2012-07-10 01:50:06 UTC Fixed In Version 1.7-SNAPSHOT (20120710-0026)
Ding-Yi Chen 2012-07-10 01:50:20 UTC Status ON_QA VERIFIED
Sean Flanigan 2012-09-11 05:11:18 UTC Status VERIFIED CLOSED
Resolution --- CURRENTRELEASE
Last Closed 2012-09-11 01:11:18 UTC
Patrick Huang 2012-09-13 01:16:52 UTC Doc Text Cause
User wants to use positional printf variables in translation.

Consequence
Positional printf variables will be marked as invalid by current normal printf validation rule.

Change
added a new validation rule to validate against positional printf. This rule and the normal printf rule is mutually exclusive so that users won't get confusing results.

Result
User will be able to use positional printf variables in their translation and still being able to validate.
Patrick Huang 2012-09-13 01:18:55 UTC Doc Type Bug Fix Enhancement
Red Hat Bugzilla 2012-09-13 01:18:55 UTC Doc Type Enhancement Bug Fix

Back to bug 814599