text:
National Network of Libraries of Medicine
Pacific Northwest Region
Quarterly Report
February to April 2003
Table of Contents
- Health Professional Access to Information
- Assess Needs of Health Science Librarians
- Network Membership Program
- Document Delivery
- Resource Libraries
- Communication
- Regional Advisory Committee
- Monitor Region's Programs
- User Feedback
- Training Facility
- NLM User/Non-User Needs Assessment
- NLM Grants
- Follow-up with NLM-funded Projects
- Outreach to Health Professionals
- Consumer Health Information Services
- Training to Support Electronic Access to Health Information
- Exhibits and Presentations at Meetings
- Technology Awareness and Integration
- Library Improvement
- Connections
1. Health
Professional Access to Information
The Pacific Northwest Chapter, Medical Library
Association, has decided to explore whether consortial
purchasing of electronic journals and databases could be
part of its functions. A committee has been named to
begin this investigation, with Susan Barnes, Resource
Sharing Coordinator, as a member. This effort would
replace the Washington Medical Library Association
consortial purchasing, which has been regional from the
beginning because more libraries than just those in
Washington were needed to bring more purchasing power.
Participants in the existing WMLA consortial subscription
to 142 Lippincott Williams & Wilkins titles are
enthusiastic about being able to provide access to this
content for their users. They report that the titles are
not only important for their institution's work, but that
providing access to the titles is also excellent public
relations for the libraries in the group.
2. Assess Needs of
Health Science Librarians
Staff attended the annual meeting of the Washington
Medical Librarians Association in April, held on the
Bastyr University campus in Kenmore, WA.
3. Network Membership
In this region as of the end of this quarter:
- 156 Full Members -- ORUTUA, Legacy Meridian Park closed due to budget cuts at its institution and ORUORD, Oregon Health and Science University's Van Hassel Dental Library withdrew from DOCLINE because OHSU has consolidated all its ILL operations into the main library, ORUORE -- another result of budget cuts. A third victim of budget cuts, WAUFGD, Kennewick General Hospital's library, lost its staff and withdrew from DOCLINE, but apparently did not close. (Note that this number does not include WAUPNR, which is counted as a full member by DOCUSER because WAUPNR is active in DOCLINE. However, WAUPNR is the LIBID for the NN/LM PNR office.)
- 151 Affiliate Members -- 2 new this quarter: the two Health Information Libraries that PeaceHealth Medical Group operates in Eugene, OR. Although these are both part of the same institution, they were each made Affiliate Members so that each could have its own DOCUSER record, thereby having its own entry in the MEDLINEplus list of consumer health libraries providing service to local residents.
- 159 DOCLINE participants -- ORUTUA, Legacy Meridian Park closed, and ORUORD and WAUFGD withdrew from DOCLINE as noted above. (3 of these are borrow-only libraries and therefore not full members.) (Note that this number omits two Demo Libraries, WAUXXF and AKUXXK, which are "active" DOCLINE participants but are not real accounts; it also omits WAUPNR, which is an active DOCLINE participant but is the LIBID for the NN/LM PNR office.)
- 14 Public Libraries, one of which is a DOCLINE participant (and therefore a full member).
148 SERHOLD participants. (Note that this number omits
the 2 demonstration libraries, WAUXXF and AKUXXK, from
DOCUSER's list of SERHOLD participants.)
The Directory of Health Science Libraries is being
printed and is due for delivery at the end of May,
4. Document
No activity.
5. Resource
Planning began for a meeting with representatives from
the region's Resource Libraries. The meeting will be held
in Seattle in June.
The winter issue of Dragonfly was closed at the end of
March 2003. There were eight original articles. These
included a new series on consumer health outreach
projects, new EFTS members in our region, and a profile
of Gail Kouame, the PNR Consumer Health Coordinator who
started in January 2003. There was also the second part
of an article by Drexie Malone, a U. of Washington
Information School student, describing a usability study
of participants with visual impairment using the NN/LM
PNR Website.
The March issue of Brainstorm, the City of
Seattle's Community Technology E-zine featured the
EthnoMed Project in the "What's Hot" section: http://seattle.gov/tech/brainstorm.
RML staff members participated in conference call for
DOCLINE Coordinators, Consumer Health Coordinators,
Outreach/Education Coordinators, Tribal Connections, and
the the NN/LM Public Library outreach evaluation
initiative, as well as the general monthly conference
There were 244 messages on HLIB-NW, the regional
discussion list. Fifty-seven of these messages, or 29%,
were sent from PNRNews, the official NN/LM PNR
announcement list.
7. Regional Advisory
See the entry under A.5. Resource Libraries.
8. Monitor Region's
Ms. Kouame assisted with facilitating an RML meeting to
discuss implementation of the NLM initiatives focusing on
Public Libraries and the Public Health workforce.
9. User
Attached is an article that appeared in the Clearwater
(ID) Tribune, February 13, 2003, following a
demonstration of MEDLINEplus and PubMed conducted by Ms.
Milgrom. Later in the quarter, Pam McBride, manager of an
IADL-funded project based at Clearwater Valley Memorial
Hospital, forwarded to the RML an e-mail from a physician
who attended the session. Dr. McGrath commented, "The
patient page MEDLINEplus through the NLM is a great
resource in patient care. I probably give patients info
from it 5 -8 times/day. I am glad we got turned onto it
at that meeting."
10. Training
The training facility was used by the NTCC trainers for
PubMed and Gateway classes on March 11 and 12.
Thirty-eight students participated.
11. NLM User/Nonuser Needs
No activity.
No activity.
13. Follow-up with
NLM-funded Projects
In February, Linda Milgrom, Outreach Coordinator, visited
three outreach sites in north central Idaho, accompanying
Pam McBride, manager of an IADL-funded project in the
Orofino area. Ms. Milgrom presented information about NLM
resources at a local hospital, a community technology
center and at the Clearwater Memorial Public
Ms. Milgrom and Ms. Kouame visited Ferry County Memorial
Hospital in Republic, WA, while on an outreach trip to
the north east section of the state in March. This small
frontier hospital is completing an Internet Connections
project funded by NLM. During their visit, Ms. Milgrom
and Ms. Kouame presented an overview of MEDLINEplus,
PubMed, and other NLM resources to an audience of
hospital staff, community members, and the local public
Ms. Milgrom surveyed the project managers of recently
completed projects funded by the RML to learn if
relationships fostered by outreach projects were
sustained and how they reflected on their experiences. We
were also interested in if we should reconsider
procedures and parameters for regional funding
opportunities. The article can be accessed at http://nnlm.gov/pnr/news/200301/fundingreview.html.
The lessons learned by project participants were:
- Work with the community from the very beginning, including when outcomes are defined.
- Offer noontime trainings, offer lunch, make it fun!
- Equipment purchased for outreach has had lasting utility throughout the institution.
- Short duration of outreach projects is beneficial because activities remain focused. (Quarterly reports also help!)
- Conversely, for community-based work, long time frames are required because active members of the community are often over-committed and group dynamics slow down any project.
- Plan evaluation to measure progress "as you go," rather than trying to wrap it all up at the end.
- Find a good contact person/collaborator, someone with power in partner agency.
- Need more money.
- Don't bite off too much.
These findings will drive a modification of the funding opportunities we offer. We are planning to offer a continuum of support -- from needs assessment prior to a full-fledged project to support to assess follow-up -- as well as funding for new directions (e.g., hardware/software for electronic document delivery and professional development).
Date | Location | Sponsor | Activity | Focus |
No. of Attendees
Staff |
02/06/03 | Clearwater, ID | Orofino Public Library | Train | Cons |
Milgrom |
02/06/03 | Clearwater, ID | Clearwater Valley Hospital Library | Train | HP |
Milgrom |
02/06/03 | Idaho County, ID | Kooskia | Train | Cons |
Milgrom |
03/12/03 | Pend Orielle, WA | Stevens County Public Library | Train | HP Cons |
Milgrom Kouame |
03/12/03 | King County, WA | Cross Cultural Health Care Resource Center | Train | HP |
Alyssa Sampson |
03/13/03 | Kettle Falls, WA | Stevens County Public Library | Train | Cons |
Milgrom Kouame |
03/13/03 | Colville, WA | Colville Community Technology Center | Train | Cons |
Milgrom Kouame |
03/13/03 | Onion Creek, WA | Stevens County Public Library | Train | Cons |
Milgrom Kouame |
03/14/03 | Republic, WA | Ferry County Memorial Hospital | Train | HP |
Milgrom Kouame |
03/18/03 | Kitittas County, WA | Kitittas Valley Community Hospital | Train | HP |
Melanie Jones |
03/19/03 | King County, WA | Cross Cultural Health Care Resource Center | Train | HP |
Alyssa Sampson |
03/20/03 | Lapwaii, ID | Nez Perce Tribe Men's Wellness Program | Train | Cons |
Milgrom |
03/24/03 | King County, WA | Cross Cultural Health Care Resource Center | Train | HP |
Alyssa Sampson |
04/01/03 | Thurston County, WA | ESD #113 | Train | HP |
Milgrom |
04/09/03 | Jackson County, Or | SW Oregon AHEC Cyber Health Camp | Train | Cons |
Brendan Ashby |
04/17/03 | Multnomah County, OR | SW Oregon AHEC Cyber Health Camp | Train | Cons |
Brendan Ashby |
04/22/03 | Jackson County, OR | SW Oregon AHEC Cyber Health Camp | Train | Cons |
Brendan Ashby, |
04/22/03 | Jackson County, OR | SW Oregon AHEC Cyber Health Camp | Train | Cons |
Brendan Ashby |
Focus (targeted program area): HP=health professional, Cons=consumer, TA=technology awareness, LI=library improvement, Conn=connections
1. Outreach to Health
Maryanne Blake, Education/Communication Coordinator, was
asked to review and comment on a new Web site for the
Medical Home project based at the University of
Washington. She is also working with the project's staff
to explore ways to promote health information resources
to the Medical Home teams in the state of Washington. On
March 18th Ms. Blake and Ms. Kouame were invited guests
at a Medical Home Project Board of Director's meeting.
Ms. Kouame was able to talk about NLM and the Regional
Medical Library's resources for consumer health
information with meeting attendees. This was advantageous
since the concept of Medical Home relies on both parents
and health professionals working together to care for
children with special health care needs.
Ms. Milgrom taught a hands-on workshop -- Navigating the Web: Internet Resources for School Nurses -- at Educational Service District #113 in Olympia, WA, in April. The invitation to present this workshop came from a nurse who had attended a presentation given by Ms. Milgrom at a school nurses CE class in January.
Mr. Rambo attended the Partners in Information Access for Public Health Professionals steering committee meeting at NLM on March 17.
Mr. Rambo attended the Northwest Regional Public
Health Network steering committee meeting in Seattle on
March 24.
2. Consumer Health
Information Services
Funding for five Electronic Access to Health Information
proposals was awarded effective March 2003. However,
since they had no substantial activity during this
quarter, their individual reports will begin next
quarter. The projects will run for 18 months and will be
monitored by Ms. Kouame.
As part of the Tribal Connections (phase 3) project, Ms. Barnes developed a health information Web site for the Samish tribe in collaboration with the tribal health committee. Priorities that the health committee had established for their tribal health plan provided a framework for a small selection of quality resources that provide useful personal health information. These priority topics include Arthritis and Musculoskeletal Disorders; Cancer; Food and Herbs; Heart Disease, Stroke, and Diabetes; Immunization and Infectious Disease; Mental Health, Substance Abuse, and Tobacco; Oral Health; and Respiratory Disease. (The categories are grounded in the Healthy People 2010 areas of emphasis, with additions to accommodate the community's needs.) MEDLINEplus, healthfinder.gov Just for You: American Indian and Alaska Natives, Easy-to-Read Health and Medical Sites, Information for Elders, Nutrition.gov, and Tox Town round out the offerings, providing a large collection of links for those whose needs or curiosity extends beyond the priority topic selections.
Roy Sahali, Tribal Connections project manager and Community Resources Coordinator, provided technology consultation to the Samish tribe for telephone conversion to Voice-Over-IP and network security upgrades.
Also as part of the Tribal Connections (phase 3) project, Ms. Milgrom and Mr. Sahali were invited to give a presentation on "Finding Accurate Health Information" at the Nimiipuu Health Men's Cancer Awareness and Healthy Lifestyles Conference in Lewiston, ID.
Ms. Kouame arranged with a subcontractor to update the HealthInfoquest Web site, a previously funded project designed to provide librarians with pathfinders to health information. The update was completed in April.
Mr. Rambo planned and chaired monthly conference calls
for the Medical Library Association Task Force on Health
Information Literacy.
3. Training to
Support Electronic Access to Health
Ms. Milgrom and Ms. Kouame traveled to the remote
northeast corner of Washington state. They gave
presentations to public librarians, health professionals,
parents of special needs children, and other consumers in
five towns in three counties.
Quarterly reports from six subcontractors are included with this report. These include --
Final quarterly reports for three that officially end in May 2003:
- CyberCamp, (AHEC of SW Oregon)
- Cross Cultural Resource Center (Cross Cultural Health Care Program)
- Finding It on the Internet: Health Access for Elders (OHSU Resource Library subcontract)
Initial quarterly reports for three that began in December 2002 are also attached. Since these three spent the first weeks dealing with administrative matters, the reports this quarter cover Dec 2002-Apr 2003:
- Central Washington REACH (Washington State University)
- X-plain Vietnamese Breast Cancer Tutorial (Ethnomed, Harborview Medical Center)
- Locating Resources for Children at Risk (Oregon Pacific AHEC)
4. Exhibits and
Presentations at Meetings
The RML and regional colleagues exhibited at the
following national and regional meetings. Exhibit reports
are included in the appendix.
Date | Location | Sponsor | Activity | Focus | No. of Attendees | Staff |
03/19/03 | Seattle, WA | Society for Adolescent Medicine | Exhibit | HP |
Barnes |
03/22/03 | San Francisco, CA | American Academy of Dermatology | Exhibit | HP |
Blake Milgrom Mary Buttner |
04/09/03 | Yakima, WA | Washington Library Association | Exhibit | Cons |
Kouame |
05/14/03 | Albany, OR | "Drugs and Dialogue: A view from the Trenches" | Exhibit | HP |
Karen Bondley |
04/23/03 | Corvallis, OR | Oregon Library Association | Exhibit | Cons |
Rogers |
04/23/03 | Butte, MT | Montana Library Association | Exhibit | Cons |
Bill Kehler |
Focus (targeted program area): HP=health professional, Cons=consumer, TA=technology awareness, LI=library improvement, Conn=connections
National exhibits during the quarter:
- Society of Adolescent Medicine, Seattle WA, Mar 19-22 [Ms. Kouame, Ms. Barnes]
- American Academy of Dermatology, San Francisco CA, Mar 22-25 [Ms. Blake, Ms. Milgrom]
Local/Regional exhibits:
- Washington Library Association, Yakima WA, Apr 9-12 [Gail Kouame]
- Drugs and Dialog: Practical Tools for Pharmacists and Nurses, Albany OR, Apr 11
- Oregon Library Association, Corvallis OR, Apr 24-25 [Liisa Rogers]
- Montana Library Association, Butte MT, Apr 24-25
The Montana Library Assn exhibit was done by Bill Kehler, a network member librarian, funded in part by an RML mini-award. Another network member, Laurel Egan of St. James Hospital in Butte, MT, gave a presentation about MEDLINEplus at the meeting.
The Drugs and Dialog exhibit was done by Karen Bondley of the Oregon Pacific AHEC as part of her RML-funded outreach project.
Ms. Kouame and Ms. Milgrom presented an RML update at
the Washington Medical Library Association annual in
April. They focused on outreach by showing slides and
telling stories from their recent visit to northeast
Washington state.
5. Technology Awareness
and Integration
National exhibits during the quarter:
- Society of Adolescent Medicine, Seattle WA, Mar 19-22 [Ms. Kouame, Ms. Barnes]
- American Academy of Dermatology, San Francisco CA, Mar 22-25 [Ms. Blake, Ms. Milgrom]
Local/Regional exhibits:
- Washington Library Association, Yakima WA, Apr 9-12 [Gail Kouame]
- Drugs and Dialog: Practical Tools for Pharmacists and Nurses, Albany OR, Apr 11
- Oregon Library Association, Corvallis OR, Apr 24-25 [Liisa Rogers]
- Montana Library Association, Butte MT, Apr 24-25
The Montana Library Assn exhibit was done by Bill Kehler, a network member librarian, funded in part by an RML mini-award. Another network member, Laurel Egan of St. James Hospital in Butte, MT, gave a presentation about MEDLINEplus at the meeting.
The Drugs and Dialog exhibit was done by Karen Bondley of the Oregon Pacific AHEC as part of her RML-funded outreach project.
Ms. Kouame and Ms. Milgrom presented an RML update at
the Washington Medical Library Association annual in
April. They focused on outreach by showing slides and
telling stories from their recent visit to northeast
Washington state.
6. Library
No activity.
Mr. Sahali:
- Participated in the winter Affiliated Tribes of Northwest Indians (ATNI) conference in Portland, OR, and provided resource information for a e-health grant and support for the Internet Café.
- In March, met with new consumer health coordinator, Gail Koume, and former consumer health librarian, Nancy Press, regarding her participation in the African American Reach and Teach Health ministry project (AARTH); during that time, we also met with new project manager, Ron Burroughs, to arrange training schedules and web support.
- Negotiated with the Makah Tribe (Neah Bay, WA) to place the MedlinePlus icon on their new intranet health portal. This site will be demonstrated at ATNI-sponsored Visioning Conference II in May.
- Participated in field trip to Yakama Tribe and Heritage College (central WA) as part of a tour sponsored by UW Office of Educational Partnership and Learning Technologies.
- In April, consulted with the Camas Institute regarding the Kalispell tribe's technology project, which was made possible by a TOPs grant from the U. S. Department of Commerce.
The Tribal Connections Internet portal -- www.TribalConnections.org -- continues to be developed to provide wellness information, as well as health careers educational opportunities and other resources for and about American Indian and Alaska Native health issues. Pat Chinn-Sloan, fiscal technician in the PNR office, has taken on the bulk of the Web development and maintenance work, working with Mr. Sahali and with occasional consultation from Michael Boer, Technology Coordinator.
Tribal Connections Phase 3: See also relevant entries under B.2. Consumer Health
Ms. Milgrom, Roy Sahali, Community Resources Coordinator, and Joan LaFrance, project evaluator and chronicler, visited the Nez Perce Reservation in Idaho. They met with community health staff in Lapwai and Kamiah to finalize plans for making short videos on health and wellness topics starring tribal members and to investigate possibilities for training.
Other Tribal Connections: Mr. Sahali provided support to MCR discussions about the TC Four Corners Project. He provided follow-up consulting with Jacarja Pueblo in New Mexico (was part of Phase 2); a referral from Larry Berry, a systems manger with the Indian Health Service.
Miles White, a UW Ph.D. candidate in ethnomusicology, was hired on an hourly basis as editor/writer to assist with the development of the Tribal Connections Web site.
In February, we migrated three NN/LM servers to a new
network subnet featuring gigabit Ethernet, a tenfold
increase in bandwidth. This project involved changing the
IP numbers of Alpha, Bravo, and Charlie, the three
servers. The new subnet is dedicated to housing servers,
so we believe it will be more stable and secure than
subnets shared with labs and staff workstations. The
increased bandwidth is also beneficial to the
The Partners in Public Health website was migrated from a folder on nnlm.gov to its own domain name, PHPartners.org. This site is housed on the same NN/LM servers as nnlm.gov and www.tribalconnections.org.
Michael Boer, Technology Coordinator and NN/LM system administrator worked with other technical coordinators to research improvements in the quality and appearance of the nnlm.gov search engine, htdig. The most visible result of this research is the ability to include subsite templates in the results pages. The first of these new templates was implemented for the PHPartners.org site.
Several content management system (CMS) experiments were conducted to explore the potential for offering Weblog (blog) and Wiki services on the nnlm.gov servers. Some of these prototypes will be presented at the May 2003 NN/LM Web Developers Conference.
Mr. Boer continues to participate in the National Outreach Mapping Center Technical Advisory Committee. In addition to weekly conference calls, his role includes maintaining the NOMC.Role_Assignments table. The NOMC.Projects database was frozen and its contents were transferred to NLM for inclusion in the new Outreach and Consumer Health System.
NN/LM Web Service: |
February | March | April |
71974 | 80390 | 89042 |
89303 | 97313 | 95795 |
NN/LM Web Service: /members/reports/Transmitted |
Year | February | March | April |
2003 | 3121 | 3151 | 3661 |
2002 | 6450 | 6477 | 6761 |
Dr. Fuller and Mr. Rambo attended the mid-year RML
Directors meeting at the New
York Academy of Medicine in February.
Ms. Milgrom, Ms. Blake and Ms. Kouame taught a session of Dr. Sherrilynne Fuller's U. of Washington Information School health sciences class in February. The topic for the session was consumer health information.
A considerable amount of staff time this quarter was spent testing NLM and NOMC reporting forms and systems and inputting or importing records. Several staff members worked on NLM's Outreach and Consumer Health Project Database and NOMC Mapping Applications. Ms. Milgrom tested and entered Outreach Activities Report Forms data for the entire contract period.
Ms. Kouame attended the March NTCC training on PubMed, the NLM Gateway, and ClinicalTrials.gov at the U. of Washington.
Ms. Kouame and Ms. Milgrom attended the outreach evaluation class -- Measuring the Difference -- taught by Catherine Burroughs and Ms. Blake, at the U. of Washington in Seattle, WA, in February.
Dr. Fuller, Ms. Kouame, and Roy Sahali, Community Resources Coordinator, participated in a faculty field trip to the Yakima Valley (in central Washington) focusing on community partnerships, especially with minority institutions. The tour was sponsored by the University of Washington's Office of Educational Partnerships and Learning Technologies.
Mr. Rambo participated on a University of Washington Librarian Peer Review committee throughout March and April.


text:
Cakes By Sauly Cakes By Sauly 1775 W. Lincoln Ave #A, Anaheim, CA 92801 Anaheim, CA Maximum Capacity: 0 people Capacity: 0 people Custom cakes that taste as good as they look because they are baked fresh to order. Weddings, birthd... www.cakesbysauly.com
Dolcissimo Bakeshop Dolcissimo Bakeshop 13855 City Center Drive, Chino Hills, CA 91709 Chino Hills, CA Maximum Capacity: 0 people Capacity: 0 people We bake our goods from scratch throughout the day in small batches so everything is fresh. At Dolcis... www.DolcissimoBakeshop.com
Rockwell's Rockwell's 17853 Santiago Blvd., Villa Park, CA 92861 Villa Park, CA Maximum Capacity: 0 people Capacity: 0 people www.rockwellsbakery.com
ABC Cake Decorating Shoppe and Bakery ABC Cake Decorating Shoppe and Bakery 429 N Tustin St, Orange, CA 92867 Orange, CA Maximum Capacity: 0 people Capacity: 0 people www.abccakes.com
Scrumptious Wedding & Speciality Cakes Scrumptious Wedding & Speciality Cakes 1722 North Tustin Street, Orange, CA 92865 Orange, CA Maximum Capacity: 0 people Capacity: 0 people www.scrumptiousweddingcakes.com
Creative Cakes Creative Cakes 145 North Lemon Street, Orange, CA 92866 Orange, CA Maximum Capacity: 0 people Capacity: 0 people www.creativecakesoc.com
Community featured forum posts Ask a question to the Villa Park, CA Community In need of wedding venue in fullerton, ca or close (Fullerton, CA)(343 views / 2 posts) Last Post by nancy1130084 posted March 9, 2014 Seeking Last Minute Event Space! (Irvine, CA)(181 views / 1 posts) Last Post by ladan1224754 posted August 21, 2014 Campground wedding for a weekend in summer 2015 (Costa Mesa, CA)(766 views / 3 posts) Last Post by btens669854 posted November 14, 2013 Wedding Centerpieces(18149 views / 38 posts) Last Post by etern1398350 posted 3 days ago The First 10 Steps for Wedding Planning(30621 views / 35 posts) Last Post by rkdph801746 posted 10 days ago start a new discussion see more posts
Top Articles featured event planning article Choosing the Right Providers for Your Wedding Posted by admin Planning your wedding can be overwhelming, but taking the time to choose the right venue, caterer, photographer, DJ, and other vendors will help create an unforgettable experience for you and your guests. Consider these tips as you begin your search and learn from the experiences of other brides. Read More
featured event planning article Party Planning 101 Posted by eventective Planning a party can be a very stressful task and many people don't know where to start. Eventective helps walk you through the process and guide your critical decisions. Read More

subset: commoncrawl


text:
- Published: Boston, Mass. : Little, Brown, 2000.
- Year Published: 2000
- Description: [48] p. : col. ill. ; 21 x 26 cm.
- Language: English
- Format: Book
ISBN/Standard Number
- 0316365939 :
Recently Listed On
No tags, currently.Login to add tags
Share This
AADL currently owns no copies of this item
Where To Find It
No copies found.
Additional Details
Youth level.
Puddle teaches his friend Otto the letters of the alphabet so that Otto can write his name.
Reviews & Summaries
Community Reviews
No reviews have been written yet. You could be the first!
Login to write a review of your own.


text:
Back to
main page
Bars, Taverns and Pubs
Cafes and Restaurants
Coffee and Espresso
Coffee Lingo
Web Guides
Wine and Wineries
More Seattle
Seattle Neighborhoods
Capitol Hill
Green Lake
Pioneer Square
Queen Anne
University District
West Seattle
Travel Articles
Maritime Festival
Seafair Torchlight Parade
Washington Travel Regions and Maps
Cascade Mountains
Olympic Peninsula
Puget Sound
San Juan Islands
South Central
Quickly becoming a well-known city for foodies, Seattle's dining scene has something for everyone. Whether you're looking for crispy fish and chips, an exotic meal from Southeast Asia, or a five star rib eye steak, you'll find it in Seattle.
Because of Seattle's close proximity to the water, the city is well known for it's seafood, especially salmon. Grilled, smoked or even raw, you can find salmon prepared every which way on the Seattle dining scene.
Seattle is also known for its international fare, with hundreds of restaurants specializing in food from all over the world. The International district is home to many of these restaurants, but you can find them in every neighborhood of the city.
If you're aiming to impress, Seattle has a number of fine dining restaurants. Many world-renowned chefs own restaurants in Seattle, and most of them are incredibly affordable. A recent Zagat survey placed the average price of a meal out in Seattle below $30 dollars.
It's impossible to walk the streets of Seattle without seeing a coffee shop or espresso stand. Notably the founding place of the most well known coffee brand in the world, many are surprised to learn that Seattle is home to dozens of coffee companies, all with their own taste and style. From lattes to mochas, to grande skinny, triple, extra foam café mistos, the possibilities are endless! Ordering coffee can be a daunting task, but luckily, we have a rundown of "java jargon" so you can sound like a pro: http://www.gonorthwest.com/Washington/seattle/dining/javajargon.htm
If you're feeling thirsty, the Seattle area is home to many microbreweries and wineries. Sip a locally made IPA or freshly corked chardonnay and have some satisfaction in knowing exactly where and how your beverage was brewed, bottled and sold.
Seattleites are well known for their "green" tendencies, and many local restaurants embrace sustainability as a key business practice. Restaurant owners pride themselves on supporting local farms and business, and many go out of their way to include local products on their menus.
Food trucks are also becoming prominent on the Seattle dining scene. Announcing their locations each day through social media, these restaurants on wheels may cost less than a sit down meal, but the food is top notch. Take your pick from hundreds of mouth-watering options, like a savory pulled pork sandwich, southern cooked shrimp and grits, or handmade gelato. Food trucks also a great way to check out the city. Just seek out your favorite truck, grab a bite, and then explore a new neighborhood!
Find where to eat and drink in Seattle by exploring our dining pages.
Go Northwest!
Best selection of books on the Northwest.
Click here!
Signature Tastes of Seattle by Steven W. Siler. This collection of over 140 recipes from restaurants captures the culinary essence of Seattle. Find the authors favorite places through stories, sights and tastes. Order now...
Seattle's Best Dive Bars: Drinking & Diving in the Emerald City by Mike Seely. Read reviews of some of the grittiest, grungiest drinking establishments in the Emerald City. Avoid the tourist traps listed in those "other" bar guides and find out where the anti-globalization, anti-Starbucks, anti-Microsoft crowd goes to get wasted. Order now...
Best Places Seattle by Monica Fischer. Advice on where to dine, stay, and play is included, along with shopping reviews and profiles of three-day getaways. A simple icon system highlights bargain, family-friendly, romantic, and uniquely Seattle spots, while witty sidebars devoted to everything from taco trucks to spas to the gay scene reflect the quirkiness of the Emerald City. Order now...
Plum: Gratifying Vegan Dishes from Seattle's Plum Bistro by Makini Howell. This cookbook features 60 recipes along with photos. Recipes include entrees, soup, salads and desserts from the popular vegan restaurant Plum Bistro. Order now...
Tom Douglas' Seattle Kitchen by Tom Douglas. This cookbook has clear, simple recipes and doubles as a food lover's guide to the best restaurants, ethnic markets and neighborhoods to where to get the best breakfast in Seattle. Order now...
Insider's Guide to Seattle by Shelley Seale. Written by a local, this guide offers a comprehensive listing of all there is to see and do, and where to stay in Seattle. Learn how to live and thrive in the Emerald City and the surrounding area. Order now...
We appreciate your orders. They help keep
Go Northwest! online.
Northwest Books
from . . .
Go Northwest!® gonorthwest.com (tm)
Go Northwest!®
gonorthwest.com (tm) and GoNorthwest.com (tm) are trademarks of Go
Northwest, LLC
All original text, maps, photographs, and other images on this web site, as
well as the compilation and design thereof, are
Copyright © 1997-2015
Go Northwest, LLC. All rights reserved.


text:
No trailer is available
Awesome rhythm level! It is well-made and the gameplay is terrific.
I love that level! I thought the composed music went well with the notes and lighting... unlike many levels like this. I thought that the music was actually really good. If the competition hasn't already revealed the winners, I think you have won it. This was epic, and hard! :-))
Good work!
So much fun! I didn't do as well as I thought I did so I'll have to return and get a better score. Nice work!
Good Luck in the Comp Lambo! :) Got 2nd Place! ^^ Fun :Level, and Amazing Sync with the Song!
too hard


text:
Theatre: Performance
Western Michigan University's theatre performance program offers a wide range of opportunities with focus on vocal and physical development, script analysis and acting theory. It will give you a broad study of the theatre arts, strengthen your performance skills, and provide you with ample opportunities for on-stage experience.
As a theatre performance student, you will take concentrated courses in movement, voice and speech, and scene study. The acting classes cover all genres of theatre and film and are designed with a personalized focus in mind.
Beyond the classroom
If you choose to major in theatre performance at WMU, you will receive varied performance opportunities in the Department of Theatre's nine-show season, which offers experience in three different theatre spaces. On-stage experience is also provided through department-supported, student-directed Footlight productions, directing classes, and the New Play Project offered each summer. Several professional and summer stock companies conduct on-campus auditions, and you will also have the chance to showcase your talent for industry agents and casting directors from New York and Chicago.
After you graduate
Recent WMU graduates with degrees in theatre performance are working as:
- Actors
- Directors
- Voiceover artists
- Casting directors
- Agents
- Producers
- Teachers
Alumni work in the states and abroad in touring productions. They can be seen in:
- Broadway productions
- Films
- Television shows
- Major regional theatres
- Cruise ship productions
Where is this program offered?
- Kalamazoo


text:
Mon-Fri: 7am-1am EST / Sat-Sun: 7am-11pm EST
If you placed an order on ApplianceHelp.com the order is still valid and you can check on its status and make changes here on PartSelect.com. Click here for more details.
ApplianceGeneral Electric Dryer
Level of DifficultyEasy
Time to do repair30 - 60 mins
Age of ApplianceMore than 10 years
Tools Screw driversWrench(Adjustable)
0 out of 1 people found this instruction helpful
Actually, my boyfriend did the repair by taking off the top and back of the dryer to access the drum and belt he replaced the belt and put the dryer back together We are greatful for your service and really happy we didn't have to drive all over to find the part.
Help other customers find the most helpful instructions.
Were these instructions helpful?
Part Number: PS2350043


text:
Love limeade. I'm going to have to find some nice cherries to give this a try.
We have been enjoying these Cherry Limeades so much lately. They're a little bit addicting, but in a good way and they've been great when we have needed a little sweet treat at the end of the day. They'd be a perfect addition to your 4th of July picnic or barbecue this weekend.
Now, don't get this confused with the ever popular Sonic Cherry Limeade. I'm all for ordering one on occasion, but this recipe leaves me feeling just a tad bit less guilty since these homemade slushies don't contain any soda or high fructose corn syrup. Plus, it's supplemented with real fruit pureed with the limeade.
What's so great about this recipe is it's simplicity. One batch of homemade limeade will make you several batches of Cherry Limeade . But, if you really want, you can use an all-natural store bought limeade and then whipping up your very own slushy will only take a second.
We've tried making these slushies with other fruits as well. Get creative with whatever frozen fruit you have stashed away in the freezer. Strawberries were also popular here in our house, but we decided that we like the cherry version best.
If you are a fan of Cherry Limeade, you might also like these Cherry Limeade Cupcakes that I made for a 4th of July celebration a few years ago.
Looking for more 4th of July menu ideas?
Hope all of you in the USA have a wonderful, long weekend. Happy Independence Day!
Cherry Limeade Slushies
Limeade adapted from Strawberry Lemon-Limeade
serves 2 - 4Ingredients:
For the Cherry Limeade Slushies:
2 cups Limeade, recipe follows*
1 - 2 cups crushed ice, according to preference
1 1/2 cups frozen cherriesFor the Limeade:
1 cup sugar
1 cup of water
1 cup fresh lime juice
4-6 cups cold water (according to taste)*alternatively, use all-natural store bought limeade if desired.
For the Cherry Limeade Slushies:
Combine the 2 cups limeade, crushed ice, and frozen cherries in a blender. Start with 1 cup crushed ice and add additional ice until desired slushy-ness is achieved. Puree until blended to slushy consistency. Serve immediately.
For the Limeade
Combine the sugar and 1 cup of water in a small saucepan to make a simple syrup. Cook over medium heat until the sugar has dissolved. Let cool. In a pitcher, combine the simple syrup, lime juice, and cold water. Adjust water according to your sweet taste preferences. Chill.
Love limeade. I'm going to have to find some nice cherries to give this a try.
Those slushies sound awesome! My daughter would love 'em!
Love cherries! These sound wonderful.
that looks so refreshing when it is so hot here!
These drinks look amazing and so refreshing! Happy 4th of July!
These look so good! Perfect for summer
Peel the color skin off fruit and toss into saucepan while making syrup. The flavor is enhanced to a yummy level. Remove the peel after the syrup is cooled. Combine syrup and club soda in a tall glass of ice for a refreshing treat – learned this while in Central America – a mini-vacation in a glass.
These sound absolutely lovely , will try them over the weekend
Cherry Limeades are like my favorite drink ever. I love this!
This looks delicious. We love limeade so a slushie is even more fun.
I love cherry limeade, but as a slushie? Even better! And as cupcakes? I think I just died and went to heaven!
These look so refreshing! Perfect for today!
We just picked cherries last weekend! This will be a wonderful way to enjoy them.
I know these would be a huge hit in our house. The question is: can OxiClean handle it??! Lol, I'll just bib everyone and enjoy.
Where do you get those straws?? I've been looking all over for some cute drinking straws Looks delicious
Heidi – The straws are from Sweet Lulu. Here is the link to the shop: Stripey Straws.
This is so perfect for this weekend. I made Frozen Cherry Mojitos that looked just like these, only mine weren't kid friendly. Madeline is simply adorable.
Yum! I'm all about the fruity drinks this summer! So easy to make and so refreshing.
Wow. These slushies look amazing. I'm sort of addicted to the Sonic limeades, so I'm so glad you posted this recipe. I have only lemons and strawberries at home, so I think I'll make a Strawberry Lemonade Slushie very soon. Thank you!
Happy 4th to you too.
Am I the only one who cant find the cherry limeade slushy recipe that is referenced?
Duh, I found it! Sorry morning coffee hasnt kicked in
Just look at the rich colour. You made great slushies, dear! The combination of cherry and lime juice is fresh and cool!
Oh my goodness, these look SO thick and cold, just the way I like my smoothies. Can't wait to make these!!
Yum! Those slushies look so refreshing! Perfect summer treat!
I love the red color as well as the flavor combination!
How many limes did you need for the 1 cup of fresh lime juice?
It really just depends on the size of the lime and how much juice that lime has. Some limes are drier than others.


text:
Technical Reports |
Version | 24 |
Editors | CLDR committee members |
Date | 2013-09-18 |
This Version | http://www.unicode.org/reports/tr35/tr35-33/tr35.html |
Previous Version | http://www.unicode.org/reports/tr35/tr35-31/tr35.html |
Latest Version | http://www.unicode.org/reports/tr35/ |
Corrigenda | http://unicode.org/cldr/corrigenda.html |
Latest Proposed Update | http://www.unicode.org/reports/tr35/proposed.html |
Namespace | http://cldr.unicode.org/ |
DTDs | http://unicode.org/cldr/dtd/24/ |
Revision | 33 |
This document describes parts of an XML format (vocabulary) for the exchange of structured locale data. This format is used in the Unicode Common Locale Data Repository.
This is a partial document, describing only those parts of the LDML that are relevant for collation (sorting, searching & grouping). For the other parts of the LDML see the main LDML document and the links above.
This document has been reviewed by Unicode members and other interested parties, and has been approved for publication by the Unicode Consortium. This is a stable document and may be used as reference material or cited as a normative reference by other specifications.
A Unicode Technical Standard (UTS) is an independent specification. Conformance to the Unicode Standard does not imply conformance to any UTS.
Please submit corrigenda and other comments with the CLDR bug reporting form [Bugs]. Related information that is useful in understanding this document is found in the References. For the latest version of the Unicode Standard see [Unicode]. For a list of current Unicode Technical Reports see [Reports]. For more information about versions of the Unicode Standard, see [Versions].
The LDML specification is divided into the following parts:
Collation is the general term for the process and function of determining the sorting order of strings of characters, for example for lists of strings presented to users, or in databases for sorting and selecting records.
Collation varies by language, by application (some languages use special phonebook sorting), and other criteria (for example, phonetic vs. visual).
CLDR provides collation data for many languages and styles. The data supports not only sorting but also language-sensitive searching and grouping under index headers. All CLDR collations are based on the [UCA] default order, with common modifications applied in the CLDR root collation, and further tailored for language and style as needed.
The CLDR collation algorithm is an extension of the Unicode Collation Algorithm.
U+FFFE maps to a CE with special minimal weights on all levels, including case, quaternary and identical levels — which may require special code for those levels. Its primary weight is not "variable": U+FFFE must not become ignorable in alternate handling. This allows for Merging Sort Keys within code point space. For example, when sorting names in a database, a sortable string can be formed with last_name + '\uFFFE' + first_name. These strings would sort properly, without ever comparing the last part of a last name with the first part of another first name.
For backwards secondary level sorting, text segments separated by U+FFFE are processed in forward segment order, and within each segment the secondary weights are compared backwards. This is so that such combined strings are processed consistently with concatenating their sort keys.
Contraction matching, as in the UCA, starts from the first character of the contraction string. It slows down processing of that first character even when none of its contractions matches. In some cases, it is preferrable to change such contractions to mappings with a prefix (context before a character), so that complex processing is done only when the less-frequently occurring trailing character is encountered.
For example, the DUCET contains contractions for several variants of L· (L followed by middle dot). Collating ASCII text is slowed down by contraction matching starting with L/l. In the CLDR root collation, these contractions are replaced by prefix mappings (L|·) which are triggered only when the middle dot is encountered. CLDR also uses prefix rules in the Japanese tailoring, for processing of Hiragana/Katakana length and iteration marks.
The mapping is conditional on the prefix match but does not change the mappings for the preceding text. As a result, a contraction mapping for "px" can be replaced by a prefix rule "p|x" only if px maps to the collation elements for p followed by the collation elements for "x if after p". In the DUCET, L· maps to CE(L) followed by a special secondary CE (which differs from CE(·) when · is not preceded by L). In the CLDR root collation, L has no context-sensitive mappings, but · maps to that special secondary CE if preceded by L.
A prefix mapping for p|x behaves mostly like the contraction px, except when there is a contraction that overlaps with the prefix, for example one for "op". A contraction matches only new text (and consumes it), while a prefix matches only already-consumed text.
Note: Matching of discontiguous contractions should be implemented without rewriting the text (unlike in the [UCA] algorithm specification), so that prefix matching is predictable. (It should also help with contraction matching performance.) An implementation that does rewrite the text, as in the UCA, will get different results for some (unusual) combinations of contractions, prefix rules, and input text.
Prefix matching uses a simple longest-match algorithm (op|c wins over p|c). It is recommended that prefix rules be limited to mappings where both the prefix string and the mapped string begin with an NFC boundary (that is, with a normalization starter that does not combine backwards). (In op|ch both o and c should be starters (ccc=0) and NFC_QC=Yes.) Otherwise, prefix matching would be affected by canonical reordering and discontiguous matching, like contractions. Prefix matching is thus always contiguous.
A character can have mappings with both prefixes (context before) and contraction suffixes. Prefixes are matched first. This is to keep them reasonably implementable: When there is a mapping with both a prefix and a contraction suffix (like in Japanese: ぐ|ゞ), then the matching needs to go in both directions. The contraction might involve discontiguous matching, which needs complex text iteration and handling of skipped combining marks, and will consume the matching suffix. Prefix matching should be first because, regardless of whether there is a match, the implementation will always return to the original text index (right after the prefix) from where it will start to look at all of the contractions for that prefix.
If there is a mapping for p|c where c is a single character, and text "...pc...", then the p|c mapping should "win" over any contractions that start with c but do not have the prefix.
Consider the following mappings.
With these, text collates like this:
However, if the mapping p|c → CE(u) is missing, then text "pch" maps to CE(p)CE(d).
The CLDR root collation order is based on the Default Unicode Collation Element Table (DUCET) defined in UTS #10: Unicode Collation Algorithm [UCA]. It is used by all other locales by default, or as the base for their tailorings. (For a chart view of the UCA, see Collation Chart [UCAChart].)
Starting with CLDR 1.9, CLDR uses modified tables for the root collation order. The root locale ordering is tailored in the following ways:
As of Version 6.1.0, the DUCET puts characters into the following ordering:
(There are a few exceptions to this general ordering.)
The CLDR root locale modifies the DUCET tailoring by ordering the common characters more strictly by category:
What the regrouping allows is for users to parametrically reorder the groups. For example, users can reorder numbers after all scripts, or reorder Greek before Latin.
The relative order within each of these groups still matches the DUCET. Symbols, punctuation, and numbers that are grouped with a particular script stay with that script. The differences between CLDR and the DUCET order are:
U+09F4 ( ৴ ) [No] BENGALI CURRENCY NUMERATOR ONE
U+1D371 ( 𝍱 ) [No] COUNTING ROD TENS DIGIT NINE
There are multiple Variable-Weighting options in the UCA for symbols and punctuation, including non-ignorable and shifted. With the shifted option, almost all symbols and punctuation are ignored—except at a fourth level. The CLDR root locale ordering is modified so that symbols are not affected by the shifted option. That is, by default, symbols are not "variable" in CLDR. So shifted only causes whitespace and punctuation to be ignored, but not symbols (like ♥). The DUCET behavior can be specified with a locale ID using the "vt" keyword, to set the Variable section to include all of the symbols below it, or be set parametrically where implementations allow access.
See also:
Ten contractions are added for Tibetan: Two to fulfill well-formedness condition 5, and eight more to preserve the default order for Tibetan. For details see UTS #10, Section 3.8.2, Well-Formedness of the DUCET.
U+FFFE and U+FFFF have special tailorings:
U+FFFF: This code point is tailored to have a primary weight higher than all other characters. This allows the reliable specification of a range, such as "Sch" ≤ X ≤ "Sch\uFFFF", to include all strings starting with "sch" or equivalent.
U+FFFE: This code point produces a CE with special minimal weights on all levels. For details see the CLDR Collation Algorithm above.
UCA (beginning with version 6.3) also maps U+FFFD to a special collation element with a very high primary weight, so that it is reliably non-variable, for use with ill-formed code unit sequences.
In CLDR, so as to maintain the special collation elements, U+FFFD..U+FFFF are not further tailorable, and nothing can tailor to them. That is, neither can occur in a collation rule. For example, the following rules are illegal:
&\uFFFF < x
&x <\uFFFF
The CLDR root collation data files are in the CLDR repository and release, under the path common/uca/.
For most data files there are _SHORT versions available. They contain the same data but only minimal comments, to reduce the file sizes.
Comments with DUCET-style weights in files other than allkeys_CLDR.txt and allkeys_DUCET.txt use the weights defined in allkeys_CLDR.txt.
The file formats may change between versions of CLDR. The formats for CLDR 23 and beyond are as follows. As usual, text after a # is a comment.
This file defines CLDR's tailoring of the DUCET, as described in Section 2, Root Collation .
The format is similar to that of allkeys.txt, although there may be some differences in whitespace.
The format is illustrated by the following sample lines, with commentary afterwards.
[UCA version = 6.0.0]
Provides the version number of the UCA table.
[Unified_Ideograph 4E00..9FCC FA0E..FA0F FA11 FA13..FA14 FA1F FA21 FA23..FA24 FA27..FA29 3400..4DB5 20000..2A6D6 2A700..2B734 2B740..2B81D]
Lists the ranges of Unified_Ideograph characters in collation order. They map to collation elements with implicit (constructed) primary weights.
0000; [,,] # Zyyy Cc [0000.0000.0000] * <NULL>
Provides a weight line. The first element (before the ";") is a hex codepoint sequence. The second field is a sequence of collation elements. Each collation element has 3 parts separated by commas: the primary weight, secondary weight, and tertiary weight. The tertiary weight actually consists of two components: the top two bits (0xC0) are used for the case level, and should be masked off where a case level is not used.
A weight is either empty (meaning a zero or ignorable weight) or is a sequence of one or more bytes. The bytes are interpreted as a "fraction", meaning that the ordering is 04 < 05 05 < 06. The weights are constructed so that no weight is an initial subsequence of another: that is, having both the weights 05 and 05 05 is illegal. The above line consists of all ignorable weights.
The vertical bar ("|") character is used to indicate context, as in:
This example indicates that if U+00B7 appears immediately after U+006C, it is given the corresponding collation element instead. This syntax is roughly equivalent to the following contraction, but is more efficient. For details see the specification of Context-Sensitive Mappings above.
Single-byte primary weights are given to particularly frequent characters, such as space, digits, and a-z. More frequent characters are given two-byte weights, while relatively infrequent characters are given three-byte weights. For example:
... 0009; [03 05, 05, 05] # Zyyy Cc [0100.0020.0002] * <CHARACTER TABULATION> ... 1B60; [06 14 0C, 05, 05] # Bali Po [0111.0020.0002] * BALINESE PAMENENG ... 0031; [14, 05, 05] # Zyyy Nd [149B.0020.0002] * DIGIT ONE
The assignment of 2 vs 3 bytes does not reflect importance, or exact frequency.
# SPECIAL MAX/MIN COLLATION ELEMENTS FFFE; [02, 02, 02] # Special LOWEST primary, for merge/interleaving FFFF; [EF FE, 05, 05] # Special HIGHEST primary, for ranges
The two tailored noncharacters have their own weights.
F967; [U+4E0D] # Hani Lo [FB40.0020.0002][CE0D.0000.0000] * CJK COMPATIBILITY IDEOGRAPH-F967 2F02; [U+4E36, 10] # Hani So [FB40.0020.0004][CE36.0000.0000] * KANGXI RADICAL DOT 2E80; [U+4E36, 70, 20] # Hani So [FB40.0020.0004][CE36.0000.0000][0000.00FC.0004] * CJK RADICAL REPEAT
Some collation elements are specified by reference to other mappings. This is particularly useful for Han characters which are given implicit/constructed primary weights; the reference to a Unified_Ideograph makes these mappings independent of implementation details. This technique may also be used in other mappings to show the relationship of character variants.
The referenced character must have a mapping listed earlier in the file, or the mapping must have been defined via the [Unified_Ideograph] data line. The referenced character must map to exactly one collation element.
copies U+4E0D's entire collation element.[U+4E36, 10]
copies U+4E36's primary and secondary weights and specifies a different tertiary weight.[U+4E36, 70, 20]
only copies U+4E36's primary weight and specifies other secondary and tertiary weights.
FDD1 00A0; [03 02 02, 05, 05] # SPACE first primary starts reordering group FDD1 03A9; [5D 04 02, 05, 05] # GREEK first primary starts reordering group (compressible) FDD1 03E2; [5D 64 02, 05, 05] # COPTIC first primary
These are special mappings with primaries at the boundaries of scripts and reordering groups. They serve as tailoring boundaries, so that tailoring near the first or last character of a script or group places the tailored item into the same group. Beginning with CLDR 24, each of these is a contraction of U+FDD1 with the script sample character, mapping to the first possible primary weight per script or group. They can be enumerated for implementations of Collation Indexes. (Earlier versions mapped contractions with U+FDD0 to the last primary weights of each group but not each script.)
FDD0 0034; [11, 05, 05] # lead byte for numeric sorting
This mapping specifies the lead byte for numeric sorting. It must be different from the lead byte of any other primary weight, otherwise numeric sorting would generate ill-formed collation elements. Therefore, this mapping itself must be excluded from the set of regular mappings. This value can be ignored by implementations that do not support numeric sorting. (Other contractions with U+FDD0 can normally be ignored altogether.)
The DUCET has some weights that don't correspond directly to a character. To allow for implementations to have a mapping for each collation element (necessary for certain implementations of tailoring), this requires the construction of special sequences for those weights. These collation elements can normally be ignored.
Next, a number of tables are defined. The function of each of the tables is summarized afterwards.
# VALUES BASED ON UCA ... [first regular [0D 0A, 05, 05]] # U+0060 GRAVE ACCENT [last regular [7A FE, 05, 05]] # U+1342E EGYPTIAN HIEROGLYPH AA032 [first implicit [E0 04 06, 05, 05]] # CONSTRUCTED [last implicit [E4 DF 7E 20, 05, 05]] # CONSTRUCTED [first trailing [E5, 05, 05]] # CONSTRUCTED [last trailing [E5, 05, 05]] # CONSTRUCTED ...
This table summarizes ranges of important groups of characters for implementations.
# Top Byte => Reordering Tokens [top_byte 00 TERMINATOR ] # [0] TERMINATOR=1 [top_byte 01 LEVEL-SEPARATOR ] # [0] LEVEL-SEPARATOR=1 [top_byte 02 FIELD-SEPARATOR ] # [0] FIELD-SEPARATOR=1 [top_byte 03 SPACE ] # [9] SPACE=1 Cc=6 Zl=1 Zp=1 Zs=1 ...
This table defines the reordering groups, for script reordering. The table maps from the first bytes of the fractional weights to a reordering token. The format is "[top_byte " byte-value reordering-token "COMPRESS"? "]". The "COMPRESS" value is present when there is only one byte in the reordering token, and primary-weight compression can be applied. Most reordering tokens are script values; others are special-purpose values, such as PUNCTUATION. Beginning with CLDR 24, this table precedes the regular mappings, so that parsers can use this information while processing and optimizing mappings.
# Reordering Tokens => Top Bytes [reorderingTokens Arab 61=910 62=910 ] [reorderingTokens Armi 7A=22 ] [reorderingTokens Armn 5F=82 ] [reorderingTokens Avst 7A=54 ] ...
This table is an inverse mapping from reordering token to top byte(s). In terms like "61=910", the first value is the top byte, while the second is informational, indicating the number of primaries assigned with that top byte.
# General Categories => Top Byte [categories Cc 03{SPACE}=6 ] [categories Cf 77{Khmr Tale Talu Lana Cham Bali Java Mong Olck Cher Cans Ogam Runr Orkh Vaii Bamu}=2 ] [categories Lm 0D{SYMBOL}=25 0E{SYMBOL}=22 27{Latn}=12 28{Latn}=12 29{Latn}=12 2A{Latn}=12...
This table is informational, providing the top bytes, scripts, and primaries associated with each general category value.
# FIXED VALUES [fixed first implicit byte E0] [fixed last implicit byte E4] [fixed first trail byte E5] [fixed last trail byte EF] [fixed first special byte F0] [fixed last special byte FF] [fixed secondary common byte 05] [fixed last secondary common byte 45] [fixed first ignorable secondary byte 80] [fixed tertiary common byte 05] [fixed first ignorable tertiary byte 3C]
The final table gives certain hard-coded byte values. The "trail" area is provided for implementation of the "trailing weights" as described in the UCA.
The format for this file uses the CLDR collation syntax, see Section 3, Collation Tailorings.
<!ELEMENT collations (alias | (defaultCollation?, collation*, special*)) >
<!ELEMENT defaultCollation ( #PCDATA ) >
This element of the LDML format contains one or more collation elements, distinguished by type. Each collation contains elements with parametric settings, or rules that specify a certain sort order, as a tailoring of the root order, or both.
Each locale may have multiple sort orders. The defaultCollation element defines the default tailoring for a locale and its sublocales. For example:
To allow implementations in reduced memory environments to use CJK sorting, there are also short forms of each of these collation sequences. These provide for the most common characters in common use, and are marked with alt="short".
The version attribute is used in case a specific version of the UCA is to be specified. It is optional, and is specified if the results are to be identical on different systems. If it is not supplied, then the version is assumed to be the same as the Unicode version for the system as a whole. In general, tailorings should be defined so as to minimize dependence on the underlying UCA version, by explicitly specifying the behavior of all characters used to write the language in question.
Note: For version 3.1.1 of the UCA, the version of Unicode must also be specified with any versioning information; an example would be "3.1.1/3.2" for version 3.1.1 of the UCA, for version 3.2 of Unicode. This was changed by decision of the UTC, so that dual versions were no longer necessary. So for UCA 4.0 and beyond, the version just has a single number.
<!ELEMENT collation (alias | ( import*, settings?, suppress_contractions?, optimize?, cr*, special*)) >
The tailoring syntax is designed to be independent of the actual weights used in any particular UCA table. That way the same rules can be applied to UCA versions over time, even if the underlying weights change. The following illustrates the overall structure of a collation:
<collation> <settings caseLevel="on"/> <cr><![CDATA[ &c < k ]]></cr> </collation>
The following parametric settings are attributes of <settings>. For example, <settings strength="secondary"> will only compare strings based on their primary and secondary weights. In rule syntax, these are of the form [keyword value].
If the attribute is not present, the CLDR default (or the default for the locale, if there is one) is used. That default is listed in bold italics. Where there is a UCA default that is different, it is listed in bold with (UCA default). Note that the default value for a locale may be different than the default value for the attribute, so the defaults here are not defaults for the corresponding keywords.
The Example cells include an LDML example followed by the same example in basic syntax settings attributes as well as rule syntax. In LDML files, parametric settings should be specified via settings attributes, rather than in the rules.
BCP47 Key | Attribute | BCP47 Value | Options | Example | Description |
ks | strength | level1 | primary (1) |
strength = "primary" |
Sets the default strength for comparison, as described in the [UCA]. Note that strength setting of greater than 4 may have the same effect as identical, depending on the locale and implementation. |
level2 | secondary (2) | ||||
level3 | tertiary (3) | ||||
level4 | quaternary (4) | ||||
identic | identical (5) | ||||
ka | alternate | noignore | non-ignorable |
alternate = "non-ignorable" |
Sets alternate handling for variable weights, as described in [UCA], where "shifted" causes certain characters to be ignored in comparison. The default for LDML is different than it is in the UCA. In LDML, the default for alternate handling is non-ignorable, while in UCA it is shifted. In addition, in LDML only whitespace and punctuation are variable. |
shifted | shifted (UCA default) | ||||
n/a | blanked | ||||
kb | backwards | true | on |
backwards = "on" |
Sets the comparison for the second level to be backwards, as described in [UCA]. |
false | off | ||||
kk | normalization | true | on (UCA default) |
normalization = "off" |
If on, then the normal [UCA]
algorithm is used. If off, then all strings that
are in [FCD] and do not contain any
composite combining marks will sort correctly, but others will not
necessarily sort correctly. So should only be set off if the the strings to be compared are in FCD and do not contain any composite combining marks. Composite combining marks are: { U+0344, U+0F73, U+0F75, U+0F81 } [[:^lccc=0:]&[:toNFD=/../:]] (These characters must be decomposed for discontiguous contractions to work properly. Use of these characters is discouraged by the Unicode Standard.) Note that the default for CLDR locales may be different than in the UCA. The rules for particular locales have it set to on: those locales whose exemplar characters (in forms commonly interchanged) would be affected by normalization. |
false | off | ||||
kc | caseLevel | true | on |
caseLevel = "off" |
If set to on, a level consisting only of case characteristics will be inserted in front of tertiary level, as a "Level 2.5". To ignore accents but take case into account, set strength to primary and case level to on. For details, see Section 3.13, Case Parameters . |
false | off | ||||
kf | caseFirst | upper | upper |
caseFirst = "off" |
If set to upper, causes upper case to sort before lower case. If set to lower, causes lower case to sort before upper case. Useful for locales that have already supported ordering but require different order of cases. Affects case and tertiary levels. For details, see Section 3.13, Case Parameters . |
lower | lower | ||||
false | off | ||||
kh | hiraganaQuaternary | true | on |
hiraganaQuaternary = "on"
Controls special treatment of Hiragana code points on quaternary level. If turned on, Hiragana codepoints will get lower values than all the other non-variable code points in shifted. That is, the normal Level 4 value for a regular collation element is FFFF, as described in [UCA], Section 3.6, Variable Weighting. This is changed to FFFE for [:script=Hiragana:] characters. The strength must be greater or equal than quaternary if this attribute is to have any effect. |
false | off | ||||
kn | numeric | true | on |
numeric = "on" |
If set to on, any sequence of Decimal Digits (General_Category = Nd in the [UAX44]) is sorted at a primary level with its numeric value. For example, "A-21" < "A-123". The computed primary weights are all at the start of the digit reordering group. Thus with an untailored UCA table, "a$" < "a0" < "a2" < "a12" < "a⓪" < "aa". |
false | off | ||||
vt | variableTop | See Appendix Q: Locale Extension Keys and Types. | uXXuYYYY (the default is set to the highest punctuation, thus including spaces and punctuation, but not symbols) |
variableTop = "uXXuYYYY" |
The Option value is an encoded Unicode string, with code points in hex, leading zeros removed, and 'u' inserted between successive elements. The BCP47 value is described in Appendix Q: Locale Extension Keys and Types. Sets the string value for the variable top. All the code points with primary strengths less than or equal to that string will be considered variable, and thus affected by the alternate handling. Variables are ignorable by default in [UCA], but not in CLDR. See below for more information. |
kr | reorder | a sequence of one or more reorder codes: space, punct, symbol, currency, digit, or any BCP47 script ID |
reorder = "Grek digit" |
Specifies a reordering of scripts or other significant blocks of characters such as symbols, punctuation, and digits. For the precise meaning and usage of the reorder codes, see Section 3.12, Collation Reordering. | |
n/a | match-boundaries: | n/a | none |
match-boundaries = "whole-word"
n/a |
Defined by Section 8, Searching and Matching of [UCA]. |
n/a | whole-character | ||||
n/a | whole-word | ||||
n/a | match-style | n/a | minimal |
match-style = "medial"
n/a |
Defined by Section 8, Searching and Matching of [UCA]. |
n/a | medial | ||||
n/a | maximal |
Variable Top (vt) bears more explanation. Users may want to include more or fewer characters as Variable. For example, someone could want to restrict the Variable characters to just include space marks. In that case, variableTop would be set to U+1680 (see UCA Variable chart). Alternatively, someone could want more of the Common characters in them, and include characters up to (but not including '0'), by setting variableTop to be U+20BA (in Unicode 6.2; see UCA Common chart).
The effect of these settings is to customize to ignore different sets of characters when comparing strings. For example, the locale identifier "de-u-ka-shifted-vt-0024" is requesting settings appropriate for German, including German sorting conventions, and that '$' and characters sorting below it are ignored in sorting.
<!ELEMENT cr #PCDATA >
The goal for the collation rule syntax is to have clearly expressed rules with a concise format. The CLDR rule syntax is a subset of the [ICUCollation] syntax.
For the CLDR root collation, the FractionalUCA.txt file defines all mappings for all of Unicode directly, and it also provides information about script boundaries, reordering groups, and other details. For tailorings, this is neither necessary nor practical. In particular, while the root collation sort order rarely changes for existing characters, their numeric collation weights change with every version. If tailorings also specified numeric weights directly, then they would have to change with every version, parallel with the root collation. Instead, for tailorings, mappings are added and modified relative to the root collation. (There is no syntax to remove mappings, except via special <suppress_contractions>.)
The ASCII [:P:] and [:S:] characters are reserved for collation
[\u0021-\u002F \u003A-\u0040 \u005B-\u0060
Unicode Pattern_White_Space characters between tokens are ignored. Unquoted white space terminates reset and relation strings.
A pair of ASCII apostrophes encloses quoted literal text. They are normally used to enclose a syntax character or white space, or a whole reset/relation string containing one or more such characters, so that those are parsed as part of the reset/relation strings rather than treated as syntax. A pair of immediately adjacent apostrophes is used to encode one apostrophe.
Code points can be escaped with
escapes, as well as common escapes like
. (For details see the documentation of ICU
UnicodeString::unescape().) This is particularly useful for
default-ignorable code points, combining marks, visually indistinct
variants, hard-to-type characters, etc. These sequences are unescaped
before the rules are parsed; this means that even escaped syntax and
white space characters need to be enclosed in apostrophes. For
The ASCII double quote must be both escaped (so that the collation
syntax can be enclosed in pairs of double quotes in programming
environments) and quoted. For example:
Comments are allowed at the beginning, and after any complete reset,
relation, setting, or command. A comment begins with a
and extends to the end of the line (according to the Unicode Newline
The collation syntax is case-sensitive.
The root collation mappings form the initial state. Mappings are added and removed via a sequence of rule chains. Each tailoring rule builds on the current state after all of the preceding rules (and is not affected by any following rules). Rule chains may alternate with comments, settings, and special commands.
A rule chain consists of a reset followed by one or more relations. The reset position is a string which maps to one or more collation elements according to the current state. A relation consists of an operator and a string; it maps the string to the current collation elements, modified according to the operator.
Relation Operator | Basic Example | Description |
& |
Map Z to collation elements according to the current state. These will be modified according to the following relation operators and then assigned to the corresponding relation strings. |
< |
& a |
Make 'b' sort after 'a', as a primary (base-character) difference |
<< |
& a |
Make 'ä' sort after 'a' as a secondary (accent) difference |
<<< |
& a |
Make 'A' sort after 'a' as a tertiary (case/variant) difference |
<<<< |
& か |
Make 'カ' (Katakana Ka) sort after 'か' (Hiragana Ka) as a quaternary difference |
= |
& v |
Make 'w' sort identically to 'v' |
The following shows the result of serially applying three rules.
Rules | Result | Comment | |
1 | & a < g | ... a <1 g ... | Put g after a. |
2 | & a < h < k | ... a <1 h <1 k <1 g ... | Now put h and k after a (inserting before the g). |
3 | & h << g | ... a <1 h <1 g <1 k ... | Now put g after h (inserting before k). |
Notice that relation strings can occur multiple times, and thus override previous rules.
Each relation uses and modifies the collation elements of the immediately preceding reset position or relation. A rule chain with two or more relations is equivalent to a sequence of "atomic rules" where each rule chain has exactly one relation, and each relation is followed by a reset to this same relation string.
Rules | Equivalent Atomic Rules |
& b < q <<< Q & a < x <<< X << q <<< Q < z |
& b < q & q <<< Q & a < x & x <<< X & X << q & q <<< Q & Q < z |
This is not always possible because prefix and extension strings can occur in a relation but not in a reset (see below).
The relation operator
maps its relation string to the current collation elements. Any other
relation operator modifies the current collation elements as follows.
find the last primary or secondary CE. This CE will be modified; all
following CEs should be removed. If there is no such CE, then reset
the collation elements to a single completely-ignorable CE.
increment the secondary weight.
In all cases, even for
, the case bits are recomputed according to Section 3.13, Case Parameters. (This can be skipped if
an implementation does not support the caseLevel or caseFirst
For example,
maps 'x' to two collation elements. The first one is the same as for
'a', and the second one has a primary weight between those for 'e'
and 'f'. As a result, 'x' sorts between "ae" and "af". (If the
primary of the first collation element was incremented instead, then
'x' would sort after "az". While also sorting primary-after "ae" this
would be surprising and sub-optimal.)
Some additional operators are provided to save space with large tailorings. The addition of a * to the relation operator indicates that each of the following single characters are to be handled as if they were separate relations with the corresponding strength. In the basic syntax, these are expressed by adding a * to the operation.
Relation Operator | Example | Equivalent |
<* |
& a |
& a |
<< * |
& a |
& a |
<<< * |
& p |
& p |
<<<< * |
& k |
& k |
=* |
& v |
& v |
A multi-character relation string defines a contraction.
Example | Description |
& k |
Make the sequence 'ch' sort after 'k', as a primary (base-character) difference |
<!ELEMENT x (context?, ( p | pc | s | sc | t | tc | i | ic )*, extend? ) >
A mapping to multiple collation elements defines an expansion. This
is normally the result of a reset position (and/or preceding
relation) that yields multiple collation elements, for example
A relation string can also be followed by
and an extension string. The extension string is mapped to
collation elements according to the current state, and the relation
string is mapped to the concatenation of the regular CEs and the
extension CEs. The extension CEs are not modified, not even their
case bits. The extension CEs are not retained for following
For example,
maps 'z' to an expansion similar to
. However, the first CE of 'z' is primary-after that of 'a', and the
second CE is exactly that of 'e', which yields the order ae < x
< af < ag < ... < az < z < b.
The choice of reset-to-expansion vs. use of an extension string can
be exploited to affect contextual mappings. For example,
yields a second CE for 'x' equal to the context-sensitive
middle-dot-after-L (which is a secondary CE in the root collation).
On the other hand,
yields a second CE of the middle dot by itself (which is a primary
The two ways of specifying expansions also differ in how case bits
are computed. When some of the CEs are copied verbatim from an
extension string, then the relation string's case bits are
distributed over a smaller number of normal CEs. For example,
yields an uppercase CE and a lowercase CE, but
yields a mixed-case CE (for 'C' and 'h' together) followed by an
uppercase CE (copied from 'E').
In summary, there are two ways of specifying expansions which produce subtly different mappings. The use of extension strings is unusual but sometimes necessary.
A relation string can have a prefix (context before) which makes the mapping from the relation string to its tailored position conditional on the string occurring after that prefix. For details see the specification of Context-Sensitive Mappings.
For example, suppose that "-" is sorted like the previous vowel. Then one could have rules that take "a-", "e-", and so on. However, that means that every time a very common character (a, e, ...) is encountered, a system will slow down as it looks for possible contractions. An alternative is to indicate that when "-" is encountered, and it comes after an 'a', it sorts like an 'a', and so on.
Rules |
& a <<< a | '-' |
Both the prefix and extension strings can occur in a relation. For example, the following are allowed:
< abc | def / ghi
< def / ghi
< abc | def
There are certain circumstances where characters need to be placed before a given character, rather than after. This is the case with Pinyin, for example, where certain accented letters are positioned before the base letter. That is accomplished with the following syntax.
&[before 2] a << à
The before-strength can be 1 (primary), 2 (secondary), or 3 (tertiary).
It is an error if the strength of the reset-before differs from the strength of the immediately following relation. Thus the following are errors.
&[before 2] a < à # error
&[before 2] a <<< à # error
The CLDR table (based on UCA) has the following overall structure for weights, going from low to high.
Name | Description | UCA Examples |
first tertiary ignorable ... last tertiary ignorable |
p, s, t = ignore | Control Codes Format Characters Hebrew Points Tibetan Signs ... |
first secondary ignorable ... last secondary ignorable |
p, s = ignore | None in UCA |
first primary ignorable ... last primary ignorable |
p = ignore | Most combining marks |
first variable ... last variable |
if alternate = non-ignorable p != ignore, if alternate = shifted p, s, t = ignore |
Whitespace, Punctuation |
first regular ... last regular |
p != ignore | General Symbols Currency Symbols Numbers Latin Greek ... |
implicits | p != ignore, assigned automatically | CJK, CJK compatibility (those that are not decomposed) CJK Extension A, B Unassigned |
first trailing ... last trailing |
p != ignore, used for trailing syllable components |
Jamo Trailing Jamo Leading |
Each of the above Names (except implicits) can be used with a reset to position characters relative to that logical position. That allows characters to be ordered before or after a logical position rather than a specific character.
Note: The reason for this is so that tailorings can be more stable. A future version of the UCA might add characters at any point in the above list. Suppose that you set character X to be after Y. It could be that you want X to come after Y, no matter what future characters are added; or it could be that you just want Y to come after a given logical position, for example, after the last primary ignorable.
Each of these special reset positions always maps to a single collation element.
Here is an example of the syntax:
& [first tertiary ignorable] << à
For example, to make a character be a secondary ignorable, one can make it be immediately after (at a secondary level) a specific character (like a combining diaeresis), or one can make it be immediately after the last secondary ignorable.
Each special reset position adjusts to the effects of preceding
rules, just like normal reset position strings. For example, if a
tailoring rule creates a new collation element after
&[last variable]
(via explicit tailoring after that, or via tailoring after the
relevant character), then this new CE becomes the new last
variable CE, and is used in following resets to
[last variable]
[last regular]
is not actually the last normal CE with a primary weight before
implicit primaries. It is used to tailor large numbers of characters,
usually CJK, into the script=Hani range between the last regular
script and the first implicit CE. (The first group of implicit CEs is
for Han characters.) Therefore,
[last regular]
is set to the first Hani CE, the artificial script boundary CE at the
beginning of this range. For example:
&[last regular]<*亜唖娃阿...
[last variable]
indicates the "highest" character that is treated as
punctuation with alternate handling. Unlike the other logical
positions, it can be reset as well as referenced. For example, it can
be reset to be just above spaces if all visible punctuation are to be
treated as having distinct primary values.
Attribute | Options | Example |
variableTop | at |
& x |
after |
& x |
before |
& [before 1] x |
The default value for
[last variable]
is the highest punctuation mark, thus below symbols. The value can be
further changed by using the variable-top setting. This takes effect,
however, after the rules have been built, and does not affect any
characters that are reset relative to the
[last variable]
value when the rules are being built. The variable-top setting might
also be changed via a runtime parameter. That also does not effect
the rules.
<!ELEMENT import EMPTY >
<!ATTLIST import source
<!ATTLIST import type CDATA #IMPLIED
The import command imports rules from another collation. This allows for better maintenance and smaller rule sizes. The source is the locale of the source, and the type is the type (if any). If the source is "locale" it is the same locale. The type is defaulted to "standard".
<import source="de" type="phonebook"/>
Rule Syntax | Sub-Element of collation (preferred) |
[suppressContractions [Љ-ґ]] | <suppress_contractions> [Љ-ґ] </suppress_contractions> |
[optimize [Ά-ώ]] | <optimize> [Ά-ώ]
</optimize> |
The suppress contractions tailoring command turns off any existing contractions that begin with those characters, as well as any prefixes for those characters. It is typically used to turn off the Cyrillic contractions in the UCA, since they are not used in many languages and have a considerable performance penalty. The argument is a Unicode Set.
The suppress contractions command has immediate effect on the current set of mappings, including mappings added by preceding rules. Following rules are processed after removing any context-sensitive mappings originating from any of the characters in the set.
The optimize tailoring command is purely for performance. It indicates that those characters are sufficiently common in the target language for the tailoring that their performance should be enhanced.
The reason that these are not settings is so that their contents can be arbitrary characters.
The following is a simple example that combines portions of different tailorings for illustration. For more complete examples, see the actual locale data: Japanese, Chinese, Swedish, and German (type="phonebook") are particularly illustrative.
<collation> <settings caseLevel="on"/> <cr><![CDATA[ &Z < æ <<< Æ < å <<< Å <<< aa <<< aA <<< Aa <<< AA < ä <<< Ä < ö <<< Ö << ű <<< Ű < ő <<< Ő << ø <<< Ø &V <<<* wW &Y <<<* üÜ &[last non-ignorable] # The following is equivalent to <亜<唖<娃... <* 亜唖娃阿哀愛挨姶逢葵茜穐悪握渥旭葦芦 <* 鯵梓圧斡扱 ]]></cr> </collation>
Collation reordering allows scripts and certain other defined blocks of characters to be moved relative to each other parametrically, without changing the detailed rules for all the characters involved. This reordering is done on top of any specific ordering rules within the script or block currently in effect. Reordering can specify groups to be placed at the start and/or the end of the collation order. For example, to reorder Greek characters before Latin characters, and digits afterwards (but before other scripts), the following can be used:
Rule Syntax | Sub-Element of collation (preferred) | Locale Identifier |
[reorder Grek Latn digit] |
<settings reorder="Grek Latn digit"/> |
en-u-kr-grek-latn-digit |
In each case, a sequence of reorder_codes is used, separated by spaces in the settings attribute and in rule syntax, and by hyphens in locale identifiers.
A reorder_code is any of the following special codes:
It is an error if a code occurs multiple times.
The reordering list is interpreted as if it were processed in the following way.
The locale data may have a particular ordering. For example, the
Czech locale data could put digits after all letters, with
[reorder others digit]
. Any reordering codes specified on top of that (such as with a bcp47
locale identifier) completely replace what was there. To specify a
version of collation that completely resets any existing reordering
to the DUCET ordering, the single code others can be
used, as below.
Locale Identifier | Effect |
en-u-kr-latn-digit |
Reorder digits after Latin characters (but before other scripts like Cyrillic). |
en-u-kr-others-digit |
Reorder digits after all other characters. |
en-u-kr-arab-cyrl-others-symbol |
Reorder Arabic characters first, then Cyrillic, and put symbols at the end—after all other characters. |
en-u-kr-others |
Remove any locale-specific reordering, and use DUCET order for reordering blocks. |
The default reordering groups are defined by the FractionalUCA.txt file, based on the primary weights of associated collation elements. The [top_byte] table contains a mapping from the first (top) byte of primary weights to the associated reordering group. For example:
U+02D0 MODIFIER LETTER TRIANGULAR COLON has a fractional UCA collation weight of [0E 0B, 05, 05]. In the [top_byte] table, the line [top_byte 0E SYMBOL] indicates that 0E maps to SYMBOL.
There are some special cases:
The default reordering groups follow the allkeys_CLDR.txt ordering; they also may be tailored by implementations to different values. For more information on FractionalUCA.txt and allkeys_CLDR.txt, see Collation Auxiliary.
The DUCET ordering is slightly different from the allkeys_CLDR ordering. The reordering groups for the DUCET are not specified here. However, most reordering groups would start with the same characters as in FractionalUCA.txt.
The case level is an optional intermediate level ("2.5") between Level 2 and Level 3 (or after Level 1, if there is no Level 2 due to strength settings). The case level is used to support two parametric features: ignoring non-case variants (Level 3 differences) except for case, and giving case differences a higher-level priority than other tertiary differences. Distinctions between small and large Kana characters are also included as case differences, to support Japanese collation.
The case first parameter controls whether to swap the order of upper and lowercase. It can be used with or without the case level.
Importantly, the case parameters have no effect in many instances. For example, they have no effect on the comparison of two non-ignorable characters with different primary weights, or with different secondary weights if the strength = secondary (or higher).
When either the case level or case first parameters are set, the following describes the derivation of the modified collation elements. It assumes the original levels for the code point are [p.s.t] (primary, secondary, tertiary). This derivation may change in future versions of LDML, to track the case characteristics more closely.
For untailored characters and strings, that is, for mappings in the root collation, the case value for each collation element is computed from the tertiary weight listed in allkeys_CLDR.txt. This is used to modify the collation element.
From a computed case value, set a weight c according to the following.
Compute a new collation element according to the following table. The notation xt means that the values are numerically combined into a single level, such that xt < yu whenever x < y. The fourth level (if it exists) is unaffected.
Case Level | Strength | Original CE | Modified CE | Comment |
on | primary | 0.s.t |
0.0 |
ignore case level weights of primary-ignorable CEs |
p.s.t |
p.c |
secondary or higher |
0.0.t |
0.0.0.t |
ignore case level weights of secondary-ignorable CEs | |
0.s.t |
0.s.c.t |
p.s.t |
p.s.c.t |
off | any | 0.0.0 |
0.0.00 |
ignore case level weights of tertiary-ignorable CEs |
0.0.t |
0.0.4t |
0.s.t |
0.s.ct |
p.s.t |
p.s.ct |
Note the special case weights when s = 0. They ensure the construction of well-formed case and tertiay weights. For details, see Section 3.7, Well-Formed Collation Element Tables in [UCA].
Characters and strings that are tailored have case values computed from their root collation case bits.
Note: Almost all Cased characters have primary (non-ignorable) root collation CEs, except for U+0345 Combining Ypogegrammeni which is Lowercase. All Uppercase characters have primary root collation CEs.
<!ATTLIST collation visibility ( internal | external ) "external" >
Collators have external visibility by default, meaning that they can be displayed in a list of collation options for users to choose from. Collators marked as having internal visibility should not be shown in such a list. Collators are typically internal when they are partial sequences included in other collators.
The main data includes <exemplarCharacters> for collation indexes. See the main document, Section 5.6 Character Elements, for general information about exemplar characters.
The index characters are a set of characters for use as a UI "index", that is, a list of clickable characters (or character sequences) that allow the user to see a segment of a larger "target" list. Each character corresponds to a bucket in the target list. One may have different kinds of index lists; one that produces an index list that is relatively static, and the other is a list that produces roughly equally-sized buckets. While CLDR is mostly focused on the first, there is provision for supporting the second as well.
The index characters need to be used in conjunction with a collation for the locale, which will determine the order of the characters. It will also determine which index characters show up.
The static list would be presented as something like the following (either vertically or horizontally):
In the "A" bucket, you would find all items that are primary greater than or equal to "A" in collation order, and primary less than "B". The use of the list requires that the target list be sorted according to the locale that is used to create that list. Although we say "character" above, the index character could be a sequence, like "CH" above. The index exemplar characters must always be used with a collation appropriate for the locale. Any characters that do not have primary differences from others in the set should be removed.
For example, for index characters
[A Æ B R S {Sch*} {St*} T]
the following sample names are sorted into an index as shown.
The … items are special: each is a bucket for everything else, either less or greater. They are inserted at the start and end of the index list, and on script boundaries. These are really script boundaries, not reordering code boundaries. Each script has its own range, except where scripts sort primary-equal (e.g., Hira & Kana). All characters that sort in the low reordering groups (whitespace, punctuation, symbols, currency symbols, digits) are treated as a single script for this purpose. So if you had a collation that reordered Hebrew after Ethiopic, you would still get index boundaries between the following (and in that order):
If you tailor a Greek character into the Cyrillic script, that Greek character will be bucketed (and sorted) among the Cyrillic ones.
In the UI, an index character could also be omitted or grayed out if its bucket is empty. For example, if there is nothing in the bucket for Q, then Q could be omitted. That would be up to the implementation. Additional buckets could be added if other characters are present. For example, we might see something like the following:
Sample Greek Index |
Contents |
With only content beginning with Greek letters |
With some content before or after |
With numbers, and nothing between 9 and Alpha |
With numbers, some Latin |
Here is a sample of the XML structure:
<exemplarCharacters type="index">[A B C D E F G H I J K L M N O P Q R S T U V W X Y Z]</exemplarCharacters>
The display of the index characters can be modified with the Index labels elements, discussed in the main document, Section 5.6.4 Index Labels .
Special index markers have been added to the CJK collations for stroke, pinyin, zhuyin, and unihan. These markers allow for effective and robust use of indexes for these collations. For example, near the start of the pinyin tailoring there is the following:
<p> A</p><!-- INDEX A -->
<pc>阿呵𥥩锕𠼞𨉚</pc><!-- ā -->
<pc>翶</pc><!-- ao -->
B</p><!-- INDEX B -->
These indicate the boundaries of "buckets" that can be used for indexing. They are always two characters starting with the noncharacter U+FDD0, and thus will not occur in normal text. For pinyin the second character is A-Z; for unihan it is one of the radicals; and for stroke it is a character after U+2800 indicating the number of strokes, such as ⠁. For zhuyin the second character is one of the standard Bopomofo characters in the range U+3105 through U+3129.
The corresponding bucket label strings are the boundary strings with the leading U+FDD0 removed. For example, the Pinyin boundary string "\uFDD0A" yields the label string "A".
However, for stroke order, the label string is the stroke count (second character minus U+2800) as a decimal-digit number followed by 劃 (U+5283). For example, the stroke order boundary string "\uFDD0\u2805" yields the label string "5劃".
Copyright © 2001-2013 Unicode, Inc. All Rights Reserved. The Unicode Consortium makes no expressed or implied warranty of any kind, and assumes no liability for errors or omissions. No liability is assumed for incidental and consequential damages in connection with or arising out of the use of the information or programs contained or accompanying this technical report. The Unicode Terms of Use apply.
Unicode and the Unicode logo are trademarks of Unicode, Inc., and are registered in some jurisdictions.


text:
Holiday Ahhs: Artist Blocks for Land of Nod
Posted by
amanda de beaufort
land of nod is bringing their a-game to the holiday season with a ton of artist collaborations including this one of basswood puzzle blocks. each set forms six different puzzles featuring illustrations by artists.
shop artist collective blocks
No comments:
Post a Comment
Newer Post
Older Post
Subscribe to:
Post Comments (Atom)


text:
Get the Best Priced Jeep J4800 Starter
- Fast Shipping
- 30-Day Money-Back Guarantee
- Lowest Prices
Jeep J4800 Replacement Starter Information
Search our online starter catalog and find the lowest priced discount auto parts on the web. We sell wholesale to the public. We offer high quality new, OEM, aftermarket and remanufactured Jeep J4800 Starter parts. We specialize in a wide-variety of high-quality car parts and accessories for your car, truck or SUV. Call toll free to order or place your order online via our secure checkout system. Our online parts catalog uses real-time inventory, so you can be assured the parts you buy are in stock at the time of ordering. Most orders are shipped the same day. They are available for the following Jeep J4800 years: 1973, 1972, 1970, 73, 72, 70. This part is also sometimes called Jeep J4800 Starters. We stock starter parts for most Jeep models including Grand Cherokee, Wrangler, Cherokee, CJ5, CJ7, Liberty, TJ, Grand Wagoneer, Comanche, Commander, Wagoneer, Compass, Gladiator, Jeepster, CJ6, J10, J20, Patriot, Scrambler, DJ5, Commando, CJ3, J2500, CJ5A, J3500, J4500, J3800, J100, DJ6, J2600, J4600, J2700, J4700, J3600, CJ6A, J2800 and J3700.
We stock these Starter brands for the Jeep J4800: USA Industries, Remy and Pure Energy.
73 1973 Jeep J4800 Alternator 4.2L 6 Cyl Remy
72 1972 Jeep J4800 Distributor Cap 4.2L 6 Cyl Standard Motor Products
72 1972 Jeep J4800 Distributor Rotor 5.9L V8 Standard Motor Products
73 1973 Jeep J4800 Spark Plug Wire Set 4.2L 6 Cyl Standard Motor Products
73 1973 Jeep J4800 Spark Plug 5.9L V8 VIN: N Bosch
I ordered a mirror for my 2000 Altima and got it for 1/2 the price that other online companies were offerering. I also recieved it in a matter of a couple of days. I will definitely order from part...
Very good price. Items arrived quickly.


text:
Melanie Edwards is the publisher of the Modern Mami blog.
Blog Post List
Marissa Mayer & Yahoo Send a Clear (Negative) Message to Employees & Working Parents
March 14, 2013This story originally appeared in the Modern Mami blog. News of Yahoo CEO, Marissa Mayer, eliminating workplace flexibility and forcing all employees to work in the office (even those that were already telecommuting) hit the Internet this past weekend with much backlash. Many people felt her decision negatively affects working parents and destroys chances of moving forward with modern workplace policies. In a time when families are often choosing between work and family and struggling to manage various aspects of life, I have to agree that the decision of Yahoo and their CEO was a bad one...


text:
Quality CareFind out why Mayo Clinic is the right place for your health care. Make an appointment.
Meet the StaffFind a directory of doctors and departments at all Mayo Clinic campuses. Visit now.
Research and Clinical TrialsSee how Mayo Clinic research and clinical trials advance the science of medicine and improve patient care. Explore now.
Visit Our SchoolsEducators at Mayo Clinic train tomorrow's leaders to deliver compassionate, high-value, safe patient care. Choose a degree.
Professional ServicesExplore Mayo Clinic's many resources and see jobs available for medical professionals. Get updates.
Give to Mayo ClinicHelp set a new world standard in care for people everywhere. Give now.
Mayo Clinic offers appointments in Arizona, Florida and Minnesota and at Mayo Clinic Health System locations.
To make this way of eating work for you, let your plate be your guide. Fill half of your plate with veggies, one-quarter with whole grains and the other quarter with a small serving of lean protein. This is a simple way to ensure you have filling, healthy meals.
Need a sweet ending? Try fresh fruit and yogurt as a tasty low-calorie alternative to a slice of pie.
Mayo Clinic is a not-for-profit organization. Proceeds from website advertising help support our mission. Mayo Clinic does not endorse non-Mayo products and services.
Check out these best-sellers and special offers on books and newsletters from Mayo Clinic.