[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Messages should not contain the `\v' escape?
From: |
Sergey Poznyakoff |
Subject: |
Messages should not contain the `\v' escape? |
Date: |
Fri, 08 Sep 2006 18:46:06 +0300 |
Hello,
In some cases messages could legitimately contain the '\v' escape. One
of such cases is the use of GNU argp_parse function, for which this
character means "output the following text after the list of the
options". The GNU projects using this feature include: tar, cpio,
radius, mailutils and cflow. If there are no strong reasons against
allowing the use of `\v', I'd propose the following change:
Index: gettext-tools/src/write-po.c
--- gettext-tools-orig/src/write-po.c 2006-09-08 18:39:28.000000000 +0300
+++ gettext-tools/src/write-po.c 2006-09-08 18:20:31.000000000 +0300
@@ -603,7 +603,7 @@ wrap (const message_ty *mp, FILE *fp, co
*op++ = UC_BREAK_PROHIBITED;
/* We warn about any use of escape sequences beside
'\n' and '\t'. */
- if (c != 'n' && c != 't')
+ if (c != 'n' && c != 't' && c != 'v')
{
char *error_message =
xasprintf (_("\
Regards,
Sergey
- Messages should not contain the `\v' escape?,
Sergey Poznyakoff <=