Artikulate shall eventually provide language courses for a lot of languages. With this goal it is unpractical to create a special course for each language but provide a course skeleton that is then translated for each available language. Such a course skeleton is available here . But this file is still very small at the moment. Hence, for this task, create a new unit for our basic course.
A unit has the following characteristics:
* It is a set of words, sentences, compound of 2-3 sentences. (Those are only called "phrases" in the following)
* The unit has a topic (given by its name) and all phrases inside a unit are selected according this topic. (You can think about phrases used in a restaurant, phrases used at school/university, phrases used at an airport).
* The phrases are ordered by a specified order but in the sequence: firsts words, then expressions, then sentences, then paragraphs. The phrases will be shown in the same order later in the program.
* A unit has about 50 to 100 phrases.
* Each phrase in a unit is tagged by its length (is it a single word, an expression of some words, a complete sentence, or a set of 2-3 sentences)
* Phrases are NOT tagged by phonemes yet (hence we are talking about a course skeleton here!)
You can create such a unit in two ways:
1. Create a list with a plaintext editor and specify all necessary information to include them into the course skeleton (e.g., unit name)
2. Otherwise download and compile Artikulate [2,3] and edit the course skeleton with the internal editor (can be accessed by the menu button at the top left)
For case (1) please submit the unit by mail to email@example.com. For case (2), please fill merge the file with a review request at https://git.reviewboard.kde.org/ with the changed course skeleton file.
*** Bug 322527 has been marked as a duplicate of this bug. ***
(In reply to comment #1)
> *** Bug 322527 has been marked as a duplicate of this bug. ***
Just for the record: Bug 322527 is a duplicate of bug 323053 and not of this one (copy/paste error).
Thank you for the bug report.
As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.
If this bug is no longer persisting or relevant please change the status to resolved.