Why doesn't the guideline specify character-set for source files?
In Boost Library Guidelines, there aren't any specified character-sets. (are there?) Since some names of authors written in source files include high-ASCII characters that are incompatible with some other character-sets, they are unreadable for users setting non-ASCII character-sets as default like me (Japanese), and also compilers would generate warnings about it. Therefore, I think the guideline should specify character-set or limit available characters to low-ASCII only for source files to standardize way to read and process them. (To limit to low-ASCII is better for me.) The similar/same topics had been discussed, see links below: [boost] MSVC doesn't like some high-ASCII characters on non-US systems http://lists.boost.org/Archives/boost/2006/03/102561.php [boost] [Boost-bugs] [ boost-Bugs-1461533 ] Non-basic-source-character-set characters conflict with MSVC http://lists.boost.org/Archives/boost/2006/03/102596.php But now it seems stopped. No one interested anymore? Shintaro Sakahara
on Thu Jul 19 2007, Shintaro Sakahara <sakahara-AT-dream.big.or.jp> wrote:
In Boost Library Guidelines, there aren't any specified character-sets. (are there?)
Since some names of authors written in source files include high-ASCII characters that are incompatible with some other character-sets, they are unreadable for users setting non-ASCII character-sets as default like me (Japanese), and also compilers would generate warnings about it.
Therefore, I think the guideline should specify character-set or limit available characters to low-ASCII only for source files to standardize way to read and process them. (To limit to low-ASCII is better for me.)
Sounds OK to me. Objections, anyone? -- Dave Abrahams Boost Consulting http://www.boost-consulting.com The Astoria Seminar ==> http://www.astoriaseminar.com
David Abrahams wrote:
Therefore, I think the guideline should specify character-set or limit available characters to low-ASCII only for source files to standardize way to read and process them. (To limit to low-ASCII is better for me.)
Sounds OK to me. Objections, anyone?
No I think it maybe should be added to the inspect program, to enforce this? John.
John Maddock wrote:
David Abrahams wrote:
Therefore, I think the guideline should specify character-set or limit available characters to low-ASCII only for source files to standardize way to read and process them. (To limit to low-ASCII is better for me.) Sounds OK to me. Objections, anyone?
No I think it maybe should be added to the inspect program, to enforce this?
Great idea, IMO. -- Eric Niebler Boost Consulting www.boost-consulting.com The Astoria Seminar ==> http://www.astoriaseminar.com
on Sat Jul 21 2007, Eric Niebler <eric-AT-boost-consulting.com> wrote:
John Maddock wrote:
David Abrahams wrote:
Therefore, I think the guideline should specify character-set or limit available characters to low-ASCII only for source files to standardize way to read and process them. (To limit to low-ASCII is better for me.) Sounds OK to me. Objections, anyone?
No I think it maybe should be added to the inspect program, to enforce this?
Great idea, IMO.
Yeah. Who's going to do the work of updating the docs and the inspect program? -- Dave Abrahams Boost Consulting http://www.boost-consulting.com The Astoria Seminar ==> http://www.astoriaseminar.com
In article <87wswtmjkl.fsf@grogan.peloton>, David Abrahams <dave@boost-consulting.com> wrote:
Yeah. Who's going to do the work of updating the docs and the inspect program?
I made a patch for the inspect program. Next is to post it to Trac? Shintaro Sakahara
participants (4)
-
David Abrahams -
Eric Niebler -
John Maddock -
Shintaro Sakahara