Yaniv Abir wrote:
> In some languages, such as Arabic or Hebrew, there is a distinction
> between male and female. Accordingly, it is custom to right guides in
> the male form ( for historical reasons) and add a notice that sais
> "although this guide is written in the male form, it is directed at both
> sexes.
Questions of localisation don't concern us - the relevant translation
team can adjust the language and style of the document to suit the
particular culture.
However, we do need as a team to decide on the convention for doing this
in _English_. There was a mailing list thread about this some time ago,
and nothing was decided. What does the team feel is the best convention
to adopt for gender?
When this is decided, we can update the styleguide.
Matt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Yaniv, thanks for your bug report.
Yaniv Abir wrote:
> In some languages, such as Arabic or Hebrew, there is a distinction
> between male and female. Accordingly, it is custom to right guides in
> the male form ( for historical reasons) and add a notice that sais
> "although this guide is written in the male form, it is directed at both
> sexes.
Questions of localisation don't concern us - the relevant translation
team can adjust the language and style of the document to suit the
particular culture.
However, we do need as a team to decide on the convention for doing this
in _English_. There was a mailing list thread about this some time ago,
and nothing was decided. What does the team feel is the best convention
to adopt for gender?
When this is decided, we can update the styleguide.
Matt enigmail. mozdev. org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iD8DBQFEgjUWtSa F0w5rBv8RAoPsAJ 0TCcK73gYJcOkNJ 7NKaFNf3jHk5wCZ AQGQ 7sd7yUPyM21FE2l k=
uS/BMF+
=8SmC
-----END PGP SIGNATURE-----