User:Robin - Revision history

Robin at 20:18, 19 April 2026

2026-04-19T20:18:43Z

← Older revision		Revision as of 22:18, 19 April 2026
Line 89:		Line 89:
	==== .otf file format - aesthetics and technology of type ====		==== .otf file format - aesthetics and technology of type ====
	[[.otf file format\|[ -> .otf file format ]]]		[[.otf file format\|[ -> .otf file format ]]]

	I could call my user page 'confessions of a type nerd' at this point... I spend the last weekend reading about the technicalities of the .otf file format and font rendering engines. ( It was an amazing weekend ). I'm also starting a lil research website on this for myself. It will probably pop up in sergio at some point.		I could call my user page 'confessions of a type nerd' at this point... I spend the last weekend reading about the technicalities of the .otf file format and font rendering engines. ( It was an amazing weekend ). I'm also starting a lil research website on this for myself. It will probably pop up in sergio at some point.
	[[File:M I R A G E 03.jpg\|thumb\|217x217px]]But, what was this rabbit hole about? The '''.otf file format''', how it includes '''not only the visual of a font, but its behavior too'''. This is makes '''latin-like, 'default' scripts''' look better. But for '''<nowiki/>'complex scripts'<nowiki/>''' ( the ' ' are official terminology ), those rules are '''necessary to render the text readable to a human'''. because in 'default' scripts, '''unicode code-points''' include every from of every letter that it includes, and '''unicode's orthography documentation''' on the script corresponds to the default way of rendering readable text. for 'complex scripts', '''the font-file includes clusters of tables''', organized in two main categories: '''<nowiki/>'substitution'<nowiki/>''' and '''<nowiki/>'positioning'''' tables. so these include tables that render engine API's interpret, in order change the behavior of the script, from the default form and position of a character, to the one necessary to display correctly.		[[File:M I R A G E 03.jpg\|thumb\|217x217px]]But, what was this rabbit hole about? The '''.otf file format''', how it includes '''not only the visual of a font, but its behavior too'''. This is makes '''latin-like, 'default' scripts''' look better. But for '''<nowiki/>'complex scripts'<nowiki/>''' ( the ' ' are official terminology ), those rules are '''necessary to render the text readable to a human'''. because in 'default' scripts, '''unicode code-points''' include every from of every letter that it includes, and '''unicode's orthography documentation''' on the script corresponds to the default way of rendering readable text. for 'complex scripts', '''the font-file includes clusters of tables''', organized in two main categories: '''<nowiki/>'substitution'<nowiki/>''' and '''<nowiki/>'positioning'''' tables. so these include tables that render engine API's interpret, in order change the behavior of the script, from the default form and position of a character, to the one necessary to display correctly.

	I thought I was being original with my butler reference in relation to type. but the terminology around .otf technology reflect that relation so well.. I thought I was using it as a metaphor. turns out it is actually how it works.		I thought I was being original with my butler reference in relation to type. but the terminology around .otf technology reflect that relation so well.. I thought I was using it as a metaphor. turns out it is actually how it works.

Robin at 20:18, 19 April 2026

2026-04-19T20:18:34Z

