The "â€¦" originates from encoding confusion somewhere along
What seems to happen - and I guess Jürgen could explain better and
hopefully provide a fix somewhere - is the following. I'm looking at
AddScriptFromFileAction.py source code which is python.
1) the ellipsis character is a three byte UTF8 character in the
source code (e2 80 a6)
2) the string is read by pylupdate5 and put into a ts file as
â€¦ (this is in my linux, pylupdate5
3) those three HTML hexadecimal entities are interpreted as three
characters on the browser
If I change the three character junk string with an ellipsis
character in the ts file I download from transifex, the string is
correctly translated in QGIS. Otherwise it is not.
It is originally an ellipsis ('...' as one character). You
should translate it with an ellipsis or with three dots.
ok... I found the commits in github. They explain a lot to me.
On 11.03.2018 10:06, Ari Jolma wrote:
> On 10.03.2018 13:13, Jürgen E. Fischer wrote:
>> obsolete string replaced with
>> in 9a3bfa01c290c0ed3fb6648d5bd8171ec212b27a
> Would you care to explain this operation a bit more?
> I can see that there are a lot of strings with the "â\200¦" ending in
> the ts file that have "vanished" and a similar new string with
> ellipsis ending.