280 likes | 521 Views
Unicode Compliance and Future of WinFIBRE. 36 th Consultative Meeting of INIS Liaison Officers 4-5 October 2012, Vienna, Austria. Lubomir ILIEV. Unicode Compliance. What is Unicode? Why do we need Unicode ? How we did implement UNICODE? What is the impact?. Unicode Compliance.
E N D
Unicode Compliance and Future of WinFIBRE 36th Consultative Meeting of INIS Liaison Officers 4-5 October 2012, Vienna, Austria Lubomir ILIEV
Unicode Compliance • What is Unicode? • Why do we need Unicode? • How we did implement UNICODE? • What is the impact?
Unicode Compliance Ascii Table
Character encoding standards • ASCII (7 bit) • Extended ASCII (8 bit) • Codepage (Windows-1252) • Unicode
Unicode Compliance • Why do we need UNICODE • All others use UNICODE • Statistics for Elsevier Batch 28 • Total records 18918 • 316 different Unicode characters • 170356 total Unicode characters • Average ~ 9 chars/record
Unicode Compliance • Why do we need UNICODE • Expressions (Formulas) • Letters • Bullets and other characters • How we process data without using UNICODE
Unicode Compliance • How we implemented Unicode • Restrictions/Limitations (Fibre IRPS) • Different representation: TTF/XML • Extending the standard for “Logical Characters” (INIS-1 Guide to bibliographic description)
Unicode Compliance • Current “Logical Characters” (72 total)
Unicode Compliance • The “new” set contains 2155 symbols 0080 C1 Controls and Latin-1 Supplement 0100 Latin Extended-A 0370 Greek and Coptic 2000 General Punctuation 20A0 Currency Symbols 2100 LetterlikeSymbols 2150 Number Forms 2190 Arrows 2200 Mathematical Operators 2300 Miscellaneous Technical 25A0 Geometric Shapes 2600 Miscellaneous Symbols 27F0 Supplemental Arrows-A 2900 Supplemental Arrows-B 2980 Miscellaneous Mathematical Symbols-B 2A00 Supplemental Mathematical Operators
Unicode Compliance • Compatibility • Up compatibility • “Old” records will be valid • Down compatibility – 2 levels • 0 - Unicode • 1 - TTF-style encoding + text
Unicode Compliance • Original text • In the WKB regime, qQ≫ℏ, we obtain a simple expression for the fundamental quasinormal resonances: ω=qQ/r+−i2πTBH(n+1/2 ),... • TTF format • In the WKB regime, qQ#Much Greater-Than##Planck Constant Over Two Pi#, we obtain a simple expression for the fundamental quasinormal resonances: #Greek Small Letter Omega#=qQ/r_+#Minus Sign#i2#Greek Small Letter Pi#T_B_H(n+1/2 ),...
Unicode Compliance • Level 0 – Unicode • In the WKB regime, qQ≫ℏ, we obtain a simple expression for the fundamental quasinormal resonances: ω=qQ/r_+−i2πT_B_H(n+1/2 ),… • Level 1 - TTF-style encoding + text • In the WKB regime, qQ Much-Greater-Than Planck-Constant-Over-Two-Pi , we obtain a simple expression for the fundamental quasinormal resonances: #omega#=qQ/r_+-i2#pi#T_B_H(n+1/2 ),…
Unicode Compliance • Is using Unicode enough? • Glyphs not in Unicode • Expressions and Formulas • Future possible directions: • UnsingTeX and/or MathML
Future of WinFIBRE • What is FIBRE? • Definition • Specialised text editor with checking capabilities • Functionalities • Existing • Create and edit records • Verify records • Field-specific editing • Planned • Edit existing records (“change record”) • Managing record relations
What is FIBRE? • Actual limitations for input preparation • Checking rules • Correct but not always helpful error messages • Bibliographic and indexing part cannot be checked separately • Editing • Difficult to create and read mathematical and other expressions • Cannot manage relations between records
Future of WinFIBRE • Decisional factors
Future of WinFIBRE • Recently implemented functionalities • Expert system • Under development • Change record (under internal tests) • Re-design WinFIBRE checking rules • Unicode compliance for input preparation • Improve records editing functionalities • Manage record dependencies
Unicode Compliance for input preparation • Added functionality in WinFIBRE • Edit/Paste • Edit/Insert Special Character… • Preview (Visualisation)
Unicode Compliance for input preparation • Edit/copy-paste • #integral#_#alpha#"#beta#x"#gamma#"-"1 dx
Unicode Compliance for input preparation • Edit/copy-paste E(f)=defp(D#Divides#f,#alpha#,#beta#)=#Integral#p(D#Divides#w,#beta#,f)p(w#Divides##alpha#,f)dw.
Unicode Compliance for input preparation • Preview • P(G_p_t_,_ _m_-_v_e_c_t_o_r_ _ ,q) =#Greek Capital Letter Sigma#_i__1_=_1"3#Greek Capital Letter Sigma#_i__2_=_1"3 c_G__p__t_,_i__1_ _i__2#lambda#_i__1"m"_1#lambda#_i__2"m"_2 • P(G_{{\rmpt},\vec{m}},q) = \sum _{i_1=1}^3 \sum _{i_2=1}^3 c_{{G_{{\rmpt}}},i_1 i_2} \lambda _{i_1}^{m_1}\lambda _{i_2}^{m_2}
Unicode Compliance and Future of WinFIBRE Thank you for your attention!