← Older revision		Revision as of 22:18, 19 April 2026
Line 26:		Line 26:
	=== Zine idea for Extraterrestrial Publishing Fair ===		=== Zine idea for Extraterrestrial Publishing Fair ===
	[[Category:Aesthetics]]		[[Category:Aesthetics]]
	A few times throughout the trimester, I was reminded of '''Butler's Essay 'Imitation and Gender Insubordination'~~<nowiki/>~~'''. Where they use the figure-of-speech of a '''<nowiki/>'copy without an original'''' to talk about their unease with the category of lesbian as something that should supposedly be equal to the 'I' it encloses. They proceed to deconstruct the binary notion of gender identity / sexuality, where '''the 'gay' category is supposedly understood as a derivative of a 'straight' original'''. I have to confess I could relate a lot to their explanation of their unease in this understanding. I think I unknowingly held this notion for a long time. Coming to terms with my own gender-expression has involved coming to terms with the idea that I'm not trying, 'pretending', to be a gender that I am not, but I lacked the words to give structure to the thought.		A few times throughout the trimester, I was reminded of '''Butler's Essay 'Imitation and Gender Insubordination''''. Where they use the figure-of-speech of a '''<nowiki/>'copy without an original'''' to talk about their unease with the category of lesbian as something that should supposedly be equal to the 'I' it encloses. They proceed to deconstruct the binary notion of gender identity / sexuality, where '''the 'gay' category is supposedly understood as a derivative of a 'straight' original'''. I have to confess I could relate a lot to their explanation of their unease in this understanding. I think I unknowingly held this notion for a long time. Coming to terms with my own gender-expression has involved coming to terms with the idea that I'm not trying, 'pretending', to be a gender that I am not, but I lacked the words to give structure to the thought.

	This essay has helped me a lot in that regard. Especially when they talk about '''drag, not as imitating, performing, a pre-existing gender, but rather, as exposing the fact that all gender is a performance'''. One that only gains the understanding of a fixed identity through it's repetition.		This essay has helped me a lot in that regard. Especially when they talk about '''drag, not as imitating, performing, a pre-existing gender, but rather, as exposing the fact that all gender is a performance'''. One that only gains the understanding of a fixed identity through it's repetition.
Line 88:		Line 88:

	==== .otf file format - aesthetics and technology of type ====		==== .otf file format - aesthetics and technology of type ====
	I could call my user page 'confessions of a type nerd' at this point... I spend the last weekend reading about the technicalities of the .otf file format and font rendering engines. ( It was an amazing weekend ). I'm also starting a lil research website on this for myself. It will probably pop up in sergio at some point.[[File:M I R A G E 03.jpg\|thumb\|217x217px]]But, what was this rabbit hole about? ~~To better locate~~ how ~~digital language goes from calculated to~~ visual. ~~And to what extend a western~~-~~dominant perception of language hierarchy informs that system. So far we got already~~. But in the ~~.otf file~~, ~~some really interesting things~~ are ~~happening~~. ~~The~~ '~~visual~~' ~~layer~~ of ~~language representation~~, ~~consists~~ of ~~its own entire world~~ of ~~categorization~~ and ~~standardization ( not~~ the ~~surprising part ). How those categories are divided~~ and ~~how they are rendered~~, ~~is! And definitions here are important!~~		[[.otf file format\|[ -> .otf file format ]]]
			I could call my user page 'confessions of a type nerd' at this point... I spend the last weekend reading about the technicalities of the .otf file format and font rendering engines. ( It was an amazing weekend ). I'm also starting a lil research website on this for myself. It will probably pop up in sergio at some point.
			[[File:M I R A G E 03.jpg\|thumb\|217x217px]]But, what was this rabbit hole about? The '''.otf file format''', how it includes '''not only the visual of a font, but its behavior too'''. This is makes '''latin-like, 'default' scripts''' look better. But for '''<nowiki/>'complex scripts'<nowiki/>''' ( the ' ' are official terminology ), those rules are '''necessary to render the text readable to a human'''. because in 'default' scripts, '''unicode code-points''' include every from of every letter that it includes, and '''unicode's orthography documentation''' on the script corresponds to the default way of rendering readable text. for 'complex scripts', '''the font-file includes clusters of tables''', organized in two main categories: '''<nowiki/>'substitution'<nowiki/>''' and '''<nowiki/>'positioning'''' tables. so these include tables that render engine API's interpret, in order change the behavior of the script, from the default form and position of a character, to the one necessary to display correctly.

	.otf is the format that makes rendering 'complex scripts' possible. because, all latin-like scripts 'standard scripts' are rendered readable on any screen. but 'complex scripts' ( those are the official terminology ), can't be displayed as readable text just by referencing the drawings of the corresponding unicode points. they need to be rendered first. and the encoded behavior also exists in the font-file. the .otf format allows for adding those additional rules of behavior. they can be added as look-up's. and they reference tables with predetermined rules for properly rendering a specific script. those tables are divided into two main clusters, those for 'substitution' and those for 'positioning'.		I thought I was being original with my butler reference in relation to type. but the terminology around .otf technology reflect that relation so well.. I thought I was using it as a metaphor. turns out it is actually how it works.

	I thought I was being original with my butler reference in relation to type. the terminology around .otf technology reflect that relation so well.. I thought I was using it as a metaphor. turns out ~~its~~ actually how it works.

	( and yes, SIL is still around ) with their own rendering engine, since microsoft's only works on microsoft OS, Linux uses its own version, built on Graphite, the open-source equivalent, developed by SIL. So, rendering text readable on any device ( mac has its own version too ofc ) in a script that is not latin-like, relies either on Microsoft technology, or SIL's. And, with that, in order to reference the right API's for text rendering, any font-file will be tagged with a script and a language. The data for language names ( and how they are classified ), is the ISO standard, overseen by SIL. Those API's are build to accomodate a writing system's orthography. This one is also interesting. Because those rules are also adopted from Unicode, and scripts are classified by their functioning, to which every language can be adjusted. But orthographies, for previously undocumented languages are proposed to unicode and even developed from scratch by SIL as well. ( as in, on their website they write that they developed an orthography, and an entire writing system, for languages that did not have any or an 'insufficient' written form at all ). So they make it, they propose it to unicode, they render it on every Linux system. and playstation.

