public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: starner@okstate.edu
To: gcc-gnats@gcc.gnu.org
Subject: ada/6726: -gnaty miscounts characters in UTF-8 source text
Date: Sun, 19 May 2002 15:06:00 -0000	[thread overview]
Message-ID: <20020519220228.14655.qmail@sources.redhat.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]


>Number:         6726
>Category:       ada
>Synopsis:       -gnaty miscounts characters in UTF-8 source text
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Sun May 19 15:06:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     starner@okstate.edu
>Release:        gcc-3.1
>Organization:
>Environment:
Debian woody; ix86-linux
>Description:
-gnaty only permits 80 characters per line. However, if those characters are encoded in UTF-8, they are miscounted, and shorter lines are rejected. The Cherokee_String line in the attached file is 71 characters long, but 99 bytes long, and is rejected.
>How-To-Repeat:
Run gnatmake -gnaty test_strings.ads. It will return a "(style) This line is too long." error, when in fact this line is not too long.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/plain; name="test_strings.ads"
Content-Disposition: inline; filename="test_strings.ads"

package Test_Strings is

   Cherokee_String : constant Wide_String := "ᎠᏆᏖᏁᏙᎽ ᎠᎽᏍᏉᏟ ᏦᏰᎾ       ";

end Test_Strings;


             reply	other threads:[~2002-05-19 22:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-19 15:06 starner [this message]
2002-05-19 15:16 starner
2002-12-14 13:11 bosch
2002-12-14 19:26 starner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020519220228.14655.qmail@sources.redhat.com \
    --to=starner@okstate.edu \
    --cc=gcc-gnats@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).