Mercurial > hg > xemacs-beta
annotate tests/Dnd/README @ 4604:e0a8715fdb1f
Support new IGNORE-INVALID-SEQUENCESP argument, #'query-coding-region.
lisp/ChangeLog addition:
2009-02-07 Aidan Kehoe <kehoea@parhasard.net>
* coding.el (query-coding-clear-highlights):
Rename the BUFFER argument to BUFFER-OR-STRING, describe it as
possibly being a string in its documentation.
(default-query-coding-region):
Add a new IGNORE-INVALID-SEQUENCESP argument, document that this
function does not support it.
Bind case-fold-search to nil, we don't want this to influence what the
function thinks is encodable or not.
(query-coding-region):
Add a new IGNORE-INVALID-SEQUENCESP argument, document what it
does; reflect this new argument in the associated compiler macro.
(query-coding-string):
Add a new IGNORE-INVALID-SEQUENCESP argument, document what it
does. Support the HIGHLIGHT argument correctly.
* unicode.el (unicode-query-coding-region):
Add a new IGNORE-INVALID-SEQUENCESP argument, document what it
does, implement this. Document a potential problem.
Use #'query-coding-clear-highlights instead of reimplementing it
ourselves.
Remove some debugging messages.
* mule/arabic.el (iso-8859-6):
* mule/cyrillic.el (iso-8859-5):
* mule/greek.el (iso-8859-7):
* mule/hebrew.el (iso-8859-8):
* mule/latin.el (iso-8859-2):
* mule/latin.el (iso-8859-3):
* mule/latin.el (iso-8859-4):
* mule/latin.el (iso-8859-14):
* mule/latin.el (iso-8859-15):
* mule/latin.el (iso-8859-16):
* mule/latin.el (iso-8859-9):
* mule/latin.el (windows-1252):
* mule/mule-coding.el (iso-8859-1):
Avoid the assumption that characters not given an explicit mapping
in these coding systems map to the ISO 8859-1 characters
corresponding to the octets on disk; this makes it much more
reasonable to implement the IGNORE-INVALID-SEQUENCESP argument to
query-coding-region.
* mule/mule-cmds.el (set-language-info):
Correct the docstring.
* mule/mule-cmds.el (finish-set-language-environment):
Treat invalid Unicode sequences produced from
invalid-sequence-coding-system and corresponding to control
characters the same as control characters in redisplay.
* mule/mule-cmds.el:
Document that encode-coding-char is available in coding.el
* mule/mule-coding.el (make-8-bit-generate-helper):
Change to return the both the encode-program generated and the
relevant non-ASCII charset; update the docstring to reflect this.
* mule/mule-coding.el
(make-8-bit-generate-encode-program-and-skip-chars-strings):
Rename this function; have it return skip-chars-strings as well as
the encode program. Have these skip-chars-strings use ranges for
charsets, where possible.
* mule/mule-coding.el (make-8-bit-create-decode-encode-tables):
Revise this to allow people to specify explicitly characters that
should be undefined (= corresponding to keys in
unicode-error-default-translation-table), and treating unspecified
octets above #x7f as undefined by default.
* mule/mule-coding.el (8-bit-fixed-query-coding-region):
Add a new IGNORE-INVALID-SEQUENCESP argument, implement support
for it using the 8-bit-fixed-invalid-sequences-skip-chars coding
system property; remove some debugging messages.
* mule/mule-coding.el (make-8-bit-coding-system):
This function is dumped, autoloading it makes no sense.
Document what happens when characters above #x7f are not
specified, implement this.
* mule/vietnamese.el:
Correct spelling.
tests/ChangeLog addition:
2009-02-07 Aidan Kehoe <kehoea@parhasard.net>
* automated/query-coding-tests.el:
Add FAILING-CASE arguments to the Assert calls, making #'q-c-debug
mostly unnecessary. Remove #'q-c-debug.
Add new tests that use the IGNORE-INVALID-SEQUENCESP argument to
#'query-coding-region; rework the existing ones to respect it.
| author | Aidan Kehoe <kehoea@parhasard.net> |
|---|---|
| date | Sat, 07 Feb 2009 17:13:37 +0000 |
| parents | 3ecd8885ac67 |
| children | bc4f2511bbea |
| rev | line source |
|---|---|
| 428 | 1 * Sun May 3 1998 Oliver Graf <ograf@fga.de> |
| 2 | |
| 3 This path contains test code for the new XEmacs | |
| 4 Drag'n'Drop code. | |
| 5 | |
| 6 To test the code do the following: | |
| 7 1) call 'bash droptest.sh' to create the test files in /tmp | |
| 8 2) load and eval droptest.el in XEmacs | |
| 9 3) Try to do some internal DnD by using the sources and targets | |
| 10 in the new buffer | |
| 11 4) Do some external DnD: | |
| 12 4a) OffiX: use files and editor of OffiX | |
| 13 drag something from files or editor into XEmacs | |
| 14 drag something from XEmacs to xv (only with OffiX patch, | |
| 15 editor or files -- files can only move and copy within | |
| 16 itself, cause OffiX is not quite the right thing to do) | |
| 17 4b) CDE: use dtfile and dtpad instead, but here everything should | |
| 18 work. | |
| 19 4c) MSWindows: well, explorer should do. But only file data | |
| 20 should work, and I don't know if the test | |
| 21 already handles this. | |
| 22 | |
| 23 The misc-user-event now also responds as a button-x-event | |
| 24 to the event-* query functions. | |
| 25 | |
| 26 The function of a drag is called dragdrop-drop-dispatch | |
| 27 as you can see in droptest.el. From within the function | |
| 28 you can access the actual misc-user-event through the | |
| 29 current-mouse-event variable. | |
| 30 | |
| 31 Short description of the object part of a drop misc-user-event: | |
| 32 ( TYPE . DATA ) | |
| 33 TYPE is either the symbol dragdrop_MIME | |
| 34 or the symbol dragdrop_URL | |
| 35 | |
| 36 DATA is a list of URL strings if TYPE is dragdrop_URL | |
| 37 if TYPE is dragdrop_MIME DATA is either a string | |
| 38 which contains the MIME data, or it is a list of | |
| 39 ( CONTENT-TYPE CONTENT-ENCODING MIME-DATA ) | |
| 40 CONTENT-TYPE is encoded for tm-view (list, first element type, | |
| 41 rest key.value conses) | |
| 42 CONTENT-ENCODING is a string | |
| 43 MIME-DATA is a string | |
| 44 | |
| 45 CONTENT-TYPE and -ENCODING can be directly supplied to mime/viewer-mode. | |
| 46 |