ConScript/Submit

From Sedes Draconis

Jump to: navigation, search

The ConScript Directory grows by people submitting their scripts to me, so if you've got one, think about sending it to me.

It should

  • Be a script you invented for ConLanging purposes.
  • Be for ArtLang purposes. That is, it should be a script, and be for a language (or multiple languages) that are create for artistry (including for fictional settings).
  • Not be for AuxLang purposes. Scripts that are designed make writing English, or any other real-world established language, easier, more logical, more interesting, more accesible, etc. are not within the intended scope of this collection. Likewise scripts for languages whose primary purpose is to be a "better" language. Simple substituion schemes, i.e. "scripts" that are nothing more than new glyphs for the letters of the roman alphabet, with maybe a few letters for common digraphs, will be rejected with extreme prejudice.
  • Be in a reasonably complete form. In the case of alphabetic and syllabaric systems, all glyphs should be ready for presentation; logographic scripts should have a reasonably large set of basic glyphs. It's not a problem if you revise it at some point and would like me to update the listing. But this should be kept to a minimum. If you make a change, and you expect to make another sometime soon, wait to tell me till you're done with the bout of revision.
  • In a visually appealing form. Either scanned or computer-generated images are fine (and combinations, such as computer re-touched scans are very good too). But please no poor scans, no scans on lined paper unless the script is meant to be written on lined paper. And try to avoid overly pixelated cg images. Anti-aliasing is your friend.

If you have a script that you would like to submit, please fill out the following form and send it to me. You can send it by e-mail at mailto:aidan@sedesdraconis.com (or by PM for ZBBers).

Replace () values with the appropriate information. Fill in whichever ones you want, within reason. It is, for example, perfectly fine to not fill in any history to start with, or to have only a few features. It is somewhat less reasonable to leave your name, or the name of the script blank.

A sample text is highly desirable, and it should be in a language that the script is used to write. If all you can write, or have written, in the language is a few names, that's fine. If you've got a text of a few lines, that's great. Several people have used the Babel Text as their example. 

== (Name of Script) ==

A [[ConScript]] by (your handle or name).

=== Origins ===
Internal: (The [[ConHistory]] of the script)

External: (The story of how you made it)

Notable Features:

*(Feature 1, e.g. direction of writing)
*(Feature 2, e.g. type of script: alphabet, abjad, syllabary, etc.)
*(etc.)

Used to write: (languages that use the script.  Either simple list, or brief description of interaction of each lang with the script.)

=== Charts ===

(Name of first chart, e.g. Consonants):

(image, tell me where to get, or e-mail it to me, if necessary.  Be courteous about attachment sizes.  I'll take jpg, gif, or png.  No other file formats.  I'll put a copy on my server either way, not call it from somewhere else.  Should include glyph, transcription, and IPA, if possible.)

(caption for chart, if necessary.  Or can be covered in Notable Features)

(Name of Second Chart, if there is one):

(image)

(etc., but not too many, please)

=== Sample Text ===
(image, likewise)

Transliteration:

(using your standard transliteration)

Gloss:

(If you like)

Translation:

(translation into English)

(brief description of text)

[(your own webpage for the script, if any) External Link]

Some terms:

  • Transliteration: The representation of a text in one writing system, in a different writing system. This should be mechanical, that is, you should have one way to represent each glyph of your writing system in the roman alphabet. Say you have a glyph that you transliterate as kh, then every time that glyph appears, when you write it in English Roman, you should represent it with kh, even if, in this particular place, it makes a [s] sound. (Though if multiple languages use the same writing system, they can well have different transliterations of the same glyphs.) Well thought out, systematic excpetions to the mechanism are fine, but it should be basically mechanical.
  • Gloss: An optional "half-translation", or "breakdown". Leave the word order the same, represent morphology with hyphenation or brackets, or something of the like. So glosses look something like this:
They speak[IV pl., pt] to one-another[gen.] "Come! Make[II pl] brick[ac., pl.] and bake[II pl.] very-well." They use[IV pl, pt] brick[ac.,pl.] as stone[pl.] and asphalt[ac.] as mortar.
Retrieved from "http://www.sedesdraconis.com/index.php/ConScript/Submit"
Personal tools