Robin: /* MIRAGE Installation at Extraterrestrial Publishing Fair */

2026-04-19T20:01:56Z

MIRAGE Installation at Extraterrestrial Publishing Fair

← Older revision		Revision as of 22:01, 19 April 2026
Line 79:		Line 79:

	=== MIRAGE Installation at Extraterrestrial Publishing Fair ===		=== MIRAGE Installation at Extraterrestrial Publishing Fair ===
	~~[[File:M I R A G E 03.jpg\|thumb\|217x217px]]~~[[File:M I R A G E 01.jpg\|thumb\|217x217px]][[File:M I R A G E installation.mp4\|center\|M I R A G E installation an Extraterrestrial Publishing Fair\|frameless]]		[[File:M I R A G E 01.jpg\|thumb\|217x217px]][[File:M I R A G E installation.mp4\|center\|M I R A G E installation an Extraterrestrial Publishing Fair\|frameless]]
	[[File:M I R A G E 02.jpg\|thumb\|217x217px]]		[[File:M I R A G E 02.jpg\|thumb\|217x217px]]

Line 86:		Line 86:

	Last februari was my first time at Grauzone Festival. A festival centered around darker style electronic music. It was the first time I felt I deeply connected to a music genre. And themes in this music reminded me a lot of what we do at XPUB. So I wanted to add a little reflection on it here. Let's see where it leads...		Last februari was my first time at Grauzone Festival. A festival centered around darker style electronic music. It was the first time I felt I deeply connected to a music genre. And themes in this music reminded me a lot of what we do at XPUB. So I wanted to add a little reflection on it here. Let's see where it leads...

			==== .otf file format - aesthetics and technology of type ====
			I could call my user page 'confessions of a type nerd' at this point... I spend the last weekend reading about the technicalities of the .otf file format and font rendering engines. ( It was an amazing weekend ). I'm also starting a lil research website on this for myself. It will probably pop up in sergio at some point.[[File:M I R A G E 03.jpg\|thumb\|217x217px]]But, what was this rabbit hole about? To better locate how digital language goes from calculated to visual. And to what extend a western-dominant perception of language hierarchy informs that system. So far we got already. But in the .otf file, some really interesting things are happening. The 'visual' layer of language representation, consists of its own entire world of categorization and standardization ( not the surprising part ). How those categories are divided and how they are rendered, is! And definitions here are important!

			.otf is the format that makes rendering 'complex scripts' possible. because, all latin-like scripts 'standard scripts' are rendered readable on any screen. but 'complex scripts' ( those are the official terminology ), can't be displayed as readable text just by referencing the drawings of the corresponding unicode points. they need to be rendered first. and the encoded behavior also exists in the font-file. the .otf format allows for adding those additional rules of behavior. they can be added as look-up's. and they reference tables with predetermined rules for properly rendering a specific script. those tables are divided into two main clusters, those for 'substitution' and those for 'positioning'.

			I thought I was being original with my butler reference in relation to type. the terminology around .otf technology reflect that relation so well.. I thought I was using it as a metaphor. turns out its actually how it works.

			( and yes, SIL is still around ) with their own rendering engine, since microsoft's only works on microsoft OS, Linux uses its own version, built on Graphite, the open-source equivalent, developed by SIL. So, rendering text readable on any device ( mac has its own version too ofc ) in a script that is not latin-like, relies either on Microsoft technology, or SIL's. And, with that, in order to reference the right API's for text rendering, any font-file will be tagged with a script and a language. The data for language names ( and how they are classified ), is the ISO standard, overseen by SIL. Those API's are build to accomodate a writing system's orthography. This one is also interesting. Because those rules are also adopted from Unicode, and scripts are classified by their functioning, to which every language can be adjusted. But orthographies, for previously undocumented languages are proposed to unicode and even developed from scratch by SIL as well. ( as in, on their website they write that they developed an orthography, and an entire writing system, for languages that did not have any or an 'insufficient' written form at all ). So they make it, they propose it to unicode, they render it on every Linux system. and playstation.

