A tool or an option needed

[ron]

In this way, old readers will ignore the \uN keyword and pick up the ANSI representation properly.

So you are saying that Atlantis is an old reader, since it can't understand \u256?

Change the example to \u474 and now even wordpad uses the \u notation. Of course these are followed by ?, so the old readers can put in a question mark for things they don't understand.

With \u474, Polyedit, OpenOffice, Abiword, Wordpad and Copywriter can all open each others files. Now, Atlantis can open none (and display the proper character), and can't make its own file, unless of course \u474 is in some ANSI page.

I don't really think there is any disagreement here, Atlantis is an old reader, at least according to Microsoft.

The point for me is, when I want to put in a character from some unknown (to me) language, I will go use BabelPad (or Character Map) and paste it in from the clipboard. Not possible with Atlantis since it doesn't understand the \u notation. Much simpler than trying to find the correct ANSI page.

[Robert]

Hi,
You are correct, I am partiallly wrong. We disagree on #1, which I consider typing. But I didn't know about #2. You can do it from Wordpad, but not from other word processors that display it.

Greetings–
1. “Type” is short for “typewrite” and means “write using a keyboard or a typewriter”. If you insert characters using a menu, plus a table, plus a language option, you can hardly call it “typewriting”.
2. You can copy a “Latin Capital A with macaroni” from MS WordPad or from MS Word 2003, then paste it into Atlantis. It will display correctly in both cases.

So Atlantis follows the MS standards and specifications. Other so-called “word processors” obviously do not.

I’ll leave you to draw your own conclusions.

On the subject of inserting a “long S” into Atlantis, it cannot be done. Not yet at least. But how many users (even potential users) of Atlantis will ever want to insert a “long S” into one of their documents? Here is an extract from “Why did 18th-century writers use F inftead of S?”, which you will find at http://www.straightdope.com/classics/a1_110.html:

“The Italians often used the long s even when they should have used a short one because letters with long expressive strokes in them made for an artier-looking manuscript. Unfortunately, they also made for a manuscript that was near impossible to read, and it's probably for that reason as much as any that the use of the long s finally died out in the 19th century. The form survived in the formal German script Fraktur until Fraktur itself bit the dust after World War II. (The script had come to be associated with German militarism.) Can't say I'm sad to see it go. Spelling is enough of a crapshoot these days as it is.”

Again, I’ll leave you to draw your own conclusions.

If you are interested in more details about the “long S”, you will find them at http://en.wikipedia.org/w/index.php?title=Long_s

Cheers
Robert

[ron]

2. You can copy a “Latin Capital A with macaroni” from MS WordPad or from MS Word 2003, then paste it into Atlantis. It will display correctly in both cases.

So Atlantis follows the MS standards and specifications. Other so-called “word processors” obviously do not.

I’ll leave you to draw your own conclusions.

But not a \u474. But you can trade it among MS applications. So it is inescapable that Microsoft and you can't both be following the standard.

I'd just like to see a reason why you don't implement the \uN protocol. Possible reasons

1) It is too hard to implement.

2) It is the WRONG thing to do, even though MS and most others seem to do it.

I can understand #1.

I think Atlantis is great. I am shopping around for a word processor and it is the leading candidate. The second thing in my matrix of comparison features is being able to paste from BabelPad, and Atlantis is one of the few failures. I'm just trying to understand why. It seems to be a feature of interest from looking over the forums.

[admin]

Not possible with Atlantis since it doesn't understand the \u notation. Much simpler than trying to find the correct ANSI page.

When a UNICODE character is not followed by its ANSI representation, Atlantis tries to convert it to ANSI itself. For this Atlantis tries to find the ANSI code page containing this UNICODE character. This is not always possible because not every UNICODE character can be converted to ANSI. In addition, the latest build of Atlantis does not cover all the cases when a UNICODE character can be converted to ANSI. A few characters (mainly from the Baltic and Turkish code pages) are not converted by Atlantis from UNICODE to ANSI. The “Latin Capital A with macaroni” actually is a Latvian letter, and it belongs to the Baltic ANSI codepage. It was among those few characters not covered by the current build of Atlantis.

A new build of Atlantis 1.6 is available for download from the Betatesting page. It is able to convert the remaining few characters. But again the RTF documents must include the ANSI representation of characters when possible (it applies to the “Latin Capital A with macaroni” letter too). And if everybody followed the standards, all these workarounds would not be needed.

Atlantis will have a complete support for UNICODE in a not too distant future.

[ron]

But again the RTF documents must include the ANSI representation of characters when possible (it applies to the “Latin Capital A with macaroni” letter too). And if everybody followed the standards, all these workarounds would not be needed.

But Microsoft doesn't itself, since you can't paste even \u256 from Microsoft Character Map into Atlantis.

Atlantis will have a complete support for UNICODE in a not too distant future.

This makes me happy.

Atlantis is a great program. I never expected to find something this good with such a small footprint.

[admin]

But Microsoft doesn't itself, since you can't paste even \u256 from Microsoft Character Map into Atlantis.

You should not expect much from a simple utility.

[Guest]

Atlantis will have a complete support for UNICODE in a not too distant future.

Great! I'm looking forward to uſing it.

Med vennlig hilſen
Sigurd Haſle

[maxqnz]

Atlantis will have a complete support for UNICODE in a not too distant future.

FANTASTIC! Thanks for that great news!

[admin]

The next release of Atlantis (1.6.1) will have the Unicode support. Here is a screen capture of the new "Insert | Symbol..." dialog: