Handleiding Kompozer 07 (pagina 51 van 58) (Engels)

606646

Verklein

Vergroot

Pagina terug

1/58

Pagina verder

KompoZer User Guide — 17 December 2007 Based on version 0.7.10 51

The output code for ASCII characters is the charac-

ter code, for all characters for which an entity exists is

the entity else it is a decimal numeric character refer-

ence.

Final option

The final option should output decimal numeric

character reference for all non-ASCII characters but

has a bug so that it uses a mixture of character codes

(for ASCII characters) and entities or numeric referenc-

es for others.

Note The output will always produce valid and

operating code for the corresponding character

so files run correctly. With KompoZer 0.7.10, for

all options, there are a few detailed non-compli-

ances with the above description.

The options provided may be useful during develop-

ment if you work in source code and may make it easier

for you to read. They may also be required if transfer-

ring source code to some other applications. If, for

instance, your file was encoded as UTF-8 and you

wanted to transfer the content to an application which

could accept only text the fourth option would be useful.

This ensures that only ASCII characters appear in

the file. Unfortunately this is one option that does not

work in KompoZer 0.7.10

Note. In source view you may enter characters

using any of these systems irrespective of the

option selected. After leaving and re-entering

source view, the display will conform to the

option selected and not to the form in which it

was entered.

In Normal and Preview mode KompoZer will attempt

to render all characters correctly, irrespective of the

option selected, subject to the limitations described

under ‘Unicode support’ above.

If you need an ascii only file an alternative way to

obtain one is via the File > Save and change Character

Encoding menu item. Check the ‘Export to text’ box

and save the file as text. The original file remains

intact. Again with UTF encoding this appears to be

faulty but if the encoding is temporally switched to

ISO-8859-1 it works.

A6.4.1.2 Don't encode > outside of attribute values

This is explained under the first option above.

The section on ‘Preferences’ suggests that this be

left in the default, cleared, state but this is optional.

A6.4.2 Encoding in attribute values

One final option in Tools > Preferences > Advanced

provides the option ‘Don’t encode special characters in

Attribute values’. That is not a very precise definition of

what happens because the whole page must be encod-

ed in the same way. What it changes is the way in

which character references are used in attribute values.

When you check the box, special characters appear-

ing in the value of any attribute will be left untouched

and not encoded as entities or numerical character

references.

A6.4.2.1 Don't encode special chrs in attribute values

An example will serve to illustrate.

The table element has an attribute 'summary' and

might appear as:

The attribute is ‘summary’ and the value is ‘Resumé

of results’. If the characters were encoded as entities

the source would read

Even worse if the characters were encoded as nu-

meric character references the source would read

Any readout on the screen, whether through a

properties inspector or at the bottom of the browser

window, will be normal but those doing lot of work in

source view might prefer not to encode in this situation.

You are recommended to check the box ‘Don't

encode special characters in attribute values’ un-

less you have good reason to do otherwise.

Where the attribute value is a URL a different

encoding method is covered in the following section.

A6.5 URL encoding

A6.5.1 Percentage encoding

Special considerations apply to characters in a URL.

URLs can occur as the value of an attribute to many

elements the most common being the ‘href’.

Any Latin 1 character may occur in a URL but only

those shown against a green background in Table

A6.5-1 may be used freely. This set includes alphabet-

ics, hyphen and underscore. A number of other charac-

ters which may have specific meanings are reserved.

This includes the majority of the remaining ASCII

characters. Such characters may be used to separate

one part of the structure from an other e.g the colon

separates the protocol from the domain. These charac-

ters, from current specifications, are shown against an

orange background. Whenever such a character is

used other than for the specific reserved purpose it

must be encoded to avoid confusion. Use of the remain-

ing characters depends on specifics of the URL or part

of the URL involved.

When encoding is required in a URL a new method

referred to as ‘percentage encoding’ is used. Put simply,

percent encoded characters consist of a percentage

sign followed by two characters representing the hexa-

decimal position of the character in the Latin 1 set.

Thus %20 represents a space.

x0 x1 x2 x3 x4 x5 x6 x7 x8 x9 xA xB xC xD xE xF

! “ # $ % & ‘ ( ) * + , - . /

0 1 2 3 4 5 6 7 8 9 : ; < = > ?

A B C D E F G H I J K L M N O I

P Q R S T U V

X Y Z [ \ ] ^ _ I

` 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 { | } ~

shy

® ¯

° ± ² ³ ´ µ ¶ · ¸ ¹ º » ¼ ½ ¾ ¿

À Á Â Ã Ä Å Æ Ç È É Ê Ë Ì Í Î Ï

Ð Ñ Ò Ó Ô Õ Ö × Ø Ù Ú Û Ü Ý Þ ß

à á â ã ä å æ ç è é ê ë ì í î ï

ð ñ ò ó ô õ ö ÷ ø ù ú û ü ý þ ÿ

Table A6.5.1

Characters permissible in a URL

Kompozer 07 Handleiding

Hulp nodig? Stel uw vraag in het forum

Misbruik melden

Product:

Spelregels forum

Abonneren

Ontvang uw handleiding per email

Stel vragen via chat aan uw handleiding

Andere handleiding(en) van Kompozer 07

Uw handleiding is per email verstuurd. Controleer uw email

Er is een email naar u verstuurd om uw inschrijving definitief te maken.

U heeft geen emailadres opgegeven

Uw vraag is op deze pagina toegevoegd

Info