Re: I can't change the default font in BBedit 10.5.3

[John Delacour]

 
On 30/4/13 at 20:48, dion...@gmail.com (Aethon) wrote:

>Anyone else having this problem? It remains stuck on Conselas
>for BBedit 12 but I want to change it. And after selecting a
>different font, nothing happens.

Are you either clicking the Select button or double-clicking in
the default font box and then choosing the font in the
_system_font_palette_ that comes to the front when you do so?
It works fine in version 10.5.4 (3287).

JD

[William Reveal]

You may have to clear your font cache and have the Mac rebuild it. An old article was at http://discussions.apple.com/thread.jspa?threadID=2462847&tstart=30 but I see Apple has that down right now. I believe if you are using OSX 10.6 and greater you can open the terminal, type 'sudo atsutil databases -remove' then restart your Mac immediately and see if that will help. You can also check out some third party apps like FontNuke but I haven't used them so have no idea if they work.

Bill

On Apr 30, 2013, at 2:48 PM, Aethon <dion...@gmail.com> wrote:

> Anyone else having this problem? It remains stuck on Conselas for BBedit 12 but I want to change it. And after selecting a different font, nothing happens.
>

> -G
>
> --
> --
> You received this message because you are subscribed to the
> "BBEdit Talk" discussion group on Google Groups.
> To post to this group, send email to bbe...@googlegroups.com
> To unsubscribe from this group, send email to
> bbedit+un...@googlegroups.com
> For more options, visit this group at
> <http://groups.google.com/group/bbedit?hl=en>
> If you have a feature request or would like to report a problem,
> please email "sup...@barebones.com" rather than posting to the group.
> Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
>
> ---
> You received this message because you are subscribed to the Google Groups "BBEdit Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to bbedit+un...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[Oliver Taylor]

On May 1, 2013, at 7:24 PM, Aethon <dion...@gmail.com> wrote:

> it's not just the font that's the problem. The other settings (such as width of page text) aren't sticking either.

I've had some problems with font selection in the past. Try moving bbedit's preference files to the desktop (you can always move them back) and restarting bbedit. See if that helps.

[Terry]

Hi,
 I just updated from BBEdit 9 to 11.0, skipping 10, and I seem to be having the same problem. My files are coming up in a font I don't like and I can't seem to change the default. I'd like to try moving the BBedit preference files as suggested here - can someone tell me where to find them? Other suggestions are welcome too, although I'd rather not monkey around with things outside of BBEdit.


On Saturday, May 4, 2013 2:59:05 PM UTC-4, Aethon wrote:

Thanks man.. this is what fixed it.

[Patrick Woolsey]

On 11/7/14 at 10:36 AM, terryk...@gmail.com (Terry) wrote:

>I just updated from BBEdit 9 to 11.0, skipping 10, and I seem
>to be having the same problem. My files are coming up in a font
>I don't like and I can't seem to change the default. I'd like
>to try moving the BBedit preference files as suggested here -
>can someone tell me where to find them? Other suggestions are
>welcome too, although I'd rather not monkey around with things
>outside of BBEdit.

For anyone who encounters this issue (which is due to an OS Font
panel bug), you need not move prefs files nor otherwise monkey
around :-) but just do this:


Please close all open windows within BBEdit, then quit and
relaunch BBEdit, and you should then be able to correctly set
the default font & font size (in the Editor Defaults preference pane).


Regards,

Patrick Woolsey
==
Bare Bones Software, Inc. <http://www.barebones.com/>

[Terry]

Thanks.

[WordWeaver777]

Greetings,

Does anyone know a way to force BBEdit to correctly display CP437 high ASCII characters, such as are used on old-style BBSes?

I normally create my BBS screens in another Mac Classic program, but it is a major strain on my eyes because the canvas in that program is so small. I have also looked at Pablo Draw, but I much prefer to create manually in a regular text editor where I can manually enter the various escape codes.

With BBEdit 11, I have tried switching to ISO Latin 1, ISO Latin 9, Windows Latin 1 and Latin-US (DOS) encoding without success.

These encodings have been used with three fonts which I have used with varying degrees of success to display PC-ANSI graphics in the OS X Terminal app. They are:

ASCII.ttf
dos437
Moder DOS 437

Despite trying a mixture of the above encodings and fonts, I haven't been able to get the CP437 characters to display properly in a BBEdit text file.

Any assistance would be greatly appreciated.

Thanks!

[John Delacour]

On 9 Apr 2015, at 09:56, WordWeaver777 <wordwe...@gmail.com> wrote:

> Despite trying a mixture of the above encodings and fonts, I haven't been able to get the CP437 characters to display properly in a BBEdit text file.

