Re: [STANDARDS] Splittling into chapters?

Hi!

> Very nice!  I think this split is the overall right strategy for sanity
> of future changes, etc.

I've found a wrinkle in this script though... If we have a number of
topics with the same name ("General" seems to be most popular) then when
we use big file, the topic Postfix Operators/General is labelled as
"general-13", but in file 10-expressions.md it's now "general-3", since
it that particular file there's only three links named "General". This
requires renaming all the anchors with repeated names. Which can be
done, but then this no longer can be merged back into the single file,
at least not easily. I'll fix the script and update the pull in a bit.
Since the anchor names are generated automatically and AFAIK there's no
way to override them, the only way to avoid it would be not using the
same names, but that's hard to do.

> One thing I will advise is that since we have links all over the place
> pointing to the current all-in-one spec php-spec-draft.md, we should
> either have a redirect from it to the table of contents
> (00-specification-for-php.md) or just copy the table of contents directly
> into that file. Because I think we should remove the big blob and have
> people directed to the table of contents, if we are going this route.

I think we can put the copy of 00-specification-for-php.md when ready.
-- 
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/