Book reader feature set/lang-ko

From OLPC

< Book reader feature set
Revision as of 02:12, 4 July 2007 by Php5 (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)
Jump to: navigation, search
  번역근원 Book reader feature set 원문  
  english | português | 한국어   +/- 차이  

이 페이지는 노트북을 e북 리더로 활용하기 위해 요구되는 기능들을 논의하는 포럼입니다. e북은 종이 도서를 일정부분 대체할 수 있으므로, 노트북 도입을 망설이는 국가나 단체에 좋은 설득이 될 수 있습니다. 논의 이전에 디자이너들은 브라우저의 기본적인 HTML/XML과 더불어 에빈스를 포함하기로 결정하였습니다. DJVU에빈스의 PDF 기능을 모두 포함하는데, [DJVU]가 보다 가치있는 기능을 제공합니다.

This page serves as a forum for discussing the features required to make the device a useable eBook reader. Access to a diverse library of reading and reference materials will be a prime selling point of the olpc project. The devices are being cost-justified to interested nations based on the idea that money currently budgeted to purchase textbooks for students could be used to purchase a $100 laptop for each child and that the textbooks would be available in eBook format on the laptop itself.

Before diving into the discussion, designers have chosen to include Evince along with the basic HTML/XML capability of the browser. One would hope that this includes both DJVU and PDF capabilities of Evince, however DJVU probably provides the most value-add.

Contents

기능

리더

맑고 선명한 화면을 제공해야 합니다. 특히, 두 가지 기능이 지원되어야 하는데, 첫째는 재구매된 종이 도서입니다. DJVU의 압축 포맷은 이러한 목적으로 특별히 고안되었습니다. OLPC 대상국가들은 디지털 컨텐트보다 종이 컨텐트가 상대적으로 풍부하므로, 저작권을 구매하여 XO에 탑재할 수 있습니다. 두 번째는 우리가 흔히 알고 있는 e-북인데, 다양한 이북 리더 프로그램들에 의해 지원되는 사적 또는 공개 텍스트 포맷이 가용합니다.

The number one required feature for an ebook reader HAS to be the clearest, most easily readable text display possible on the hardware. Anti-aliasing or font-smoothing can be a great asset if implemented well or a horribly "smudgy" mess if implemented poorly...

In addition, there are two fundamentally different kinds of ebooks that must be supported. The first one is repurposed paper books. The DJVU compression format is designed specifically to make this feasible. The target countries for the OLPC do not have very much digital content available, however they have several generations worth of printed books that could be quickly repurposed. The second format is the computerised text that most people think of as E-Books, available in a bewildering array of proprietary and open text formats supported by dozens of ebook reader programs.