Open the file normally; then do menu: File::Reopen Using Encoding… and select Windows (Latin 1). You can then change the encoding to UTF-8 and save.

JD

[WordWeaver777]

Hello John,

Thanks for the tip. However, I did not meet with success. As per your instructions, I tried Windows (Latin 1), as well as the other aforementioned encodings, and I changed the font several times to the three that I mentioned previously. Again, regardless of which ones I chose, using that menu option did not make any difference. In some cases, a few of the characters displayed properly, but the vast majority did not.


Back to the drawing board.

[Walter Ian Kaye]

At 10:15 p +1000 04/09/2015, WordWeaver777 didst inscribe upon an
electronic papyrus:

>Hello John,
>
>Thanks for the tip. However, I did not meet with success. As per
>your instructions, I tried Windows (Latin 1), as well as the other
>aforementioned encodings, and I changed the font several times to
>the three that I mentioned previously. Again, regardless of which
>ones I chose, using that menu option did not make any difference.
>In some cases, a few of the characters displayed properly, but the
>vast majority did not.
>
>Back to the drawing board.

Do you want to try one more font? I have FoxPrint from the old
FoxPro, which may or may not have the same encoding as the ones you
tried. (It was a FFIL resource fork file, so I just copied it to a
DFONT datafork file; it's a TrueType font.)

In any case, the Latin-type encodings are NOT cp437, so they will not
work with that encoding. Thus the real question is for BBSW: How can
we extend the app with other encodings? Is it user extensible, or
does it require special coding by the BB developers?

-W
PS. I once created my own cp437 font, but it's bitmap only so it's
not recognized by modern OS X apps.

[Rich Siegel]

On Thursday, April 9, 2015, WordWeaver777

<wordwe...@gmail.com> wrote:

>With BBEdit 11, I have tried switching to ISO Latin 1, ISO
>Latin 9, Windows Latin 1 and Latin-US (DOS) encoding without success.

"Latin-US (DOS)" is the system-supplied name for CP437, so that
would be the correct character set to use. It's not guaranteed
that any given font will have the correct glyphs to display the
corresponding Unicode characters, but I would assume that any of
the system-supplied fonts would.

So, then, what constitutes "without success"?

R.
--
Rich Siegel Bare Bones Software, Inc.
<sie...@barebones.com> <http://www.barebones.com/>

Someday I'll look back on all this and laugh... until they
sedate me.

[WordWeaver777]

On Apr 10, 2015, at 3:59 AM, Rich Siegel <sie...@barebones.com> wrote:

"Latin-US (DOS)" is the system-supplied name for CP437, so that would be the correct character set to use. It's not guaranteed that any given font will have the correct glyphs to display the corresponding Unicode characters, but I would assume that any of the system-supplied fonts would.

So, then, what constitutes "without success"?

R.

Hi Rich,

"Latin-US (DOS)" is not shown under "File/ Reopen Using Encoding". Only "Western (ISO Latin 1)",  "Western (ISO Latin 9)" and "Western (Windows Latin 1)" are included there.

If I open a text document in BBEdit, use the status bar at the bottom of the window, and choose "Other" in the encoding list there, then I am shown a longer list of encodings, among which is included "Latin-US (DOS)", which I can then select for that specific document.

However, as I noted earlier, from my research into this -- and web scrounging -- it seems that very few fonts actually contain the full CP437 set of high ASCII characters. I only found three of them:

ASCII.ttf

dos437

Modern DOS 437

All three of the above fonts contain the full set of CP437 high ASCII characters.

Last month I installed all three of these fonts via the Font Book app.

In the OS X Terminal app, in my chosen theme -- Homebrew -- I can use any one of those three fonts, and PC-ANSI graphics will display properly when I visit my BBS, or any other BBS. "ASCII.ttf" definitely works the best of the three for me, in conjunction with other adjustments that I make in my Homebrew settings.

However, as I explained earlier, if I open one of my ANSI graphics files in BBEdit, and choose any of those three fonts, along with the "Latin-US (DOS)" encoding, or any of the others that I mentioned, the high ASCII characters do not display properly.

In other words, when I say "without success" I mean that I do not see these special characters, which, as you know, are what is used to draw PC-ANSI graphics for BBSes, such as mine. I see garbage instead:

Also of note is the fact that control-left bracket -- which is used to make the little arrow that is in front of PC-ANSI color codes -- cannot be used in BBEdit either. When I type that key combination. Nothing happens, and no symbol appears in the document.

I was really hoping that I could do this in BBEdit, because right now I use the Public Address BBS software -- which has a built-in PC-ANSI graphics viewer -- to make all of the graphics for my BBS. As with my BBS software -- Hermes II -- I am forced to run this in a virtual environment using SheepShaver. My vision has been rather poor all of my life, and even more so now that I am in my sixties, so making ANSI graphics in that environment places a real strain on my eyes. I was hoping that by using BBEdit, I could use a larger size font, and thus reduce the strain on my eyes when I make my graphics. In fact, in everyday use, I keep BBEdit set to 24-point Monaco font, because it is large and clear without serifs.

Regards,

Bill Kochman

[Rich Siegel]

On Friday, April 10, 2015, WordWeaver777 <wordwe...@gmail.com>
wrote:

>"Latin-US (DOS)" is not shown under "File/ Reopen Using Encoding".
>Only "Western (ISO Latin 1)", "Western (ISO Latin 9)" and "Western
>(Windows Latin 1)" are included there.

You can adjust which encodings are visible on the menu by using
the Text Encodings preferences. Marking the check box next to
"Latin-US (DOS)" will make it available on the encodings menu.

>If I open a text document in BBEdit, use the status bar at the bottom
>of the window, and choose "Other" in the encoding list there, then I
>am shown a longer list of encodings, among which is included "Latin-US
>(DOS)", which I can then select for that specific document.

If you do that, you are changing the encoding that will be used
when the document is saved to disk. However, since the document
has already been read in using the wrong encoding, selecting the
correct encoding here will not affect it.

So, start by adjusting your encoding settings so that you can
choose Latin-US (DOS) as encoding for Reopen Using Encoding, and
see if that helps.

[WordWeaver777]

On Apr 10, 2015, at 5:54 AM, Rich Siegel <sie...@barebones.com> wrote:

>
> You can adjust which encodings are visible on the menu by using the Text Encodings preferences. Marking the check box next to "Latin-US (DOS)" will make it available on the encodings menu.

Excellent! I should have known to do that!

> So, start by adjusting your encoding settings so that you can choose Latin-US (DOS) as encoding for Reopen Using Encoding, and see if that helps.

Bravo! 90% success rate!

All of the CP437 high ASCII characters are now displaying properly when I open a Public Address document in BBEdit, and choose File/Reopen Using Encoding/Latin-US (DOS) .

The only remaining problem is that the control character -- control-[ -- appears as upside-down Spanish question mark, or some other symbol, depending on which font I use. It is not appearing as the little arrow as it should be, in front of the color codes.

And, as I mentioned before, even with this new method of encoding, neither does anything appear when I type control-[. Without this working properly, I will still not be able to make my ANSI graphics in BBEdit.

We are almost there. Any other suggestions?

Thanks!

Bill

[WordWeaver777]

Rich,

I almost forgot.

I also need control-k to work. Just as occurs when I type control-[, nothing likewise happens when I type control-k.

This key combination is used to make forced pauses in my BBS documents so that a long text file doesn't just keep scrolling beyond 24 rows per screen.

In my ANSI documents, this key combination produces what looks like the symbol for Mars, or the male:

Regards,

Bill

[Patrick Woolsey]

On 4/10/15 at 4:20 PM, wordwe...@gmail.com (WordWeaver777) wrote:

>On Apr 10, 2015, at 5:54 AM, Rich Siegel <sie...@barebones.com> wrote:

[...]

>>So, start by adjusting your encoding settings so that you can choose

>>Latin-US (DOS) [for] Reopen Using Encoding, and see if that helps.

>
>Bravo! 90% success rate!
>
>All of the CP437 high ASCII characters are now displaying properly
>when I open a Public Address document in BBEdit, and choose
>File/Reopen Using Encoding/Latin-US (DOS) .

OK, that's good to hear.

>The only remaining problem is that the control character -- control-[
>-- appears as upside-down Spanish question mark, or some other symbol,
>depending on which font I use. It is not appearing as the little arrow
>as it should be, in front of the color codes.

That's because the character(s) in question are invisible, i.e.
they have no default glyph, and thus you may want to try the
latest BBEdit 11.1 pre-release (that we posted here earlier
today) since it should no longer display the invisible character
marker by default.

>And, as I mentioned before, even with this new method of
>encoding, neither does anything appear when I type control-[.

Since BBEdit makes no special-case treatments for control
characters, you will need to use some global means to insert
such characters, e.g. by typing their code points via the
Unicode Hex Input method, or using the OS Character Viewer
palette, or some similar utility.

Beyond that, since this thread is fast leaving the realm of
discussion for that of support :-), I suggest you follow up with
a note to tech support if you have any further questions.