Hello all,

here's the new version. I've addressed two issues:

* Providing context.

  I've followed the advice from Andreas Schwab and provided examples of
  the whole phrases as they are printed by gdb. In this way, the code is
  readable, and the message file has even more context than is provided
  by the translated string itself. I've done this only for permutations;
  obvious cases like "big endian" / "little endian" have been rewritten.
  The relevant excerpt from the output of "xgettext -o a.po -k_
  --add-comments=i18n *.c" is attached.

* String concatenation style.

  I've gone by the following guidelines:

  - If all lines of a string (including "\n" and quotes) fit in their
    respective source lines (with "printf", etc.), which means they are
    surely shorter than 80 characters, divide them as "" "". Example:
    gdb/gdb/arm-tdep.c, @@ -2902,24 +2904,23 @@.

  - If not all lines of a string fit in their source lines, divide them
    with \. Leave the first line of a string on the first source line if
    it fits in it (gdb/gdb/auxv.c, @@ -295,6 +295,6 @@); otherwise,
    place it on the next source line after "\ (gdb/gdb/amd64fbsd-nat.c,
    @@ -178,9 +178,9 @@).

Comments?

With kind regards,
Baurjan.


2004-12-15  Baurjan Ismagulov  <ibr@ata.cs.hun.edu.tr>

	* ada-valprint.c, aix-thread.c, alpha-nat.c, alphabsd-nat.c,
	alphanbsd-tdep.c, amd64-linux-nat.c, amd64-tdep.c,
	amd64bsd-nat.c, amd64fbsd-nat.c, arch-utils.c, arm-linux-nat.c,
	arm-tdep.c, armnbsd-nat.c, armnbsd-tdep.c, auxv.c, avr-tdep.c:
	i18n markup.