Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Big Footnotes #167

Closed
wants to merge 2 commits into from
Closed

Big Footnotes #167

wants to merge 2 commits into from

Conversation

TheFox
Copy link

@TheFox TheFox commented Sep 9, 2014

No description provided.

@gettalong
Copy link
Owner

As per our e-mail conversation, this option doesn't make sense for kramdown itself because it is a HTML output style change. If another person doesn't like big footnotes, but small footnotes there would be a need for yet another option. Or if the footnote list should be a description list. Or ...

@gettalong gettalong closed this Sep 11, 2014
@TheFox
Copy link
Author

TheFox commented Sep 12, 2014

If another person doesn't like big footnotes, but small footnotes there would be a need for yet another option.

I defined the default value for footnote_big to false. So this feature is for persons who like big footnotes. They must explicitly change the default settings, like any other default settings if you doesn't like the default.

I have seen webpages with superscript footnotes, I have seen webpages with big footnotes. But I have never seen footnotes starting at number 2 or higher. They always start to count with number 1. Nobody starts their footnote at number 2. Or 3. Or 4. Or 97... So the footnote_nr option doesn't make sense too. This option can be used to specify the number that is used for the first footnote. describes this option. But why should anybody ever would let their numbers to start at 2 instead of 1?

@gettalong
Copy link
Owner

footnote_nr is an option, like header_offset, that modifies how the content is interpreted but doesn't specify a specific style.

header_offset may be used if a Markdown text should be equally usable on itself and when embedded inside another document. For example, you may want to use the Markdown text itself (without header_offset) for a blog post. But when this blog post is aggregated into a collection, e.g. post archive, you may want to use header_offset to demote the headers of a single post.

For similar situations footnote_nr is used, i.e. when a document should work standalone and together with other documents.

@TheFox
Copy link
Author

TheFox commented Sep 12, 2014

For similar situations footnote_nr is used, i.e. when a document should work standalone and together with other documents.

This covers up to 1:100 usage cases. Superscript/Big footnotes covers 1:10 usage cases.

@gettalong
Copy link
Owner

I can't comment on your numbers because I haven't done research in that regard.

However, as I have said in my first comment to this pull request, this option won't be included in kramdown. If you have another argument for including this option, please tell me! Things may change but your currently stated argument is not one I can accept for kramdown.

@opattison
Copy link

Not to re-open this issue, but you could use CSS to get the same effect you are going for here. For example, for my Kramdown footnotes, I want non-superscript as well as a different style altogether.

Example: https://github.com/opattison/olivermakes/blob/master/site.css#L283
In use: https://olivermak.es/2014/10/design-better-responsive-code/

The HTML output definitely has enough hooks to style with CSS, even without classes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants