Giter Club home page Giter Club logo

koreader-translations's Introduction

KOReader

KOReader is a document viewer primarily aimed at e-ink readers.

AGPL Licence Latest release Gitter Mobileread Build Status Coverage Status Weblate Status

DownloadUser guideWikiDeveloper docs

Main features

  • portable: runs on embedded devices (Cervantes, Kindle, Kobo, PocketBook, reMarkable), Android and Linux computers. Developers can run a KOReader emulator in Linux and MacOS.

  • multi-format documents: supports fixed page formats (PDF, DjVu, CBT, CBZ) and reflowable e-book formats (EPUB, FB2, Mobi, DOC, RTF, HTML, CHM, TXT). Scanned PDF/DjVu documents can also be reflowed with the built-in K2pdfopt library. ZIP files are also supported for some formats.

  • full-featured reading: multi-lingual user interface with a highly customizable reader view and many typesetting options. You can set arbitrary page margins, override line spacing and choose external fonts and styles. It has multi-lingual hyphenation dictionaries bundled into the application.

  • integrated with calibre (search metadata, receive ebooks wirelessly, browse library via OPDS), Wallabag, Wikipedia, Google Translate and other content providers.

  • optimized for e-ink devices: custom UI without animation, with paginated menus, adjustable text contrast, and easy zoom to fit content or page in paged media.

  • extensible: via plugins

  • fast: on some older devices, it has been measured to have less than half the page-turn delay as the built in reading software.

  • and much more: look up words with StarDict dictionaries / Wikipedia, add your own online OPDS catalogs and RSS feeds, over-the-air software updates, an FTP client, an SSH server, …

Please check the user guide and the wiki to discover more features and to help us document them.

Screenshots

Installation

Please follow the model specific steps for your device:

AndroidCervantesKindleKoboLinuxPocketbookreMarkable

Development

Setting up a build environmentCollaborating with GitBuilding targetsPortingDeveloper docs

Support

KOReader is developed and supported by volunteers all around the world. There are many ways you can help:

Right now we only support liberapay donations.

Contributors

Last commit Commit activity

koreader-translations's People

Contributors

beckydtp avatar cges30901 avatar easteriq avatar eevan78 avatar elvvis avatar frenzie avatar hombretranquilo avatar ichnilatis-gr avatar ihorhordiichuk avatar jim-kirisame avatar kayazeren avatar kaznelson avatar leschek avatar lisapple avatar matthaiks avatar monirzadeh avatar oldman63 avatar pedrogmattos avatar rffontenelle avatar shinxa1 avatar silvergreen93 avatar sonix-github avatar souffly007 avatar sr093906 avatar stoyandimitrov avatar unimiso avatar weblate avatar xcomesana avatar yarons avatar zwim avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

koreader-translations's Issues

en_GB/AU?

Hello, I'm wondering if you're open to an en_GB translation?

I jumped on Weblate to ask the same question via a submission but don't seem to be able to select en_GB there (presumably due to a setting your end?).

Update Readme

to reflect change to weblate.

i am not sure what to write or i would make a PR

check in weblate for nonmatching format specifiers like %1

I wonder if someone has access to the set of rules by which weblate declares that a translation string has not passed the checks. Like, presently, non matching number of line breaks, non matching closing punctuation, translation string identical to original, etc. [some of them do not necessarily point to translation errors but that's another story].
If rules could be added, I'd suggest a stricter check for the correspondence of format argument specifiers like %1, %2, etc. in both original and translation.
I ended up updating semiregularly two different localisations (one LTR and one RTL, which makes it more interesting), and I ran into a number of mismatches - like leftover orphan %1 in the translation because the original contained it in a previous version, spaced % 1, transposed 1% and such. Some are due to the suggestions of automatic translation engines which misinterpret percents; embedded bidi in the case of RTL may make more difficult to spot them. I speculate that there may be still a number of such occurrences in the various localisations, according to the samples I found. A specific rule may help.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.