examples of utf compliance in version 20.1 yoel kortick aleph support manager

Post on 18-Jan-2018

227 Views

Category:

Documents

0 Downloads

Preview:

Click to see full reader

DESCRIPTION

3 Introduction On the specific PC used here Hebrew is the language chosen via Start > control panel > regional and language options > advanced (next slide) As a result, in pre-version 20.1 Arabic, French and German (as examples) would not display properly in specific cases. Similarly, if French were the language chosen via Start > control panel > regional and language options > advanced then Hebrew and Arabic would not display properly in specific cases.

TRANSCRIPT

Examples of UTF compliance in version 20.1

Yoel KortickAleph support manager

2

Introduction

• This presentation will show just three of the many new UTF compliant related features in version 20.1

• We will first show the problem in version 20.0 (problem which exists in all versions pre-dating 20.1) and then show how it is fixed in 20.1

• The fixes presented here relate to a situation where a language in used in specific cases and that language is not the default language defined in the PC regional settings

3

Introduction

• On the specific PC used here Hebrew is the language chosen via Start > control panel > regional and language options > advanced (next slide)

• As a result, in pre-version 20.1 Arabic, French and German (as examples) would not display properly in specific cases.

• Similarly, if French were the language chosen via Start > control panel > regional and language options > advanced then Hebrew and Arabic would not display properly in specific cases.

4

The PC regional settings

5

Problem #1 pre version 20.1

• This is a problem which occurs any time the non “regional” language is added to the item description or call number.

• Instead of the actual language question marks or other “wrong” characters appear.

6

Problem #1 pre version 20.1

• For example we have a bibliographic record related to a Holding record and the holding record has Arabic in the call number

7

Problem #1 pre version 20.1

• When the Holding record is connected to the item the question marks appear in the call number instead of the Arabic

8

Problem #1 pre version 20.1

• Now we will try to add the string in German “Über Größe” to the item description

• It does not appear properly

German characters appear wrong

9

Problem #1 fixed in version 20.1

• We have the same situation in 20.1

Arabic in Holding record

10

Problem #1 fixed in version 20.1

• The item is linked to the Holding record

Now the Arabic appears correctly

11

Problem #1 fixed in version 20.1

• Now we will add “Über Größe” to the item description

The German characters appear correctly

12

Problem #2 pre version 20.1

• Now I search in the GUI for three languages: German, Hebrew and Arabic: Größe and שלום and ،شعبان

One result

13

Problem #2 pre version 20.1

• When we view the results the query does not appear properly

14

Problem #2 fixed in version 20.1

• We perform the same search in 20.1 for three languages: German, Hebrew and Arabic: Größe and שלום and شعبان،

One result

15

Problem #2 fixed in version 20.1

• And now the search query appears correctly

16

Problem #3 fixed in version 20.1• " We would like to use "Fast cataloging" function. It

means in Circulation module Items => Catalog Record and Create Item. System opens the form for keying in bibliographic information. It is necessary to key in Cyrillic characters for Author and Title fields.“

• Here it is in version 18

17

Problem #3 fixed in version 20.1

• Here it is in version 20.1

• Cyrillic (and any other characters) appear perfect

18

Summary

• Pre version 20.1

• Version 20.1

19

Summary

• Pre version 20.1

• Version 20.1

20

Summary

• Pre version 20.1

• Version 20.1

21

Thank You

Yoel.Kortick@exlibrisgroup.com

top related