Re: [brlcad-devel] locales fro BRL-CAD Devs

[Tom B. <tom...@gm...>]

On Fri, Sep 16, 2011 at 14:27, Christopher Sean Morrison <br...@ma...> wrote:
>
> On Sep 16, 2011, at 2:59 PM, Tom Browder wrote:
>
>>> The HACKING file establishes a minimum set of conventions and expectations.
...
> My inclination is to just document the expectations of the documentation IN the documentation section.  That is, document any requirements, expectations, character conversions, whatever in the doc/docbook/README file.

Okay.

> I was surprised by the pdf renderings of the STIX fonts at how symbol-lacking they seemed.
> Maybe something to do with my system.

But the font should be embedded in the pdfs.  Can you give me an
example of one or two missing?

>> Any suggestions for my xemacs configuration?  It seems to be
...
> Several variables in play.
...

Thanks.

>> I vote for the ascii and encoded symbols for all English docs--period.
>> Text for other languages is fair game for those using them.
>
> That sounds reasonable to me and what I'd expect, but only for the English docs.
> Certainly don't want to discourage foreign language translations.
> That said, if it's going to be an expectation (documented in doc/docbook/README) then there should
> also be a script that validates/detects non-ASCII so we can add it to the distcheck process.

How about a special pre-commit hook script?

Cheers!

-Tom