This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: GCC2 native language support now available


Paul Eggert <eggert@twinsun.com> writes:

>    Let me suggest that you use `cc', with no capitals and no prefix `g',
>    for a single domain name.

> I like this suggestion, but it has some technical consequences: if gcc2
> and egcs both use `cc', and if both install translation files in the
> usual places, then gcc2 and egcs would share translation files.

> One solution is to share the `cc' textdomain between gcc2 and egcs.
> [...]  I hope that gcc2 and egcs development will merge soon; this will
> simplify matters greatly.

According to Ulrich, it is not going to happen soon.  And the little needs
of the translation project are far from being a sufficient incentive for
a merge.  Let's consider it is not happening.  What about `cc' (or maybe
`gcc2' -- yet I do not like the `g' prefix -- but that's my own problem :-)
as a textual name for `gcc2', and `egcs' as a textual domain name for `egcs'?

> For your convenience I placed a compressed copy of that file at:
> ftp://alpha.gnu.org/eggert/gcc.pot.gz

To repeat extracts from the blurb I sent to you in a previous mail:

   Please send ready POT files to `translation@iro.umontreal.ca', using MIME,
   `mailshar', `uuencode' or any other popular means ensuring its integral
   transmission.  Use the string "DOMAIN-VERSION.pot" somewhere in the
   subject line of your invoice.

This is at least how I know the textual domain and precise version numbers,
as these are not set within the POT file itself.  I also want to be damn
sure that the real maintainers of the compilers, those responsible for it,
agree on the textual domain name.  It is inconvenient to change, once set,
so I prefer that we have a prudent attitude, and check well.

The blurb also says:

   The very first time you submit a POT file, the translation project also
   needs to know which email address to use for notifications, and if you want
   PO files sent in full to you (instead of a mere URL where to find them).

Normally, the notification address is the official maintainer of the package.
If delegation occurs, I presume the maintainer should do the delegation.
About needing translation disclaimers or not from the translators, I also
presume there is no choice about this, as long as the C compilers are
meant to be distributed by the FSF, as they make an obligation for them.

By GNU rules, `en_UK' translations should not be distributed without
proper translation legalese having been filled and returned to the FSF
by the translator.  The FSF acknowledges the receipt of such legalese
to the translation project, and this "unlocks" the uploading mechanism
for that translator (as long as the translation teams agree, which is the
usual case).  If you did that PO file, Paul, let me suggest that you fill
and return a translation disclaimer (file DISCLAIM in the `gettext' package.
Let me suggest, as a translator, that you fetch and read:

   http://www.iro.umontreal.ca/contrib/po/reply

to know how translators usually proceed.  I may also send it to you by
email, on request.

> Sorry, I don't easily see how to shoehorn GCC's version numbers into
> the forms currently allowed by the translation project.

I'm not sure, but maybe the maintainers will find a way that is agreeable
to them, which fits the schemes we currently use.  If not, I'll prefer that
the C compiler maintainers decide how they want to proceed, rather than
see us choosing something in their name, or otherwise forcing their hand.

> How about if we set PACKAGE=cc and VERSION=2.8.1.19980813 for the August 13
> snapshot?  This numbering scheme sorts lexicographically in the proper way.

Whatever the scheme is, I will have to adjust the translation project scripts
if it is not in the usual list of schemes.  This is much more a matter of
decision to take, than a matter of technical difficulty.  I'm surely opened
to more versioning scheme, yet it is good for everybody that we make some
effort for recycling existing ones, if they fit, than inventing new ones.

-- 
François Pinard                            mailto:pinard@iro.umontreal.ca
Join the free Translation Project!    http://www.iro.umontreal.ca/~pinard


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]