Michalis Kamburelis

Ah, sorry, I see you mentioned `@exclude` already:)

To be clear, I'm Ok with adding an option to ignore undocumented items. It's just a new feature:) And it should be carefully chosen what it omits -- e.g. procedure/function/property...

I agree. I want to remake HTML output one day to just use [Bootstrap](https://getbootstrap.com/). This will rearrange alll the HTML markup (and hopefully make our PasDoc CSS much smaller --...

Yes, for custom CSS it will be configurable whether you want to start with Bootstrap or just nothing. As for `pasdoc.css` being outside of code -- right now we place...

I also sometimes raise e.g. `EConvertError` when my routine uses StrToInt internally. So I would prefer more general mechanism, not hardcoding `Exception` :) A proposal: - First check is the...

I reproduced this with latest PasDoc code from GitHub, today. ( Yeah, the version line with `PasDoc 0.15.0 [2018-02-08...` is misleading, that's just version number and date hardcoded, corresponding to...

I would prefer a different solution, that allows to put in `@author` any content and format it following normal PasDoc rules. Right now: the `@author` tag has very special detection...

I would be fine with this compromise *for now* :) I mean, in `TGenericHTMLDocGenerator.WriteAuthors`, when you use `ExtractWebAddress`, if it detects `(Trim(S1) '') and (Trim(S2) = '')` then it can...

I tested PasDoc with modified 'author' tag, to have `toRecursiveTags, toAllowOtherTagsInsideByDefault, toAllowNormalTextInside`: ```pascal TTag.Create(TagManager, 'author', nil, {$IFDEF FPC}@{$ENDIF} StoreAuthorTag, [toParameterRequired, toRecursiveTags, toAllowOtherTagsInsideByDefault, toAllowNormalTextInside]); ``` It also needs fix in the...

My general desire here is both make `@author` more powerful, but also make it simpler to implement and consistent with other tags (the consistency is good both for users and...