Xtermfont: -fixed-18- This informs xterm to use the fixed font at size 18. Append a line to the file such as. Xresources to store your preferences for various X programs. If you dont already have one, create a file in your home directory named.Run OS X Disk Utility to repair disk permissions on your HD Shut Down the Mac, wait a few minutes before starting up. This preference has been available since at least 10.4.6, but I don't know how long before that.Launch OS X Font Book to Resolve Duplicate Fonts & Validate Fonts delete, not just disable, any bad fonts or duplicates. Next select 'Te' in the first instance of 'Test' in your demonstration document text, and step through the code again.I just discovered, to my great relief, that TextEdit can convert rich text constructed using the native Cocoa text, font, and style features (including lists and tables) to well-formed HTML by selecting the proper setting in the Open and Save tab of TextEdit's Preferecnes window.
Word insists on inserting invalid - or simply overly heavy-handed - CSS styles in order to produce HTML that matches the look and feel of the original Word document, and to my knowledge, it provides no way to bypass this. All main headings use the new font, even the red heading: the direct style doesn't specify a font so the font setting comes through from the base style.Any of you who've struggled with converting Word documents to HTML over the years know what a pain it has been. 2) Modify the 'Heading 1' style to use a different font. ![]() However, unlike those apps, the surprisingly powerful TextEdit provides some very handy, simple options to produce clean HTML when you need that. That's probably because in its default mode, it is. You don't need to export the file to RTF or HTML or whatever from the application in question.Until yesterday, I thought TextEdit's HTML conversion ability was on a par with that of Word and Pages. If you do the same, you'll find that you can build tables, lists, and any other text you like in such an application and then, if you need to convert it to HTML, simply copy and paste it into TextEdit. (For any geeks among you who'd like to learn more about the Cocoa text system, here's a link to get you started.)Yes, there are many native HTML editors for the Mac that can do this as well - which don't likewise introduce extraneous code - but I was delighted to find I could basically develop HTML in any native Cocoa app as well! For example, I currently do a lot of data entry in DevonThink Pro, which - like SohoNotes, Journaler, Yojimbo, Curio, VoodooPad, and many others - enables word processing through the native Cocoa toolset. But I wouldn't want to do that on a regular basis!Instead, what I discovered is that if you work in a native Cocoa application like TextEdit using only the tools Apple provides for word processing (which admittedly take some getting used to, and handle only basic formatting needs - much like basic HTML itself), you can easily work in a WYSIWYG mode and then convert the file to clean HTML that you won't be embarrassed to call your own. Note that this will strip all font and style information from the file, except for the basics like bold and italics. Change Styling to No CSS. Change Document Type to either HTML 4.01 Strict or XHTML 1.0 Strict, depending on whether you want your code to be XHTML compliant or not. Open TextEdit's Preferences and select the Open and Save tab. (Hint: TextEdit provides an Application Service (New Window Containing Selection) in the Services menu for this once you select the text in the originating app.) Copy and paste your Cocoa-formatted text into a new TextEdit document. The only 'bad' thing I noticed was that the Cocoa HTML Writer that does the conversion still uses for boldface rather than the 'correct'. If you examine the source code, you'll see nothing but simple, pure HTML (or XHTML). Then, change the File Format selection to HTML, and click Save.Now, when you click on your new HTML file in the Finder, it will open with your default web browser. In the Save As dialog box, give your file a name and hard disk location. I don't know how many times I've tried to drive home to developers the point that we want to leave fonts and other "how it looks" issues in the hands of the IMporting application. Quite often we don't want to move the WYSIWYG formatting to another document, we just want to move HTML or character/paragraph styles along with the text. (I'm looking at you Microsoft.) Give them a simple problem, and they'll make it more complicated to create a challenge and add job security.Llscots is right. This is going to be a real time-saver for me, since it'll let me format lists and tables in any Cocoa app and not have to worry about how I'm going to convert the data to HTML later on!Sigh, this is a classic problem with all too many programmers, or at least those in the paid, corporate world. Google drive for mac not logging in sending to enable or disable cookiesThey could hire probably hire a bright 12-year-old who could code that.And that's the problem. All I want are character and paragraph style tags (which could also be HTML tags). And yes, it can also export in XML now, but importing XML into InDesign is poorly documented and needlessly complex. And that's a small company that I talked with over and over about the need to export the styles they're so proud of inside their application. I gave up getting it when I discovered that Mellel's rtf export strips out Mellel's styles and just created raw, highly formatted text. I almost had a book go to print with some weird, brief passages in Times Roman (the virus font) that Word didn't strip out when it exported rtf and that InDesign didn't strip out when it imported rtf.Earlier this week I evalutated Mellel, a lightweight but powerful word processor that makes very effective use of styles. InDesign's interchange format for paragraph style names is almost identical to HTMLs. For simply transfering style names, that's a trivial task. On export it writes those tags out in a form other applications understand, HTML for the web, RTF for Word, MIF for Framemaker, IDIF for InDesign and so forth. It's much more fun to muck about with all sorts of complex coding to recreate the "look and feel."What we need is a text editor that simply tags text, tagging both paragraphs and sections of text (i.e. That'd let us interchange documents in HTML, Word, InDesign, Framemaker or whatever without having to cut out a lot of useless formatting clutter. Heading 1 in Word/RTF on import, could become H1 for HTML on export. This application could also be smart enough to change styles names between import and export.
0 Comments
Leave a Reply. |
AuthorSandra ArchivesCategories |