Merge lp:~deryck/launchpad/upstream-empty-display-707825 into lp:launchpad
Status: | Merged |
---|---|
Approved by: | Deryck Hodge |
Approved revision: | no longer in the source branch. |
Merged at revision: | 12586 |
Proposed branch: | lp:~deryck/launchpad/upstream-empty-display-707825 |
Merge into: | lp:launchpad |
Diff against target: |
62 lines (+9/-8) 2 files modified
lib/lp/translations/stories/standalone/xx-translationmessage-translate.txt (+2/-5) lib/lp/translations/templates/translations-macros.pt (+7/-3) |
To merge this branch: | bzr merge lp:~deryck/launchpad/upstream-empty-display-707825 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Abel Deuring (community) | code | Approve | |
Review via email: mp+53050@code.launchpad.net |
Commit message
[r=adeuring][bug=707825] When sharing translations between upstream and a package, display a "(not translated yet)" message if one side has set the translation to an empty string.
Description of the change
This is a fix for bug 707825, which outlines the situation
where a translation has been set to an empty string upstram,
causing the message to not appear as a suggestion for the
package side.
This fix ensure that a "(not translated yet)" message
appears if the suggested text is ''.
I discussed this a couple different times with Henning.
I fixed up the existing page test to display the text I
expected and then added a couple conditions in the template
to make this work out.
= Launchpad lint =
Checking for conflicts and issues in changed files.
Linting changed files:
lib/lp/
lib/lp/
./lib/lp/
151: not well-formed (invalid token)
150: Line has trailing whitespace.
nice branch! Just a minor remark:
@@ -65,7 +68,8 @@
tal:attributes= "id string: ${submission/ origin_ html_id} ; "submission/ suggestion_ text">
</tr>
<tr
- class string:discreet secondary ${dismissable}">
+ class string:discreet secondary ${dismissable}"
+ tal:condition=
I'd prefer to have "tal:condition" before "tal:attributes". While the ZPT machinery does not care about the order of tag attributes, I find it easier to read the tal: attributes in ZPT's execution order.