On May 17, 2014, at 7:57 PM, Jack Bates <6ny...@nottheoilrig.com> wrote:
> Good point,
> I'll look into whether those strings can be translated somehow.
I looked at this patch more today, and while I think it's a nice piece of work,
I question whether we should be splitting our API documentation
Good point,
I'll look into whether those strings can be translated somehow.
On 17/05/14 07:17 AM, Masakazu Kitajo wrote:
Extracting strings from sources would be nice, however, it makes me sad
because API reference pages will be untranslatable. But it's much better
than nothing or not maintained
Extracting strings from sources would be nice, however, it makes me sad
because API reference pages will be untranslatable. But it's much better
than nothing or not maintained. So, that's fine with me.
Personally, and as for API references, I don't build my own HTML docs
because I can't google/yah
On May 16, 2014, at 2:18 PM, James Peach wrote:
> Does anyone have any concerns about bringing in doxygen as a documentation
> build dependency?
As long as it’s optional, that seems fine. I doubt many (any?) people build the
docs, in fact, I still think we should stop building some of our doc
Does anyone have any concerns about bringing in doxygen as a documentation
build dependency?
On May 13, 2014, at 12:22 PM, jablko wrote:
> GitHub user jablko opened a pull request:
>
>https://github.com/apache/trafficserver/pull/85
>
>docs: Add Doxygen group commands to API sections
>
