[Tickets #10829] Re: Add missing units current wind condition

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/10829
------------------------------------------------------------------------------
  Ticket             | 10829
  Updated By         | Jan Schneider <jan at horde.org>
  Summary            | Add missing units current wind condition
  Queue              | Horde Base
  Version            | Git master
  Type               | Bug
  State              | Resolved
  Priority           | 1. Low
  Milestone          |
  Patch              | 1
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Jan Schneider <jan at horde.org> (2011-12-05 11:22) wrote:

> For translators it is in many cases better to have an idea about the  
> context in which words are used.

This is generally true and a common problem when using gettext for  
translations.

> Also, you removed a number of ':' characters. As an example, until  
> now I use different translations for 'Humidity: ' and 'Humidity'. In  
> current conditions there is ample of space for the full translation  
> 'Relatieve vochtigheid' (the previous translation 'vochtigheid' is  
> incorrect in this context), but in the forecast table this would  
> take up way too much space, so here the abbreviation 'RV' (which is  
> also common) is used. By removing the colon, I have no way to make  
> this difference anymore.

This doesn't make sense. The idea behind the gettext approach is to  
*avoid* strings that only have minor difference, to make the  
translator's life easier and reduce redundancy. Adding arbitrary  
punctuation or whitespace just to allow different translations is  
completely against this idea and actually makes it harder for  
translators.

> In fact, it would prefer (in table headers) to include the HTML  
> codes <th> and </th> in the gettext string, so that for a translator  
> it is immediately clear how this string is used (and that a short  
> translation is preferred over a longer one).

No. Adding markup is completely unacceptable and even worse than  
adding whitespace or unnecessary punctuation.

> Last, you also changed the "Precipitation<br />chance" to  
> "Precipitation%schance", effectively hardcoding the <br /> in the  
> process. Even if a language would have a very short translation for  
> this, the break is now mandatory. I can imaging that for instance in  
> Japanese of Chinese this would require a few characters, making the  
> break undesireable.

This could be solved by using newlines instead, and wrap the  
translated text with nl2br().