From 5a30a80867b7439934ce97bfa1e93703a5a34269 Mon Sep 17 00:00:00 2001 From: Morten Kromberg Date: Sun, 8 Sep 2024 16:08:40 +0200 Subject: [PATCH] Fix #648 - dead link in Usage/Arrays --- docs/Usage/Arrays.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Usage/Arrays.md b/docs/Usage/Arrays.md index cda6edc1..32143363 100644 --- a/docs/Usage/Arrays.md +++ b/docs/Usage/Arrays.md @@ -2,7 +2,7 @@ By default, Link uses *APL Array Notation (APLAN)* to store arrays in text files. While APLAN is a good format for describing numeric data, nested arrays and many high rank arrays, it is not ideal for storing text data. Link 4.0 introduces experimental support for storing multi-line character data in simple text files. -The configuration setting `text` can be used to enable this feature: If `text` is set to `'aplan'` (the default) then all arrays will be store using APLAN. If `text` is set to `'plain'` then text arrays that adhere to a set of very specific criteria will instead be stored in plain text files. You can set this option when a link is created, or using [`Link.Configure`](../API/Link.Configure). +The configuration setting `text` can be used to enable this feature: If `text` is set to `'aplan'` (the default) then all arrays will be store using APLAN. If `text` is set to `'plain'` then text arrays that adhere to a set of very specific criteria will instead be stored in plain text files. You can set this option when a link is created, or using [`Link.Configure`](../API/Link.Configure.md). Text files which are not in APLAN format will have a penultimate "sub-extension" section in the file name which records the format of the original array in the workspace. The below table describes the array file extensions, what the content represents, and the specific criteria for storage in plain text file.