Robin: /* Writing Machines Ensemble */

2026-04-07T12:12:12Z

Writing Machines Ensemble

← Older revision		Revision as of 14:12, 7 April 2026
Line 6:		Line 6:
	=== '''Writing Machines Ensemble''' ===		=== '''Writing Machines Ensemble''' ===
	[[Projects SI 28/Writing Machine Ensemble\|[ -> Projects SI 28/Writing Machine Ensemble]] ]		[[Projects SI 28/Writing Machine Ensemble\|[ -> Projects SI 28/Writing Machine Ensemble]] ]

			CUPS on localhost:631, for direct printing through terminal

	With Daan and Ema, we developed our performace for SI28's event. Writing Machines Ensemble became an experimental orchestral performance using printers and writing machines from the XPUB studio!		With Daan and Ema, we developed our performace for SI28's event. Writing Machines Ensemble became an experimental orchestral performance using printers and writing machines from the XPUB studio!

Robin at 12:14, 2 April 2026

2026-04-02T12:14:58Z

← Older revision		Revision as of 14:14, 2 April 2026
Line 79:		Line 79:
	[[File:M I R A G E 03.jpg\|thumb\|217x217px]][[File:M I R A G E 01.jpg\|thumb\|217x217px]][[File:M I R A G E installation.mp4\|center\|M I R A G E installation an Extraterrestrial Publishing Fair\|frameless]]		[[File:M I R A G E 03.jpg\|thumb\|217x217px]][[File:M I R A G E 01.jpg\|thumb\|217x217px]][[File:M I R A G E installation.mp4\|center\|M I R A G E installation an Extraterrestrial Publishing Fair\|frameless]]
	[[File:M I R A G E 02.jpg\|thumb\|217x217px]]		[[File:M I R A G E 02.jpg\|thumb\|217x217px]]

			==== EBM music ====
			[[EBM music\|[ -> EBM music ]]]

			Last februari was my first time at Grauzone Festival. A festival centered around darker style electronic music. It was the first time I felt I deeply connected to a music genre. And themes in this music reminded me a lot of what we do at XPUB. So I wanted to add a little reflection on it here. Let's see where it leads...

Robin: /* SI29 Workshop */

2026-04-02T12:05:46Z

SI29 Workshop

← Older revision		Revision as of 14:05, 2 April 2026
Line 77:		Line 77:

	=== MIRAGE Installation at Extraterrestrial Publishing Fair ===		=== MIRAGE Installation at Extraterrestrial Publishing Fair ===
	[[File:M I R A G E 03.jpg\|thumb\|~~499x499px~~]][[File:M I R A G E 01.jpg\|thumb\|~~497x497px~~]][[File:M I R A G E installation.mp4\|center\|M I R A G E installation an Extraterrestrial Publishing Fair\|frameless]]		[[File:M I R A G E 03.jpg\|thumb\|217x217px]][[File:M I R A G E 01.jpg\|thumb\|217x217px]][[File:M I R A G E installation.mp4\|center\|M I R A G E installation an Extraterrestrial Publishing Fair\|frameless]]
	[[File:M I R A G E 02.jpg\|thumb\|~~495x495px~~]]		[[File:M I R A G E 02.jpg\|thumb\|217x217px]]

Robin: /* Queering our Keyboard */

2026-04-02T11:47:37Z

Queering our Keyboard

← Older revision		Revision as of 13:47, 2 April 2026
Line 72:		Line 72:

	===== Queering our Keyboard =====		===== Queering our Keyboard =====
			[[Queering our keyboard workshop\|[ -> Queering our Keyboard ]]]

	The workshop will investigate how your computer knows which character to display when you press one of the keys on your keyboard. By making our own letters and making a keyboard out of them, we will encounter some of the technologies, standards and protocols involved in this process, and we will touch on some of the politics surrounding them. Our self-made keyboard will show why this part of our computer, phone, or other device, is maybe less self-evident and fixed then we might realize.		The workshop will investigate how your computer knows which character to display when you press one of the keys on your keyboard. By making our own letters and making a keyboard out of them, we will encounter some of the technologies, standards and protocols involved in this process, and we will touch on some of the politics surrounding them. Our self-made keyboard will show why this part of our computer, phone, or other device, is maybe less self-evident and fixed then we might realize.

