Documentation

Books

Help Us by buying books

We get a small percentage of the money you will spend on the books listed here provided you buy directly after you click the link. If you're going to buy one of these books, please do so via these links. There will be no charge on you, the price remains the same, we just get paid from Amazon. Thank you!

Open Access, Scholarly Publishing, Digital Libraries

( categories: Documentation )

Training Courses

The HyperJournal Association offers hands-on training courses on HyperJournal. So far we offer 2 types of courses:

  • Creating and managing a Journal with HyperJournal (This course is for a non-technical audience).
  • Installing, configuring and customizing HyperJournal.

The following is a list of past and upcoming courses. If you want us to organize a course at your site, please contact us at info@hjournal.org

( categories: Documentation )

Italian translation of the user manual

Submitted by barbz on February 21, 2006 - 16:41.

An italian translation of HyperJournal 4 Dummies. A beginner's guide to HyperJournal has been released today. The italian version "HyperJournal 4 Dummies. Una guida per principianti" can be downloaded from the documentation section of the web site.

( categories: Documentation )

Translating HyperJournal

HyperJournal uses a smarty configuration file to handle translations. A config file is loaded at the beginning of each template:
{config_load file="$lang.cfg"}

The HyperJournal's smarty templates contains some identifiers that are substituted with a localization string before the output is sent to the browser.

There is a localization file for each language which contains the translations of all the identifiers of hyperjournal. The name of the localization file is the ISO 3166-1 alpha-2 country code (lowercase) followed by .cfg (e.g. en.cfg for english, it.cfg for italian) and the file is placed in the i18n directory.

Creating a localization file and adding a new language

To localize HyperJournal you need to create a cfg file and place it in the i18n/ directory, hyperjournal will then load your localization file and the new language can be selected in control panel-->journal. It's suggested to use an existing localization file and modify the identifier's values to match your language.

Anatomy of a localization string

Do not forget that you cannot place carriage returns into localization strings (they must be one line long).

HTML character entities

All accented and special characters must be escaped with HTML character entities. Some characters must be escaped to avoid conflict with XHTML markup: angle brackets (< and >), and ampersands (&). In addition, there are a few other characters that must be escaped, such as non-breaking spaces ( ), angle quotes (« and »), curly apostrophes (’) and curly quotes. For more information about the W3C's best practices involving character encodings and character entities, see the following references:

Caution: Be sure to save your localization file using an utf-8 encoding!

( categories: Documentation )

Citation Extraction: extracting text from PDF/PS: result table

( categories: Documentation )
Caso Programma Versione Licenza Input Output Lettere accentate Fedeltà Separa paragrafi Separa pagine Spazi e indentazione Dimensione carattere Corsivo, grassetto Testo su più colonne Posizione assoluta elementi Modalità di esecuzione, file prodotti
1 pdftotext xpdf v 3.00 GPL PDF plain Sì (ISO-8859), ma non per TeX Può perdere caratteri No, mette tutto di seguito, anche i titoli ^L No No No Testo in ordine sequenziale, ma pu fare confusione No Produce un file txt: nome.pdf -> nome.txt
2 pdftotext -layout xpdf v 3.00 GPL PDF plain Sì (ISO-8859), ma non per TeX Può introdurre righe spurie e spazi nelle parole No, li separa solo se verticalmente e uniformemente separati (non affidabile) ^L No No Viene mantenuto il layout a colonne Approssimata (plain text con layout) Produce un file txt: nome.pdf -> nome.txt.
3 pdftohtml -nomerge -noframes