User:Kim/Prototyping 2nd year/GitPub Cite - Revision history

Kim: /* fixed */

2026-02-06T09:26:45Z

fixed

← Older revision		Revision as of 11:26, 6 February 2026
Line 117:		Line 117:

	== fixed ==		== fixed ==
	[[File:What is literature nelson.png\|thumb\|ted nelson in literary machines about literature 'as a system of interconnected writings'. in print we dont see these links and other writings...]]~~issue: reference rendering~~		[[File:What is literature nelson.png\|thumb\|ted nelson in literary machines about literature 'as a system of interconnected writings'. in print we dont see these links and other writings...]]

	should do: output only one global reference list, instead of one per file		=== issue: reference rendering ===
			'''should do:''' output only one global reference list, instead of one per file

	why did it break?: in gitpub v 0.4 ++ the [[User:Kim/Prototyping 2nd year/GitPub#reference rendering\|reference rendering]] works with a combination of supress bibliography: true (for individual files) and a separate reference.md file that renders all citations using nocite: '@*'. In cite-meta this broke when I added a custom csl file, which did not correspond / listen to supress bibliography true... (and lacking documentation did not help)		'''why did it break?:''' in gitpub v 0.4 ++ the [[User:Kim/Prototyping 2nd year/GitPub#reference rendering\|reference rendering]] works with a combination of supress bibliography: true (for individual files) and a separate reference.md file that renders all citations using nocite: '@*'. In cite-meta this broke when I added a custom csl file, which did not correspond / listen to supress bibliography true... (and lacking documentation did not help)

	fix: (not the most elegant solution but works)		'''fix:''' (not the most elegant solution but works)

	# references.md file is provided with slightly different metadata: <code>"---\nreferences:" + file_commits + "\nbibliography: ./references.bib\ncsl: harvard-meta-bib.csl\nnocite: '@*'\n---"</code>		# references.md file is provided with slightly different metadata: <code>"---\nreferences:" + file_commits + "\nbibliography: ./references.bib\ncsl: harvard-meta-bib.csl\nnocite: '@*'\n---"</code>

Kim: /* fixed */

2026-02-06T09:25:54Z

fixed

← Older revision		Revision as of 11:25, 6 February 2026
Line 125:		Line 125:
	fix: (not the most elegant solution but works)		fix: (not the most elegant solution but works)

	# references.md file is provided with slightly different metadata: "---\nreferences:" + file_commits + "\nbibliography: ./references.bib\ncsl: harvard-meta-bib.csl\nnocite: '@*'\n---"		# references.md file is provided with slightly different metadata: <code>"---\nreferences:" + file_commits + "\nbibliography: ./references.bib\ncsl: harvard-meta-bib.csl\nnocite: '@*'\n---"</code>
			# it has a specific cls file that conatains <code><bibliography></code>, which is removed from the standard csl file to omit bibliography output
			# adding the option <code>nnocite: '@*'</code> includes all references contained in the linked .bib file
			# removed self referential .yaml file (references.yaml) from bibliography list to avoid confusion

Kim: /* To Do */

2026-02-06T09:22:28Z

To Do

@@ Line 115: / Line 115: @@
 ** a regular citation contains descriptive metadata (such as author, year) of an external resource/ document that it points to
 ** a gitpub citation contains technical and structural metadata of itself. it does not point to an external file but to itself.
 [[File:What is literature nelson.png|thumb|ted nelson in literary machines about literature 'as a system of interconnected writings'. in print we dont see these links and other writings...]]

Kim: /* To Do */

2026-02-06T09:14:57Z

To Do

← Older revision		Revision as of 11:14, 6 February 2026
Line 105:		Line 105:
	# add linebreaks after text elements. (specification states [https://docs.citationstyles.org/en/stable/specification.html#formatting formatting] options for tags, as well as [https://docs.citationstyles.org/en/stable/specification.html#group affixes or display] options for groups)		# add linebreaks after text elements. (specification states [https://docs.citationstyles.org/en/stable/specification.html#formatting formatting] options for tags, as well as [https://docs.citationstyles.org/en/stable/specification.html#group affixes or display] options for groups)
	# add a default stylesheet that makes more sense than the current one (especially metacontainer)		# add a default stylesheet that makes more sense than the current one (especially metacontainer)
	# reference rendering is broken (but works in gitpub v4) ''> exclude references.md from loops ?''		# <s>reference rendering is broken (but works in gitpub v4) ''> exclude references.md from loops ?''</s>

	metadata citation workflow: rn, in order to cite a git commit by its short has, the user has to do <code>git log --pretty=format:%h</code> or check the remote repository on a platform		metadata citation workflow: rn, in order to cite a git commit by its short has, the user has to do <code>git log --pretty=format:%h</code> or check the remote repository on a platform

Kim: /* to think about */

2026-02-04T14:18:55Z

to think about

← Older revision		Revision as of 16:18, 4 February 2026
Line 109:		Line 109:
	metadata citation workflow: rn, in order to cite a git commit by its short has, the user has to do <code>git log --pretty=format:%h</code> or check the remote repository on a platform		metadata citation workflow: rn, in order to cite a git commit by its short has, the user has to do <code>git log --pretty=format:%h</code> or check the remote repository on a platform

	=== to think about ===		=== think about ===
	[[File:Windowing hypertext nelson.png\|thumb\|windowing hypertext in ted nelsons literary machines (1/16) via https://archive.org/details/literarymachines00nels]]		[[File:Windowing hypertext nelson.png\|thumb\|windowing hypertext in ted nelsons literary machines (1/16) via https://archive.org/details/literarymachines00nels]]
	* styling of the inline citation (is it breaking the text or is it inline? is it distinguishable from the 'regular' citations?)		* styling of the inline citation (is it breaking the text or is it inline? is it distinguishable from the 'regular' citations?)

Kim: /* to think about */

2026-02-04T13:58:34Z

to think about

← Older revision		Revision as of 15:58, 4 February 2026
Line 115:		Line 115:
	** a regular citation contains descriptive metadata (such as author, year) of an external resource/ document that it points to		** a regular citation contains descriptive metadata (such as author, year) of an external resource/ document that it points to
	** a gitpub citation contains technical and structural metadata of itself. it does not point to an external file but to itself.		** a gitpub citation contains technical and structural metadata of itself. it does not point to an external file but to itself.
			[[File:What is literature nelson.png\|thumb\|ted nelson in literary machines about literature 'as a system of interconnected writings'. in print we dont see these links and other writings...]]

Kim: /* to think about */

2026-02-04T13:53:26Z

to think about

← Older revision		Revision as of 15:53, 4 February 2026
Line 110:		Line 110:

	=== to think about ===		=== to think about ===
			[[File:Windowing hypertext nelson.png\|thumb\|windowing hypertext in ted nelsons literary machines (1/16) via https://archive.org/details/literarymachines00nels]]
	* styling of the inline citation (is it breaking the text or is it inline? is it distinguishable from the 'regular' citations?)		* styling of the inline citation (is it breaking the text or is it inline? is it distinguishable from the 'regular' citations?)
	* what is its relation to the regular citations?		* what is its relation to the regular citations?
	** a regular citation contains descriptive metadata (such as author, year) of an external resource/ document that it points to		** a regular citation contains descriptive metadata (such as author, year) of an external resource/ document that it points to
	** a gitpub citation contains technical and structural metadata of itself. it does not point to an external file but to itself.		** a gitpub citation contains technical and structural metadata of itself. it does not point to an external file but to itself.
	~~[[File:Windowing hypertext nelson.png\|thumb\|windowing hypertext in ted nelsons literary machines (1/16) via https://archive.org/details/literarymachines00nels]]~~

Kim: /* to think about */

2026-02-04T13:52:57Z

to think about

← Older revision		Revision as of 15:52, 4 February 2026
Line 115:		Line 115:
	** a regular citation contains descriptive metadata (such as author, year) of an external resource/ document that it points to		** a regular citation contains descriptive metadata (such as author, year) of an external resource/ document that it points to
	** a gitpub citation contains technical and structural metadata of itself. it does not point to an external file but to itself.		** a gitpub citation contains technical and structural metadata of itself. it does not point to an external file but to itself.
			[[File:Windowing hypertext nelson.png\|thumb\|windowing hypertext in ted nelsons literary machines (1/16) via https://archive.org/details/literarymachines00nels]]

Kim: /* To Do */

2026-02-04T13:45:14Z

To Do

← Older revision		Revision as of 15:45, 4 February 2026
Line 108:		Line 108:

	metadata citation workflow: rn, in order to cite a git commit by its short has, the user has to do <code>git log --pretty=format:%h</code> or check the remote repository on a platform		metadata citation workflow: rn, in order to cite a git commit by its short has, the user has to do <code>git log --pretty=format:%h</code> or check the remote repository on a platform

			=== to think about ===

			* styling of the inline citation (is it breaking the text or is it inline? is it distinguishable from the 'regular' citations?)
			* what is its relation to the regular citations?
			** a regular citation contains descriptive metadata (such as author, year) of an external resource/ document that it points to
			** a gitpub citation contains technical and structural metadata of itself. it does not point to an external file but to itself.

Kim: /* To Do */

2026-02-02T13:45:59Z

To Do

← Older revision		Revision as of 15:45, 2 February 2026
Line 105:		Line 105:
	# add linebreaks after text elements. (specification states [https://docs.citationstyles.org/en/stable/specification.html#formatting formatting] options for tags, as well as [https://docs.citationstyles.org/en/stable/specification.html#group affixes or display] options for groups)		# add linebreaks after text elements. (specification states [https://docs.citationstyles.org/en/stable/specification.html#formatting formatting] options for tags, as well as [https://docs.citationstyles.org/en/stable/specification.html#group affixes or display] options for groups)
	# add a default stylesheet that makes more sense than the current one (especially metacontainer)		# add a default stylesheet that makes more sense than the current one (especially metacontainer)
	# reference rendering is broken (~~might be the same for~~ gitpub v4) ''> exclude references.md from loops ?''		# reference rendering is broken (but works in gitpub v4) ''> exclude references.md from loops ?''

	metadata citation workflow: rn, in order to cite a git commit by its short has, the user has to do <code>git log --pretty=format:%h</code> or check the remote repository on a platform		metadata citation workflow: rn, in order to cite a git commit by its short has, the user has to do <code>git log --pretty=format:%h</code> or check the remote repository on a platform