From MAILER-DAEMON Thu Nov 05 09:10:01 2015 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1ZuLEn-0003Zh-Hb for mharc-bug-gettext@gnu.org; Thu, 05 Nov 2015 09:10:01 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:48048) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZuIW1-0005BA-UF for bug-gettext@gnu.org; Thu, 05 Nov 2015 06:15:39 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZuIVy-0007h7-E5 for bug-gettext@gnu.org; Thu, 05 Nov 2015 06:15:37 -0500 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:47168) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZuIVy-0007ga-6V for bug-gettext@gnu.org; Thu, 05 Nov 2015 06:15:34 -0500 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 59BED21221 for ; Thu, 5 Nov 2015 06:15:27 -0500 (EST) Received: from web3 ([10.202.2.213]) by compute3.internal (MEProxy); Thu, 05 Nov 2015 06:15:27 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=qFGsUHeAWgyl97/S9k89ED21wmY=; b=ibWuw pxFG0mRABTF7xe8abo8jmSLDyI2DSc4egA4bDArZLjr3L4HWGYZaT+qoQUGzF4TA +nLuF7uO8YLynXt4P8ArxSZz4E8CicRaipsXn7mCE1DqFBxTIOtE/dpIhMUBAXtU 6aoLqFIu2uwnJ9BxMWABw0VALQtMlagxdQUZS0= Received: by web3.nyi.internal (Postfix, from userid 99) id 2307F10CEBD; Thu, 5 Nov 2015 06:15:27 -0500 (EST) Message-Id: <1446722127.376164.429872729.4407A38B@webmail.messagingengine.com> X-Sasl-Enc: ueKM2qKOwLxba23Yirk7DhF34d3jO5tRe9p9JhL9QR1f 1446722127 From: Chris Lamb To: bug-gettext@gnu.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/mixed; boundary="_----------=_14467221273761641"; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-341322f1 X-Forwarded-Message-Id: <1446721669.375161.429866105.5A9DF6B0@webmail.messagingengine.com> Date: Thu, 05 Nov 2015 11:15:27 +0000 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 66.111.4.29 X-Mailman-Approved-At: Thu, 05 Nov 2015 09:10:00 -0500 Subject: [bug-gettext] [PATCH] Please respect SOURCE_DATE_EPOCH wen generating ChangeLog entries X-BeenThere: bug-gettext@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for GNU gettext List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2015 11:15:39 -0000 This is a multi-part message in MIME format. --_----------=_14467221273761641 Content-Transfer-Encoding: 7bit Content-Type: text/plain Hi, Whilst working on the "reproducible builds" effort [0], we noticed that the gettextize tool generates ChangeLog files and entries which include the current date, rendering generated builds unreproducible (eg. avahi et al). The timestamps are also additionally timezone-specific. The attached patch modifies gettextize to respect SOURCE_DATE_EPOCH[1] if available. I have a GNU contributor agreement (lamby@gnu.org) [0] https://wiki.debian.org/ReproducibleBuilds [1] https://reproducible-builds.org/specs/source-date-epoch/ Regards, -- ,''`. : :' : Chris Lamb `. `'` lamby@debian.org / chris-lamb.co.uk `- --_----------=_14467221273761641 Content-Disposition: attachment; filename="gettext.diff.txt" Content-Id: <1446721584.375027.dde5e400bbf560c145e04b661e98b1bfc3f05069.6E7264B1@content.messagingengine.com> Content-Transfer-Encoding: base64 Content-Type: text/plain; name="gettext.diff.txt" ZGlmZiAtLWdpdCBhL2dldHRleHQtdG9vbHMvbWlzYy9nZXR0ZXh0aXplLmlu IGIvZ2V0dGV4dC10b29scy9taXNjL2dldHRleHRpemUuaW4KaW5kZXggYTRh NzdmNC4uMGQ0MGQyOSAxMDA2NDQKLS0tIGEvZ2V0dGV4dC10b29scy9taXNj L2dldHRleHRpemUuaW4KKysrIGIvZ2V0dGV4dC10b29scy9taXNjL2dldHRl eHRpemUuaW4KQEAgLTM5OCw3ICszOTgsNyBAQCBwbGVhc2U9CiAKICMgVmFy aWFibGU6CiAjIC0gZGF0ZSAgICAgICAgICAgIGN1cnJlbnQgZGF0ZSwgZm9y IHVzZSBpbiBDaGFuZ2VMb2cgZW50cmllcy4KLWRhdGU9YGRhdGUgLS11dGMg KyVZLSVtLSVkYAorZGF0ZT1gZGF0ZSAtLXV0YyAtLWRhdGU9IkAke1NPVVJD RV9EQVRFX0VQT0NIOi0kKGRhdGUgKyVzKX0iICslWS0lbS0lZGAKIAogIyBm dW5jX2NvcHkgZnJvbSB0bwogIyBjb3BpZXMgYSBmaWxlLgo= --_----------=_14467221273761641-- From MAILER-DAEMON Sat Nov 07 09:50:41 2015 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1Zv4pF-0004Rj-CN for mharc-bug-gettext@gnu.org; Sat, 07 Nov 2015 09:50:41 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60876) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zv3u6-0002M5-3B for bug-gettext@gnu.org; Sat, 07 Nov 2015 08:51:38 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zv3u5-0001Nw-7g for bug-gettext@gnu.org; Sat, 07 Nov 2015 08:51:38 -0500 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:42131) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zv3u5-0001Ns-4Z; Sat, 07 Nov 2015 08:51:37 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:37561) by fencepost.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1Zv3u4-0007px-Ee for bug-gnu-gettext@gnu.org; Sat, 07 Nov 2015 08:51:36 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zv3u3-0001Nh-Cl for bug-gnu-gettext@gnu.org; Sat, 07 Nov 2015 08:51:36 -0500 Received: from mail-yk0-x22e.google.com ([2607:f8b0:4002:c07::22e]:36226) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zv3u3-0001Nd-93 for bug-gnu-gettext@gnu.org; Sat, 07 Nov 2015 08:51:35 -0500 Received: by ykba4 with SMTP id a4so211842158ykb.3 for ; Sat, 07 Nov 2015 05:51:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=VnavYp59nlYwOxT1gaTopA2uq0q58LilthskLVE727o=; b=uTDp1Y6KEGPDbi5VxseSM1U897buyI6Ls2Hal4G2bmXYRKPc9apBZMgpWdWjxgQRQR dyJFujO8RG0g2WUpIAAELqcQCjEjHxwQ/NAiI27cY89d5T4y9ms2MTbk6/aqEE2ebu5j 6CcLYZ6GAkN18DEyZwPMAZle8z8T962l+lDIkodwwGUE4BMvlY2GsA5FjAKrr8atsXVQ DkZ1BTYu9fNty/TiEnLfT/DapE2LLXNVkJKzmjQtJrXnDCs5jA9L35gw4jp34F+Nu2hC hQLeFywy+ceUWrpg1aZ2NnjCNmWwzK2GcNLp2ENbogVS1pT9IdRL5nRydlBeh6DQ3Oku lbGQ== MIME-Version: 1.0 X-Received: by 10.129.117.197 with SMTP id q188mr6040911ywc.42.1446904294799; Sat, 07 Nov 2015 05:51:34 -0800 (PST) Received: by 10.129.82.193 with HTTP; Sat, 7 Nov 2015 05:51:34 -0800 (PST) Date: Sat, 7 Nov 2015 14:51:34 +0100 Message-ID: From: =?UTF-8?B?TcOheGltbyBDYXN0YcOxZWRh?= To: bug-gnu-gettext@gnu.org Content-Type: text/plain; charset=UTF-8 X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2001:4830:134:3::e X-Mailman-Approved-At: Sat, 07 Nov 2015 09:50:39 -0500 Subject: [bug-gettext] [RFE] Fail when a not standard concatenation is found X-BeenThere: bug-gettext@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for GNU gettext List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Nov 2015 13:51:38 -0000 Consider this bit of C code: #define CONFIG_FILE "/etc/should/not/do/this" ... char *s = gettext( "Configuration options " "can be changed in:\n" CONFIG_FILE "\n" "with no documentation." ); This is clearly documented as a no-no, but you can find it in the wild anyway. xgettext swallows it, generating: msgid "Configuration options can be changed in:\n" msgstr "" As a translator, I'd rather it errored out and refused to make the po file until the string is well formatted for translation or not marked as translatable. Coders may think otherwise, of course. Is there currently an option to at least detect these cases? If there's not, would it be possible to add it (as just said, I'd prefer no option but an error)? From MAILER-DAEMON Sun Nov 08 09:01:00 2015 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1ZvQWi-0000Ge-Ox for mharc-bug-gettext@gnu.org; Sun, 08 Nov 2015 09:01:00 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39662) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZvIzG-0000zb-UT for bug-gettext@gnu.org; Sun, 08 Nov 2015 00:57:59 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZvIzF-0002c7-4p for bug-gettext@gnu.org; Sun, 08 Nov 2015 00:57:58 -0500 Received: from mail-pa0-x22a.google.com ([2607:f8b0:400e:c03::22a]:33270) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZvIzE-0002c3-W4 for bug-gettext@gnu.org; Sun, 08 Nov 2015 00:57:57 -0500 Received: by pabfh17 with SMTP id fh17so164662108pab.0 for ; Sat, 07 Nov 2015 21:57:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:in-reply-to:references; bh=VRXvd9YKZCajNujUOeCsBcklFWqzA585bSSh+6ZcfDg=; b=Py/656oBBRNpM/C+DJ6S6UNlJrpuf1VIm/dQrozWh70s+2POikm5whqNCqusR7Eqyd 4lVOL9vyMln4lTLiwng4EigweYsX07bkqv3Rr75rcW4wZUalPSmq2FCFHWzj7NawDbBu VFJe2hbFrjER/5zOYbYbRo0JH9u/+G1SNHDIdAG/J5UKlnk9YDCZxLgTti5O45FPd+yH +mKZHPzmoy3XQC2LA9rMxK68prsG/7Tszav7p+L0DJl0H9kilXm6hYuI+EZ9TFAFVv9i TTVa7UA9wxbQjH/eg9qqN5MW+kxYpznpoQ9NSaaQzZYa4kn4UkL/rcrLg21kKJSzbePe NR5A== X-Received: by 10.68.113.194 with SMTP id ja2mr29533193pbb.52.1446962276133; Sat, 07 Nov 2015 21:57:56 -0800 (PST) Received: from localhost.localdomain ([211.108.117.26]) by smtp.gmail.com with ESMTPSA id sz9sm8992671pab.13.2015.11.07.21.57.55 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 07 Nov 2015 21:57:55 -0800 (PST) From: KO Myung-Hun X-Google-Original-From: KO Myung-Hun To: bug-gettext@gnu.org Date: Sun, 8 Nov 2015 14:57:57 +0900 Message-Id: <1446962284-8820-2-git-send-email-komh@chollian.net> X-Mailer: git-send-email 2.6.0 In-Reply-To: <1446962284-8820-1-git-send-email-komh@chollian.net> References: <1446962284-8820-1-git-send-email-komh@chollian.net> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400e:c03::22a X-Mailman-Approved-At: Sun, 08 Nov 2015 09:00:59 -0500 Subject: [bug-gettext] [PATCH 1/8] moop: Replace CR as well as NL with a space X-BeenThere: bug-gettext@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for GNU gettext List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Nov 2015 05:57:59 -0000 * gnulib-local/bulid-aux/moopp (func_check_header_syntax): Replace CR as well as NL with a space. --- gnulib-local/build-aux/moopp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) mode change 100755 => 100644 gnulib-local/build-aux/moopp diff --git a/gnulib-local/build-aux/moopp b/gnulib-local/build-aux/moopp old mode 100755 new mode 100644 index 96a50a6..0e2dbb1 --- a/gnulib-local/build-aux/moopp +++ b/gnulib-local/build-aux/moopp @@ -306,12 +306,12 @@ func_check_header_syntax () } class_end_lineno=`expr $methods_lineno + $class_end_lineno` sed_extract_methods="$class_end_lineno"',$d;1,'"$methods_lineno"'d' - methods=`sed -e "$sed_remove_comments" < "$file" | sed -e "$sed_extract_methods" | tr '\n' ' ' | tr ';' '\n' | sed -e 's,[ ]*$,,'` + methods=`sed -e "$sed_remove_comments" < "$file" | sed -e "$sed_extract_methods" | tr '\r\n' ' ' | tr ';' '\n' | sed -e 's,[ ]*$,,'` sed_remove_valid_arg1_lines='/([ ]*'"$classname"'_t[ ]*[A-Za-z_0-9]*[ ]*[,)]/d' sed_extract_method_name='s,^.*[^A-Za-z_0-9]\([A-Za-z_0-9][A-Za-z_0-9]*\)[ ]*(.*$,\1,' methods_with_bad_arg1=`echo "$methods" | sed -e "$sed_remove_empty_lines" -e "$sed_remove_valid_arg1_lines" -e "$sed_extract_method_name"` if test -n "$methods_with_bad_arg1"; then - methods_with_bad_arg1=`{ echo "$methods_with_bad_arg1" | sed -e 's/$/, /' | tr -d '\n'; echo; } | sed -e 's/\(, \)*$//'` + methods_with_bad_arg1=`{ echo "$methods_with_bad_arg1" | sed -e 's/$/, /' | tr -d '\r\n'; echo; } | sed -e 's/\(, \)*$//'` func_fatal_error "$file: some methods don't have a first argument of type ${classname}_t: $methods_with_bad_arg1" fi } -- 2.6.0 From MAILER-DAEMON Sun Nov 08 09:01:01 2015 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1ZvQWj-0000Hx-5s for mharc-bug-gettext@gnu.org; Sun, 08 Nov 2015 09:01:01 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39661) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZvIzG-0000za-UP for bug-gettext@gnu.org; Sun, 08 Nov 2015 00:57:59 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZvIzD-0002by-PR for bug-gettext@gnu.org; Sun, 08 Nov 2015 00:57:58 -0500 Received: from mail-pa0-x236.google.com ([2607:f8b0:400e:c03::236]:33967) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZvIzD-0002bu-Jw for bug-gettext@gnu.org; Sun, 08 Nov 2015 00:57:55 -0500 Received: by padhx2 with SMTP id hx2so156303643pad.1 for ; Sat, 07 Nov 2015 21:57:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id; bh=CyqixL7DM19HBBrp+xiYxqiA9FdK1oiilbrJGIJ/Ooc=; b=Nxx3p9Khh0mNQKr2CyptWhgGmcHlrL0oZo36f1Y5G4aisOwgeJh3zOJOqwAYPXtQZm +5NwfCsxxKFZqr4QTfLKkt12+FUgaVSmMi+iKFKxgZmDQtyDdO++oyaCA7qdktZb0gHD OZlmjSBJ6rcd96LP6IMsn7waLatPeDw8qhEuttQhpzjnZLCAsnAAz2Z8twUbYF8e5zv7 3Ztjd8PpMAh7WWoXM6VmZ+8uuJAEC9KERJO1MGnMVuD+yzTEkXdVomJJJbffaAAdFwC7 Y00F+UIYJ0519Qs3VvPxjUDXwz2FtZpBxUt2XhKg7WdQ6A+tNK3k5fzdI4yfrFhhpf4d 7YZQ== X-Received: by 10.68.106.130 with SMTP id gu2mr29796280pbb.98.1446962274805; Sat, 07 Nov 2015 21:57:54 -0800 (PST) Received: from localhost.localdomain ([211.108.117.26]) by smtp.gmail.com with ESMTPSA id sz9sm8992671pab.13.2015.11.07.21.57.53 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 07 Nov 2015 21:57:54 -0800 (PST) From: KO Myung-Hun X-Google-Original-From: KO Myung-Hun To: bug-gettext@gnu.org Date: Sun, 8 Nov 2015 14:57:56 +0900 Message-Id: <1446962284-8820-1-git-send-email-komh@chollian.net> X-Mailer: git-send-email 2.6.0 X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400e:c03::236 X-Mailman-Approved-At: Sun, 08 Nov 2015 09:00:59 -0500 Subject: [bug-gettext] [PATCH] OS/2 patches X-BeenThere: bug-gettext@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for GNU gettext List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Nov 2015 05:58:00 -0000 Hi/2. These are OS/2 patches. Review, please... [PATCH 1/8] moop: Replace CR as well as NL with a space [PATCH 2/8] test-lock: Do not include sched.h on kLIBC [PATCH 3/8] build: Do not include os2compat.[ch] [PATCH 4/8] gettext-runtime: Fix name resolution failures on kLIBC [PATCH 5/8] intl: Support UNIXROOT in BINDTEXTDOMAIN () on EMX [PATCH 6/8] libasprintf: Build a shared library on OS/2 [PATCH 7/8] gettext-tools: Use a short name for DLLs on OS/2 [PATCH 8/8] xgettext, cldr-plurals: Fix linkage on OS/2 From MAILER-DAEMON Sun Nov 08 09:01:01 2015 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1ZvQWj-0000JF-K3 for mharc-bug-gettext@gnu.org; Sun, 08 Nov 2015 09:01:01 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39660) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZvIzG-0000zZ-UL for bug-gettext@gnu.org; Sun, 08 Nov 2015 00:57:59 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZvIzG-0002cG-50 for bug-gettext@gnu.org; Sun, 08 Nov 2015 00:57:58 -0500 Received: from mail-pa0-x22b.google.com ([2607:f8b0:400e:c03::22b]:33271) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZvIzF-0002cC-Vn for bug-gettext@gnu.org; Sun, 08 Nov 2015 00:57:58 -0500 Received: by pabfh17 with SMTP id fh17so164662382pab.0 for ; Sat, 07 Nov 2015 21:57:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:in-reply-to:references; bh=cPYbasmrWWpQT9kqGwa9a7FGA9KHoW56GcnY8VJ6VkM=; b=vVoC3cN1oPLxNaHvB+T6vi5r6b0a/YH8L/AKEe7VqyT52jPAAcaWrTJLu1h2oJPaB0 19q/w/91ppNo9PuW2lDX2ouwKr1CajqJMGAR2BH5N3/nE5RQPbdus+pON34R/jiFny2k fbhVFRV1me6NzFeoheVCzX8lFy/76efCslBOL11FQfpXeywWd8Y2A62sZe2wjVk+FpMk 73XDeojkLTBKBNTrS28ED1CE/O8wpYAfsWA0KswvdM3HR5gtG0cQIxAZAofRVot/Bhg3 N7ubQjZ3ZMX//GsO++7CbNwsQVM8zQoTUfodRy7kEVkI9RQZ3es39xwxE2eloMzmAVxw yAPg== X-Received: by 10.67.13.107 with SMTP id ex11mr30272704pad.126.1446962277463; Sat, 07 Nov 2015 21:57:57 -0800 (PST) Received: from localhost.localdomain ([211.108.117.26]) by smtp.gmail.com with ESMTPSA id sz9sm8992671pab.13.2015.11.07.21.57.56 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 07 Nov 2015 21:57:57 -0800 (PST) From: KO Myung-Hun X-Google-Original-From: KO Myung-Hun To: bug-gettext@gnu.org Date: Sun, 8 Nov 2015 14:57:58 +0900 Message-Id: <1446962284-8820-3-git-send-email-komh@chollian.net> X-Mailer: git-send-email 2.6.0 In-Reply-To: <1446962284-8820-1-git-send-email-komh@chollian.net> References: <1446962284-8820-1-git-send-email-komh@chollian.net> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400e:c03::22b X-Mailman-Approved-At: Sun, 08 Nov 2015 09:00:59 -0500 Subject: [bug-gettext] [PATCH 2/8] test-lock: Do not include sched.h on kLIBC X-BeenThere: bug-gettext@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for GNU gettext List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Nov 2015 05:57:59 -0000 kLIBC does not have sched.h * gettext-runtime/tests/test-lock.c: Do not include sched.h on kLIBC. --- gettext-runtime/tests/test-lock.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/gettext-runtime/tests/test-lock.c b/gettext-runtime/tests/test-lock.c index 0be81f2..ec5695c 100644 --- a/gettext-runtime/tests/test-lock.c +++ b/gettext-runtime/tests/test-lock.c @@ -81,7 +81,11 @@ #if TEST_POSIX_THREADS # include -# include +# ifndef __KLIBC__ +# include +# else +# define sched_yield() pthread_yield() +# endif typedef pthread_t gl_thread_t; static inline gl_thread_t gl_thread_create (void * (*func) (void *), void *arg) { -- 2.6.0 From MAILER-DAEMON Sun Nov 08 09:01:02 2015 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1ZvQWk-0000Lm-Em for mharc-bug-gettext@gnu.org; Sun, 08 Nov 2015 09:01:02 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39694) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZvIzJ-000108-KV for bug-gettext@gnu.org; Sun, 08 Nov 2015 00:58:02 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZvIzI-0002cz-M4 for bug-gettext@gnu.org; Sun, 08 Nov 2015 00:58:01 -0500 Received: from mail-pa0-x22e.google.com ([2607:f8b0:400e:c03::22e]:36412) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZvIzI-0002cu-GN for bug-gettext@gnu.org; Sun, 08 Nov 2015 00:58:00 -0500 Received: by pacdm15 with SMTP id dm15so140372729pac.3 for ; Sat, 07 Nov 2015 21:58:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:in-reply-to:references; bh=CNe0ry8VgCfiNf4aG5RTVDpp6rZvO9ZMk38qLFDebyE=; b=gjhTTHEn0cxa2LF12/VhShDKNxXtZZgcWJOXMNzLysPaj0md5ZEXAY4aebrk1QkBOM 4lzFlxeuJ8b15E65bdzC0v5yaxQ1vxaot66hGdeUs3GCBnLeGBMO3ll0EXRhG/kk0yxC FU4nsqsnS+oKdndb6IV3v2ad2klUku57mz6HS6YyKQMg81OlLCvx+Mq1pOhYgtak3ztq IRL2jgBNZMTXz/hSqAA4DwCRwb6hfLxo1PZPSYfiisdE3SirxJjigFEoW0d4dUJ7N77z gk4f+T1idr4wPxChR6Manw28Au/tywS3Bb8Gum6YdLIUxbVnbruy7VWQYGsK/ohuQiH6 JJ3Q== X-Received: by 10.66.124.135 with SMTP id mi7mr30549792pab.102.1446962280037; Sat, 07 Nov 2015 21:58:00 -0800 (PST) Received: from localhost.localdomain ([211.108.117.26]) by smtp.gmail.com with ESMTPSA id sz9sm8992671pab.13.2015.11.07.21.57.58 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 07 Nov 2015 21:57:59 -0800 (PST) From: KO Myung-Hun X-Google-Original-From: KO Myung-Hun To: bug-gettext@gnu.org Date: Sun, 8 Nov 2015 14:58:00 +0900 Message-Id: <1446962284-8820-5-git-send-email-komh@chollian.net> X-Mailer: git-send-email 2.6.0 In-Reply-To: <1446962284-8820-1-git-send-email-komh@chollian.net> References: <1446962284-8820-1-git-send-email-komh@chollian.net> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400e:c03::22e X-Mailman-Approved-At: Sun, 08 Nov 2015 09:00:59 -0500 Subject: [bug-gettext] [PATCH 4/8] gettext-runtime: Fix name resolution failures on kLIBC X-BeenThere: bug-gettext@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for GNU gettext List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Nov 2015 05:58:02 -0000 kLIBC already has _nl_default_dirname and _nl_msg_cat_cntr in its own gettext implmenetation. * gettext-runtime/intl/dcigettext.c: Do not declare _nl_default_dirname on kLIBC. * gettext-runtime/intl/gettextP.h: Define _nl_msg_cat_cntr to libintl_nl_msg_cat_cntr on kLIBC. --- gettext-runtime/intl/dcigettext.c | 2 +- gettext-runtime/intl/gettextP.h | 3 +++ 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/gettext-runtime/intl/dcigettext.c b/gettext-runtime/intl/dcigettext.c index 8a3f091..c0faf18 100644 --- a/gettext-runtime/intl/dcigettext.c +++ b/gettext-runtime/intl/dcigettext.c @@ -323,7 +323,7 @@ const char *_nl_current_default_domain attribute_hidden #endif /* Contains the default location of the message catalogs. */ -#if defined __EMX__ +#if defined __EMX__ && !defined __KLIBC__ extern const char _nl_default_dirname[]; #else # ifdef _LIBC diff --git a/gettext-runtime/intl/gettextP.h b/gettext-runtime/intl/gettextP.h index bbd2139..f3a9ded 100644 --- a/gettext-runtime/intl/gettextP.h +++ b/gettext-runtime/intl/gettextP.h @@ -219,6 +219,9 @@ struct binding /* A counter which is incremented each time some previous translations become invalid. This variable is part of the external ABI of the GNU libintl. */ +#if defined __KLIBC__ && !defined _LIBC +# define _nl_msg_cat_cntr libintl_nl_msg_cat_cntr +#endif #ifdef IN_LIBGLOCALE # include extern LIBGLOCALE_DLL_EXPORTED int _nl_msg_cat_cntr; -- 2.6.0 From MAILER-DAEMON Sun Nov 08 09:01:03 2015 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1ZvQWl-0000Ny-GQ for mharc-bug-gettext@gnu.org; Sun, 08 Nov 2015 09:01:03 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39736) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZvIzM-00010g-1L for bug-gettext@gnu.org; Sun, 08 Nov 2015 00:58:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZvIzL-0002dz-8s for bug-gettext@gnu.org; Sun, 08 Nov 2015 00:58:03 -0500 Received: from mail-pa0-x22f.google.com ([2607:f8b0:400e:c03::22f]:36417) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZvIzL-0002du-4D for bug-gettext@gnu.org; Sun, 08 Nov 2015 00:58:03 -0500 Received: by pacdm15 with SMTP id dm15so140373344pac.3 for ; Sat, 07 Nov 2015 21:58:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:in-reply-to:references; bh=5V7+tSrp0VrFHuET6oDtLNtwBAj4ZfpELWAXZdfx8bY=; b=ayFeHsu91c/S/VsVAZgTM2q8LYJzq6kpg96/eCXKeDzkBE+xJHDDtHynau++bSWAnF txdpZva4pKR9CQGLcrUCLjIcUw9cbChKrrkr+4gWOlKIpL8tGPE5JHYTfxCDpzmsOvZm 9WUwkr1OPMBnqZN4plVnS6qx7sPWTERiZ9+TdElN/gOT38lUEQ2WrtA7OhzZhwUwo1m8 0FRvKd7Eik/So3JJfhQvl60aCbjxkLCKVmOcud85+Cm2tiwX2nnoqZDuRfPyXWjGA9H1 3m2s1CAxYM1EoiezvL+W1vVdev/oinpofX/BAceURYc7gDG8H17X2OLUAbM1MOfsijRH 9wbw== X-Received: by 10.66.222.68 with SMTP id qk4mr30308370pac.89.1446962282636; Sat, 07 Nov 2015 21:58:02 -0800 (PST) Received: from localhost.localdomain ([211.108.117.26]) by smtp.gmail.com with ESMTPSA id sz9sm8992671pab.13.2015.11.07.21.58.01 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 07 Nov 2015 21:58:02 -0800 (PST) From: KO Myung-Hun X-Google-Original-From: KO Myung-Hun To: bug-gettext@gnu.org Date: Sun, 8 Nov 2015 14:58:02 +0900 Message-Id: <1446962284-8820-7-git-send-email-komh@chollian.net> X-Mailer: git-send-email 2.6.0 In-Reply-To: <1446962284-8820-1-git-send-email-komh@chollian.net> References: <1446962284-8820-1-git-send-email-komh@chollian.net> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400e:c03::22f X-Mailman-Approved-At: Sun, 08 Nov 2015 09:00:59 -0500 Subject: [bug-gettext] [PATCH 6/8] libasprintf: Build a shared library on OS/2 X-BeenThere: bug-gettext@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for GNU gettext List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Nov 2015 05:58:07 -0000 * gettext-runtime/libasprintf/configure.ac (LTNOUNDEF): Set to -no-undefined on OS/2. --- gettext-runtime/libasprintf/configure.ac | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gettext-runtime/libasprintf/configure.ac b/gettext-runtime/libasprintf/configure.ac index a7c2811..659e414 100644 --- a/gettext-runtime/libasprintf/configure.ac +++ b/gettext-runtime/libasprintf/configure.ac @@ -44,7 +44,7 @@ LT_INIT([win32-dll]) case "$host_os" in # On Cygwin, without -no-undefined, a warning is emitted and only a static # library is built. - beos* | mingw* | cygwin*) LTNOUNDEF='-no-undefined' ;; + beos* | mingw* | cygwin* | os2*) LTNOUNDEF='-no-undefined' ;; *) LTNOUNDEF='' ;; esac AC_SUBST([LTNOUNDEF]) -- 2.6.0 From MAILER-DAEMON Sun Nov 08 09:01:04 2015 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1ZvQWl-0000Oc-Ra for mharc-bug-gettext@gnu.org; Sun, 08 Nov 2015 09:01:03 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39815) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZvIzP-000118-Ad for bug-gettext@gnu.org; Sun, 08 Nov 2015 00:58:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZvIzM-0002eZ-KN for bug-gettext@gnu.org; Sun, 08 Nov 2015 00:58:07 -0500 Received: from mail-pa0-x22d.google.com ([2607:f8b0:400e:c03::22d]:33981) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZvIzM-0002eN-FM for bug-gettext@gnu.org; Sun, 08 Nov 2015 00:58:04 -0500 Received: by padhx2 with SMTP id hx2so156305608pad.1 for ; Sat, 07 Nov 2015 21:58:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:in-reply-to:references; bh=RTZ1heW7d4OSmkSTx+QMVl/WPR977ubAZzboCrkTTeA=; b=IgIw5rkHfbCwJx0pP5Z/X+NcqMKL/VxK4H27O3fWC5v0YfvnH/yOXqBfkIl6N64bEc hIlog+JHu23VPun3VcXRTNCiIHDmchPnPZ1JlsSbnrjiJWnvEO9pZVeoToBYSDEPvdwz sud20tZpwPBRN/BF7cO9WLMmB1HhO+mCzLhfvZG3Pxi2wN4w2WOsjPBff2/qn36r9mJU N7SfbEL6/P4/7TGJXeE3xC8KQRnb8QNxydA0EyFmQSGbTLF/1/QR6zNrc+/9mv4p9Fnl Tj3MyFLRCoXRhQlMHyx3ZdeEEO3oDc1DvZb58pHAFuxqUvXlpIW6iff/Z7/FD/peisbE EufA== X-Received: by 10.68.106.69 with SMTP id gs5mr29456667pbb.91.1446962283956; Sat, 07 Nov 2015 21:58:03 -0800 (PST) Received: from localhost.localdomain ([211.108.117.26]) by smtp.gmail.com with ESMTPSA id sz9sm8992671pab.13.2015.11.07.21.58.02 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 07 Nov 2015 21:58:03 -0800 (PST) From: KO Myung-Hun X-Google-Original-From: KO Myung-Hun To: bug-gettext@gnu.org Date: Sun, 8 Nov 2015 14:58:03 +0900 Message-Id: <1446962284-8820-8-git-send-email-komh@chollian.net> X-Mailer: git-send-email 2.6.0 In-Reply-To: <1446962284-8820-1-git-send-email-komh@chollian.net> References: <1446962284-8820-1-git-send-email-komh@chollian.net> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400e:c03::22d X-Mailman-Approved-At: Sun, 08 Nov 2015 09:00:59 -0500 Subject: [bug-gettext] [PATCH 7/8] gettext-tools: Use a short name for DLLs on OS/2 X-BeenThere: bug-gettext@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for GNU gettext List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Nov 2015 05:58:08 -0000 OS/2 does not support a DLL name longer than 8 characters. * gettext-tools/configure.ac (OS2): Define on OS/2. * gettext-tools/gnulib-lib/Makefile.am (libgettextlib_la_LDFLAGS): Set a DLL name to gtlib on OS/2. * gettext-tools/libgettextpo/Makefile.am (libgettextpo_la_LDFLAGS): Set a DLL name to gtpo on OS/2. * gettext-tools/src/Makefile.am (libgettextsrc_la_LDFLAGS): Set a DLL name to gtsrc on OS/2. --- gettext-tools/configure.ac | 2 ++ gettext-tools/gnulib-lib/Makefile.am | 5 +++++ gettext-tools/libgettextpo/Makefile.am | 5 +++++ gettext-tools/src/Makefile.am | 5 +++++ 4 files changed, 17 insertions(+) diff --git a/gettext-tools/configure.ac b/gettext-tools/configure.ac index e2598eb..d9a2788 100644 --- a/gettext-tools/configure.ac +++ b/gettext-tools/configure.ac @@ -105,6 +105,8 @@ case "$host_os" in esac AM_CONDITIONAL([WOE32], [test $is_woe32 = yes]) +AM_CONDITIONAL([OS2], [test "${host_os#os2}" != "${host_os}"]) + dnl On Cygwin 1.7.10-1 or later, error_* variables are defined in the dnl Cygwin DLL. To avoid any conflict with gettext DLLs, always link dnl to gnulib's error.c. See GETTEXTLIB_EXPORTS_FLAGS setting below. diff --git a/gettext-tools/gnulib-lib/Makefile.am b/gettext-tools/gnulib-lib/Makefile.am index 9e43721..c930367 100644 --- a/gettext-tools/gnulib-lib/Makefile.am +++ b/gettext-tools/gnulib-lib/Makefile.am @@ -61,6 +61,11 @@ include Makefile.gnulib # Which classes to export from the shared library. MOOPPFLAGS += --dllexport=styled_ostream +# OS/2 does not support a DLL name longer than 8 characters. +if OS2 +libgettextlib_la_LDFLAGS += -os2dllname gtlib +endif + # Linking with C++ libraries is needed _only_ on mingw and Cygwin. if !WOE32DLL libgettextlib_la_LINK = $(LIBTOOL) $(AM_V_lt) --tag=CC \ diff --git a/gettext-tools/libgettextpo/Makefile.am b/gettext-tools/libgettextpo/Makefile.am index 5a4404d..7b26ac2 100644 --- a/gettext-tools/libgettextpo/Makefile.am +++ b/gettext-tools/libgettextpo/Makefile.am @@ -117,6 +117,11 @@ libgettextpo_la_SOURCES += ../woe32dll/gettextpo-exports.c libgettextpo_la_LDFLAGS += -Wl,--export-all-symbols endif +# OS/2 does not support a DLL name longer than 8 characters. +if OS2 +libgettextpo_la_LDFLAGS += -os2dllname gtpo +endif + # Version information according to Woe32 conventions. EXTRA_DIST += libgettextpo.rc if WOE32 diff --git a/gettext-tools/src/Makefile.am b/gettext-tools/src/Makefile.am index d88b8fd..0e05cd7 100644 --- a/gettext-tools/src/Makefile.am +++ b/gettext-tools/src/Makefile.am @@ -253,6 +253,11 @@ libgettextsrc_la_LDFLAGS = \ -release @VERSION@ \ ../gnulib-lib/libgettextlib.la $(LTLIBUNISTRING) @LTLIBINTL@ @LTLIBICONV@ @LTLIBEXPAT@ -lc -no-undefined +# OS/2 does not support a DLL name longer than 8 characters. +if OS2 +libgettextsrc_la_LDFLAGS += -os2dllname gtsrc +endif + libgettextsrc_la_CPPFLAGS = $(AM_CPPFLAGS) # Tell the mingw or Cygwin linker which symbols to export. -- 2.6.0 From MAILER-DAEMON Sun Nov 08 09:01:04 2015 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1ZvQWm-0000QP-Oc for mharc-bug-gettext@gnu.org; Sun, 08 Nov 2015 09:01:04 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39814) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZvIzP-000117-A5 for bug-gettext@gnu.org; Sun, 08 Nov 2015 00:58:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZvIzN-0002fK-R4 for bug-gettext@gnu.org; Sun, 08 Nov 2015 00:58:07 -0500 Received: from mail-pa0-x22c.google.com ([2607:f8b0:400e:c03::22c]:35184) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZvIzN-0002ew-LW for bug-gettext@gnu.org; Sun, 08 Nov 2015 00:58:05 -0500 Received: by pasz6 with SMTP id z6so168944345pas.2 for ; Sat, 07 Nov 2015 21:58:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:in-reply-to:references; bh=0IgLKVPNMcxV10K1EETKgibMdCN43CgheA05ML+6RO4=; b=XEmTc/I4DMwviCgIMckHYkT8XQSyE/MHEZPqR//r7QAmJuR6zukorgQTV6dNhf4a3k WVIslqbnwYRL/kltoM44TiocX9RCqhRsH5Tv2he3iBj98tVUpXHZEAXRpwM4LtZk6da9 uETMN+05S8iAOQ9PiF3CgInL2pBFPrNdt428yXWIJlOVcOcJFkzjBCFYxjGPbD65130J AmZgP4jVFXex09UDW4PtVEls5lJ6nzgLxsHiQfBMm3heBvmwrXCtv7MVis+YxTwnjuzW QqLxGkoZyKklVZbKLDb+3zt1wGtgKe+xJvmsIn/ESlsOgYk4auoThiUwOrgsD9hqSXJ/ ExVQ== X-Received: by 10.66.216.167 with SMTP id or7mr436332pac.17.1446962285198; Sat, 07 Nov 2015 21:58:05 -0800 (PST) Received: from localhost.localdomain ([211.108.117.26]) by smtp.gmail.com with ESMTPSA id sz9sm8992671pab.13.2015.11.07.21.58.04 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 07 Nov 2015 21:58:04 -0800 (PST) From: KO Myung-Hun X-Google-Original-From: KO Myung-Hun To: bug-gettext@gnu.org Date: Sun, 8 Nov 2015 14:58:04 +0900 Message-Id: <1446962284-8820-9-git-send-email-komh@chollian.net> X-Mailer: git-send-email 2.6.0 In-Reply-To: <1446962284-8820-1-git-send-email-komh@chollian.net> References: <1446962284-8820-1-git-send-email-komh@chollian.net> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400e:c03::22c X-Mailman-Approved-At: Sun, 08 Nov 2015 09:00:59 -0500 Subject: [bug-gettext] [PATCH 8/8] xgettext, cldr-plurals: Fix linkage on OS/2 X-BeenThere: bug-gettext@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for GNU gettext List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Nov 2015 05:58:08 -0000 xgettext.exe and cldr-plurals.exe require libexpat for linkage on OS/2. * gettext-tools/src/Makefile.am (xgettext_LDADD, cldr_plurals_LDADD): Add @LTLIBEXPAT@ on OS/2. --- gettext-tools/src/Makefile.am | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/gettext-tools/src/Makefile.am b/gettext-tools/src/Makefile.am index 0e05cd7..cfe7123 100644 --- a/gettext-tools/src/Makefile.am +++ b/gettext-tools/src/Makefile.am @@ -240,6 +240,9 @@ hostname_SOURCES = hostname.c urlget_SOURCES = urlget.c cldr_plurals_SOURCES = cldr-plural.y cldr-plural-exp.c cldr-plurals.c cldr_plurals_LDADD = libgettextsrc.la $(LDADD) +if OS2 +cldr_plurals_LDADD += @LTLIBEXPAT@ +endif # How to build libgettextsrc.la. # Need ../gnulib-lib/libgettextlib.la. @@ -288,6 +291,9 @@ msgfmt_LDADD = libgettextsrc.la @INTL_MACOSX_LIBS@ $(WOE32_LDADD) msgmerge_LDADD = libgettextsrc.la @INTL_MACOSX_LIBS@ @MSGMERGE_LIBM@ $(WOE32_LDADD) $(OPENMP_CFLAGS) msgunfmt_LDADD = libgettextsrc.la @INTL_MACOSX_LIBS@ $(WOE32_LDADD) xgettext_LDADD = libgettextsrc.la @INTL_MACOSX_LIBS@ @LTLIBICONV@ $(WOE32_LDADD) +if OS2 +xgettext_LDADD += @LTLIBEXPAT@ +endif msgattrib_LDADD = libgettextsrc.la @INTL_MACOSX_LIBS@ $(WOE32_LDADD) msgcat_LDADD = libgettextsrc.la @INTL_MACOSX_LIBS@ $(WOE32_LDADD) msgcomm_LDADD = libgettextsrc.la @INTL_MACOSX_LIBS@ $(WOE32_LDADD) -- 2.6.0 From MAILER-DAEMON Sun Nov 08 09:01:02 2015 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1ZvQWk-0000KJ-1s for mharc-bug-gettext@gnu.org; Sun, 08 Nov 2015 09:01:02 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39684) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZvIzI-0000zt-TG for bug-gettext@gnu.org; Sun, 08 Nov 2015 00:58:01 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZvIzH-0002ci-RW for bug-gettext@gnu.org; Sun, 08 Nov 2015 00:58:00 -0500 Received: from mail-pa0-x232.google.com ([2607:f8b0:400e:c03::232]:35172) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZvIzH-0002ca-MZ for bug-gettext@gnu.org; Sun, 08 Nov 2015 00:57:59 -0500 Received: by pasz6 with SMTP id z6so168942863pas.2 for ; Sat, 07 Nov 2015 21:57:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:in-reply-to:references; bh=PxfPaoPJhAcmDYS5G6/xtybAErevnkd1NsOf24hDo5k=; b=JTHUV4lxRJbTEjgCAFVXW2hkNj7gYBa0jl9xq0NBeLx7OtwKa9EIYLAnN5aKomGdST +suH8CfTsZFAKZbX/jrBbD9XAnfjmc/ZuG0VER8L4yO4mGW63g3E0oS0R1Hacq9GU7Gm EmNidNLbeMr6ng4jaTkDH3LAEpBgigl2n4yAYNeSfg6hBz3SGcbPRErg4lHtS74AC9+j KGiqMq5bzZfyknj2aiG+9dj3NdbUY48y3JYrny7t0VQv2RZPCCBAoWgL9Ptk5GTttZ0S j+s3b1gCwBRJmySGeLl0vnEPjnmCSUjsycKrhUjb24+TI/U9V2WGhzQpo6E9a4erbLqD uEOw== X-Received: by 10.66.163.131 with SMTP id yi3mr41885pab.44.1446962278713; Sat, 07 Nov 2015 21:57:58 -0800 (PST) Received: from localhost.localdomain ([211.108.117.26]) by smtp.gmail.com with ESMTPSA id sz9sm8992671pab.13.2015.11.07.21.57.57 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 07 Nov 2015 21:57:58 -0800 (PST) From: KO Myung-Hun X-Google-Original-From: KO Myung-Hun To: bug-gettext@gnu.org Date: Sun, 8 Nov 2015 14:57:59 +0900 Message-Id: <1446962284-8820-4-git-send-email-komh@chollian.net> X-Mailer: git-send-email 2.6.0 In-Reply-To: <1446962284-8820-1-git-send-email-komh@chollian.net> References: <1446962284-8820-1-git-send-email-komh@chollian.net> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400e:c03::232 X-Mailman-Approved-At: Sun, 08 Nov 2015 09:00:59 -0500 Subject: [bug-gettext] [PATCH 3/8] build: Do not include os2compat.[ch] X-BeenThere: bug-gettext@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for GNU gettext List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Nov 2015 05:58:01 -0000 kLIBC does not need os2compat.[ch] * gettext-runtime/configure.ac (AH_BOTTOM): Do not include intl/os2compat.h on kLIBC. * gettext-runtime/intl/osdep.c: Do not include os2compat.c on kLIBC. * gettext-tools/configure.ac (AH_BOTTOM): Do not include intl/os2compat.h on kLIBC. --- gettext-runtime/configure.ac | 2 +- gettext-runtime/intl/osdep.c | 2 +- gettext-tools/configure.ac | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/gettext-runtime/configure.ac b/gettext-runtime/configure.ac index e9299b6..77e954b 100644 --- a/gettext-runtime/configure.ac +++ b/gettext-runtime/configure.ac @@ -102,7 +102,7 @@ AH_BOTTOM([ #endif /* Extra OS/2 (emx+gcc) defines. */ -#ifdef __EMX__ +#if defined __EMX__ && !defined __KLIBC__ # include "intl/os2compat.h" #endif ]) diff --git a/gettext-runtime/intl/osdep.c b/gettext-runtime/intl/osdep.c index 25f8dfa..eda9d28 100644 --- a/gettext-runtime/intl/osdep.c +++ b/gettext-runtime/intl/osdep.c @@ -16,7 +16,7 @@ #if defined __CYGWIN__ || defined __MINGW32__ # include "intl-exports.c" -#elif defined __EMX__ +#elif defined __EMX__ && !defined __KLIBC__ # include "os2compat.c" #else /* Avoid AIX compiler warning. */ diff --git a/gettext-tools/configure.ac b/gettext-tools/configure.ac index 920eeb6..e2598eb 100644 --- a/gettext-tools/configure.ac +++ b/gettext-tools/configure.ac @@ -286,7 +286,7 @@ AH_BOTTOM([ #endif /* Extra OS/2 (emx+gcc) defines. */ -#ifdef __EMX__ +#if defined __EMX__ && !defined __KLIBC__ # include "intl/os2compat.h" #endif ]) -- 2.6.0 From MAILER-DAEMON Sun Nov 08 09:01:04 2015 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1ZvQWm-0000Pm-DT for mharc-bug-gettext@gnu.org; Sun, 08 Nov 2015 09:01:04 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39712) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZvIzK-00010P-Ri for bug-gettext@gnu.org; Sun, 08 Nov 2015 00:58:03 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZvIzJ-0002dP-Tt for bug-gettext@gnu.org; Sun, 08 Nov 2015 00:58:02 -0500 Received: from mail-pa0-x230.google.com ([2607:f8b0:400e:c03::230]:35176) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZvIzJ-0002d8-OV for bug-gettext@gnu.org; Sun, 08 Nov 2015 00:58:01 -0500 Received: by pasz6 with SMTP id z6so168943427pas.2 for ; Sat, 07 Nov 2015 21:58:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:in-reply-to:references; bh=PAX6P4gxrZCW48Xt3IBP4fm/K5LpPCnzNHcivwzsfIk=; b=ICY0TfuHh35uvP1J8bwHu/lTGouEZvJdGxzh16U2U+pDbn4RVJKL9spBKs9ngb4esA TU4/f/DKe5+33qaPLohK6V31rNagV52iRHxhmGrQPCTNR/8Gi+qp96UcF49E9DnYmeDb 7NEDji0l9cyQ0cplz1I0YyFaMMiCFrddaWoEQXNuCwKN0Zwe0YF8jVUHK+NmbgYxsJsu Z+6yotUPMSr4SX35MK8uiv88585oswBFAaey3851RbfqRiODRHDZoAJk4Mj96ABTFroI VPV36wYSOYxUDpBob7s/UIvnJQIsG/1nJ8RS8lq8FH8P9LNF3KZnNanGt4IOsw5umwE4 Q7Hg== X-Received: by 10.66.228.3 with SMTP id se3mr29688884pac.75.1446962281303; Sat, 07 Nov 2015 21:58:01 -0800 (PST) Received: from localhost.localdomain ([211.108.117.26]) by smtp.gmail.com with ESMTPSA id sz9sm8992671pab.13.2015.11.07.21.58.00 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 07 Nov 2015 21:58:00 -0800 (PST) From: KO Myung-Hun X-Google-Original-From: KO Myung-Hun To: bug-gettext@gnu.org Date: Sun, 8 Nov 2015 14:58:01 +0900 Message-Id: <1446962284-8820-6-git-send-email-komh@chollian.net> X-Mailer: git-send-email 2.6.0 In-Reply-To: <1446962284-8820-1-git-send-email-komh@chollian.net> References: <1446962284-8820-1-git-send-email-komh@chollian.net> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400e:c03::230 X-Mailman-Approved-At: Sun, 08 Nov 2015 09:00:59 -0500 Subject: [bug-gettext] [PATCH 5/8] intl: Support UNIXROOT in BINDTEXTDOMAIN () on EMX X-BeenThere: bug-gettext@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for GNU gettext List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Nov 2015 05:58:03 -0000 $UNIXROOT is a drive on which a root of FHS is. * gettext-runtime/intl/bindtextdom.c (BINDTEXTDOMAIN): Prepend $UNIXROOT to dirname if it is started '/' or it is an empty string. --- gettext-runtime/intl/bindtextdom.c | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/gettext-runtime/intl/bindtextdom.c b/gettext-runtime/intl/bindtextdom.c index 887393c..0d530be 100644 --- a/gettext-runtime/intl/bindtextdom.c +++ b/gettext-runtime/intl/bindtextdom.c @@ -317,7 +317,32 @@ set_binding_values (const char *domainname, char * BINDTEXTDOMAIN (const char *domainname, const char *dirname) { +#ifdef __EMX__ + const char *saved_dirname = dirname; + char dirname_with_drive[_MAX_PATH]; + + if (dirname && (dirname[0] == '/' || dirname[0] == '\\' )) + { + const char *unixroot = getenv ("UNIXROOT"); + size_t len = strlen (dirname) + 1; + + if (unixroot + && unixroot[0] != '\0' + && unixroot[1] == ':' + && unixroot[2] == '\0' + && 2 + len <= _MAX_PATH) + { + memcpy (dirname_with_drive, unixroot, 2); + memcpy (dirname_with_drive + 2, dirname, len); + + dirname = dirname_with_drive; + } + } +#endif set_binding_values (domainname, &dirname, NULL); +#ifdef __EMX__ + dirname = saved_dirname; +#endif return (char *) dirname; } -- 2.6.0 From MAILER-DAEMON Thu Nov 12 09:20:32 2015 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1Zwsjo-0008SY-GR for mharc-bug-gettext@gnu.org; Thu, 12 Nov 2015 09:20:32 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35428) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZwnDR-0003Bp-FP for bug-gettext@gnu.org; Thu, 12 Nov 2015 03:26:46 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZwnDQ-0000Uq-G3 for bug-gettext@gnu.org; Thu, 12 Nov 2015 03:26:45 -0500 Received: from mail-wm0-x229.google.com ([2a00:1450:400c:c09::229]:38058) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZwnDQ-0000Ua-9C for bug-gettext@gnu.org; Thu, 12 Nov 2015 03:26:44 -0500 Received: by wmec201 with SMTP id c201so80066904wme.1 for ; Thu, 12 Nov 2015 00:26:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wiggy_net.20150623.gappssmtp.com; s=20150623; h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=+fjjlbb86aggXIb+vLUvjZYmCEIwiy03300aIkprCt8=; b=La/Kdjwc6oHfwgZAr4gAEkq3zb1yfAbFXbp0u35CvqiUtWtojwY6Y+mjz4Gxf5Ysgj KNzbaNtuUB2TJKN85+hQHSSEkDz8/s+4315emokomYtvRKNuFp57YV+zcV4dqsuyop9Q aUrfWjJ7fMh6xPVje7dc464bIejPBdGGL0nT+ROCIdsneoL000tUdWYlPI27W1W60aB/ I/rrJs0lswzIKusfc19H9IWSgjNwX6wuDvM+nhla8Di6ergCH/vnYUAMVDmrWG+RIgyf dP6u0x44wvbNsgn/QVeUyIUA1f61yWNrLOEJMuf9mOLsHpBu4x6Ufbh7DWM1iK7FmLEL zoaQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:content-transfer-encoding :subject:message-id:date:to:mime-version; bh=+fjjlbb86aggXIb+vLUvjZYmCEIwiy03300aIkprCt8=; b=QOs70mkF5N5mbAFnzPNRXRU0oGUD9xAfK4zs82onQVHQ/I4zkL6mpkwblU+STvoBXE 7/uFVc7AC42m+00nJSANKa7UGBCdfwIRu4ylYGAquS6Q2FqdK6QKTVz7FzjXQ2SYk30l 9GSKAaaDsSa/CgyZuoi9jydr/2U494QQhraGntPu0mpU9QddhUJ+T6yU5GXUjg54DzVe fKHxQ6ibTdWgypmm2gL6HutHJHdHT2saXvHBPKrFjH3Sq76KHKETDUaO30KJYpczFfsK J+sP4iGQxLzc9O3WuYaTd/ViBXzPMfYGB8pRCVj3Etl7d5ioqPY5t+vyXlxP3MjDwbIt pJnA== X-Gm-Message-State: ALoCoQniTikrQb5XvczyWMHLx4hIC+3Kk8APjEwGsmX+/fbv/fRU+tFB/qD7nwzZ3ZIr9PEZVm4s X-Received: by 10.194.114.70 with SMTP id je6mr14530159wjb.7.1447316803360; Thu, 12 Nov 2015 00:26:43 -0800 (PST) Received: from ?IPv6:2001:980:58a6:1:65b4:6f98:26c:54ee? ([2001:980:58a6:1:65b4:6f98:26c:54ee]) by smtp.gmail.com with ESMTPSA id m64sm10254364wmf.14.2015.11.12.00.26.42 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 12 Nov 2015 00:26:42 -0800 (PST) From: Wichert Akkerman Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-Id: <98A04C11-94A2-4590-9F9A-02C11D5ED35A@wiggy.net> Date: Thu, 12 Nov 2015 09:26:41 +0100 To: bug-gettext@gnu.org Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\)) X-Mailer: Apple Mail (2.3096.5) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c09::229 X-Mailman-Approved-At: Thu, 12 Nov 2015 09:20:31 -0500 Subject: [bug-gettext] Allow custom flags in msgmerge X-BeenThere: bug-gettext@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for GNU gettext List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Nov 2015 08:26:46 -0000 Hi, for a few projects I find myself needing an ability to add custom flags = to messages to help manage our translation toolchain. For example: * Some of our messages are in markdown format. I want to be able to add = a flag to them so our tooling can verify a translation is still valid = markdown. * We run a number of automated checks on messages to check for things = like=20 consistent use of punctuation. For some messages this is not necessary = and often leads to false positives, so I would like to be able to use a = flag to indicate which checks can be skipped for a message We use lingua (see https://github.com/wichert/lingua/ ) to create the = pot file, which allows adding such flags in translation comments, = somewhat similar to how xgettext allows format hints in comments. I = would like to keep using msgmerge to sync our pot and po files; I=E2=80=99= ve seen other re-implementations of msgmerge do bad things, and I would = rather have not to reinvent that wheel. Unfortunately currently = msgmerge will skip all flags it does not know about. I do understand the = rationale for wanting to keep an official list of flags and filtering = out unofficial ones, but for situations like ours it would be very = useful if there was a way to tell msgmerge to copy our flags over to our = po files. That can be either a command-line option = (=E2=80=94keep-unofficial-flags), or require unofficial flags to be = prefixed with x- . I=E2=80=99m happy to help implementing such a = feature, but before doing so I would like to know if there is interest = in such a feature. Regards, Wichert. From MAILER-DAEMON Fri Nov 13 09:15:30 2015 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1ZxF8U-00038Q-3c for mharc-bug-gettext@gnu.org; Fri, 13 Nov 2015 09:15:30 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54872) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zx3pS-00017c-K0 for bug-gettext@gnu.org; Thu, 12 Nov 2015 21:11:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zx3pR-0001YL-Mk for bug-gettext@gnu.org; Thu, 12 Nov 2015 21:11:06 -0500 Received: from mail-oi0-x22d.google.com ([2607:f8b0:4003:c06::22d]:33633) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zx3pR-0001YE-IU for bug-gettext@gnu.org; Thu, 12 Nov 2015 21:11:05 -0500 Received: by oixx65 with SMTP id x65so31024362oix.0 for ; Thu, 12 Nov 2015 18:11:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=EsGVo7Eowe+yX9u4J9u+x6a/I2kO7WVzwea1GOU+5os=; b=CQojEiD9pHi8Thk7MTMKeUdLaor91eoBuX4lxcV/vzIgk36dc/m8n/1EM66c58K+4g 2YME0DVEzrDY9sILUTHszYjM5p8f1bTAE2qJjHQ9Fj6c27Z9SUJ8wexxKhJ+LtTW/PDt hCz5++oonyu/UkqBHsQU28MUtNt/KaShkdYF/W+VednDFQg9aiEcxzyBwdUULKqxDi1+ Prr8KnI2LVYFZEfIU8CIoGnmHOqOVhs4xroROOBHgOfRHhJ7MUh2oG4PDweMBn22Xc33 KBa+Ehih3FMqtXL3jdXx95sImq45sRoco4MWr5+TyiAZVJ3jkZ18/GQt8ySqzT0Dq0r2 ytlQ== X-Received: by 10.202.214.131 with SMTP id n125mr10488295oig.104.1447380665059; Thu, 12 Nov 2015 18:11:05 -0800 (PST) MIME-Version: 1.0 Received: by 10.182.78.138 with HTTP; Thu, 12 Nov 2015 18:10:25 -0800 (PST) From: Kylie McClain Date: Thu, 12 Nov 2015 21:10:25 -0500 Message-ID: To: bug-gettext@gnu.org Content-Type: text/plain; charset=UTF-8 X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:4003:c06::22d X-Mailman-Approved-At: Fri, 13 Nov 2015 09:15:28 -0500 Subject: [bug-gettext] gettext.m4 and musl-libc X-BeenThere: bug-gettext@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for GNU gettext List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Nov 2015 02:11:07 -0000 Hi, I am trying to use the gettext built into musl-libc for programs which use autoconf+automake for building. I know the program in question (hunspell) supports musl's gettext, but the issue is that whenever I run ./configure, it insists on using the included gettext, rather than musl's built in gettext. After talking to people on musl's IRC, it was determined that the issue is that gettext.m4 has a bad check for if the libc has a gettext implementation; namely, it only uses the libc's implementation if the libc is glibc. Could this be improved so that it works with musl's gettext? Thanks. From MAILER-DAEMON Fri Nov 13 11:11:25 2015 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1ZxGwf-0000UP-L7 for mharc-bug-gettext@gnu.org; Fri, 13 Nov 2015 11:11:25 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38108) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZxGwa-0000Tt-Fk for bug-gettext@gnu.org; Fri, 13 Nov 2015 11:11:23 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZxGwZ-0004tR-Eg for bug-gettext@gnu.org; Fri, 13 Nov 2015 11:11:20 -0500 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:57378) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZxGwZ-0004tM-BY; Fri, 13 Nov 2015 11:11:19 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43017) by fencepost.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1ZxGwX-0006lw-TU for bug-gnu-gettext@gnu.org; Fri, 13 Nov 2015 11:11:18 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZxGwW-0004s6-W7 for bug-gnu-gettext@gnu.org; Fri, 13 Nov 2015 11:11:17 -0500 Received: from [2001:4830:134:6::a] (port=34094 helo=frontend.savannah.gnu.org) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZxGwR-0004q0-FQ; Fri, 13 Nov 2015 11:11:11 -0500 Received: from www-data by frontend.savannah.gnu.org with local (Exim 4.72) (envelope-from ) id 1ZxGwQ-0002fN-OK; Fri, 13 Nov 2015 16:11:10 +0000 Date: Fri, 13 Nov 2015 16:11:10 +0000 To: bruno@clisp.org, ueno@gnu.org, bug-gnu-gettext@gnu.org X-PHP-Originating-Script: 0:sendmail.php From: anonymous X-Savane-Server: savannah.gnu.org:443 [208.118.235.70] MIME-Version: 1.0 Content-Type: text/plain;charset=UTF-8 X-Savane-Project: gettext X-Savane-Tracker: bugs X-Savane-Item-ID: 46436 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:42.0) Gecko/20100101 Firefox/42.0 X-Apparently-From: 152.26.228.30 Message-Id: <20151113-161109.sv0.59150@savannah.gnu.org> References: In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2001:4830:134:3::e Subject: [bug-gettext] [bug #46436] gettext.m4 does not detect musl-libc's gettext implementation X-BeenThere: bug-gettext@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for GNU gettext List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Nov 2015 16:11:23 -0000 URL: Summary: gettext.m4 does not detect musl-libc's gettext implementation Project: GNU gettext Submitted by: None Submitted on: Fri 13 Nov 2015 04:11:09 PM UTC Category: None Severity: 3 - Normal Item Group: None Status: None Privacy: Public Assigned to: None Open/Closed: Open Discussion Lock: Any _______________________________________________________ Details: musl's built in gettext implementation provides enough functionality to satisfy gt_cv_func_gnugettext{1,2}_libc, but the checks fail because it's not glibc. The checks require being overridden in order to compile without the included gettext, and should be improved to work on musl. _______________________________________________________ Reply to this item at: _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/ From MAILER-DAEMON Fri Nov 13 12:35:28 2015 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1ZxIFz-0002H5-TN for mharc-bug-gettext@gnu.org; Fri, 13 Nov 2015 12:35:27 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60621) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZxIFw-0002Es-Kt for bug-gettext@gnu.org; Fri, 13 Nov 2015 12:35:25 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZxIFv-00043p-PC for bug-gettext@gnu.org; Fri, 13 Nov 2015 12:35:24 -0500 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:58794) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZxIFv-00043j-MQ; Fri, 13 Nov 2015 12:35:23 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:37298) by fencepost.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1ZxIFv-0001T8-8d for bug-gnu-gettext@gnu.org; Fri, 13 Nov 2015 12:35:23 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZxIFu-000435-9H for bug-gnu-gettext@gnu.org; Fri, 13 Nov 2015 12:35:23 -0500 Received: from [2001:4830:134:6::a] (port=43814 helo=frontend.savannah.gnu.org) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZxIFq-00042a-HJ; Fri, 13 Nov 2015 12:35:18 -0500 Received: from www-data by frontend.savannah.gnu.org with local (Exim 4.72) (envelope-from ) id 1ZxIFn-0004Sj-Uw; Fri, 13 Nov 2015 17:35:16 +0000 Date: Fri, 13 Nov 2015 17:35:15 +0000 To: Kylie McClain , bruno@clisp.org, ueno@gnu.org, bug-gnu-gettext@gnu.org X-PHP-Originating-Script: 0:sendmail.php From: Kylie McClain X-Savane-Server: savannah.gnu.org:443 [208.118.235.70] MIME-Version: 1.0 Content-Type: text/plain;charset=UTF-8 X-Savane-Project: gettext X-Savane-Tracker: bugs X-Savane-Item-ID: 46436 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:42.0) Gecko/20100101 Firefox/42.0 X-Apparently-From: 152.26.228.30 (Savane authenticated user somasis) Message-Id: <20151113-173515.sv101753.45835@savannah.gnu.org> References: <20151113-161109.sv0.59150@savannah.gnu.org> In-Reply-To: <20151113-161109.sv0.59150@savannah.gnu.org> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2001:4830:134:3::e Subject: [bug-gettext] [bug #46436] gettext.m4 does not detect musl-libc's gettext implementation X-BeenThere: bug-gettext@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for GNU gettext List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Nov 2015 17:35:26 -0000 Follow-up Comment #1, bug #46436 (project gettext): Also, musl+gettext utilities satisfies gt_cv_func_gnugettext3_libc anyway. Additional references: - http://lists.gnu.org/archive/html/bug-gettext/2015-04/msg00002.html - https://bugs.debian.org/786885 _______________________________________________________ Reply to this item at: _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/ From MAILER-DAEMON Sat Nov 14 04:40:35 2015 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1ZxXJz-0001jD-BH for mharc-bug-gettext@gnu.org; Sat, 14 Nov 2015 04:40:35 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60081) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZxWZ0-0008RW-QJ for bug-gettext@gnu.org; Sat, 14 Nov 2015 03:52:03 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZxWYx-0006RF-I6 for bug-gettext@gnu.org; Sat, 14 Nov 2015 03:52:02 -0500 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:49013) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZxWYx-0006RB-EZ; Sat, 14 Nov 2015 03:51:59 -0500 Received: from du-a.org ([219.94.251.20]:49099 helo=debian) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1ZxWYw-0004QB-Bn; Sat, 14 Nov 2015 03:51:58 -0500 Message-ID: <87egft2cco.fsf-ueno-ueno@gnu.org> From: Daiki Ueno To: Kylie McClain In-Reply-To: (Kylie McClain's message of "Thu, 12 Nov 2015 21:10:25 -0500") References: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) Date: Sat, 14 Nov 2015 17:51:52 +0900 MIME-Version: 1.0 Content-Type: text/plain X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2001:4830:134:3::e Cc: bug-gettext@gnu.org Subject: Re: [bug-gettext] gettext.m4 and musl-libc X-BeenThere: bug-gettext@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for GNU gettext List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Nov 2015 08:52:04 -0000 Kylie McClain writes: > I am trying to use the gettext built into musl-libc for programs > which use autoconf+automake for building. I know the program in > question (hunspell) supports musl's gettext, but the issue is that > whenever I run ./configure, it insists on using the included gettext, > rather than musl's built in gettext. > > After talking to people on musl's IRC, it was determined that the > issue is that gettext.m4 has a bad check for if the libc has a > gettext implementation; namely, it only uses the libc's implementation > if the libc is glibc. > > Could this be improved so that it works with musl's gettext? Assuming that the problem you mean as a "bad check" is: http://lists.gnu.org/archive/html/bug-gettext/2015-04/msg00002.html According to the post linked from the above, the check seems to be there to exclude incompatible implementations of gettext(), like Solaris 7 and NetBSD: https://lists.gnu.org/archive/html/bug-gnu-utils/2006-03/msg00011.html If musl's gettext implementation is compatible with GNU gettext, I guess we could adjust the check to accept it. However, I have no idea which symbols or macros can be used for the check. It would be helpful if musl people could chime in and give us a hint. Regards, -- Daiki Ueno From MAILER-DAEMON Mon Nov 16 19:47:33 2015 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1ZyUQn-00066T-9s for mharc-bug-gettext@gnu.org; Mon, 16 Nov 2015 19:47:33 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54324) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZyNP6-0001Mm-1i for bug-gettext@gnu.org; Mon, 16 Nov 2015 12:17:20 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZyNP1-0006Gw-2V for bug-gettext@gnu.org; Mon, 16 Nov 2015 12:17:19 -0500 Received: from csn1.chautara.co.uk ([64.22.81.43]:58311) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZyNP0-0006Gp-Rk for bug-gettext@gnu.org; Mon, 16 Nov 2015 12:17:14 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=inf.org; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Date: Message-ID:Subject:From:To; bh=venzlu9q7bdQLSrKbeDErmOs8Bfo4HkDsaqkC51U9PE=; b=JfVl0MqSe3KurJQvZ4xkurIsaoQIp3l8tNwbpYJ0IeDt2nz3QwKSlN15S+ulw4WigYGQzF9gkn HRP+WOYVLQegh9vxUjr84LSnohkhhxeu3SIRui06ySYwyDaOxCVGxfO1iPkH1GsO6FFij0kwBJS+e LNOL/mwcAbL0vKwLOc5cfCxtQZ+azo3KxwU30d9wKRXE0YgUL99DKsAwlBRwYv4bINmNiPo8caFG+ wVN3YleOkvRTl0QHiDpWKVvEtVFcMsTkcxXKTHimFTUYBSfNBqe5wt0h4RI+SvCgwOwFGjHEJWakA /C41DAGT2M/tYI/ps6aN9nXt4KkkZ2ieoenRg==; Received: from [124.41.218.111] (port=4190 helo=[10.49.65.2]) by csn1.chautara.co.uk with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.86) (envelope-from ) id 1ZyNOw-000CIu-Nj for bug-gettext@gnu.org; Mon, 16 Nov 2015 12:17:12 -0500 To: bug-gettext@gnu.org From: Phil Davis Message-ID: <564A0F94.6040706@inf.org> Date: Mon, 16 Nov 2015 23:02:08 +0545 User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-OutGoing-Spam-Status: No, score=-1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - csn1.chautara.co.uk X-AntiAbuse: Original Domain - gnu.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - inf.org X-Get-Message-Sender-Via: csn1.chautara.co.uk: authenticated_id: phil.davis@inf.org X-Authenticated-Sender: csn1.chautara.co.uk: phil.davis@inf.org X-Source: X-Source-Args: X-Source-Dir: X-From-Rewrite: unmodified, already matched X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 64.22.81.43 X-Mailman-Approved-At: Mon, 16 Nov 2015 19:47:29 -0500 Subject: [bug-gettext] gettext doc minor errors and typos X-BeenThere: bug-gettext@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for GNU gettext List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Nov 2015 17:17:21 -0000 I have just been reading the gettext documentation at http://www.gnu.org/software/gettext/manual/gettext.html and am noticing little errors/typos as I go. For example this fragment of a code example is missing a ")": static const char *messages[] = { gettext_noop ("some very meaningful message", gettext_noop ("and another one") }; Is there somewhere where I can get the "original source" of the documentation, make fixes, and provide the changed file back for review? Or how else can I provide doc update assistance? -- Phil Davis Phone: +977 9819573437 Email: phil.davis@inf.org Skype: phillip.davis.oz From MAILER-DAEMON Mon Nov 16 21:09:08 2015 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1ZyVhk-0006Q6-Iy for mharc-bug-gettext@gnu.org; Mon, 16 Nov 2015 21:09:08 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57596) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZyVhi-0006P3-EV for bug-gettext@gnu.org; Mon, 16 Nov 2015 21:09:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZyVhf-0002OJ-1u for bug-gettext@gnu.org; Mon, 16 Nov 2015 21:09:06 -0500 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:53492) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZyVhe-0002OF-V6; Mon, 16 Nov 2015 21:09:02 -0500 Received: from du-a.org ([219.94.251.20]:58642 helo=dhcp-217-92.nrt.redhat.com) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1ZyVhe-00021h-4U; Mon, 16 Nov 2015 21:09:02 -0500 Message-ID: From: Daiki Ueno To: Phil Davis References: <564A0F94.6040706@inf.org> Date: Tue, 17 Nov 2015 11:08:56 +0900 In-Reply-To: <564A0F94.6040706@inf.org> (Phil Davis's message of "Mon, 16 Nov 2015 23:02:08 +0545") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2001:4830:134:3::e Cc: bug-gettext@gnu.org Subject: Re: [bug-gettext] gettext doc minor errors and typos X-BeenThere: bug-gettext@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for GNU gettext List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Nov 2015 02:09:07 -0000 Phil Davis writes: > I have just been reading the gettext documentation at > http://www.gnu.org/software/gettext/manual/gettext.html and am > noticing little errors/typos as I go. > > For example this fragment of a code example is missing a ")": > > static const char *messages[] = { > gettext_noop ("some very meaningful message", > gettext_noop ("and another one") > }; Thanks for pointing that. I have installed the fix in your name: http://git.sv.gnu.org/cgit/gettext.git/commit/?id=87642183 > Is there somewhere where I can get the "original source" of the > documentation, make fixes, and provide the changed file back for > review? The source of the gettext manual resides in gettext-tools/doc/ in Texinfo format (*.texi). Further corrections would be greatly appreciated. Regards, -- Daiki Ueno From MAILER-DAEMON Tue Nov 17 03:06:08 2015 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1ZybHE-0001eA-LR for mharc-bug-gettext@gnu.org; Tue, 17 Nov 2015 03:06:08 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44013) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZybHC-0001cO-3a for bug-gettext@gnu.org; Tue, 17 Nov 2015 03:06:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZybH8-0003wR-Tp for bug-gettext@gnu.org; Tue, 17 Nov 2015 03:06:06 -0500 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:57780) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZybH8-0003wN-QV; Tue, 17 Nov 2015 03:06:02 -0500 Received: from du-a.org ([219.94.251.20]:58686 helo=dhcp-217-92.nrt.redhat.com) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1ZybH7-0002cT-Vd; Tue, 17 Nov 2015 03:06:02 -0500 Message-ID: From: Daiki Ueno To: KO Myung-Hun References: <1446962284-8820-1-git-send-email-komh@chollian.net> Date: Tue, 17 Nov 2015 17:05:56 +0900 In-Reply-To: <1446962284-8820-1-git-send-email-komh@chollian.net> (KO Myung-Hun's message of "Sun, 8 Nov 2015 14:57:56 +0900") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2001:4830:134:3::e Cc: bug-gettext@gnu.org Subject: Re: [bug-gettext] [PATCH] OS/2 patches X-BeenThere: bug-gettext@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for GNU gettext List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Nov 2015 08:06:06 -0000 KO Myung-Hun writes: Thanks for the patches. Some comments below. > [PATCH 1/8] moop: Replace CR as well as NL with a space I'm not sure who adds CR here. Can't we assume that all source files use NL line termination? Or some other tools add CR on OS/2? Also, I worry about the portability of '\r' as an argument of tr. > [PATCH 2/8] test-lock: Do not include sched.h on kLIBC > [PATCH 3/8] build: Do not include os2compat.[ch] > [PATCH 4/8] gettext-runtime: Fix name resolution failures on kLIBC Those seem to be OK. > [PATCH 5/8] intl: Support UNIXROOT in BINDTEXTDOMAIN () on EMX Doesn't this conflict with the UNIXROOT resolution in os2compat.c? Also, since it changes the calling convention of bindtextdomain(), which previously assumed that it is user's responsibility to resolve DIRNAME, doesn't it break existing programs? > [PATCH 6/8] libasprintf: Build a shared library on OS/2 > [PATCH 7/8] gettext-tools: Use a short name for DLLs on OS/2 Those look a bit ugly, but should be OK. > [PATCH 8/8] xgettext, cldr-plurals: Fix linkage on OS/2 After merging the ITS branch (wip/ueno/its2), I plan to replace the libexpat dependencies with libxml2 (for tools) and a hand written XML parser (for libgettextpo, maybe ported from GLib's gmarkup.c). So this shouldn't be necessary. Regards, -- Daiki Ueno From MAILER-DAEMON Tue Nov 17 09:00:58 2015 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1Zygoc-0007vt-Ow for mharc-bug-gettext@gnu.org; Tue, 17 Nov 2015 09:00:58 -0500 Received: from eggs.gnu.org ([208.118.235.92]:35569) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zyfmo-00031z-0U for bug-gettext@gnu.org; Tue, 17 Nov 2015 07:55:02 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zyfmm-0005vk-SP for bug-gettext@gnu.org; Tue, 17 Nov 2015 07:55:01 -0500 Received: from earth.ccil.org ([192.190.237.11]:34053) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zyfmj-0005uS-3g; Tue, 17 Nov 2015 07:54:57 -0500 Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from ) id 1ZyfmX-00044q-8h; Tue, 17 Nov 2015 07:54:49 -0500 Date: Tue, 17 Nov 2015 07:54:45 -0500 From: John Cowan To: Daiki Ueno Message-ID: <20151117125440.GA12024@mercury.ccil.org> References: <1446962284-8820-1-git-send-email-komh@chollian.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Sender: John Cowan X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 192.190.237.11 X-Mailman-Approved-At: Tue, 17 Nov 2015 09:00:57 -0500 Cc: bug-gettext@gnu.org, KO Myung-Hun Subject: Re: [bug-gettext] [PATCH] OS/2 patches X-BeenThere: bug-gettext@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for GNU gettext List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Nov 2015 12:55:03 -0000 Daiki Ueno scripsit: > I'm not sure who adds CR here. Can't we assume that all source files > use NL line termination? Or some other tools add CR on OS/2? Also, I > worry about the portability of '\r' as an argument of tr. Yes, it's definitely better to use '\015' for portability. -- John Cowan http://www.ccil.org/~cowan cowan@ccil.org SAXParserFactory [is] a hideous, evil monstrosity of a class that should be hung, shot, beheaded, drawn and quartered, burned at the stake, buried in unconsecrated ground, dug up, cremated, and the ashes tossed in the Tiber while the complete cast of Wicked sings "Ding dong, the witch is dead." --Elliotte Rusty Harold on xml-dev From MAILER-DAEMON Wed Nov 18 08:54:43 2015 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1Zz3C7-00087z-Tf for mharc-bug-gettext@gnu.org; Wed, 18 Nov 2015 08:54:43 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54274) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZyuH8-00052r-5l for bug-gettext@gnu.org; Tue, 17 Nov 2015 23:23:19 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZyuH3-0005tR-3B for bug-gettext@gnu.org; Tue, 17 Nov 2015 23:23:18 -0500 Received: from plane.gmane.org ([80.91.229.3]:41820) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZyuH2-0005tK-Sm for bug-gettext@gnu.org; Tue, 17 Nov 2015 23:23:13 -0500 Received: from public by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1ZyuGz-00013c-RR for bug-gettext@gnu.org; Wed, 18 Nov 2015 05:23:09 +0100 Received: from mail-pa0-f46.google.com ([209.85.220.46]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZyuGr-0000nI-4p; Wed, 18 Nov 2015 05:23:01 +0100 Received: by pabfh17 with SMTP id fh17so32232497pab.0; Tue, 17 Nov 2015 20:22:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:message-id:date:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=zFKjJFmIOp6YGqe2Wb8UMsOkydgKSnL0hMk3oXv49JU=; b=uiCy5Ve/Xdmi76Tha61Iy6tYZUEQ+Cw72yQq9ebxyFiwHxMqyOw8UROMIoH6dhQ/9j v9u9V1JtbmMFMk0ngdZ98OUivyw6Io39ordSdF6u0OEQehyCi+9LPemRi0zBVga/oYXm nhI8SrkZ36H8gntA/Yx6GMwiWqCgkIoup1/ft5Hxn5JCpNMtFiuPrV2vxgGD0asnrjzZ dx5N8Qse27OEG3yFWq+ZFZ5epCK/i4GFrWSRR0CEzWY8ObEd1M58e2PHK4lGHT39b/yg sz9CJcyjHPCAT62554cCPrzdTp37QYBfrkpH70jXdAbXXfStoc3sYDchP+FqoDgbiwOz iqRQ== X-Received: by 10.68.203.233 with SMTP id kt9mr44349478pbc.39.1447820579684; Tue, 17 Nov 2015 20:22:59 -0800 (PST) Received: from [10.0.2.15] ([58.29.79.85]) by smtp.gmail.com with ESMTPSA id at5sm812898pbc.32.2015.11.17.20.22.58 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 17 Nov 2015 20:22:59 -0800 (PST) From: KO Myung-Hun X-Google-Original-From: KO Myung-Hun Message-ID: <564BFD25.7030006@chollian.net> Date: Wed, 18 Nov 2015 13:23:01 +0900 User-Agent: Mozilla/5.0 (OS/2; Warp 4.5; rv:10.0.6esrpre) Gecko/20120715 Firefox/10.0.6esrpre SeaMonkey/2.7.2 MIME-Version: 1.0 To: Daiki Ueno References: <1446962284-8820-1-git-send-email-komh@chollian.net> In-Reply-To: X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset=EUC-KR Content-Transfer-Encoding: 7bit X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-Mailman-Approved-At: Wed, 18 Nov 2015 08:54:43 -0500 Cc: public-bug-gettext-mXXj517/zsQ@plane.gmane.org Subject: Re: [bug-gettext] [PATCH] OS/2 patches X-BeenThere: bug-gettext@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for GNU gettext List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Nov 2015 04:23:19 -0000 Hi/2. Daiki Ueno wrote: > KO Myung-Hun writes: > > Thanks for the patches. Some comments below. > >> [PATCH 1/8] moop: Replace CR as well as NL with a space > > I'm not sure who adds CR here. Can't we assume that all source files > use NL line termination? Or some other tools add CR on OS/2? Also, I > worry about the portability of '\r' as an argument of tr. > sed. On OS/2, many utils such as sed, coreutils and sh use CR+LF as a EOL marker instead of LF only. I replaced '\r' with '\015' in according to John Cowan >> [PATCH 2/8] test-lock: Do not include sched.h on kLIBC >> [PATCH 3/8] build: Do not include os2compat.[ch] >> [PATCH 4/8] gettext-runtime: Fix name resolution failures on kLIBC > > Those seem to be OK. > >> [PATCH 5/8] intl: Support UNIXROOT in BINDTEXTDOMAIN () on EMX > > Doesn't this conflict with the UNIXROOT resolution in os2compat.c? > I removed the dependencies on os2compat.[ch] from kLIBC code paths at With [PATCH 3/8]. So this will not conflict with os2compat.c Even if EMX is used, it will be no problem because this patch check the condition strictly. That is, once os2compat.c resolved UNIXROOT, this patch does not prepend UNIXROOT. > Also, since it changes the calling convention of bindtextdomain(), which > previously assumed that it is user's responsibility to resolve DIRNAME, > doesn't it break existing programs? No, it will not. Because this patch will prepend a drive to an absolute path starting with '/' or '\'. And all unix utils following FHS as well as gettext is installed on the drive. > >> [PATCH 6/8] libasprintf: Build a shared library on OS/2 >> [PATCH 7/8] gettext-tools: Use a short name for DLLs on OS/2 > > Those look a bit ugly, but should be OK. > >> [PATCH 8/8] xgettext, cldr-plurals: Fix linkage on OS/2 > > After merging the ITS branch (wip/ueno/its2), I plan to replace the > libexpat dependencies with libxml2 (for tools) and a hand written XML > parser (for libgettextpo, maybe ported from GLib's gmarkup.c). So this > shouldn't be necessary. Then, @LTLIBEXPAT@ is removed from libgettextsrc, too ? -- KO Myung-Hun Using Mozilla SeaMonkey 2.7.2 Under OS/2 Warp 4 for Korean with FixPak #15 In VirtualBox v4.1.32 on Intel Core i7-3615QM 2.30GHz with 8GB RAM Korean OS/2 User Community : http://www.ecomstation.co.kr From MAILER-DAEMON Wed Nov 18 08:54:44 2015 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1Zz3C8-00088A-0S for mharc-bug-gettext@gnu.org; Wed, 18 Nov 2015 08:54:44 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57489) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZyuXI-0007Fv-51 for bug-gettext@gnu.org; Tue, 17 Nov 2015 23:40:01 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZyuXE-0001Hk-U3 for bug-gettext@gnu.org; Tue, 17 Nov 2015 23:40:00 -0500 Received: from plane.gmane.org ([80.91.229.3]:42670) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZyuXE-0001Hg-Jq for bug-gettext@gnu.org; Tue, 17 Nov 2015 23:39:56 -0500 Received: from public by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1ZyuXD-0000Xi-CK for bug-gettext@gnu.org; Wed, 18 Nov 2015 05:39:55 +0100 Received: from mail-pa0-f53.google.com ([209.85.220.53]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZyuX4-0000JC-1c for public-bug-gettext-mXXj517/zsQ@plane.gmane.org; Wed, 18 Nov 2015 05:39:46 +0100 Received: by padhx2 with SMTP id hx2so31554098pad.1 for ; Tue, 17 Nov 2015 20:39:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:message-id:date:user-agent:mime-version:newsgroups:to:subject :references:in-reply-to:content-type; bh=40b8zrpzSNORVS/JyomrgZDTroQlozhXoSE1CPlK5uM=; b=X+g7dg9bQF9xIrGOh1F0SQ5+TS89QC2oy/KMuoY4kr38DzWnQz+L2iM5g6CSgLeRQV +ReC49mMsalRCnMnEfGTMtfxXL2Y5r18jBRjuLy35lKW+7YxFJJksmC+NJbsOKx3JdcU e82LHu28gv9kTvj6e78rhleXBhlwpX8zC6J+CxRopeUgyEacsEOSGG+xixKBKDJNyOTE 1ZC1i4XByeReyI3f1RP5ydK/QuzetYGJ1owUGJYwcLOz+ikXbeB80V7JhjTXnx1EI2R+ WY5JAG1NaDjG85X3lrblJ2zvlec8qdavcKz7+oZpiz2t7BH4mJ5phuit3Ggk8/QBpH6B rjNw== X-Received: by 10.66.161.35 with SMTP id xp3mr69368402pab.13.1447821584575; Tue, 17 Nov 2015 20:39:44 -0800 (PST) Received: from [10.0.2.15] ([58.29.79.85]) by smtp.gmail.com with ESMTPSA id bd10sm900260pbd.29.2015.11.17.20.39.43 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 17 Nov 2015 20:39:44 -0800 (PST) From: KO Myung-Hun X-Google-Original-From: KO Myung-Hun Message-ID: <564C0110.5020705@chollian.net> Date: Wed, 18 Nov 2015 13:39:44 +0900 User-Agent: Mozilla/5.0 (OS/2; Warp 4.5; rv:10.0.6esrpre) Gecko/20120715 Firefox/10.0.6esrpre SeaMonkey/2.7.2 MIME-Version: 1.0 Newsgroups: gmane.comp.gnu.gettext.bugs To: public-bug-gettext-mXXj517/zsQ@plane.gmane.org References: <1446962284-8820-1-git-send-email-komh@chollian.net> <1446962284-8820-2-git-send-email-komh@chollian.net> In-Reply-To: <1446962284-8820-2-git-send-email-komh@chollian.net> X-Enigmail-Version: 1.3.5 Content-Type: multipart/mixed; boundary="------------030700020101000204010409" X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-Mailman-Approved-At: Wed, 18 Nov 2015 08:54:43 -0500 Subject: Re: [bug-gettext] [PATCH 1/8] moop: Replace CR as well as NL with a space X-BeenThere: bug-gettext@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for GNU gettext List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Nov 2015 04:40:01 -0000 This is a multi-part message in MIME format. --------------030700020101000204010409 Content-Type: text/plain; charset=EUC-KR Content-Transfer-Encoding: 7bit KO Myung-Hun wrote: > * gnulib-local/bulid-aux/moopp (func_check_header_syntax): > Replace CR as well as NL with a space. > --- > gnulib-local/build-aux/moopp | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > mode change 100755 => 100644 gnulib-local/build-aux/moopp > > diff --git a/gnulib-local/build-aux/moopp b/gnulib-local/build-aux/moopp > old mode 100755 > new mode 100644 > index 96a50a6..0e2dbb1 > --- a/gnulib-local/build-aux/moopp > +++ b/gnulib-local/build-aux/moopp > @@ -306,12 +306,12 @@ func_check_header_syntax () > } > class_end_lineno=`expr $methods_lineno + $class_end_lineno` > sed_extract_methods="$class_end_lineno"',$d;1,'"$methods_lineno"'d' > - methods=`sed -e "$sed_remove_comments" < "$file" | sed -e "$sed_extract_methods" | tr '\n' ' ' | tr ';' '\n' | sed -e 's,[ ]*$,,'` > + methods=`sed -e "$sed_remove_comments" < "$file" | sed -e "$sed_extract_methods" | tr '\r\n' ' ' | tr ';' '\n' | sed -e 's,[ ]*$,,'` > sed_remove_valid_arg1_lines='/([ ]*'"$classname"'_t[ ]*[A-Za-z_0-9]*[ ]*[,)]/d' > sed_extract_method_name='s,^.*[^A-Za-z_0-9]\([A-Za-z_0-9][A-Za-z_0-9]*\)[ ]*(.*$,\1,' > methods_with_bad_arg1=`echo "$methods" | sed -e "$sed_remove_empty_lines" -e "$sed_remove_valid_arg1_lines" -e "$sed_extract_method_name"` > if test -n "$methods_with_bad_arg1"; then > - methods_with_bad_arg1=`{ echo "$methods_with_bad_arg1" | sed -e 's/$/, /' | tr -d '\n'; echo; } | sed -e 's/\(, \)*$//'` > + methods_with_bad_arg1=`{ echo "$methods_with_bad_arg1" | sed -e 's/$/, /' | tr -d '\r\n'; echo; } | sed -e 's/\(, \)*$//'` > func_fatal_error "$file: some methods don't have a first argument of type ${classname}_t: $methods_with_bad_arg1" > fi > } Replaced '\r' with '\015'. -- KO Myung-Hun Using Mozilla SeaMonkey 2.7.2 Under OS/2 Warp 4 for Korean with FixPak #15 In VirtualBox v4.1.32 on Intel Core i7-3615QM 2.30GHz with 8GB RAM Korean OS/2 User Community : http://www.ecomstation.co.kr --------------030700020101000204010409 Content-Type: application/x-patch; name="0001-moop-Replace-CR-as-well-as-LF-with-a-space.patch" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="0001-moop-Replace-CR-as-well-as-LF-with-a-space.patch" RnJvbSA3YTFkZjZjZjRmN2Y5MTYzMTY1YTFjN2QyMjhjMmU1MWUyYTRhNmNmIE1vbiBTZXAg MTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBLTyBNeXVuZy1IdW4gPGtvbWhAY2hvbGxpYW4ubmV0 PgpEYXRlOiBTYXQsIDQgTWF5IDIwMTMgMTU6NDk6MDEgKzA5MDAKU3ViamVjdDogW1BBVENI XSBtb29wOiBSZXBsYWNlIENSIGFzIHdlbGwgYXMgTEYgd2l0aCBhIHNwYWNlCgpPbiBPUy8y LCBFT0wgbWFya2VyIGlzIENSK0xGLgoKKiBnbnVsaWItbG9jYWwvYnVsaWQtYXV4L21vb3Bw IChmdW5jX2NoZWNrX2hlYWRlcl9zeW50YXgpOgpSZXBsYWNlIENSIGFzIHdlbGwgYXMgTEYg d2l0aCBhIHNwYWNlLgotLS0KIGdudWxpYi1sb2NhbC9idWlsZC1hdXgvbW9vcHAgfCA0ICsr LS0KIDEgZmlsZSBjaGFuZ2VkLCAyIGluc2VydGlvbnMoKyksIDIgZGVsZXRpb25zKC0pCiBt b2RlIGNoYW5nZSAxMDA3NTUgPT4gMTAwNjQ0IGdudWxpYi1sb2NhbC9idWlsZC1hdXgvbW9v cHAKCmRpZmYgLS1naXQgYS9nbnVsaWItbG9jYWwvYnVpbGQtYXV4L21vb3BwIGIvZ251bGli LWxvY2FsL2J1aWxkLWF1eC9tb29wcApvbGQgbW9kZSAxMDA3NTUKbmV3IG1vZGUgMTAwNjQ0 CmluZGV4IDk2YTUwYTYuLjMwOGI4NzcKLS0tIGEvZ251bGliLWxvY2FsL2J1aWxkLWF1eC9t b29wcAorKysgYi9nbnVsaWItbG9jYWwvYnVpbGQtYXV4L21vb3BwCkBAIC0zMDYsMTIgKzMw NiwxMiBAQCBmdW5jX2NoZWNrX2hlYWRlcl9zeW50YXggKCkKICAgfQogICBjbGFzc19lbmRf bGluZW5vPWBleHByICRtZXRob2RzX2xpbmVubyArICRjbGFzc19lbmRfbGluZW5vYAogICBz ZWRfZXh0cmFjdF9tZXRob2RzPSIkY2xhc3NfZW5kX2xpbmVubyInLCRkOzEsJyIkbWV0aG9k c19saW5lbm8iJ2QnCi0gIG1ldGhvZHM9YHNlZCAtZSAiJHNlZF9yZW1vdmVfY29tbWVudHMi IDwgIiRmaWxlIiB8IHNlZCAtZSAiJHNlZF9leHRyYWN0X21ldGhvZHMiIHwgdHIgJ1xuJyAn ICcgfCB0ciAnOycgJ1xuJyB8IHNlZCAtZSAncyxbIAldKiQsLCdgCisgIG1ldGhvZHM9YHNl ZCAtZSAiJHNlZF9yZW1vdmVfY29tbWVudHMiIDwgIiRmaWxlIiB8IHNlZCAtZSAiJHNlZF9l eHRyYWN0X21ldGhvZHMiIHwgdHIgJ1wwMTVcbicgJyAgJyB8IHRyICc7JyAnXG4nIHwgc2Vk IC1lICdzLFsgCV0qJCwsJ2AKICAgc2VkX3JlbW92ZV92YWxpZF9hcmcxX2xpbmVzPScvKFsg CV0qJyIkY2xhc3NuYW1lIidfdFsgCV0qW0EtWmEtel8wLTldKlsgCV0qWywpXS9kJwogICBz ZWRfZXh0cmFjdF9tZXRob2RfbmFtZT0ncyxeLipbXkEtWmEtel8wLTldXChbQS1aYS16XzAt OV1bQS1aYS16XzAtOV0qXClbIAldKiguKiQsXDEsJwogICBtZXRob2RzX3dpdGhfYmFkX2Fy ZzE9YGVjaG8gIiRtZXRob2RzIiB8IHNlZCAtZSAiJHNlZF9yZW1vdmVfZW1wdHlfbGluZXMi IC1lICIkc2VkX3JlbW92ZV92YWxpZF9hcmcxX2xpbmVzIiAtZSAiJHNlZF9leHRyYWN0X21l dGhvZF9uYW1lImAKICAgaWYgdGVzdCAtbiAiJG1ldGhvZHNfd2l0aF9iYWRfYXJnMSI7IHRo ZW4KLSAgICBtZXRob2RzX3dpdGhfYmFkX2FyZzE9YHsgZWNobyAiJG1ldGhvZHNfd2l0aF9i YWRfYXJnMSIgfCBzZWQgLWUgJ3MvJC8sIC8nIHwgdHIgLWQgJ1xuJzsgZWNobzsgfSB8IHNl ZCAtZSAncy9cKCwgXCkqJC8vJ2AKKyAgICBtZXRob2RzX3dpdGhfYmFkX2FyZzE9YHsgZWNo byAiJG1ldGhvZHNfd2l0aF9iYWRfYXJnMSIgfCBzZWQgLWUgJ3MvJC8sIC8nIHwgdHIgLWQg J1wwMTVcbic7IGVjaG87IH0gfCBzZWQgLWUgJ3MvXCgsIFwpKiQvLydgCiAgICAgZnVuY19m YXRhbF9lcnJvciAiJGZpbGU6IHNvbWUgbWV0aG9kcyBkb24ndCBoYXZlIGEgZmlyc3QgYXJn dW1lbnQgb2YgdHlwZSAke2NsYXNzbmFtZX1fdDogJG1ldGhvZHNfd2l0aF9iYWRfYXJnMSIK ICAgZmkKIH0KLS0gCjIuNi4wCgo= --------------030700020101000204010409-- From MAILER-DAEMON Fri Nov 27 05:51:23 2015 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1a2Gcd-0008IH-NP for mharc-bug-gettext@gnu.org; Fri, 27 Nov 2015 05:51:23 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53324) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a2GcV-0008I4-AW for bug-gettext@gnu.org; Fri, 27 Nov 2015 05:51:21 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a2GcO-00011M-IC for bug-gettext@gnu.org; Fri, 27 Nov 2015 05:51:15 -0500 Received: from csn1.chautara.co.uk ([64.22.81.43]:57585) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a2GcO-00011I-4K; Fri, 27 Nov 2015 05:51:08 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=inf.org; s=default; h=Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Cc: References:To:Subject; bh=ih8suI6nPhQGMGiLqBhyO8B/nCVY/lK9At/YIxoxh3w=; b=QH1 i2v2Q5tacSS9kgwBBFtEhG4pUXuIuWuEpIdIv9dSiI1itZ9klymGdlDVhBAG++WA/HHNLVOvQIJnt 0485TACI56ACDwCPLyGHZ6IvzN3aRiWxpqGt2V6wwRg3/QfMmZdUqlkJmvuJR9cVIGMnf4D5JqWEz mENfXo3Zf9VJ0gYeXfkl4jJJ2785ZfIbosDy3fMdiWfgEyPJtSi4BY8tQfOLffyHAE1mtsvDJhgpu N5Q20hpCP7+mH+Yyp1P+b7TkoLqHf5mx84ASeFeh2lzuVHOhsRCOU4mp2SrrYa7XMDAX0e+35hBue SXCmyLDDvzHRt3HB4q88IHOvXM+Ca0Q==; Received: from [124.41.220.139] (port=53496 helo=[10.49.65.2]) by csn1.chautara.co.uk with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.86) (envelope-from ) id 1a2Gc2-0005n5-Cc; Fri, 27 Nov 2015 05:51:05 -0500 To: Daiki Ueno References: <564A0F94.6040706@inf.org> From: Phil Davis Message-ID: <56583583.2080302@inf.org> Date: Fri, 27 Nov 2015 16:35:43 +0545 User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/mixed; boundary="------------070707040602000307020400" X-OutGoing-Spam-Status: No, score=-1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - csn1.chautara.co.uk X-AntiAbuse: Original Domain - gnu.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - inf.org X-Get-Message-Sender-Via: csn1.chautara.co.uk: authenticated_id: phil.davis@inf.org X-Authenticated-Sender: csn1.chautara.co.uk: phil.davis@inf.org X-Source: X-Source-Args: X-Source-Dir: X-From-Rewrite: unmodified, already matched X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 64.22.81.43 Cc: bug-gettext@gnu.org Subject: Re: [bug-gettext] gettext doc minor errors and typos X-BeenThere: bug-gettext@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for GNU gettext List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2015 10:51:22 -0000 This is a multi-part message in MIME format. --------------070707040602000307020400 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit I have attached a bunch of patches for various doc grammar and typos. I couldn't see how to submit anything directly to the gettext.git repo for review. The submission and review process is so easy for projects that have repos hosted on Github - just fork/clone, edit away then press the Pull Request button. Is there a similar way for mere mortals to submit change requests for review to the repos in git.sv.gnu.org ? Phil Davis Phone: +977 9819573437 Email: phil.davis@inf.org Skype: phillip.davis.oz On 11/17/2015 7:53 AM, Daiki Ueno wrote: > Phil Davis writes: > >> I have just been reading the gettext documentation at >> http://www.gnu.org/software/gettext/manual/gettext.html and am >> noticing little errors/typos as I go. >> >> For example this fragment of a code example is missing a ")": >> >> static const char *messages[] = { >> gettext_noop ("some very meaningful message", >> gettext_noop ("and another one") >> }; > Thanks for pointing that. I have installed the fix in your name: > http://git.sv.gnu.org/cgit/gettext.git/commit/?id=87642183 > >> Is there somewhere where I can get the "original source" of the >> documentation, make fixes, and provide the changed file back for >> review? > The source of the gettext manual resides in gettext-tools/doc/ in > Texinfo format (*.texi). Further corrections would be greatly > appreciated. > > Regards, --------------070707040602000307020400 Content-Type: text/plain; charset=UTF-8; name="0001-doc-review.patch" Content-Transfer-Encoding: 8bit Content-Disposition: attachment; filename="0001-doc-review.patch" >From 300433d308fc69e1d30725e7f6fe0b037ea48c23 Mon Sep 17 00:00:00 2001 From: Phil Davis Date: Fri, 27 Nov 2015 16:07:59 +0545 Subject: [PATCH] doc review --- INSTALL | 4 +- gettext-runtime/ABOUT-NLS | 2 +- gettext-runtime/INSTALL | 4 +- gettext-tools/INSTALL | 4 +- gettext-tools/doc/FAQ.html | 6 +- gettext-tools/doc/gettext.texi | 243 ++++++++++++++++++++------------------- gettext-tools/doc/msgattrib.texi | 2 +- gettext-tools/doc/msgcat.texi | 2 +- gettext-tools/doc/msgcomm.texi | 2 +- gettext-tools/doc/msgconv.texi | 2 +- gettext-tools/doc/msgen.texi | 2 +- gettext-tools/doc/msgfilter.texi | 2 +- gettext-tools/doc/msgfmt.texi | 2 +- gettext-tools/doc/msggrep.texi | 2 +- gettext-tools/doc/msginit.texi | 2 +- gettext-tools/doc/msgmerge.texi | 2 +- gettext-tools/doc/msgunfmt.texi | 2 +- gettext-tools/doc/msguniq.texi | 2 +- gettext-tools/doc/xgettext.texi | 2 +- 19 files changed, 145 insertions(+), 144 deletions(-) diff --git a/INSTALL b/INSTALL index 671b157..f2914df 100644 --- a/INSTALL +++ b/INSTALL @@ -38,7 +38,7 @@ The simplest way to compile this package is: ‘sh ./configure’ instead to prevent ‘csh’ from trying to execute ‘configure’ itself. - Running ‘configure’ takes awhile. While running, it prints some + Running ‘configure’ takes a while. While running, it prints some messages telling which features it is checking for. 2. Type ‘make’ to compile the package. @@ -77,7 +77,7 @@ directory where you want the object files and executables to go and run the ‘configure’ script. ‘configure’ automatically checks for the source code in the directory that ‘configure’ is in and in ‘..’. - If you have to use a ‘make’ that does not supports the ‘VPATH’ + If you have to use a ‘make’ that does not support the ‘VPATH’ variable, you have to compile the package for one architecture at a time in the source code directory. After you have installed the package for one architecture, use ‘make distclean’ before reconfiguring for another diff --git a/gettext-runtime/ABOUT-NLS b/gettext-runtime/ABOUT-NLS index dd9c5de..d12d06f 100644 --- a/gettext-runtime/ABOUT-NLS +++ b/gettext-runtime/ABOUT-NLS @@ -72,7 +72,7 @@ example, 'de_AT' is used for Austria, and 'pt_BR' for Brazil. The country code serves to distinguish the dialects. The locale naming convention of 'LL_CC', with 'LL' denoting the -language and 'CC' denoting the country, is the one use on systems based +language and 'CC' denoting the country, is the one used on systems based on GNU libc. On other systems, some variations of this scheme are used, such as 'LL' or 'LL_CC.ENCODING'. You can get the list of locales supported by your system for your language by running the command diff --git a/gettext-runtime/INSTALL b/gettext-runtime/INSTALL index 671b157..f2914df 100644 --- a/gettext-runtime/INSTALL +++ b/gettext-runtime/INSTALL @@ -38,7 +38,7 @@ The simplest way to compile this package is: ‘sh ./configure’ instead to prevent ‘csh’ from trying to execute ‘configure’ itself. - Running ‘configure’ takes awhile. While running, it prints some + Running ‘configure’ takes a while. While running, it prints some messages telling which features it is checking for. 2. Type ‘make’ to compile the package. @@ -77,7 +77,7 @@ directory where you want the object files and executables to go and run the ‘configure’ script. ‘configure’ automatically checks for the source code in the directory that ‘configure’ is in and in ‘..’. - If you have to use a ‘make’ that does not supports the ‘VPATH’ + If you have to use a ‘make’ that does not support the ‘VPATH’ variable, you have to compile the package for one architecture at a time in the source code directory. After you have installed the package for one architecture, use ‘make distclean’ before reconfiguring for another diff --git a/gettext-tools/INSTALL b/gettext-tools/INSTALL index 671b157..f2914df 100644 --- a/gettext-tools/INSTALL +++ b/gettext-tools/INSTALL @@ -38,7 +38,7 @@ The simplest way to compile this package is: ‘sh ./configure’ instead to prevent ‘csh’ from trying to execute ‘configure’ itself. - Running ‘configure’ takes awhile. While running, it prints some + Running ‘configure’ takes a while. While running, it prints some messages telling which features it is checking for. 2. Type ‘make’ to compile the package. @@ -77,7 +77,7 @@ directory where you want the object files and executables to go and run the ‘configure’ script. ‘configure’ automatically checks for the source code in the directory that ‘configure’ is in and in ‘..’. - If you have to use a ‘make’ that does not supports the ‘VPATH’ + If you have to use a ‘make’ that does not support the ‘VPATH’ variable, you have to compile the package for one architecture at a time in the source code directory. After you have installed the package for one architecture, use ‘make distclean’ before reconfiguring for another diff --git a/gettext-tools/doc/FAQ.html b/gettext-tools/doc/FAQ.html index 4f154eb..fd7f717 100644 --- a/gettext-tools/doc/FAQ.html +++ b/gettext-tools/doc/FAQ.html @@ -138,7 +138,7 @@ list.
build error “text relocations remain” in the libasprintf subdirectory libtool (or more precisely, the version of libtool that was available -at the time the gettext release waas made) doesn't support linking C++ +at the time the gettext release was made) doesn't support linking C++ libraries with some versions of GCC. As a workaround, you can configure gettext with the option --disable-libasprintf.

