ETSI's Bug Tracker - Part 01: TTCN-3 Core Language
View Issue Details

ID | Project | Category | View Status | Date Submitted | Last Update
0006727 | Part 01: TTCN-3 Core Language | New Feature | public | 11-04-2014 10:28 | 06-01-2015 18:20

Reporter | Gyorgy Rethy |
Assigned To | Gyorgy Rethy |
Priority | normal | Severity | minor | Reproducibility | have not tried
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | v4.6.1 (published 2014-06) |
Target Version | v4.7.1 (published 2015-06) | Fixed in Version | v4.7.1 (published 2015-06) |
Clause Reference(s) | 6.1.1, B.1.5, but all uses of quadruple shall be checked
Source (company - Author) | L.M.Ericsson

Summary | 0006727: Alternative reference of unicode characters
Description | TTCN-3 today provides only the quadruple syntax to refer to non-ISO646 universal characters. ISO 10646:212 uses other ways of identifying character codes, therefore it become quite difficult for the user to calculate the quadruple from the character code and vice versa. More ISO 10646-conformant syntax(es) should be added to TTCN-3 to make the life of testers easier.
Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files | CR6727_v1.docx (60,213) 19-06-2014 16:23 http://oldforge.etsi.org/mantis/file_download.php?file_id=3060&type=bug CR6727_v2.docx (69,313) 30-06-2014 11:02 http://oldforge.etsi.org/mantis/file_download.php?file_id=3076&type=bug CR6727_v3.docx (71,720) 07-10-2014 09:05 http://oldforge.etsi.org/mantis/file_download.php?file_id=3088&type=bug

Issue History
Date Modified | Username | Field | Change
11-04-2014 10:28 | Gyorgy Rethy | New Issue |
17-06-2014 10:59 | Gyorgy Rethy | Assigned To | => Axel Rennoch
17-06-2014 10:59 | Gyorgy Rethy | Status | new => assigned
19-06-2014 11:15 | Axel Rennoch | Note Added: 0012139 |
19-06-2014 11:18 | Axel Rennoch | Assigned To | Axel Rennoch => Gyorgy Rethy
19-06-2014 11:19 | Axel Rennoch | Note Added: 0012140 |
19-06-2014 11:19 | Axel Rennoch | Status | assigned => confirmed
19-06-2014 16:23 | Tomas Urban | File Added: CR6727_v1.docx |
19-06-2014 16:24 | Tomas Urban | Note Added: 0012155 |
30-06-2014 11:02 | Gyorgy Rethy | File Added: CR6727_v2.docx |
30-06-2014 11:09 | Gyorgy Rethy | Note Added: 0012197 |
30-06-2014 11:09 | Gyorgy Rethy | Assigned To | Gyorgy Rethy => Axel Rennoch
30-06-2014 11:09 | Gyorgy Rethy | Status | confirmed => assigned
30-06-2014 11:09 | Gyorgy Rethy | Status | assigned => confirmed
30-06-2014 11:10 | Gyorgy Rethy | Note Edited: 0012197 | bug_revision_view_page.php?bugnote_id=12197#r65
07-10-2014 09:05 | Axel Rennoch | File Added: CR6727_v3.docx |
07-10-2014 09:06 | Axel Rennoch | Note Added: 0012244 |
07-10-2014 09:06 | Axel Rennoch | Assigned To | Axel Rennoch => Gyorgy Rethy
07-10-2014 09:06 | Axel Rennoch | Status | confirmed => assigned
07-10-2014 09:07 | Axel Rennoch | Status | assigned => resolved
07-10-2014 09:07 | Axel Rennoch | Resolution | open => fixed
06-01-2015 18:20 | Gyorgy Rethy | Note Added: 0012648 |
06-01-2015 18:20 | Gyorgy Rethy | Status | resolved => closed
06-01-2015 18:20 | Gyorgy Rethy | Fixed in Version | => v4.7.1 (published 2015-06)

Notes

(0012139)
Axel Rennoch
19-06-2014 11:15

Following ISO10646:2012 section 6.2 characters can be represented by a (six digit) integer between 000000 and 10FFFF to identify its code point. For BMF plane leading '00' and for other defined planes leading '0' may be omitted.
The following notation has been proposed for "short identifiers for code points" (UIDs):
{ U | u } {+}(xxxx | xxxxx | xxxxxx)
where “x” represents one hexadecimal digit (0 to 9, A to F, or a to f).
In addition section 6.6 proposes a syntax for sequences of code points by the following BNF:
“<” (xxxx | xxxxx | xxxxxx) ((“,” space?) (xxxx | xxxxx | xxxxxx))+ “>”
where “x” represents one hexadecimal digit (0 to 9, A to F, or a to f).
It is proposed to adapt this syntax in TTCN-3 to address code points, e.g.:
char(U0054 U0054 U0043 U004E)
char(U000054 U000054 U000043 U00004E)
char(U000054, U000054, U000043, U00004E)

(0012140)
Axel Rennoch
19-06-2014 11:19

first proposal to express UCS characters

(0012155)
Tomas Urban
19-06-2014 16:24

Formal proposal uploaded, please check.

(0012197)
Gyorgy Rethy
30-06-2014 11:09 (edited on: 30-06-2014 11:10)

See version CR6727_v2.docx. In general: technically fine with me. Some small comments: - added changes to pattern matching (in quadruple metacharacter both formats allowed); - actually, we are deviating so much from UID that I found it better not to call our new format USI and UID.

(0012244)
Axel Rennoch
07-10-2014 09:06

final check: - addition of two abbreviations - one typo correction upload of final version v3

(0012648)
Gyorgy Rethy
06-01-2015 18:20

Added to draft V4.6.3