Message-ID: <1362024324.1928.1556113111534.JavaMail.javamailuser@localhost> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1927_712544228.1556113111533" ------=_Part_1927_712544228.1556113111533 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Please note that the German de_DE localization for other open so= urce sw often comes in two versions: in a formal ("Sie") and an i= nformal ("Du") version. For instance, many WordPress users prefer= the informal version (about 60% of the users). However, for professional b= logs in corporate environments, the formal version is often more appropriat= e.
Now, when I started translating from EN to DE for Ushahidi, I used the f= ormal version but then quickly switched to the informal version because - a= nd that's what I am still missing with the strings on transifex - most text= seems to be for the backend only. So the German de_De version is now based= on the informal "Du" (only).=C2=A0
It would be great to have= a test sandbox which directly pulls the localization for an instant previe= w and also some kind of info which text belongs to the frontend and which t= ext belongs to be backend (as this sometimes matters). Thx!=C2=A0
This also applies to Crowdmap!
einheitlicher / unique Synta= x:
alert =3D=3D> Meldung
alerts =3D=3D> Meldungen
report =3D=3D> Bericht
reports =3D=3D> Berichte
Deployment =3D=3D> Installation
Badge =3D=3D> Emblem
post =3D=3D> Artikel
Follower/s =3D=3D> Follower/s
Following =3D=3D> ???
t.b.c.
------=_Part_1927_712544228.1556113111533--