Robin at 11:46, 2 April 2026

2026-04-02T11:46:23Z

← Older revision		Revision as of 13:46, 2 April 2026
Line 74:		Line 74:
	The workshop will investigate how your computer knows which character to display when you press one of the keys on your keyboard. By making our own letters and making a keyboard out of them, we will encounter some of the technologies, standards and protocols involved in this process, and we will touch on some of the politics surrounding them. Our self-made keyboard will show why this part of our computer, phone, or other device, is maybe less self-evident and fixed then we might realize.		The workshop will investigate how your computer knows which character to display when you press one of the keys on your keyboard. By making our own letters and making a keyboard out of them, we will encounter some of the technologies, standards and protocols involved in this process, and we will touch on some of the politics surrounding them. Our self-made keyboard will show why this part of our computer, phone, or other device, is maybe less self-evident and fixed then we might realize.

	===== MIRAGE Installation at Extraterrestrial Publishing Fair =====		=== MIRAGE Installation at Extraterrestrial Publishing Fair ===
	[[File:M I R A G E 03.jpg\|thumb\|499x499px]][[File:M I R A G E 01.jpg\|thumb\|497x497px]][[File:M I R A G E installation.mp4\|center\|M I R A G E installation an Extraterrestrial Publishing Fair\|frameless]]		[[File:M I R A G E 03.jpg\|thumb\|499x499px]][[File:M I R A G E 01.jpg\|thumb\|497x497px]][[File:M I R A G E installation.mp4\|center\|M I R A G E installation an Extraterrestrial Publishing Fair\|frameless]]
	[[File:M I R A G E 02.jpg\|thumb\|495x495px]]		[[File:M I R A G E 02.jpg\|thumb\|495x495px]]

Robin: /* SI29 Workshop */

2026-04-02T11:45:48Z

SI29 Workshop

← Older revision		Revision as of 13:45, 2 April 2026
Line 69:		Line 69:
	I did a prototype to use GIT with a remote on a server to have a way to keep a back-up of files. In this case, I lost the templates I use for my invoices and the folder where I keep them when my laptop broke. I started a web-to-print set-up so I can use html / css to and print to pdf to make my invoices. And as an extra step, now I can use GIT to do versioning to keep a back-up of this set-up on a remote server, without using GitHub!		I did a prototype to use GIT with a remote on a server to have a way to keep a back-up of files. In this case, I lost the templates I use for my invoices and the folder where I keep them when my laptop broke. I started a web-to-print set-up so I can use html / css to and print to pdf to make my invoices. And as an extra step, now I can use GIT to do versioning to keep a back-up of this set-up on a remote server, without using GitHub!
	=== SI29 Workshop ===		=== SI29 Workshop ===
	[https://hub.xpub.nl/sergio/SI29~~/intro~~/Queering%20our%20Keyboard/ <nowiki>[ -> workshop web page ]</nowiki>]		[https://hub.xpub.nl/sergio/SI29/Queering%20our%20Keyboard/ <nowiki>[ -> workshop web page ]</nowiki>]

	===== Queering our Keyboard =====		===== Queering our Keyboard =====

Robin at 20:31, 29 March 2026

2026-03-29T20:31:30Z

← Older revision		Revision as of 22:31, 29 March 2026
Line 75:		Line 75:

	===== MIRAGE Installation at Extraterrestrial Publishing Fair =====		===== MIRAGE Installation at Extraterrestrial Publishing Fair =====
			[[File:M I R A G E 03.jpg\|thumb\|499x499px]][[File:M I R A G E 01.jpg\|thumb\|497x497px]][[File:M I R A G E installation.mp4\|center\|M I R A G E installation an Extraterrestrial Publishing Fair\|frameless]]
	[[File:M I R A G E installation.mp4\|center\|M I R A G E installation an Extraterrestrial Publishing Fair\|frameless]]		[[File:M I R A G E 02.jpg\|thumb\|495x495px]]