NISUS Archives

February 2011

NISUS@LISTSERV.DARTMOUTH.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Reply To:
Date:
Sat, 12 Feb 2011 23:27:28 +0900
Content-Type:
text/plain
Parts/Attachments:
text/plain (24 lines)
On 2011-02-12 [+0900 JST], at 9:04 PM, Kino wrote:

> Now, the font names *should* be treated in the same way as NWP's Character palette but I may still miss something important.

And I missed this:

> 		$styleAttr = $style.attributes

should be
		$styleAttr = $style.displayAttributes

but... oup! displayAttributes (Style Object property) seems to be buggy, oh, well.

I explain. If the font is not defined in the current paragraph style nor in the based-on style, your default font defined in NWP's 'Preferences - New File:Format'. And characters not found in the default font are displayed by a substitute font chosen automatically. In such a situation, NWP's Character palette shows the default font name in red or the colour you have set for 'Font substituted' in 'Preferences - Appearance'.

In my understanding, $paragraphStyleObject.displayAttributes should return fontName and fontFamilyName properties at least but it does not. Then, it is impossible for a macro to get the original font name.

I uploaded a new versions of the macros in question but, for the reason explained above, they cannot treat properly substituted a font supplied as the default font in your New File pref settings. Such a font will not be treated as the original and substituted font but as the substituting font.
<http://www2.odn.ne.jp/alt-quinon/files/NWPro/convert/RemapFonts_20110212_nwm.zip> 'rev. 1.2' in the title
<http://www2.odn.ne.jp/alt-quinon/files/NWPro/select/SelectByFont_20110212_nwm.zip>'rev. 2.2' in the title


Kino

ATOM RSS1 RSS2