About Oracc: Essentials for Oracc users

Browsers

Oracc emphasizes standards-compliant, cross-platform software so FireFox is a good choice of browser. Safari and Chrome are also supported, and reports about Opera are welcome. Internet Explorer is not supported.

Fonts and Encodings

Oracc uses Unicode in the UTF-8 encoding. You may like to install the Ungkam font, which provides all the characters Oracc uses for transliterated cuneiform. If you would like to make it easier to type accented characters you might find the Oracc keyboards page useful.

Information

Oracc has several pages describing its organization, practicalities and philosopy which begin with the About Oracc page. There are also plenty of help pages.

Oracc notes and news are disseminated on the blog [http://oracc.blogspot.com], FaceBook page [http://www.facebook.com/opencuneiform] and two Twitter accounts: @oracctivity [http://www.twitter.com/oracctivity/] regularly posts links to tidbits from Oracc, while @opencuneiform [http://www.twitter.com/opencuneiform/] tweets technical news and updates.

Licensing

Unless otherwise stated, all Oracc content is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License [http://creativecommons.org/licenses/by-sa/3.0/], which is described in more detail on the licensing page.

See the page on how to re-use elements of Oracc for concrete examples of what this means in practice.

Accessibility

Oracc sites aim to be as accessible as possible, whichever standards-compliant browser you use. If you have any access difficulties please contact the Oracc Steering Committee at osc at oracc dot org. For more information see our pages on:

Access Keys: A list of shortcuts to key Oracc help pages.
Site Map: A listing of all Oracc information and help pages to help navigation.
Cookies: A simple explanation of Oracc's use of cookies, in compliance with EU Cookies law.
Accessibility: A simple description of Oracc's policy of compliance with web accessibility standards.

Contributing

Oracc corpus contributions are properly described on the contributing page, along with the how-and-why page. But the short story is:

If you are done with your stuff and would like to put it on Oracc under a license that allows it to be reused by other people and included in the CDLI transliterations file, just send it to us.
If you would like to continue looking after your stuff under a license that allows it to be reused by other people and included in the CDLI transliterations file, just contact us.

Standards

Oracc aims to be compatible with major international standards; see the following documentation:

Schemas
O-ATF and C-ATF
OpenDocument
Text Encoding Initiative

Contact

Oracc can be reached via blog [http://oracc.blogspot.com], FaceBook [http://www.facebook.com/opencuneiform] and either [http://www.twitter.com/oracctivity/] of our Twitter [http://www.twitter.com/opencuneiform/] accounts, as well as by email to the Oracc Steering Committee at osc at oracc dot org.

18 Dec 2019 osc at oracc dot org

Steve Tinney & Eleanor Robson

Steve Tinney & Eleanor Robson, 'About Oracc: Essentials for Oracc users', Oracc: The Open Richly Annotated Cuneiform Corpus, Oracc, 2019 [http://oracc.museum.upenn.edu/doc/about/]