포함되어야 할 유용한기능들

  • 사용자가 사이즈와 타입 등을 조절할 수 있는 "스타일 시트"
  • 다양한 포맷의 디스플레이 그래픽: 백터와 비트맵
  • 복잡한 공식 표현 가능
  • 사운드와 비디오파일과 같은 멀티미디어 요소에 링크 (이것은 이북이 아닙니다. 이북은 텍스트와 정지화상에 제한함으로써, 합리적으로 전력을 사용할 수 있습니다. 사람들은 멀티미디어 컨텐트를 볼 수 있는 다른 어플리케이션들을 선택할 수 있습니다.)
  • 북마킹; 네트워크를 통해 공유 가능한 것
  • 에노테이션; 네트워크를 통해 공유 가능한 것
  • 교사와 학생들 간에 주고 받을 수 있는 워크시트, 랩스 등과 같은 코스웨어를 위한 외부 프로그램들과의 링크.
  • 사람이 읽을 수 있지만, 효율적인 마크업 언어 (기존의 이북 마크업 언어를 이용해야만 하는데, 툴들과 더불어 많은 이북들이 가용하게 될 것이기 때문입니다.)
  • 압축된 파일 (쉽게 압축 해제될 수 있는). (이것은 JFFS2 파일 시스템의 빌트인 압축과 균형을 잡도록 주의 깊게 처리되어야 합니다. 왜냐하면, JFFS2JFFS2 개발에 좋은 영향을 미칠 수 있는 다른 압축 포맷을 다룰 수 있기 때문입니다. 이상적으로, 이북은 현대의 데스크탑 상에서 단단히 압축될 것이고, OLPC는 CPU/전력 자원의 소모를 최소화하면서 신속히 그것들을 압축 해제할 수 있을 것입니다.)
  • 단순하고 직관적인 인터페이스
  • 로컬라이즈 가능
  • (아랍어나 태국어와 같은) 복잡한 언어를 지원 (특히 복잡한 곳은 bidirectional)
  • 단순하고, 자연스러워며, 쉽게 익힐 수 있는 스크롤, 또는 페이지 전환
  • 사용자는 다큐먼트를 encrypt 및 볼 수 있어야 합니다. 그러한 문서의 적합성을 폭넓게 분석할 수 있도록 매우 민감한 방식으로 컨텐트를 다뤄야 하비낟.
  • 텍스트-투-스피치 옵션은 읽는 법을 배우는 데 도움이 됩니다.
  • 텍스트-투-스피치 옵션은 읽는 것보다 듣는 것이 편한 아이들에게 도움이 됩니다.
  • 단어의 뜻을 이해하기 위한 사전/테사우루스 연결.
  • User definable "style sheets" to control font size and type face, etc.
  • Display graphics in various formats; both vector and bitmap formats
  • Display complex formulae
  • Link in multimedia elements such as sound or video files (this is not an e-book. Ebooks should be limited to text and still images in order to get maximum use of electricity. People can still choose other apps to view multimedia content)
  • Bookmarking, preferably sharable via network
  • Annotations, preferably sharable via network
  • Link to external programs for coursework such as worksheets, labs, etc. which can be forwarded BY the teacher to the students, and sent back to the teacher once the homework is done.
  • Human readable, yet efficient markup language (should use an existing e-book markup language since many e-books will be available as well as tools. Existing e-book formats are often based on a simplified HTML markup)
  • Compressed files (easily decompressed to access original files) (this needs to be carefully balanced against the built-in compression of the JFFS2 file system. Since JFFS2 can handle alternate compression formats it may be better to influence the JFFS2 development. Ideally, ebooks will be tightly compressed on modern desktops, and the OLPC will be able to quickly decompress them without using too much CPU/electricity)
  • Simple, intuitive interface
  • Localizable
  • Supports complex-text language rendering (for example, Arabic and Thai)(bidirectional is where the real complexity is)
  • A way to scroll, or "turn pages" of ebooks with the following properties: simple, natural, low-learning curve.
  • Users should be able to encrypt and view documents. Special care should be taken to treat the contents in a highly sensitive manner to make wide-scale analysis of such documents infeasible.
  • A text to speech option can help kids learn to read.
  • A text to speech option might help kids that do not like to read a lesson but would not mind listening to it at a speed they could understand it.
  • Linking to a dictionary/thesaurus to define and gain understanding of words. Students unsure about a word can select it and tell the app define it and the definition of it could either pop up within the application or display it in a secondary program.

라이버러리

이 노트북은 수백 권의 책, 기사, 이야기, 에세이 등을 저장할 수 있으므로, 카탈로그, 조직화, 및 검색이 주용합니다. 포함되어야 할 유용한 기능들로는;

  • 카테고리를 위한 표준화된 메타 데이터 스키마
  • 스키마 필드 소팅 및 마지막 읽은 페이지와 같은 시스템 생성 데이터
  • 모든 타이틀을 관통하는 풀 텍스트 서치 기능 - 인덱싱이 필요하므로, 속도가 빨라야 합니다.
  • 검색된 단어들을 하이라이팅
  • 추가 타이틀들을 다운로드할 수 있도록 보다 큰 라이버러리로 네트워크 액세스

오픈소스 제품인 그린스톤은 이러한 기능들을 다수 제공하며, 저개발국의 이북 컬렉션 배포에 이미 이용되고 있습니다.

The laptop has the storage capacity for many hundreds of books, articles, stories, essays, etc., so cataloging, organizing and searching will be crucial.

Useful features might include:

  • A standardized schema of metadata for categorizing work
  • Sorting on any of the fields in the schema, plus system generated data like last page read, etc.
  • Full-text search capability across all titles - MUST be speedy so indexing will be necessary
  • Highlighting the words that are searched.
  • Network access to larger library to allow downloads of additional titles

