To elaborate on my earlier post:
VHDL legal character sets:
VHDL-1987 CHARACTER type supports 7 bit ASCII.
VHDL-1993 and greater CHARACTER type supports an 8 bit ISO character
set.
( ISO 8859 Latin-1 8-bit character set, according to Ashenden's VHDL
Tutorial )
PowerShell Pipe Issue:
The complib.ps1 '-Encoding ASCII' pipe options currently used
suppport only 7 bit ASCII, hence the substitution problem.
Solution:
So the trick would be to get PowerShell to pipe ghdlfilter input and
output as 8 bit characters with neither character set translation, nor
writing out an initial BOM as in Ticket #35.
My present knowledge of PowerShell is insufficient to know how to do
this.
-Brian
Earlier today, I wrote:
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.
The substitution *only* occurs when running the PowerShell build script.
Running ghdlfilter from the original batch file preserves the copyright
symbol.
That's why I suspected the PowerShell pipe mechanism in my original
post comparing the .bat vs. .ps1 build results:
Difference noted, probably not worth much effort to fix:
- Copyright symbols in the 2008 ieee library source comments
have been replaced by "?" after preprocessing
( Some sort of PowerShell pipe character set issue? )
-Brian
_______________________________________________
Ghdl-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/ghdl-discuss
