Sorry, I must not follow.
According to TR 29 spec :
Do not break after ambiguous terminators like period,
if they are immediately followed by a number or lowercase letter, if they
are between uppercase letters, if the first following letter (optionally
after certain punctuation) is lowercase, or if they are followed by “continuation”
punctuation such as comma, colon, or semicolon. For example, a period may
be an abbreviation or numeric period, and thus may not mark the end of
a sentence.
SB6. ATerm × Numeric SB7.
Upper ATerm × Upper SB8. ATerm Close*
Sp* × ( ¬(OLetter | Upper | Lower | Sep | CR | LF | STerm | ATerm) )* Lower
SB8a. (STerm | ATerm) Close* Sp* ×
(SContinue | STerm | ATerm)
Does this not allow one to define tailoring
rules for abbreviations? There is also ability to specify acronyms. Same
for things like hyphens, apostrophes, quotation marks, and colon. Perhaps
I am missing something very obvious here?
Note ATerm is a terminator character
in this case, e.g. period.
From:
Yves Savourel <>
To:
Helena S Chapman/San
Jose/IBM@IBMUS, "'Rodolfo M. Raya'" <>
Cc:
"'Peter Reynolds'"
<>, <>
Date:
03/29/2011 11:03 AM
Subject:
RE: [xliff]
OSCAR committee
Hi Helena,
In short: SRX adds to
TR29.
TR29 defines breaks only
based on characters, while SRX let you specify things like abbreviations,
acronyms, and many other things that cannot be specified with TR29.
Cheers,
-yves
From: Helena S Chapman [mailto:]
Sent: Tuesday, March 29, 2011 8:50 AM
To: Rodolfo M. Raya
Cc: 'Peter Reynolds';
Subject: RE: [xliff] OSCAR committee
I don't quite understand the purpose of having
both SRX and Unicode TR29(http://www.unicode.org/reports/tr29/).
I haven't been around long enough to understand the history and politics.
Why both?
From: "Rodolfo
M. Raya" <>
To: "'Peter
Reynolds'" <>, <>
Date: 03/29/2011
09:08 AM
Subject: RE:
[xliff] OSCAR committee
Hi Peter,
LISA is shutting down and OSCAR work will cease as is. Before work on LISA’s
standards (TMX, TBX, SRX, etc.) continues somewhere else, LISA has to release
those standards to public domain. Those open standards are free to use
but LISA owns copyright and trademarks.
I would like to continue working on SRX and TMX under OASIS’ umbrella,
but that should happen on new TCs if ever happen.
LISA/OSCAR standards are outside our charter. However, nothing stops us
from modifying the charter and adopting TMX and SRX (or clones) as complementary
tools for XLIFF.
Best regards,
Rodolfo
--
Rodolfo M. Raya <>
Maxprograms http://www.maxprograms.com
From: Peter Reynolds [mailto:]
Sent: Tuesday, March 29, 2011 9:55 AM
To:
Subject: [xliff] OSCAR committee
Hi Bryan, All,
I guess we are having a call today but I have yet to see the notice.
Can we discuss the OSCAR group and the LISA standards at this meeting.
My understanding is the LISA would like another standards body to take
over some or all of the standards the OSCAR group was working on. Can I
suggest we discuss this today and maybe have a joint meeting with those
who have been involved in OSCAR to look at what they would like to see
happen and what our TC and OASIS can do.
Thanks,
Peter.
Peter Reynolds
CEO & Translation Management Consultant
tel. +48
22 4808 806
Mobile +48 503 154 766
fax +48 22 3305 207
Skype: preynolds1
e-mail:
TM-Global
A MAart business
No.3, Kopernika St.
00-367 Warsaw
Poland
http://www.tm-global.com
The email transmitted is intended only for use by the addressee. The information
it contains is confidential and may be legally privileged. Access to this
email by anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted to
be taken in reliance on it, is prohibited.
