Everything’s gone FUBAR
-
-
A google search says: FUBAR is an acronym that originated in the military to stand for the words f***ed up beyond all repair.
-
ah, thank you for clearing that. gathered as much the first two acronyms but the rest was tricky.
-
In this case all the OP has to do is use NoteTab or BlogDesk http://www.blogdesk.org/en/index.htm and his problems will disappear. So the acronym isn’t really accurate. :)
-
I appreciate the help (and glad to educate people on the acronyms to use for when you’re ready to pull out your six-shooter and blast the computer to kingdom come… in West Texas, that’s a relatively rational response to the kind of problems I was experiencing).
I tried both blogdesk and notetab. Both have their merits, and have some uses for me. However, neither of them have the capability to pick up type-faces or change font size on the fly… which I find extremely important. I’m often quoting several paragraphs from an article… or dropping in a 1000 word translation that needs to be clearly NOT part of the main text. I’m primarily a writer and editor, but learned typesetting back in the days when it was done by hand. I know that people can’t read more than a short paragrah in italic.
I put long quotes in ten-point Ariel, with 0.5 inch left and right margins, with 0.2 inches between paragraphs. Regular text is the automatic 12 point Times Roman. Italics are for the occasional Spanish, Portugese or Nahuatl word I have to drop in (Most of what I post are translations from Mexican sources).
Blogdesk’s other drawback is that it can’t support all my “categories” (about 700 and growing) … I’d migrated from Bl*gg*r (can I say that word in here?) mostly because it didn’t support categories and subcategories… and the “look and feel” was even more limited than WP. And, although I’d marked my experimental post to take comments, when it came up on WP, it marked it as not accepting comments.
What I’m publishing is basically a limited interest on-line magazine. It’s built a decent reputation at its wordpress address, and changing to another system really isn’t something I’m considering. But, I have attracted a few other writers with something relevant to say about the subject matter (basically, the entire Mexican Republic) whom I can’t pay a thing, and I have to be especially nice to. I can’t expect them to learn coding, which means I’m having to work from whatever they’re using. I wouldn’t expect them to learn HTML, and hope the NEXT version of WordPress takes into account users like me, who are finding OTHER uses for blogs beyond family letters and diaries.
-
If you’re the editor of the magazine, why not edit the HTML yourself, instead of having contributors do it or use a program that is always going to mess up? It’s probably much less time-consuming and probably would result in a more consistent style if one person did the formatting anyway.
-
@richmx: there you go again. A text editor for publishing might require completely different characteristics than one for web writing. As we keep explaining – and then some – we do not need to format in our text editor. It has to be done in CSS. For Windows users I suggest Notepad ++ or PSPad. I use Kate.
-
rich, you don’t seriously do a newspaper in Word, do you? I’m in the industry as well and no-one I know of publishes from Word: they put it into something specific for print first and fix it there. If you’ve ever done publishing using Word you should know how strangely it interacts with other programs; that is why people invented Pagemaker, Quark, etc. Those are designed for print journalism, and the WordPress software is designed for the web. If you wish to display blockquotes, etc, in a different fashion than that enabled here you will need to use something compatible with Web publishing, which Word isn’t. That is why we made all of those recommendations. Nothing is perfect, and all of those options involve work on your part that using Word doesn’t, but none of those options will cause the critical errors that Word does, and which caused you to start this thread in the first place. If you don’t want those errors, you cannot use Word.
-
One comment about BlogDesk. The problem with comments being turned off when you upload has been fixed. Just grab the new version of it on the website.
Second. What about a WYSIWYG HTML editor like Nvu? Format all you’d like in it and then switch to the code view. Copy everything between the body tags. Paste it into the code view on WordPress.
Ideally, you do all your markup by hand, but I totally understand it’s not everyone’s cup of tea.
Just an idea…
- The topic ‘Everything’s gone FUBAR’ is closed to new replies.
WordPress.com Forums 