Hello Tristan, > Is is due to ghdlfilter ? In that case, we could either set the encoding (I > have > to look at the GNAT doc to understand that issue), or we can modify > ghdlfilter to avoid that issue.
No, it's not a ghdlfilter issue. It's the source file itself. I assume it's
downloaded
from ieee. So the question is, which encoding did they use and are we allowed
to fix the encoding locally?
Solutions:
a) Rewrite © to (c) like the 'old' files.
b) Let the IEEE fix there sources :) -> I suggest ASCII or proper UTF-8
c) PowerShell could re-encode the file
d) ghdlfilter could re-encode the file
Regards
Patrick
> -----Original Message-----
> From: Ghdl-discuss [mailto:[email protected]] On Behalf Of
> Tristan Gingold
> Sent: Monday, February 09, 2015 6:51 AM
> To: [email protected]
> Subject: Re: [Ghdl-discuss] New build scripts for GHDL on Windows
>
> On 09/02/15 02:03, Lehmann, Patrick wrote:
> > Hello Brian,
>
> [...]
>
> > ---------------------------------------
> > (3) Copyright symbols in the 2008 ieee library source comments have
> > been replaced by "?" after preprocessing
> >
> > I used the Get-HexDump CmdLet to analyze the file. The copyright
> > symbol is not in range of ASCII encoding (© = 169; it's translated to '?' =
> > 63)
> Encoding © as 0xA9 (decimal 169) is used by: ANSI, ISO-8859-1 (Latin1), ...
> > It's not UTF-8 encoded, because there is no prefix byte (=> 0xC2)
> >
> > Where can I find the correct encodings?
>
> Is is due to ghdlfilter ? In that case, we could either set the encoding (I
> have
> to look at the GNAT doc to understand that issue), or we can modify
> ghdlfilter to avoid that issue.
>
> Tristan.
>
>
> _______________________________________________
> Ghdl-discuss mailing list
> [email protected]
> https://mail.gna.org/listinfo/ghdl-discuss
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Ghdl-discuss mailing list [email protected] https://mail.gna.org/listinfo/ghdl-discuss
