[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         | arjen+horde at de-korte.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
------------------------------------------------------------------------------


arjen+horde at de-korte.org (2011-12-05 09:58) wrote:

> The strings should be mostly cleaned up now.

I'm not to thrilled about some changes you made here. You removed a  
lot of context information from the gettext strings. :-)

For translators it is in many cases better to have an idea about the  
context in which words are used. For instance, the word 'at' can have  
at least half a dozen meanings in Dutch, depending in which context it  
is used. So I welcome the change in line 206, but something similar  
would be needed in line 313. In the worst possible scenario, someone  
would add a gettext where 'at' is used to indicate a location and at  
least for the Dutch translation I would run into trouble.

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. 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).

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.

We really shouldn't go down the road of removing all context  
information from the translation, since that will degrade the quality  
of translation.