Index » PageStream Support » General » Insert Characters on Amiga 4.1.5.6 |
Sign in to add a comment. | Pages: 1 |
2014-04-04 06:39:36 CT | #1 |
---|---|
Peter Swallow From: United Kingdom Registered: 2006-02-07 Posts: 28 |
Hi, I am trying to enter japanese fonts (kanji) on my Amigaone, using Aozora Mincho .ttf I can enter (insert) individual characters, but I am trying to locate individual kanji and PGS won’t print the font specimen, presumably because it is too large. Everytime I insert 1 character the insert window closes, and I have to re-open it scroll down 8 times and select the next character. All the font characters show a Ctrl-D value, and I thought that would probably be a better way. i have looked at the pagestream documentation web site, and it states that shift ctrl-D should allow me to enter individual characters quicker. But I cannot get shift Ctrl-D to work. I have tried several key combinations, but all I get is alternative’s of character D, or the date prefs, or script window, or preferences. Does anyone have any idea what I am doing wrong? Do I need any particular settings, or other programs installed to get this to work. I am running PGS 4.1.5.6 on a Amigaone G3/800, using OS4.1 update 6. thanks for any help. Peter Swallow (aka Swoop) |
2014-04-04 11:53:52 CT | #2 |
---|---|
admfubar From: Unknown Registered: 2011-11-19 Posts: 198 |
On Fri, 04 Apr 2014 09:39:36 -0400, <peter.ams@virgin.net> wrote:
I have a feeling that shift ctrl d key combos are intercepted by the os first. in linux and KDE certain key combos get os/window manager priority over a program. so it may be happening on the amigaone. Check the amigaone documentation to see if there is a new key combo to do the character insertion. you may want to head over to here http://forum.amigaos.net/ and ask in the forums if anything has changed in the newer versions of amigados
|
2014-04-05 10:15:20 CT | #3 |
---|---|
Anthony Hoffman From: New Zealand Registered: 2007-04-28 Posts: 25 |
Received from peter.ams@virgin.net on 04/04/2014 Hi Peter. > All the font characters show a Ctrl-D value, and I thought that would probably be a better way.
So to insert any character, you first need to find its number. e.g. if I wanted to insert a bullet point as part of the Triumvirate-Normal font: Key: [blank] Key = blank means you cannot insert this character using a single key press, while with some characters you obviously can, e.g. just pressing the A key types an A chr Remember the bu and 8226 codes which are specific to this character in this font. Once you know these codes, you don't need to open the insert window box again. 4. Close the insert window This works fine for me with OS3.9 and PGS v4.1.5.6.
Or you could do as above, but use an Arexx script to globally go through and replace all of the different English neumonics with their respective Kanji character instead of manually replacing them one at a time.
|
2014-04-05 08:11:34 CT | #4 |
---|---|
P. Marquard From: Denmark Registered: 2006-10-29 Posts: 79 |
I know this will not be of any help to
you, for which I apologize.
I have tried many times to make PageStream understand Japanese (kana and kanji) but with no luck what-so-ever. I tried on my Amiga 4000 with no luck (which I can understand, since the good old AOS 3.1 never was much use for Japanese anyways). I have tried on my Windows set-up (which otherwise work very well with Japanese), but with no luck. I can't even copy and paste Japanese into PageStream. I am obviously doing it all wrong. So I wonder - how do you guys get kana and kanji into PageStream? (As I am abroad at the moment and do not have PageStream installed on this machine, I can not test any suggestions right away, but this seemed the right time to ask.) Greetings, Philip Marquard On 04-04-2014 22:39, peter.ams@virgin.net wrote: Hi, |
2014-04-04 19:09:48 CT | #5 |
---|---|
Tim Doty From: United States Registered: 2006-02-06 Posts: 2939 |
A good, informative reply. But I can add just a little: ctrl-d: you do not have to enter all five digits *but* there has to be a way for PgS to know that you are done. For example, if you wanted to insert 8226 followed by a one ctrl-d 8, 2, 2, 6, 1 would not insert the bullet followed by a one. But if you type ctrl-d 8, 2, 2, 6, space — that will insert a bullet character followed by a space. find/replace and fonts: PgS doesn’t care what the font is, the substitution will work just fine no matter your font. However, if the font doesn’t have a glyph for the character then it won’t display the way you want. But if you were to use mnemonics in Times Roman you could use the Find requester to replace things just fine. They wouldn’t display right because Times Roman doesn’t have kanji characters — but all you would need to do is switch to a font that does have the characters. Not a big deal, really. If I was doing this I would do one of two things: 1. use a script to provide an input mechanism. Basically, it would open a dialog, enter the mnemonic and it would insert the desired character. This would be okay for inputting small amounts of text and is what I did for Sumerian cuneiform. 2. use a script to automate the replacing of mnemonics with characters. This would be handy because you could make it somewhat readable by using dashes between mnemonics that should appear without white space between them and the script could strip out the dashes as it encountered them. I guess there is, technically, a third option. A bit more technical and requiring access to a modern font editor. The short of it is that you can define — in the font — character sequences that are replaced by an arbitrary character. Think ligatures and you get the idea. PgS supports this, though there are some issues (reported to Deron, not sure when an update to address them will occur). I did this for a special font that has unusual ligatures (aa, bb, cc, …, in addition to ch, ph, th, sh and some others). In short, you have the *font* do the translation from mnemonic to glyph. Importantly, the typed characters are still there and if you switch the font to something else they are what will be displayed. Its amazing stuff and allows for some really cool things. (Not to mention security implications if you could get a browser to display a URL using a special font…) Tim Doty On Apr 4, 2014, at 4:15 PM, Anthony Hoffman <ahoffman@clear.net.nz> wrote: > Received from peter.ams@virgin.net on 04/04/2014 |
2014-04-04 15:17:22 CT | #6 |
---|---|
Bart Mathias From: United States Registered: 2007-01-13 Posts: 320 |
On 04/05/2014, Anthony wrote: > [...] I have essentially the same problem as Peter (though I'm not sure jsut I just tried your method, more or less. Ctrl-z does nothing, so I go Glyph: uni4F55 I go ahead at this point and click the Insert button, lower left, Typing a string of Japanese writing in PgS is torture. Unfortunately, -- |
2014-04-04 22:24:58 CT | #7 |
---|---|
Tim Doty From: United States Registered: 2006-02-06 Posts: 2939 |
> I just tried your method, more or less. Ctrl-z does nothing, so I go ctrl-z? The discussion has been about ctrl-c (on some platforms a copy command, though in context in PgS it can be used with mnemonics and unicode entry. Ctrl-d is the other contender for entering characters. > I go ahead at this point and click the Insert button, lower left, That’s strange. When I do the same thing I get a y dieresis because although I may select an appropriate font in the dialog it isn’t set in the article and PgS just inserts the character, it doesn’t change the font to match the choice in the dialog. Not sure what the correct behavior there is supposed to be. > Typing a string of Japanese writing in PgS is torture. Unfortunately, I have no idea what Amiga OS does for clipboard and text encoding, but that suggests that the text is getting mangled going through the clipboard. Although in principle a clipboard can be simple, on other platforms it certainly isn’t. There is usually a scheme for having multiple representations of whatever has been copied and the app has to do the right thing to get the right representation. If you get one to four question marks per character then it may well be a problem going from utf-8 to an ascii interpretation. I happened to see recently that Indic uses three bytes per character in UTF-8, I’d have to look to see what happens with Japanese (and it likely depends on whether or not it is kanji or katakana or hiragana). |
2014-04-04 21:39:33 CT | #8 |
---|---|
Bart Mathias From: United States Registered: 2007-01-13 Posts: 320 |
Hello Tim On 04/04/2014, you wrote: > Anthony Hoffman listed it as step 1: Open insert character box >> I go ahead at this point and click the Insert button, lower If you select the y dieresis and change to an appropriate font, you'll >> Typing a string of Japanese writing in PgS is torture. I'm pretty sure kanji is all two-byte code like the 4F55 I mentioned |
Sign in to add a comment. | Pages: 1 |
Index » PageStream Support » General » Insert Characters on Amiga 4.1.5.6 |