You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Imported from Trac ticket #16 reported by boonebgorges on 2010-08-04:
Posting as a separate ticket from feed content, which will be a whole other bag of worms
Getting comments is pretty easy; the question is how to present them in the UI and in the output.
UI: Maybe on the project organizer, items have a 'use comments' toggle. But does it have to be more fine grained than that? Maybe 'show comments' (in the ui) and then user can select which ones to display in the final version
TEI: Patrick, it'll be a fairly simple process to add comments to the queries you're using to get content out of WP
Outputs: How to display them? As footnotes? Endnotes? Sidebar? (Endnotes seem the most true to the blog format, and are probably the easiest to handle?)
The text was updated successfully, but these errors were encountered:
"Outputs: How to display them? As footnotes? Endnotes? Sidebar? (Endnotes seem the most true to the blog format, and are probably the easiest to handle?)"
Footnotes and endnotes have a very particular meaning in printed texts. By nature, they are meant to be keyed to particular locations in the inline text. They're also usually (though not always) generated by the author.
Margin comments are closer to blog comments, but even these are usually location specific. We could perhaps create something that looks for quotes and tries to key them back to the text, but I suspect that covers only a fraction of blog comments.
In other words, I think blog comments are blog comments. They come after the main text in a section called "Comments," and elaborate on or challenge the main text in various ways. I don't see any reason to map them onto a codex convention that is foreign to their original purpose.
I agree with that, Steve. My question was more about physical placement than about conceptual mapping. It's easy to pull the comments out of WordPress and pass them along to Patrick; from his point of view, in turn, it'll be easy to put them under whatever TEI heading he'd like. We just have to decide where they actually appear in the output.
Imported from Trac ticket #16 reported by boonebgorges on 2010-08-04:
Posting as a separate ticket from feed content, which will be a whole other bag of worms
Getting comments is pretty easy; the question is how to present them in the UI and in the output.
UI: Maybe on the project organizer, items have a 'use comments' toggle. But does it have to be more fine grained than that? Maybe 'show comments' (in the ui) and then user can select which ones to display in the final version
TEI: Patrick, it'll be a fairly simple process to add comments to the queries you're using to get content out of WP
Outputs: How to display them? As footnotes? Endnotes? Sidebar? (Endnotes seem the most true to the blog format, and are probably the easiest to handle?)
The text was updated successfully, but these errors were encountered: