5 Commits (139b24942e72bd26ce1bf98d59974993bd2ecea2)

Author	SHA1	Message	Date
Martin Atkins	ba21e33372	lang/funcs: Rename the base64 character encoding functions ... These were initially introduced as functions with "encode" and "decode" prefixes, but that doesn't match with our existing convention of putting the encoding format first so that the encode and decode functions will group together in a alphabetically-ordered function list. "text" is not really a defined serialization format, but it's a short word that hopefully represents well enough what these functions are aiming to encode and decode, while being consistent with existing functions like jsonencode/jsondecode, yamlencode/yamldecode, etc. The "base64" at the end here is less convincing because there is precedent for that modifier to appear both at the beginning and the end in our existing function names. I chose to put it at the end here because that seems to be our emergent convention for situations where the base64 encoding is a sort of secondary modifier alongside the primary purpose of the function, as we see with "filebase64". (base64gzip is an exception here, but it seems outvoted by the others.)	6 years ago
r0bnet	76ffe8aa7d	lang/funcs: Functions for encoding text in specific character encodings	6 years ago
Nick Fagerlund	2c50808bbb	website: Version notes: Add new -> old links to 0.12 language docs (function pages)	8 years ago
Nick Fagerlund	17873ae61b	website: Update functions section page titles	8 years ago
Martin Atkins	a491013054	website: Docs for all of the "encoding" functions	8 years ago