Re: Encoding and validation

Laurent Carcone wrote:
> Just to be clear, if you "Save As" a document in Amaya and change the 
> 'Charset' information, Amaya not only change the xml declaration and 
> the meta tag but encode all the characters accordingly.

Some anecdotal evidence...

If I have the screen split showing the source markup (Views > Show 
source or double clicking the pink band) and the focus is in the lower 
split (editing the markup code), File > Save As appears with two fields:
- Document ocation (with browser icon)
- Mime type (drop down menu)

If the focus is on the upper split where the code is rendered, then File 
 > Save As delivers the full range of options, including Charset.

This is generically the same behavior I reported for using the "Show 
parsing errors" button on the lower right corner. When focus is on the 
lower split, no response to clicking the button; when focus is on the 
upper split, the button opens the dialogue box.

Bill B