An open source product, called Greenstone has a number of these features, and is already used to distribute collections of books to developing countries.

포맷

여러가지 포맷이 지원될 것이입니다.이북에서 자세히 논의합니다. 유용한 포맷으로는 HTML, PDF, DJVU, 그리고 OpenDocument이 있습니다. 일부 사람들이 공통의 위키 마크업 언어 WikiCreole에 참여하고 있으며, OLPC 팀은 WikiCreole의 슈퍼세트를 사용하는 위키 엔진을 제작하고 있습니다.

Several formats will need to be supported; Ebooks discusses this in more detail. Probably-useful formats include HTML, PDF, DJVU, and OpenDocument. Some people are working on a common wiki markup language called WikiCreole. A wiki engine using a superset of WikiCreole is being built by the OLPC team.

No access to Microsoft Word Files? MEXICO, AGS. --Dagoflores 16:27, 14 March 2007 (EDT)

인터페이스

OLPC는 기존의 PC 운영시스템과 상당히 다른 유저 인터페이스를 가지고 있습니다. 이북 인터페이스는 여기에 적합하여야 합니다. 인터페이스 샘플을 참조하십시오. 이북 아이디어를 여기에 게재하십시오

  • Adobe Reader[1]와 비슷한 인터페이스?
  • Evince와 비슷한 것?

First and foremost, the OLPC has a user interface that is not quite like most existing PC operating systems. The Ebook interface should fit into that context. Look here for interface examples.

Post eBook interface ideas here.

  • Should the eBook interface look like Adobe Reader[2]? (The UI can be completely hidden, the page can be rotated to be read like an open book, and pages can be turned with the right-arrow key, conveniently located on the bottom corner of the keyboard near where your left thumb would hold it.)
  • Should it look like Evince? (Most UI stuff can be hidden)
  • Should it have a status bar? (If so the it's not an ebook reader. All UI elements, including status bars, should be hideable).

조그 리딩휠 Jog Reading Wheel

A few years for a ridiculous sum of money, considering the fact that the units are no longer supported or sold, I bought a stony clié PDA T625 C ( I still have it on my desk if someone wants to make me an offer:) Anyway one of the most salable features and indeed usable things about this PDA is the thumb wheel on the side of the case. It allows me to read PDF or whatever documents and scroll up or down the pages of the document using this little plastic wheel, if you push the wheel in you can also reset to the start of the document. Don't take my word for it here is what many other people say about this neat feature;

http://www.the-gadgeteer.com/review/sony_clie_peg_n760c_review "On the left side of the Clie are the jog-wheel, back button and hold. The jog-wheel? “What a dumb idea,” I thought when I started using the unit. “What is the point when you can just touch the screen to select objects and items?”

Well In less than a week I found this little addition to be an absolutely wonderful feature. I can fly though addresses or to-do’s with a flick of my thumb while driving, on the phone, etc."

The Sharp Zaurus models that look like little laptops also have this feature.

Down Arrow: I do the same thing reading e-books on my laptop web browser by holding down the down-arrow key.

PGUP/PGDN Buttons: The Gemstar/Rocket/RCA/eBookwise Ebooks (Picture Here) has PGUP/PGDN buttons near the grip (which was also very nice and was designed to be held like the spine of a book). I've been using one of these for two years, but I'm very interested in upgrading to something more flexible. I think that the design of the unit was very well thought out and should be experienced by anyone designing hardware that is meant to be suited for reading ebooks.

블랙베리 스타일 휠 Blackberry style control

The Blackberry has one thing that is really right in that both the enter/fwd key and the esc/bck key are easily available. The OLPC/Sugar interface should have use the 4-way pad an Enter and an Esc. This way, you can follow links in your PDF and HTML ebooks. If a user can't jump back to the place where they were reading easily, they will not be as willing to look up terms in the glossary (for example). eBooks will be made assuming that the user can jump back -- authors should not have to re-format their works for the OLPC.

The 4-way pad is already in the hardware specification as is the enter/fwd; an esc/bck should be added now. It will come in handy for many applications.

Personal tools
  • Log in
  • Login with OpenID
About OLPC
About the laptop
About the tablet
Projects
OLPC wiki
Toolbox
In other languages