From 406d56c3601faee789a6c6a956aac96684bb984f Mon Sep 17 00:00:00 2001 From: Hasso Date: Thu, 5 Oct 2023 16:57:39 -0500 Subject: [PATCH] Add documentation about lacking documentation --- README.md | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 35153cb6..d8243982 100644 --- a/README.md +++ b/README.md @@ -69,13 +69,13 @@ The following list of features should help you understand why we built this laye any piece of data, and to carry on conversations about the data until they mark the note as "resolved". -### Status +## Status Chorus is functional and being used in several applications with different development teams. However, we are not really interested in supporting any further uses until things mature and someone writes good developer documentation. -Documentation (what little exists) drips out in the form of occasional blogs -[here](http://chorussr.wordpress.com/). +Documentation (what little exists) was kept in [this blog](http://chorussr.wordpress.com/), +which contains three posts from August 2009. ## Testers @@ -128,4 +128,8 @@ Further instructions at https://github.com/sillsdev/libpalaso/wiki/Developing-wi ### Debugging LibChorus in client projects -Copy `src/LibChorus/Properties/launchSettings.json.sample` to `launchSettings.json`; verify paths to executables and in arguments. \ No newline at end of file +Copy `src/LibChorus/Properties/launchSettings.json.sample` to `launchSettings.json`; verify paths to executables and in arguments. + +### Localization + +Chorus is localized with [L10NSharp](https://github.com/sillsdev/l10nsharp). Chorus-specific documentation has been lost to history.