“make install” fails

@@ -635,7 +635,7 @@ and link command lines. Otherwise you might end up calling the libc.lib, whereas intl.dll is using the getenv() function -from Mictosoft's msvcrt.lib. +from Microsoft's msvcrt.lib.
  • Check that you set the environment variable using both SetEnvironmentVariable() and
    Use of wide strings L"..." doesn't help solving the problem, because on systems like FreeBSD or -Solaris, the way how wide string literals are stored in compiled code +Solaris, the way that wide string literals are stored in compiled code depends on the compilation  character set, just as it does for narrow strings "...". Moreover, wide strings have problems of their own.
    diff --git a/gettext-tools/doc/gettext.texi b/gettext-tools/doc/gettext.texi index ed01f87..d5941d5 100644 --- a/gettext-tools/doc/gettext.texi +++ b/gettext-tools/doc/gettext.texi @@ -195,7 +195,7 @@ The User's View Setting the Locale through Environment Variables -* Locale Names:: How a Locale Specification Looks Like +* Locale Names:: What a Locale Specification Looks Like * Locale Environment Variables:: Which Environment Variable Specfies What * The LANGUAGE variable:: How to Specify a Priority List of Languages @@ -548,7 +548,7 @@ and free software. Using a common language is quite handy for communication between developers, maintainers and users from all countries. On the other hand, most people are less comfortable with English than with their own native language, and would prefer to -use their mother tongue for day to day's work, as far as possible. +use their mother tongue for day to day work, as far as possible. Many would simply @emph{love} to see their computer screen showing a lot less of English, and far more of their own language. @@ -600,7 +600,7 @@ GNU @code{gettext} is designed to minimize the impact of internationalization on program sources, keeping this impact as small and hardly noticeable as possible. Internationalization has better chances of succeeding if it is very light weighted, or at least, -appear to be so, when looking at program sources. +appears to be so, when looking at program sources. The Translation Project also uses the GNU @code{gettext} distribution as a vehicle for documenting its structure and methods. This goes @@ -625,7 +625,7 @@ tired of writing these long words over and over again, took the habit of writing @dfn{i18n} and @dfn{l10n} instead, quoting the first and last letter of each word, and replacing the run of intermediate letters by a number merely telling how many such letters there are. -But in this manual, in the sake of clarity, we will patiently write +But in this manual, for the sake of clarity, we will patiently write the names in full, each time@dots{} @cindex internationalization @@ -647,7 +647,7 @@ cultural habits. This is a particularisation process, by which generic methods already implemented in an internationalized program are used in specific ways. The programming environment puts several functions to the programmers disposal which allow this runtime configuration. -The formal description of specific set of cultural habits for some +The formal description of the specific set of cultural habits for some country, together with all associated translations targeted to the same native language, is called the @dfn{locale} for this language or country. Users achieve localization of programs by setting proper @@ -713,7 +713,7 @@ translating them properly would require a prior translation of the RFC itself. @item -Almost all programs accept options, which are often worded out so to +Almost all programs accept options, which are often worded out so as to be descriptive for the English readers; one might want to consider offering translated versions for program options as well. @@ -801,10 +801,11 @@ For example, the following numbers are all written correctly for their respective locales: @example -12,345.67 English -12.345,67 German - 12345,67 French -1,2345.67 Asia + 12,345,678.09 English + 12.345.678,09 German + 12 345 678,09 French + 1234,5678.09 Chinese +1,23,45,678.09 South Asian @end example Some programs could go further and use different unit systems, like @@ -844,7 +845,7 @@ or less reasonable support for at least some of the missing components. @section Files Conveying Translations @cindex files, @file{.po} and @file{.mo} -The letters PO in @file{.po} files means Portable Object, to +The letters PO in @file{.po} files mean Portable Object, to distinguish it from @file{.mo} files, where MO stands for Machine Object. This paradigm, as well as the PO file format, is inspired by the NLS standard developed by Uniforum, and first implemented by @@ -1012,7 +1013,7 @@ represents the target language. See @ref{Creating} for details. Then comes the initial translation of messages. Translation in itself is a whole matter, still exclusively meant for humans, and whose complexity far overwhelms the level of this manual. -Nevertheless, a few hints are given in some other chapter of this +Nevertheless, a few hints are given in some other chapters of this manual (@pxref{Translators}). You will also find there indications about how to contact translating teams, or becoming part of them, for sharing your translating concerns with others who target the same @@ -1025,8 +1026,8 @@ for ensuring that your efforts fully respect the PO file format, and quoting conventions (@pxref{PO Files}). This is surely not an impossible task, as this is the way many people have handled PO files around 1995. On the other hand, by using a PO file editor, most details -of PO file format are taken care of for you, but you have to acquire -some familiarity with PO file editor itself. +of the PO file format are taken care of for you, but you have to acquire +some familiarity with the PO file editor itself. If some common translations have already been saved into a compendium PO file, translators may use PO mode for initializing untranslated @@ -1035,7 +1036,7 @@ the compendium, updating it (@pxref{Compendium}). Compendium files are meant to be exchanged between members of a given translation team. Programs, or packages of programs, are dynamic in nature: users write -bug reports and suggestion for improvements, maintainers react by +bug reports and suggestions for improvements, maintainers react by modifying programs in various ways. The fact that a package has already been internationalized should not make maintainers shy of adding new strings, or modifying strings already translated. @@ -1199,7 +1200,7 @@ prompt, merely execute @file{.login} or @file{.profile} file, once and for all. @menu -* Locale Names:: How a Locale Specification Looks Like +* Locale Names:: What a Locale Specification Looks Like * Locale Environment Variables:: Which Environment Variable Specfies What * The LANGUAGE variable:: How to Specify a Priority List of Languages @end menu @@ -1355,7 +1356,7 @@ Languages are not equally well supported in all packages using GNU use the translations that are shipped with the operating system or with particular packages that you install afterwards. But you can also install newer localizations directly. For doing this, you will need an -understanding where each localization file is stored on the file system. +understanding of where each localization file is stored on the file system. @cindex @file{ABOUT-NLS} file For programs that participate in the Translation Project, you can start @@ -1373,7 +1374,7 @@ For programs that are part of the GNOME project, the starting point is: For other programs, you may check whether the program's source code package contains some @file{@var{ll}.po} files; often they are kept together in a directory called @file{po/}. Each @file{@var{ll}.po} file contains the -message translations for the language whose abbreviation of @var{ll}. +message translations for the language whose abbreviation is @var{ll}. @node PO Files, Sources, Users, Top @chapter The Format of PO Files @@ -1423,9 +1424,9 @@ through GNU @code{gettext} tools, there is exactly one blank line between entries. Then comments follow, on lines all starting with the character @code{#}. There are two kinds of comments: those which have some white space immediately following the @code{#} - the @var{translator -comments} -, which comments are created and maintained exclusively by the +comments} -, these comments are created and maintained exclusively by the translator, and those which have some non-white character just after the -@code{#} - the @var{automatic comments} -, which comments are created and +@code{#} - the @var{automatic comments} -, these comments are created and maintained automatically by GNU @code{gettext} tools. Comment lines starting with @code{#.} contain comments given by the programmer, directed at the translator; these comments are called @var{extracted comments} @@ -1453,7 +1454,7 @@ takes care of quoting for her. The @code{msgid} strings, as well as automatic comments, are produced and managed by other GNU @code{gettext} tools, and PO mode does not provide means for the translator to alter these. The most she can -do is merely deleting them, and only by deleting the whole entry. +do is merely delete them, and only by deleting the whole entry. On the other hand, the @code{msgstr} string, as well as translator comments, are really meant for the translator, and PO mode gives her the full control she needs. @@ -1473,7 +1474,7 @@ string might not be a correct translation (anymore). Only the translator can judge if the translation requires further modification, or is acceptable as is. Once satisfied with the translation, she then removes this @code{fuzzy} attribute. The @code{msgmerge} program inserts this -when it combined the @code{msgid} and @code{msgstr} entries after fuzzy +when it combines the @code{msgid} and @code{msgstr} entries after fuzzy search only. @xref{Fuzzy Entries}. @item c-format @@ -1678,7 +1679,7 @@ and an absent @code{msgctxt} line do not mean the same thing. @kwindex msgid_plural @cindex plural forms, in PO files -A different kind of entries is used for translations which involve +A different kind of entry is used for translations which involve plural forms. @example @@ -1870,16 +1871,16 @@ The use of @code{LC_ALL} might not be appropriate for you. @code{LC_ALL} includes all locale categories and especially @code{LC_CTYPE}. This latter category is responsible for determining character classes with the @code{isalnum} etc. functions from -@file{ctype.h} which could especially for programs, which process some -kind of input language, be wrong. For example this would mean that a +@file{ctype.h} which could, especially for programs which process some +kind of input language, be wrong. For example this would mean that source code using the @,{c} (c-cedilla character) is runnable in France but not in the U.S. Some systems also have problems with parsing numbers using the -@code{scanf} functions if an other but the @code{LC_ALL} locale category is +@code{scanf} functions if other than the @code{LC_ALL} locale category is used. The standards say that additional formats but the one known in the @code{"C"} locale might be recognized. But some systems seem to reject -numbers in the @code{"C"} locale format. In some situation, it might +numbers in the @code{"C"} locale format. In some situations, it might also be a problem with the notation itself which makes it impossible to recognize whether the number is in the @code{"C"} locale or the local format. This can happen if thousands separator characters are used. @@ -1926,7 +1927,7 @@ such as found in the modules @samp{c-ctype}, @samp{c-strcase}, @samp{c-strcasestr}, @samp{c-strtod}, @samp{c-strtold} in the GNU gnulib source distribution. -It is also possible to switch the locale forth and back between the +It is also possible to switch the locale back and forth between the environment dependent locale and the C locale, but this approach is normally avoided because a @code{setlocale} call is expensive, because it is tedious to determine the places where a locale switch @@ -1941,7 +1942,7 @@ Before strings can be marked for translations, they sometimes need to be adjusted. Usually preparing a string for translation is done right before marking it, during the marking phase which is described in the next sections. What you have to keep in mind while doing that is the -following. +following: @itemize @bullet @item @@ -2051,7 +2052,7 @@ puts ("On the next stack overflow we will crash!!!"); @end example @noindent -Should these two statements merged into a single one? I would recommend to +Should these two statements be merged into a single one? I would recommend to merge them if the two sentences are related to each other, because then it makes it easier for the translator to understand and translate both. On the other hand, if one of the two messages is a stereotypic one, occurring @@ -2230,7 +2231,7 @@ functions. But this is not universal usage, and some translatable strings appear in structured initializations. @xref{Special cases}. The second goal of the marking operation is to help @code{xgettext} -at properly extracting all translatable strings when it scans a set +to properly extract all translatable strings when it scans a set of program sources and produces PO file templates. The canonical keyword for marking translatable strings is @@ -2250,7 +2251,7 @@ sources for those trying to keep them within 79 or 80 columns. Many packages use @samp{_} (a simple underline) as a keyword, and write @samp{_("Translatable string")} instead of @samp{gettext ("Translatable string")}. Further, the coding rule, from GNU standards, -wanting that there is a space between the keyword and the opening +specifying that there is a space between the keyword and the opening parenthesis is relaxed, in practice, for this particular usage. So, the textual overhead per translatable string is reduced to only three characters: the underline and the two parentheses. @@ -2305,7 +2306,7 @@ strings in the program sources, while simultaneously producing a set of translation in some language, for the package being internationalized. @emindex @code{etags}, using for marking strings -The set of program sources, targeted by the PO mode commands describe +The set of program sources, targeted by the PO mode commands described here, should have an Emacs tags table constructed for your project, prior to using these PO file commands. This is easy to do. In any shell window, change the directory to the root of your project, then @@ -2387,11 +2388,11 @@ However, by giving a prefix argument to the command @w{(@kbd{C-u from the first program source; but in this case, strings that you recently marked as translatable will be automatically skipped. -Using this @kbd{,} command does not prevent using of other regular +Using this @kbd{,} command does not prevent use of other regular Emacs tags commands. For example, regular @code{tags-search} or @code{tags-query-replace} commands may be used without disrupting the independent @kbd{,} search sequence. However, as implemented, the -@emph{initial} @kbd{,} command (or the @kbd{,} command is used with a +@emph{initial} @kbd{,} command (or the @kbd{,} command used with a prefix) might also reinitialize the regular Emacs tags searching to the first tags file, this reinitialization might be considered spurious. @@ -2442,8 +2443,8 @@ There is no provision in PO mode, currently, for deleting a known keyword, you have to quit the file (maybe using @kbd{q}) and reopen it afresh. When a PO file is newly brought up in an Emacs window, only @samp{gettext} and @samp{_} are known as keywords, and @samp{gettext} -is preferred for the @kbd{M-.} command. In fact, this is not useful to -prefer @samp{_}, as this one is already built in the @kbd{M-,} command. +is preferred for the @kbd{M-.} command. In fact, it is not useful to +prefer @samp{_}, as this one is already built into the @kbd{M-,} command. @node c-format Flag, Special cases, Marking, Sources @section Special Comments preceding Keywords @@ -2469,7 +2470,7 @@ A possible German translation for the above string might be: A C programmer, even if he cannot speak German, will recognize that there is something wrong here. The order of the two format specifiers -is changed but of course the arguments in the @code{printf} don't have. +is changed but of course the arguments in the @code{printf} have not. This will most probably lead to problems because now the length of the string is regarded as the address. @@ -2482,7 +2483,7 @@ use of @samp{msgfmt -c} will catch the error, so that it cannot cause problems at runtime. @noindent -If the word order in the above German translation would be correct one +If the word order in the above German translation is correct one would have to write @example @@ -2595,7 +2596,7 @@ from the array. So one solution can look like this: @end example Please convince yourself that the string which is written by -@code{fputs} is translated in any case. How to get @code{xgettext} know +@code{fputs} is translated in any case. How to get @code{xgettext} to know the additional keyword @code{gettext_noop} is explained in @ref{xgettext Invocation}. @@ -3318,7 +3319,7 @@ Quit processing, possibly after confirmation (@code{po-confirm-and-quit}). @item 0 @efindex 0@r{, PO Mode command} -Temporary leave the PO file window (@code{po-other-window}). +Temporarily leave the PO file window (@code{po-other-window}). @item ? @itemx h @@ -3343,10 +3344,10 @@ The command @kbd{_} (@code{po-undo}) interfaces to the Emacs Editor}. Each time @kbd{_} is typed, modifications which the translator did to the PO file are undone a little more. For the purpose of undoing, each PO mode command is atomic. This is especially true for -the @kbd{@key{RET}} command: the whole edition made by using a single -use of this command is undone at once, even if the edition itself +the @kbd{@key{RET}} command: the whole of the edits made by a single +use of this command are undone at once, even if the edit itself implied several actions. However, while in the editing window, one -can undo the edition work quite parsimoniously. +can undo the editing work quite parsimoniously. @efindex Q@r{, PO Mode command} @efindex q@r{, PO Mode command} @@ -3404,11 +3405,11 @@ as well as all individual entries. The program @code{msgfmt} runs asynchronously with Emacs, so the translator regains control immediately while her PO file is being studied. Error output is collected in the Emacs @samp{*compilation*} buffer, -displayed in another window. The regular Emacs command @kbd{C-x`} +and displayed in another window. The regular Emacs command @kbd{C-x`} (@code{next-error}), as well as other usual compile commands, allow the translator to reposition quickly to the offending parts of the PO file. Once the cursor is on the line in error, the translator may decide on -any PO mode action which would help correcting the error. +any PO mode action which would help correct the error. @node Entry Positioning, Normalizing, Main PO Commands, PO Mode @subsection Entry Positioning @@ -3424,7 +3425,7 @@ the PO file, this also selects on which entry commands operate. @emindex moving through a PO file Some PO mode commands alter the position of the cursor in a specialized -way. A few of those special purpose positioning are described here, +way. A few of those special purpose positionings are described here, the others are described in following sections (for a complete list try @kbd{C-h m}): @@ -3497,7 +3498,7 @@ how @emph{others} should do translation. @efindex p@r{, PO Mode command} @efindex po-previous-entry@r{, PO Mode command} The commands @kbd{n} (@code{po-next-entry}) and @kbd{p} -(@code{po-previous-entry}) move the cursor the entry following, +(@code{po-previous-entry}) move the cursor to the entry following, or preceding, the current one. If @kbd{n} is given while the cursor is on the last entry of the PO file, or if @kbd{p} is given while the cursor is on the first entry, no move is done. @@ -3512,7 +3513,7 @@ entry, of the PO file. When the cursor is located past the last entry in a PO file, most PO mode commands will return an error saying @samp{After last entry}. Moreover, the commands @kbd{<} and @kbd{>} have the special property of being able to work even when the cursor -is not into some PO file entry, and one may use them for nicely +is not in some PO file entry, and one may use them for nicely correcting this situation. But even these commands will fail on a truly empty PO file. There are development plans for the PO mode for it to interactively fill an empty PO file from sources. @xref{Marking}. @@ -3691,8 +3692,8 @@ Find the previous translated entry (@code{po-previous-translated-entry}). @efindex T@r{, PO Mode command} @efindex po-previous-translated-entry@r{, PO Mode command} The commands @kbd{t} (@code{po-next-translated-entry}) and @kbd{T} -(@code{po-previous-translated-entry}) move forwards or backwards, chasing -for an translated entry. If none is found, the search is extended and +(@code{po-previous-translated-entry}) move forwards or backwards, looking +for a translated entry. If none is found, the search is extended and wraps around in the PO file buffer. @evindex po-auto-fuzzy-on-edit@r{, PO Mode variable} @@ -3718,10 +3719,10 @@ to have a fuzzy translation. They are called fuzzy entries, for short. Fuzzy entries, even if they account for translated entries for most other purposes, usually call for revision by the translator. Those may be produced by applying the program @code{msgmerge} to -update an older translated PO files according to a new PO template +update an older translated PO file according to a new PO template file, when this tool hypothesises that some new @code{msgid} has -been modified only slightly out of an older one, and chooses to pair -what it thinks to be the old translation for the new modified entry. +been modified only slightly from an older one, and chooses to pair +what it thinks to be the old translation with the new modified entry. The slight alteration in the original string (the @code{msgid} string) should often be reflected in the translated string, and this requires the intervention of the translator. For this reason, @code{msgmerge} @@ -3754,7 +3755,7 @@ Remove the fuzzy attribute of the current entry (@code{po-unfuzzy}). @efindex F@r{, PO Mode command} @efindex po-previous-fuzzy-entry@r{, PO Mode command} The commands @kbd{f} (@code{po-next-fuzzy-entry}) and @kbd{F} -(@code{po-previous-fuzzy-entry}) move forwards or backwards, chasing for +(@code{po-previous-fuzzy-entry}) move forwards or backwards, looking for a fuzzy entry. If none is found, the search is extended and wraps around in the PO file buffer. @@ -3764,7 +3765,7 @@ around in the PO file buffer. The command @kbd{@key{TAB}} (@code{po-unfuzzy}) removes the fuzzy attribute associated with an entry, usually leaving it translated. Further, if the variable @code{po-auto-select-on-unfuzzy} has not -the @code{nil} value, the @kbd{@key{TAB}} command will automatically chase +the @code{nil} value, the @kbd{@key{TAB}} command will automatically look for another interesting entry to work on. The initial value of @code{po-auto-select-on-unfuzzy} is @code{nil}. @@ -3775,19 +3776,19 @@ ensure some kind of double check, later. In this case, the usual paradigm is that an entry becomes fuzzy (if not already) whenever the translator modifies it. If she is satisfied with the translation, she then uses @kbd{@key{TAB}} to pick another entry to work on, clearing the fuzzy attribute -on the same blow. If she is not satisfied yet, she merely uses @kbd{@key{SPC}} +in the same blow. If she is not satisfied yet, she merely uses @kbd{@key{SPC}} to chase another entry, leaving the entry fuzzy. @efindex DEL@r{, PO Mode command} @efindex po-fade-out-entry@r{, PO Mode command} The translator may also use the @kbd{@key{DEL}} command (@code{po-fade-out-entry}) over any translated entry to mark it as being -fuzzy, when she wants to easily leave a trace she wants to later return -working at this entry. +fuzzy, when she wants to easily leave a trace that she wants to later return +to work on this entry. Also, when time comes to quit working on a PO file buffer with the @kbd{q} -command, the translator is asked for confirmation, if fuzzy string -still exists. +command, the translator is asked for confirmation, if any fuzzy strings +still exist. @node Untranslated Entries, Obsolete Entries, Fuzzy Entries, PO Mode @subsection Untranslated Entries @@ -3819,7 +3820,7 @@ Find the next untranslated entry (@code{po-next-untranslated-entry}). @item U @efindex U@r{, PO Mode command} -Find the previous untranslated entry (@code{po-previous-untransted-entry}). +Find the previous untranslated entry (@code{po-previous-untranslated-entry}). @item k @efindex k@r{, PO Mode command} @@ -3830,10 +3831,10 @@ Turn the current entry into an untranslated one (@code{po-kill-msgstr}). @efindex u@r{, PO Mode command} @efindex po-next-untranslated-entry@r{, PO Mode command} @efindex U@r{, PO Mode command} -@efindex po-previous-untransted-entry@r{, PO Mode command} +@efindex po-previous-untranslated-entry@r{, PO Mode command} The commands @kbd{u} (@code{po-next-untranslated-entry}) and @kbd{U} -(@code{po-previous-untransted-entry}) move forwards or backwards, -chasing for an untranslated entry. If none is found, the search is +(@code{po-previous-untranslated-entry}) move forwards or backwards, +looking for an untranslated entry. If none is found, the search is extended and wraps around in the PO file buffer. @efindex k@r{, PO Mode command} @@ -3892,7 +3893,7 @@ Make an active entry obsolete, or zap out an obsolete entry @efindex po-previous-obsolete-entry@r{, PO Mode command} The commands @kbd{o} (@code{po-next-obsolete-entry}) and @kbd{O} (@code{po-previous-obsolete-entry}) move forwards or backwards, -chasing for an obsolete entry. If none is found, the search is +looking for an obsolete entry. If none is found, the search is extended and wraps around in the PO file buffer. PO mode does not provide ways for un-commenting an obsolete entry @@ -3923,8 +3924,8 @@ guesses at retrieving the most probable candidate, among all obsolete entries, for initializing the translation of a newly appeared string. I think it might be a quite hard problem to do this algorithmically, as we have to develop good and efficient measures of string similarity. -Right now, PO mode completely lets the decision to the translator, -when the time comes to find the adequate obsolete translation, it +Right now, PO mode completely leaves the decision to the translator. +When the time comes to find the adequate obsolete translation, it merely tries to provide handy tools for helping her to do so. @node Modifying Translations, Modifying Comments, Obsolete Entries, PO Mode @@ -3934,7 +3935,7 @@ merely tries to provide handy tools for helping her to do so. PO mode prevents direct modification of the PO file, by the usual means Emacs gives for altering a buffer's contents. By doing so, -it pretends helping the translator to avoid little clerical errors +it pretend it is helping the translator to avoid little clerical errors about the overall file format, or the proper quoting of strings, as those errors would be easily made. Other kinds of errors are still possible, but some may be caught and diagnosed by the batch @@ -3980,7 +3981,7 @@ Replace the translation, taking the new from the kill ring The command @kbd{@key{RET}} (@code{po-edit-msgstr}) opens a new Emacs window meant to edit in a new translation, or to modify an already existing translation. The new window contains a copy of the translation taken from -the current PO file entry, all ready for edition, expunged of all quoting +the current PO file entry, all ready for editing, expunged of all quoting marks, fully modifiable and with the complete extent of Emacs modifying commands. When the translator is done with her modifications, she may use @w{@kbd{C-c C-c}} to close the subedit window with the automatically requoted @@ -3996,10 +3997,10 @@ normally used when the translator wants to redo a fresh translation of the original string, disregarding any previous work. @evindex po-auto-edit-with-msgid@r{, PO Mode variable} -It is possible to arrange so, whenever editing an untranslated +It is possible to arrange that, whenever editing an untranslated entry, the @kbd{@key{LFD}} command be automatically executed. If you set @code{po-auto-edit-with-msgid} to @code{t}, the translation gets -initialised with the original string, in case none exists already. +initialised with the original string, if none exists already. The default value for @code{po-auto-edit-with-msgid} is @code{nil}. @emindex starting a string translation @@ -4060,9 +4061,9 @@ the translator may travel along the kill ring for saved strings, until she finds the string she really wanted. When a string is yanked into a PO file entry, it is fully and -automatically requoted for complying with the format PO files should +automatically requoted to comply with the format PO files should have. Further, if the entry is obsolete, PO mode then appropriately -push the inserted string inside comments. Once again, translators +puts the inserted string inside comments. Once again, translators should not burden themselves with quoting considerations besides, of course, the necessity of the translated string itself respective to the program using it. @@ -4088,16 +4089,16 @@ not wanted anymore, and may be safely deleted. When the translator finds an untranslated entry and suspects that a slight variant of the translation exists, she immediately uses @kbd{m} -to mark the current entry location, then starts chasing obsolete +to mark the current entry location, then starts looking for obsolete entries with @kbd{o}, hoping to find some translation corresponding to the unmodified string. Once found, she uses the @kbd{@key{DEL}} command -for deleting the obsolete entry, knowing that @kbd{@key{DEL}} also @emph{kills} +to delete the obsolete entry, knowing that @kbd{@key{DEL}} also @emph{kills} the translation, that is, pushes the translation on the kill ring. Then, @kbd{r} returns to the initial untranslated entry, and @kbd{y} then @emph{yanks} the saved translation right into the @code{msgstr} -field. The translator is then free to use @kbd{@key{RET}} for fine -tuning the translation contents, and maybe to later use @kbd{u}, -then @kbd{m} again, for going on with the next untranslated string. +field. The translator is then free to use @kbd{@key{RET}} to fine +tune the translation contents, and maybe to later use @kbd{u}, +then @kbd{m} again, to go on to the next untranslated string. When some sequence of keys has to be typed over and over again, the translator may find it useful to become better acquainted with the Emacs @@ -4112,7 +4113,7 @@ capability of learning these sequences and playing them back under request. Any translation work done seriously will raise many linguistic difficulties, for which decisions have to be made, and the choices further documented. These documents may be saved within the -PO file in form of translator comments, which the translator +PO file in the form of translator comments, which the translator is free to create, delete, or modify at will. These comments may be useful to herself when she returns to this PO file after a while. @@ -4134,12 +4135,12 @@ Interactively edit the translator comments (@code{po-edit-comment}). @item K @efindex K@r{, PO Mode command} -Save the translator comments on the kill ring, and delete it +Save the translator comments on the kill ring, and delete them (@code{po-kill-comment}). @item W @efindex W@r{, PO Mode command} -Save the translator comments on the kill ring, without deleting it +Save the translator comments on the kill ring, without deleting them (@code{po-kill-ring-save-comment}). @item Y @@ -4151,7 +4152,7 @@ Replace the translator comments, taking the new from the kill ring These commands parallel PO mode commands for modifying the translation strings, and behave much the same way as they do, except that they handle -this part of PO file comments meant for translator usage, rather +the part of PO file comments meant for translator usage, rather than the translation strings. So, if the descriptions given below are slightly succinct, it is because the full details have already been given. @xref{Modifying Translations}. @@ -4163,7 +4164,7 @@ containing a copy of the translator comments on the current PO file entry. If there are no such comments, PO mode understands that the translator wants to add a comment to the entry, and she is presented with an empty screen. Comment marks (@code{#}) and the space following them are automatically -removed before edition, and reinstated after. For translator comments +removed before editing, and reinstated after. For translator comments pertaining to obsolete entries, the uncommenting and recommenting operations are done twice. Once in the editing window, the keys @w{@kbd{C-c C-c}} allow the translator to tell she is finished with editing the comment. @@ -4201,7 +4202,7 @@ may initialize the translator comments with the previous translation, still at the head of the kill ring. Because editing already pushed the previous translation on the kill ring, she merely has to type @kbd{M-w} prior to @kbd{#}, and the previous translation will be right there, -all ready for being introduced by some explanatory text. +all ready to be introduced by some explanatory text. On the other hand, presume there are some translator comments already and that the translator wants to add to those comments, instead @@ -4211,7 +4212,7 @@ regular Emacs commands @kbd{C-y} (@code{yank}) and @kbd{M-y} (@code{yank-pop}) to get the previous translation where she likes. @node Subedit, C Sources Context, Modifying Comments, PO Mode -@subsection Details of Sub Edition +@subsection Details of Sub Editing @emindex subedit minor mode The PO subedit minor mode has a few peculiarities worth being described @@ -4221,11 +4222,11 @@ of Emacs, which are described below. @table @kbd @item C-c C-c @efindex C-c C-c@r{, PO Mode command} -Complete edition (@code{po-subedit-exit}). +Complete editing (@code{po-subedit-exit}). @item C-c C-k @efindex C-c C-k@r{, PO Mode command} -Abort edition (@code{po-subedit-abort}). +Abort editing (@code{po-subedit-abort}). @item C-c C-a @efindex C-c C-a@r{, PO Mode command} @@ -4248,10 +4249,10 @@ sight or if buffers were switched. If the translator becomes unsatisfied with her translation or comment, to the extent she prefers keeping what was existent prior to the @kbd{@key{RET}} or @kbd{#} command, she may use the command @w{@kbd{C-c C-k}} -(@code{po-subedit-abort}) to merely get rid of edition, while preserving +(@code{po-subedit-abort}) to merely get rid of the edits, while preserving the original translation or comment. Another way would be for her to exit -normally with @w{@kbd{C-c C-c}}, then type @code{U} once for undoing the -whole effect of last edition. +normally with @w{@kbd{C-c C-c}}, then type @code{U} once to undo the +whole effect of the last edits. @efindex C-c C-a@r{, PO Mode command} @efindex po-subedit-cycle-auxiliary@r{, PO Mode command} @@ -4275,7 +4276,7 @@ at the end of the string being edited, but this @code{<} is not really part of the string. On exiting the editing window with @w{@kbd{C-c C-c}}, PO mode automatically removes such @kbd{<} and all whitespace added after it. If the translator adds characters after the terminating @code{<}, it -looses its delimiting property and integrally becomes part of the string. +loses its delimiting property and integrally becomes part of the string. If she removes the delimiting @code{<}, then the edited string is taken @emph{as is}, with all trailing newlines, even if invisible. Also, if the translated string ought to end itself with a genuine @code{<}, then @@ -4285,18 +4286,18 @@ in the editing window, as ending with two @code{<} in a row. @emindex editing multiple entries When a translation (or a comment) is being edited, the translator may move the cursor back into the PO file buffer and freely move to other entries, -browsing at will. If, with an edition pending, the translator wanders in the +browsing at will. If, with edits pending, the translator wanders in the PO file buffer, she may decide to start modifying another entry. Each entry being edited has its own subedit buffer. It is possible to simultaneously edit the translation @emph{and} the comment of a single entry, or to edit entries in different PO files, all at once. Typing @kbd{@key{RET}} on a field already being edited merely resumes that particular edit. Yet, -the translator should better be comfortable at handling many Emacs windows! +the translator had better be comfortable with handling many Emacs windows! @emindex pending subedits Pending subedits may be completed or aborted in any order, regardless of how or when they were started. When many subedits are pending and the -translator asks for quitting the PO file (with the @kbd{q} command), subedits +translator asks to quit the PO file (with the @kbd{q} command), subedits are automatically resumed one at a time, so she may decide for each of them. @node C Sources Context, Auxiliary, Subedit, PO Mode @@ -4329,11 +4330,11 @@ translator should not be shy at taking a look, once in a while. It is most probable that she will still be able to find some of the hints she needs. She will learn quickly to not feel uncomfortable in program code, paying more attention to programmer's comments, -variable and function names (if he dared choosing them well), and +variable and function names (if he dared to choose them well), and overall organization, than to the program code itself. @emindex find source fragment for a PO file entry -The following commands are meant to help the translator at getting +The following commands are meant to help the translator to get program source context for a PO file entry. @table @kbd @@ -4409,8 +4410,8 @@ also looked for, but relative to the directory immediately above it. Those two cases take proper care of most PO files. However, it might happen that a PO file has been moved, or is edited in a different place than its normal location. When this happens, the translator -should tell PO mode in which directory normally sits the genuine PO -file. Many such directories may be specified, and all together, they +should tell PO mode in which directory the genuine PO file is normally +found. Many such directories may be specified, and all together, they constitute what is called the @dfn{search path} for program sources. The command @kbd{S} (@code{po-consider-source-path}) is used to interactively enter a new directory at the front of the search path, and the command @@ -4470,9 +4471,9 @@ PO file to the list of auxiliary files, while command @kbd{M-A} @efindex po-cycle-auxiliary@r{, PO Mode command} The command @kbd{a} (@code{po-cycle-auxiliary}) seeks all auxiliary PO files, round-robin, searching for a translated entry in some other language -having an @code{msgid} field identical as the one for the current entry. +having an @code{msgid} field identical to the one for the current entry. The found PO file, if any, takes the place of the current PO file in -the display (its window gets on top). Before doing so, the current PO +the display (its window pops on top). Before doing so, the current PO file is also made into an auxiliary file, if not already. So, @kbd{a} in this newly displayed PO file will seek another PO file, and so on, so repeating @kbd{a} will eventually yield back the original PO file. @@ -4482,22 +4483,22 @@ so repeating @kbd{a} will eventually yield back the original PO file. The command @kbd{C-c C-a} (@code{po-select-auxiliary}) asks the translator for her choice of a particular auxiliary file, with completion, and then switches to that selected PO file. The command also checks if -the selected file has an @code{msgid} field identical as the one for +the selected file has an @code{msgid} field identical to the one for the current entry, and if yes, this entry becomes current. Otherwise, the cursor of the selected file is left undisturbed. For all this to work fully, auxiliary PO files will have to be normalized, -in that way that @code{msgid} fields should be written @emph{exactly} +so that @code{msgid} fields are written @emph{exactly} the same way. It is possible to write @code{msgid} fields in various -ways for representing the same string, different writing would break the +ways to represent the same string, but different writing would break the proper behaviour of the auxiliary file commands of PO mode. This is not -expected to be much a problem in practice, as most existing PO files have +expected to be much of a problem in practice, as most existing PO files have their @code{msgid} entries written by the same GNU @code{gettext} tools. @efindex normalize@r{, PO Mode command} However, PO files initially created by PO mode itself, while marking strings in source files, are normalised differently. So are PO -files resulting of the @samp{M-x normalize} command. Until these +files resulting from the @samp{M-x normalize} command. Until these discrepancies between PO mode and other GNU @code{gettext} tools get fully resolved, the translator should stay aware of normalisation issues. @@ -4540,7 +4541,7 @@ msgcat -o compendium.po file1.po file2.po By default, @code{msgcat} will accumulate divergent translations for the same string. Those occurrences will be marked as @code{fuzzy} -and highly visible decorated; calling @code{msgcat} on +and highly visibly decorated; calling @code{msgcat} on @file{file1.po}: @example @@ -4581,7 +4582,7 @@ has to decide whether the first or the second version is appropriate finally to remove the @code{fuzzy} mark. If the translator knows in advance the first found translation of a -message is always the best translation she can make use to the +message is always the best translation she can make use of the @samp{--use-first} switch: @example @@ -4827,7 +4828,7 @@ get colorized output in this situation nevertheless, use the command The @samp{--color=html} option will produce output that can be viewed in a browser. This can be useful, for example, for Indic languages, -because the renderic of Indic scripts in browser is usually better than +because the renderic of Indic scripts in a browser is usually better than in terminal emulators. Note that the output produced with the @code{--color} option is @emph{not} @@ -4992,7 +4993,7 @@ This matches the translator comments. @item .extracted-comment This matches the extracted comments, i.e.@: the comments placed by the -programmer at the attention of the translator. +programmer for the attention of the translator. @item .reference-comment This matches the source file reference comments (entire lines). @@ -5092,7 +5093,7 @@ properties will be silently ignored. @table @asis @item @code{color} (CSS2 spec, section 14.1) @itemx @code{background-color} (CSS2 spec, section 14.2.1) -These properties is supported. Colors will be adjusted to match the terminal's +These properties are supported. Colors will be adjusted to match the terminal's capabilities. Note that many terminals support only 8 colors. @item @code{font-weight} (CSS2 spec, section 15.2.3) @@ -5412,7 +5413,7 @@ files. They would make the file unnecessarily large, and the platform dependent as well.) This particular issue has been strongly debated in the GNU -@code{gettext} development forum, and it is expectable that MO file +@code{gettext} development forum, and it is expected that MO file format will evolve or change over time. It is even possible that many formats may later be supported concurrently. But surely, we have to start somewhere, and the MO file format described here is a good start. @@ -6570,7 +6571,7 @@ string is always the same. One way to use this is: @end example @noindent -But this solution is not usable in all situation (e.g.@: when the locale +But this solution is not usable in all situations (e.g.@: when the locale selection changes) nor does it lead to legible code. For this reason, GNU @code{gettext} caches previous translation results. @@ -6627,7 +6628,7 @@ by @end example @noindent -Additionally we run the program @file{xgettext} on all source code file +Additionally we run the program @file{xgettext} on all source code files which contain translatable strings and that's it: we have a running program which does not depend on translations to be available, but which can use any that becomes available. @@ -6649,8 +6650,8 @@ your own ease. Now to @code{catgets}. The main problem is the work for the programmer. Every time he comes to a translatable string he has to -define a number (or a symbolic constant) which has also be defined in -the message catalog file. He also has to take care for duplicate +define a number (or a symbolic constant) which has to also be defined in +the message catalog file. He also has to take care of duplicate entries, duplicate message IDs etc. If he wants to have the same quality in the message catalog as the GNU @code{gettext} program provides he also has to put the descriptive comments for the strings and @@ -6689,7 +6690,7 @@ printf (number_count == 1 ? gettext ("you should see %d number") @end example We believe that we can solve all conflicts with this method. If it is -difficult one can also consider changing one of the conflicting string a +difficult one can also consider changing one of the conflicting strings a little bit. But it is not impossible to overcome. @code{catgets} allows same original entry to have different translations, @@ -6720,7 +6721,7 @@ is a list comments: @cindex language selection at runtime For interactive programs it might be useful to offer a selection of the -used language at runtime. To understand how to do this one need to know +used language at runtime. To understand how to do this one needs to know how the used language is determined while executing the @code{gettext} function. The method which is presented here only works correctly with the GNU implementation of the @code{gettext} functions. @@ -6758,8 +6759,8 @@ words: the used language is changed. But there is one little hook. The code for gcc-2.7.0 and up provides some optimization. This optimization normally prevents the calling of the @code{dcgettext} function as long as no new catalog is loaded. But -if @code{dcgettext} is not called the program also cannot find the -@code{LANGUAGE} variable be changed (@pxref{Optimized gettext}). A +if @code{dcgettext} is not called the program also cannot find when the +@code{LANGUAGE} variable has changed (@pxref{Optimized gettext}). A solution for this is very easy. Include the following code in the language switching function. @@ -7687,7 +7688,7 @@ teams drive themselves and are fully responsible of their linguistic choices for the Translation Project. Keep in mind that translator teams are @emph{not} driven by maintainers. You can help by carefully redirecting all communications and reports from users about linguistic matters to the -appropriate translation team, or explain users how to reach or join +appropriate translation team, or explain to users how to reach or join their team. The simplest might be to send them the @file{ABOUT-NLS} file. Maintainers should @emph{never ever} apply PO file bug reports diff --git a/gettext-tools/doc/msgattrib.texi b/gettext-tools/doc/msgattrib.texi index f895141..9a2c117 100644 --- a/gettext-tools/doc/msgattrib.texi +++ b/gettext-tools/doc/msgattrib.texi @@ -261,7 +261,7 @@ Note that this file format doesn't support plural forms. @opindex --width@r{, @code{msgattrib} option} Set the output page width. Long strings in the output files will be split across multiple lines in order to ensure that each line's width -(= number of screen columns) is less or equal to the given @var{number}. +(= number of screen columns) is less than or equal to the given @var{number}. @item --no-wrap @opindex --no-wrap@r{, @code{msgattrib} option} diff --git a/gettext-tools/doc/msgcat.texi b/gettext-tools/doc/msgcat.texi index 7c15050..76a4afb 100644 --- a/gettext-tools/doc/msgcat.texi +++ b/gettext-tools/doc/msgcat.texi @@ -183,7 +183,7 @@ Note that this file format doesn't support plural forms. @opindex --width@r{, @code{msgcat} option} Set the output page width. Long strings in the output files will be split across multiple lines in order to ensure that each line's width -(= number of screen columns) is less or equal to the given @var{number}. +(= number of screen columns) is less than or equal to the given @var{number}. @item --no-wrap @opindex --no-wrap@r{, @code{msgcat} option} diff --git a/gettext-tools/doc/msgcomm.texi b/gettext-tools/doc/msgcomm.texi index ae7c927..523e225 100644 --- a/gettext-tools/doc/msgcomm.texi +++ b/gettext-tools/doc/msgcomm.texi @@ -164,7 +164,7 @@ Note that this file format doesn't support plural forms. @opindex --width@r{, @code{msgcomm} option} Set the output page width. Long strings in the output files will be split across multiple lines in order to ensure that each line's width -(= number of screen columns) is less or equal to the given @var{number}. +(= number of screen columns) is less than or equal to the given @var{number}. @item --no-wrap @opindex --no-wrap@r{, @code{msgcomm} option} diff --git a/gettext-tools/doc/msgconv.texi b/gettext-tools/doc/msgconv.texi index 805a76f..99507a2 100644 --- a/gettext-tools/doc/msgconv.texi +++ b/gettext-tools/doc/msgconv.texi @@ -136,7 +136,7 @@ Note that this file format doesn't support plural forms. @opindex --width@r{, @code{msgconv} option} Set the output page width. Long strings in the output files will be split across multiple lines in order to ensure that each line's width -(= number of screen columns) is less or equal to the given @var{number}. +(= number of screen columns) is less than or equal to the given @var{number}. @item --no-wrap @opindex --no-wrap@r{, @code{msgconv} option} diff --git a/gettext-tools/doc/msgen.texi b/gettext-tools/doc/msgen.texi index 3f61fa4..503549f 100644 --- a/gettext-tools/doc/msgen.texi +++ b/gettext-tools/doc/msgen.texi @@ -136,7 +136,7 @@ Note that this file format doesn't support plural forms. @opindex --width@r{, @code{msgen} option} Set the output page width. Long strings in the output files will be split across multiple lines in order to ensure that each line's width -(= number of screen columns) is less or equal to the given @var{number}. +(= number of screen columns) is less than or equal to the given @var{number}. @item --no-wrap @opindex --no-wrap@r{, @code{msgen} option} diff --git a/gettext-tools/doc/msgfilter.texi b/gettext-tools/doc/msgfilter.texi index 61c2f57..00050ce 100644 --- a/gettext-tools/doc/msgfilter.texi +++ b/gettext-tools/doc/msgfilter.texi @@ -241,7 +241,7 @@ Note that this file format doesn't support plural forms. @opindex --width@r{, @code{msgfilter} option} Set the output page width. Long strings in the output files will be split across multiple lines in order to ensure that each line's width -(= number of screen columns) is less or equal to the given @var{number}. +(= number of screen columns) is less than or equal to the given @var{number}. @item --no-wrap @opindex --no-wrap@r{, @code{msgfilter} option} diff --git a/gettext-tools/doc/msgfmt.texi b/gettext-tools/doc/msgfmt.texi index a808b7c..4279ec6 100644 --- a/gettext-tools/doc/msgfmt.texi +++ b/gettext-tools/doc/msgfmt.texi @@ -303,7 +303,7 @@ Sometimes a keyboard accelerator is also called "keyboard mnemonic". This check verifies that if the untranslated string has exactly one @samp{&} character, the translated string has exactly one @samp{&} as well. If this option is given with a @var{char} argument, this @var{char} should -be a non-alphanumeric character and is used as keyboard accelerator mark +be a non-alphanumeric character and is used as a keyboard accelerator mark instead of @samp{&}. @item -f diff --git a/gettext-tools/doc/msggrep.texi b/gettext-tools/doc/msggrep.texi index 229b924..fdb89eb 100644 --- a/gettext-tools/doc/msggrep.texi +++ b/gettext-tools/doc/msggrep.texi @@ -236,7 +236,7 @@ Note that this file format doesn't support plural forms. @opindex --width@r{, @code{msggrep} option} Set the output page width. Long strings in the output files will be split across multiple lines in order to ensure that each line's width -(= number of screen columns) is less or equal to the given @var{number}. +(= number of screen columns) is less than or equal to the given @var{number}. @item --no-wrap @opindex --no-wrap@r{, @code{msggrep} option} diff --git a/gettext-tools/doc/msginit.texi b/gettext-tools/doc/msginit.texi index 3be6e17..5fc3737 100644 --- a/gettext-tools/doc/msginit.texi +++ b/gettext-tools/doc/msginit.texi @@ -137,7 +137,7 @@ Note that this file format doesn't support plural forms. @opindex --width@r{, @code{msginit} option} Set the output page width. Long strings in the output files will be split across multiple lines in order to ensure that each line's width -(= number of screen columns) is less or equal to the given @var{number}. +(= number of screen columns) is less than or equal to the given @var{number}. @item --no-wrap @opindex --no-wrap@r{, @code{msginit} option} diff --git a/gettext-tools/doc/msgmerge.texi b/gettext-tools/doc/msgmerge.texi index ad76f0e..5105315 100644 --- a/gettext-tools/doc/msgmerge.texi +++ b/gettext-tools/doc/msgmerge.texi @@ -224,7 +224,7 @@ Note that this file format doesn't support plural forms. @opindex --width@r{, @code{msgmerge} option} Set the output page width. Long strings in the output files will be split across multiple lines in order to ensure that each line's width -(= number of screen columns) is less or equal to the given @var{number}. +(= number of screen columns) is less than or equal to the given @var{number}. @item --no-wrap @opindex --no-wrap@r{, @code{msgmerge} option} diff --git a/gettext-tools/doc/msgunfmt.texi b/gettext-tools/doc/msgunfmt.texi index ed85f81..1fc19fd 100644 --- a/gettext-tools/doc/msgunfmt.texi +++ b/gettext-tools/doc/msgunfmt.texi @@ -177,7 +177,7 @@ Note that this file format doesn't support plural forms. @opindex --width@r{, @code{msgunfmt} option} Set the output page width. Long strings in the output files will be split across multiple lines in order to ensure that each line's width -(= number of screen columns) is less or equal to the given @var{number}. +(= number of screen columns) is less than or equal to the given @var{number}. @item --no-wrap @opindex --no-wrap@r{, @code{msgunfmt} option} diff --git a/gettext-tools/doc/msguniq.texi b/gettext-tools/doc/msguniq.texi index 4bb6ffd..d30666d 100644 --- a/gettext-tools/doc/msguniq.texi +++ b/gettext-tools/doc/msguniq.texi @@ -161,7 +161,7 @@ Note that this file format doesn't support plural forms. @opindex --width@r{, @code{msguniq} option} Set the output page width. Long strings in the output files will be split across multiple lines in order to ensure that each line's width -(= number of screen columns) is less or equal to the given @var{number}. +(= number of screen columns) is less than or equal to the given @var{number}. @item --no-wrap @opindex --no-wrap@r{, @code{msguniq} option} diff --git a/gettext-tools/doc/xgettext.texi b/gettext-tools/doc/xgettext.texi index 34794aa..b5a3e8a 100644 --- a/gettext-tools/doc/xgettext.texi +++ b/gettext-tools/doc/xgettext.texi @@ -506,7 +506,7 @@ Note that this file format doesn't support plural forms. @opindex --width@r{, @code{xgettext} option} Set the output page width. Long strings in the output files will be split across multiple lines in order to ensure that each line's width -(= number of screen columns) is less or equal to the given @var{number}. +(= number of screen columns) is less than or equal to the given @var{number}. @item --no-wrap @opindex --no-wrap@r{, @code{xgettext} option} -- 1.9.5.github.0 --------------070707040602000307020400-- From MAILER-DAEMON Fri Nov 27 08:32:20 2015 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1a2J8O-0001Nq-59 for mharc-bug-gettext@gnu.org; Fri, 27 Nov 2015 08:32:20 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46783) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a2Hni-0006Xx-3T for bug-gettext@gnu.org; Fri, 27 Nov 2015 07:06:54 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a2Hnh-00063A-09 for bug-gettext@gnu.org; Fri, 27 Nov 2015 07:06:54 -0500 Received: from mail-yk0-x234.google.com ([2607:f8b0:4002:c07::234]:32830) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a2Hng-000635-Oe for bug-gettext@gnu.org; Fri, 27 Nov 2015 07:06:52 -0500 Received: by ykdv3 with SMTP id v3so116118939ykd.0 for ; Fri, 27 Nov 2015 04:06:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=2rpIbk0uI+uZmCE/ImK/Mb1RYtqtE1zNLZ3SzfFg2vc=; b=C0wrHLvwRdssQ5C/HKS/lzGdgHX5RCdBvhGJczG03RibRpz1ix6rNe515NYYh8sqyM SUrYNIePPDahwbV4+LIgy28X2WWhRordDi5hECEy3QynSaDBzFPGsa+/gaJp1NTEw1Lj XY7QVE4IXHk4H0F3ifonr8NbtTW91cc0m7alBDxojqel0Wsos05eyIjBnYFw3wTkDXNg vkx3Fy5aijQiW1FVgWF4zYYN0tN4IlQI5XlhaOh+29El8Q/LwHcZ/coUkfFGXnOu1vJx gXOUY07gFDMhAVoVw/VtwDCWTy+iAoaHdjPcSni/Ky30teDUUAhAKPJ/xz0hNNIdNTVq ObOw== MIME-Version: 1.0 X-Received: by 10.129.24.211 with SMTP id 202mr45003152ywy.21.1448626012138; Fri, 27 Nov 2015 04:06:52 -0800 (PST) Received: by 10.13.232.193 with HTTP; Fri, 27 Nov 2015 04:06:52 -0800 (PST) Date: Fri, 27 Nov 2015 15:06:52 +0300 Message-ID: From: =?UTF-8?B?0JTQvNC40YLRgNC40Lkg0K/QutC+0LLQu9C10LI=?= To: bug-gettext@gnu.org Content-Type: multipart/alternative; boundary=001a1142851addb4cd05258486b8 X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:4002:c07::234 X-Mailman-Approved-At: Fri, 27 Nov 2015 08:32:18 -0500 Subject: [bug-gettext] gettext cache X-BeenThere: bug-gettext@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for GNU gettext List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2015 12:06:55 -0000 --001a1142851addb4cd05258486b8 Content-Type: text/plain; charset=UTF-8 Hi, I'm using gettext extension in my php project. When I create new .mo file with the new translations, they do not appear until a restart web server. As I understand, gettext store results in memory. This solution does not help: http://stackoverflow.com/questions/13625659/how-to-clear-phps-gettext-cache-without-restart-apache-nor-change-domain How I can clear cache without restart Apache? Regards, Dmitry Yakovlev --001a1142851addb4cd05258486b8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
    Hi,
    I'm using gettext extension in my php pro= ject.
    When I create new .mo file with the new translations, they = do not appear until a restart web server.
    As I understand, gettex= t store results in memory.
    This solution does not help:


    How I can= clear cache without restart Apache?

    Regards= ,
    Dmitry Yakovlev
    --001a1142851addb4cd05258486b8-- From MAILER-DAEMON Sun Nov 29 22:32:59 2015 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1a3FD1-0006CF-0E for mharc-bug-gettext@gnu.org; Sun, 29 Nov 2015 22:32:59 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53144) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a3FCz-0006C7-Hq for bug-gettext@gnu.org; Sun, 29 Nov 2015 22:32:58 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a3FCu-0003kK-Pp for bug-gettext@gnu.org; Sun, 29 Nov 2015 22:32:57 -0500 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:35964) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a3FCu-0003kG-N0; Sun, 29 Nov 2015 22:32:52 -0500 Received: from du-a.org ([219.94.251.20]:39711 helo=dhcp-217-92.nrt.redhat.com) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1a3FCu-0006Y8-8g; Sun, 29 Nov 2015 22:32:52 -0500 Message-ID: From: Daiki Ueno To: Phil Davis References: <564A0F94.6040706@inf.org> <56583583.2080302@inf.org> Date: Mon, 30 Nov 2015 12:32:45 +0900 In-Reply-To: <56583583.2080302@inf.org> (Phil Davis's message of "Fri, 27 Nov 2015 16:35:43 +0545") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2001:4830:134:3::e Cc: bug-gettext@gnu.org Subject: Re: [bug-gettext] gettext doc minor errors and typos X-BeenThere: bug-gettext@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for GNU gettext List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Nov 2015 03:32:58 -0000 Phil Davis writes: > I have attached a bunch of patches for various doc grammar and typos. Thanks, will look into the patch soon. > I couldn't see how to submit anything directly to the gettext.git repo > for review. The submission and review process is so easy for projects > that have repos hosted on Github - just fork/clone, edit away then > press the Pull Request button. > > Is there a similar way for mere mortals to submit change requests for > review to the repos in git.sv.gnu.org ? No, gettext uses a traditional email-based workflow, like many other free software projects, so you are doing it the right way. I personally don't think it is too much hurdle for contributing. More importantly, we might need a copyright assignment, if the patch contains legally significant changes: http://www.gnu.org/prep/maintain/maintain.html#Legally-Significant I will let you know if the paperwork is necessary. Regards, -- Daiki Ueno