--- Comment #20 from goeran at uddeborg dot se 2010-01-11 21:02 ---
(In reply to comment #19)
> Yes please.
I've filed bug 42693 about that.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36161
--- Comment #19 from burnus at gcc dot gnu dot org 2010-01-11 20:21 ---
(In reply to comment #1)
> One detail I happened to see: The messages defined in gfc_arith_error doesn't
> get any gcc-internal-format marker, though they do contain %L. Do you want a
> separate bugzilla about that?
--- Comment #18 from goeran at uddeborg dot se 2010-01-11 17:27 ---
I did try it out as you suggested, and it seems to work just fine.
(I.e. messages from fortran/arith.c were said to come from fortraarith.c in the
pot file. But I didn't bother to investigate that, it wasn't what I was
--- Comment #17 from burnus at gcc dot gnu dot org 2010-01-04 21:13 ---
FIXED. Thanks Göran for the suggestion! If you want to try, I can send you the
gcc.pot file of the current 4.5 trunk (or do "cd $GCC_build_dir/gcc; make
gcc.pot" to create ./po/gcc.pot yourself.)
See also http://gcc
--- Comment #16 from burnus at gcc dot gnu dot org 2010-01-04 21:01 ---
Subject: Bug 36161
Author: burnus
Date: Mon Jan 4 21:01:10 2010
New Revision: 155632
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=155632
Log:
2010-01-04 Tobias Burnus
PR fortran/36161
--- Comment #15 from burnus at gcc dot gnu dot org 2010-01-04 07:45 ---
I believe the patch at
http://gcc.gnu.org/ml/fortran/2010-01/msg00023.html
should be sufficient.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36161
--- Comment #14 from dfranke at gcc dot gnu dot org 2009-12-19 11:38
---
(In reply to comment #7)
> Support for this type of format has now been added to xgettext. The support
> will be contained in gettext 0.18.
I got as far as recreating the .pot for testing. Tried to compile the upd
--- Comment #13 from dfranke at gcc dot gnu dot org 2009-12-18 18:27
---
Tobias, thanks for your description. I'm still a bit hazy on the details, but I
changed my tree according to what I picked up. Question is, how do I verify
that the issue described in the initial report is fixed?
--- Comment #12 from burnus at gcc dot gnu dot org 2009-12-18 09:56 ---
> With the upcoming release of 4.5, I think it would be nice to fix/improve the
> translation related bugs now, i.e. this, PR38573 and PR40489.
>
> As I have no idea how to reproduce/check/whatever this kind of PR,
--- Comment #11 from dfranke at gcc dot gnu dot org 2009-12-17 23:07
---
[Adding Paul as CC]
(In reply to comment #10)
> Would you be so kind as to follow this. It's been unconfirmed for 18 months.
> Is it a bug or not and will we or won't we fix it?
>
> I vote for a WONTFIX to be h
--- Comment #10 from pault at gcc dot gnu dot org 2009-12-17 20:54 ---
(In reply to comment #9)
> With the upcoming release of 4.5, I think it would be nice to fix/improve the
> translation related bugs now, i.e. this, PR38573 and PR40489.
>
> As I have no idea how to reproduce/check/wh
--- Comment #9 from dfranke at gcc dot gnu dot org 2009-12-07 18:40 ---
With the upcoming release of 4.5, I think it would be nice to fix/improve the
translation related bugs now, i.e. this, PR38573 and PR40489.
As I have no idea how to reproduce/check/whatever this kind of PR, could
so
--- Comment #8 from joseph at codesourcery dot com 2009-03-29 16:59 ---
Subject: Re: gfc_error formats are not marked
gcc-internal-format in po file
On Sun, 29 Mar 2009, bruno at clisp dot org wrote:
> The xgettext options that need to be passed to "xgettext
> --language=GCC-source"
--- Comment #7 from bruno at clisp dot org 2009-03-29 16:55 ---
(In reply to comment #4)
> The Fortran front-end diagnostic strings have a specific format, that is an
> extension of the C printf format. It is not the same as the
> gcc-internal-format. Thus, if you want it to be supported
--- Comment #6 from goeran at uddeborg dot se 2009-03-29 16:53 ---
It didn't take long for this to be added to xgettext. It's already in the
development version (see https://savannah.gnu.org/bugs/?26040#comment1 for
details).
So then maybe I can reopen this, to have the new functionali
--- Comment #5 from goeran at uddeborg dot se 2009-03-28 18:27 ---
I see. I've sent an enhancement suggestion to the gettext project.
https://savannah.gnu.org/bugs/index.php?26040
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36161
--- Comment #4 from fxcoudert at gcc dot gnu dot org 2009-03-28 16:39
---
The Fortran front-end diagnostic strings have a specific format, that is an
extension of the C printf format. It is not the same as the
gcc-internal-format. Thus, if you want it to be supported, it first needs to
--- Comment #3 from dfranke at gcc dot gnu dot org 2009-01-03 23:58 ---
No idea about translation, but PR38573 is surely related.
--
dfranke at gcc dot gnu dot org changed:
What|Removed |Added
---
--- Comment #2 from goeran at uddeborg dot se 2008-05-19 20:15 ---
I'm not saying they should be marked "c-format", but "gcc-internal-format".
That special marker is known by msgfmt for the "printf inspired" error messages
in GCC.
Tobias Burnus has pointed out in a mail, however, that
--- Comment #1 from kargl at gcc dot gnu dot org 2008-05-19 19:48 ---
I don't understand this PR. gfc_error's format strings may look
like C's printf format strings, but these are different. These
format strings are parsed and used by gfortran, and are not passed
directly to libc. So,
20 matches
Mail list logo
