Meeting minutes
Follow-up on i18n issue #144
Janina: belive that status is that we have the pieces we need to show to i18n, but don't have them in the correct document type
Janina: have xml but need ebook and html - currently is not in the correct format
janina: once we have correct format, need to share with i18n
JF: clarification, epub is xhtml
Janina: yes, meant epub and not ebook
Janina: are showing shifts from left to right and right to left lanugage direction. We show inline symbols but preference is for symbol above. But, believe that showing symbols above should just be a matter of adding css
CharlesL: where is these files?
<Lionel_Wolberger> Lionel says to all: forwarding the email now
<Lionel_Wolberger> Sample of the code,
<Lionel_Wolberger> {{22909:cooking,cookery,preparation_(general)}}Ingredients · 2 {{22590:tin,can}}cans of garbanzo {{24021:bean_(dried),chick-pea,kidney_bean,pinto_bean}}beans · 2 cloves {{14423:garlic}}garlic, {{15989:peel-(to)}}peeled · {{14406:fruit_juice,juice}}Juice of 1 {{15221:little,small}}small {{15190:lemon}}lemon ... {{13408:cook-(to)}}Method 1. {{13872:drain,sift,strain-(to)}}Drain the {{24021:bean_(dr[CUT]
LisaSeemanKest: in the extension there were lots of user preferences, for example how much content was desired for the complexity setting. We did have a setting in extension for where to place the symbol
LisaSeemanKest: it is an implementation question and CSS seems like the way to solve; Thus, this is part of the user agent implementation
janina: believe that is beyond the need for solving the i18n issue (#144); yes, there are other issues that the user agents need to handle. It is task of reccomendation status to make sure other requirements are met. Right now we just need to satisfy i18n that we don't have a left to right / right to left issue
Janina: believe we have looked at this in other user agents, some handle language direction better than others
Charles: we say that Mac implementation issues where okay, but does depend upon what reading system, browser, and OS is being used
<LisaSeemanKest> I need to jump off for a bit, but just to say we have an extention that allows right to left or left to right or above
Janina: even when implementation / justification was not ideal, the symbols were in the correct order
CharlesL: Steve's implementation is in XML rather than xhtml
Janina: will forward message from Steve to the personalization list
https://
Janina: need to take Steve's information and put it into the correct xhtml format
CharlesL: I have provided the skeleton xhtml file. That needs to be updated with the information from Steve. Probably a couple of hours of work
CharlesL: I might have time to update the English version today. Someone will need to update the hebrew version of the file
Janina: believe we need to just do a few lines of the recipe rather than the entire thing
becky: reviews the info posted above by Lionel
JF: this seems like an analogy to sign language - is not exactly the same syntax and structure that native English text speakers are familiar with
<Lionel_Wolberger> Lionel says to Charles, I will do the Hebrew as soon as I have the HTML for the English
CharlesL: will have to add spans for text that need specific symbols. I will give it a shot and write down any assumptions I need
Janina: accuracy isn't a requirement, we just need to prove that changing the language direction works correctly
CharlesL: I think we still have a chrome or firefox demo that may work?
Janina: we need to make sure we point out in issue 144 that the symbol direction is correct but that some of the justification and other issues are general brower/reader issues
CharlesL: no ebook readers currently show the symbols; but we are demonstrating this on the web - that should be enough
Janina: but we need to see that it works inline
Charles: so we need to combine the english and hebrew into one file
<Lionel_Wolberger> Lionel to Charles: I will put the hebrew under the english, in the same file.
<Lionel_Wolberger> Lionel says to Charles, I will need that <span> pattern as sometimes two words become one symbol
JF: how much do we have to prove to i18n? We should be able to prove the capability and not all the specific use cases.
Janina: agreed, just want to suggest that we need to put english and hebrew within the same file
Implementations Update: Who is implementing Module 1? We need two implemenations...
janina: this is a post CR problem. This is not an issue for the group, yet
becky: don't we have potential people lined up?
<Lionel_Wolberger> Lionel says to all, we have access-board started, and a Canadian bank potentially interested.
Janina: no one has committed to the user agent implementation
Janina: US Access Board has agree to update an application form on github branch
Janina: we need to show that a user can have a preferred symbol set and render between them
janina: access board will give us the content and markup but not the rendering - we need an extension to digest/present the content and personalization markup
Janina: US Access board example becomes our test file(s) but may need other examples to include all options
Janina: need to see how current extension will handle the rendering
Janina: may need Steve's help again with mappings
Janina: still need more implementers
Janina: need to review US Access Board example to see how many of our "must" requirements are met
Janina: Any chance that Thorium might pick this up? It is open source
Janina: CR has to last at least 60 days, we know we need at least two - so we have 120 days
CR draft Status
janina: are there any issues with the text Sharon sent around for the CR draft status? I have no issues, we just need to fill in the publication dates. Need feedback from Shawn
Janina: we have the potential of privacy issues being raised, I believe we can resolve them during CR because we did get reviews from privacy and security already
janina: we just need to clear #144 before we can determine publication dates
Module 2.0 Updates and Next Steps
Janina: JF gave us the reformatting; have asked COGA to review module 2 and 3 for content and prioritization
JF: I just updated the structure of the mod. 2 & 3 documents to match with mod. 1. No content changes
JF: just need to review the attributes and values and make sure they are still relevant; Believe we can move faster based on what we have learned from module 1.
JF: do we want to work on mod 2 & 3 concurrently or sequentially?
Janina: that is why I want COGA to review again for priority of item because membership in COGA has changed
Janina: still need to address the question of how to get these specs implemented? Still fighting for ARIA implementaion who is going to take on personalization and pronunciation? Believe this is a wider WAI issue that needs to be driven
CharlesL: believe symbols is going to be the most challenging; other attributes are not as difficult - legal-ease, jokes, complexity
CharlesL: at least getting some of module 1 implemented in Thorium or other extension to get more interest and implementation
janina: for example, may want to ask bliss to provide list in csv or other format rather than PDF so could look up symbols via some sort of tool.
Janina: talk to aria and others about making updates at once rather than piecemeal
JF: I want to look into tinyMCE - WYSIWHG editor that supports extensions. If we could get an authoring module for personalization - two drop downs with attribute and value for authors to use. TinyMCE is widely used so may be an implementation possibility
<Matthew_Atkinson> +1 to JF's idea of investigating editors such as TinyMCE.
Janina: we can become a rec. without solving wider issue of wide implementation and complexities of implementation
<Matthew_Atkinson> and also +1 to CharlesL's of submitting patches to open source reading software.
January
Janina: is January 4 a holiday?
becky: most companies seem to be doing the Friday before, Dec. 30
Janina: please check with your companies; so we will likely resume on the 4th of january
<Matthew_Atkinson> The 3rd of January is a bank (public) holiday in the UK (c.f. https://
<Matthew_Atkinson> s/The 3rd of January/Monday the 3rd of January/
<JF> @Matthew - we should chat you and I about getting an extension for TinyMCE. May look to you for some assistance
Janina: personalization if off Dec 20 and 27. Two meetings after today
CharlesL: for authoring we may talk to Daisy as they have an epub converter
<Matthew_Atkinson> @JF: Yes, sure; sounds good :-).