TinyMCE has a plugin (PowerPaste) that supports pasting content from Word.
TinyMCE also has a plugin (Page Break) that supports adding page breaks to documents.
However. Using an editor instance that has both of these plugins enabled (such as the one on this page https://www.tiny.cloud/docs/demo/full-featured/) pasting content from Word that contains page breaks, using the 'Retain Formatting' option when prompted, does not result in those page breaks being retained in the pasted content.
This seems like a bug. Does anyone know whether this is indeed a bug, or just a missing feature, and most importantly whether there is some way to get this to work correctly?
TinyMCE has a plugin (Page Break) and TinyMCE also has a plugin (Print Preview). Page Breaks don't show in Print Preview.
Related
I'm copying a large number of articles into a blog
When I copy and paste one blog post to another by hand, it pastes with styling (h1 tags, bold, italics, paragraph breaks, etc..). When I use the Selenium IDE to "store text" and "edit content" to bring the content over, it adds the content without any styling, so it's just one long run-on article without breaks or anything else.
I saw a similar question about using "type" instead "edit content" to bring over page breaks, but I'm unable to use the type command for reasons I can't remember at the moment.
What are my options here?
I want PyCharm (IntelliJ) to display HTML-files in a browser, not open them in an editor, when I double click them in the project browser. Googling for a solution didn't return anything useful. Is this possible? How?
(This request also applies to PNG and some other filetypes but HTML is my main need at the moment)
Both IDEA and PyCharm are editors, and they will default to editing; that is, they will open the HTML file and allow you to edit it instead of displaying any kind of web page.
If you want to see the rendered HTML, you can hover to the top right corner and select one of the browsers recognized by IntelliJ and installed on your system to open it in a browser then. Be aware that this may not render things correctly if you rely on a language-specific functionality (like JSP, Jinja2 templates or Less) to generate code on your behalf.
I am tagging a small PDF (4pg), and midway through the second page the tags stopped appearing in the tags and the reading order panel after I chose the tag I wanted via TouchUp Reading Order. If I open the content panel, correct containers are created, so i see:
- Container <H3>Some text
- Container <H3>Some text
- Container <H3>Some text
- Text: Some Text
Does anybody know how to get the three panels synced again?
The PDF mentioned above has some major internal errors, specifically "General Format Errors."
To find these, I ran a PDF Syntax Issue report - which provides details about the PDF in question. This PDF had ~4 pages of errors.
The conclusion was to regenerate the PDF from the source file. (I don't have this yet so I will edit this after I get it.)
To run the Report
Acrobat 9.5- Advanced menu > Print Production > Prefllight. By default, all reports/profiles will be shown. The Syntax Report is under the PDF analysis section, or use the find. Highlight the report then click analyze.
Acrobat X- The Print Production is now a panel, and there is a Preflight section.
I'd like to create hyperlink references to a text selection or offset in an external PDF document, as if there were an anchor defined. E.g., http://lib.extern.org/doc1.pdf?page=3¶graph=4 so that when the user follows the link in their browser, the PDF document opens positioned at the offset specified. I'm looking for any granularity, e.g. page, paragraph, line, word, character or even pixel em or inch offset would be acceptable. If a range for a selection could be specified that would be ideal, the purpose being to highlight and link directly to quotes in external PDF docs (to which the app has read-only access.) Seems so basic, but I haven't found a solution. Ideas?
It appears it works for page numbers
EDIT: And also check this (it should open on page 8)
There are no standards for commandline parameters for the plugins.
But if you can render a fresh PDF each time (make a copy and put in a new object via some PDF manipulation API), you can include an OpenAction that jumps to the page in question. You can even set more viewer parameters (or do some other personalization, watermarks, whatever...).
SEO issue red characters
Hi all
I'm building webstes using dreamweaver, but when I look at the source code it is red for " characters. I'm told anything appearing in red puts off Google's seo. Does anyone know why this appears in red?
For example when I view code source on the site i get the gt; in red
Find out more>></span>
</div>
Thanks for your help
Regards
Judi
I'm told anything appearing in red puts off googles seo.
That is garbage.
Does anyone know why this appears in red?
Probably because it is an entity and has been marked by the syntax highlighter so you can spot in amongst literals.
Google SEO aside, it's important to understand that there's a world of difference between using CSS to control the colour of text, and the syntax highlighting done by the DreamWeaver editor.
Colours seen when you are viewing the HTML source of your page in a tool like Dreamweaver have nothing to do with the colours seen when viewing your page in a browser.
All that's happening is that Dreamweaver is syntax colouring HTML escape characters in red, I am pretty sure that you have nothing to worry about.
Edit
You clarified that in fact you're not viewing the HTML source in Dreamweaver.
Are you viewing source from Firefox?
Firefox syntax colours HTML in its "source of" viewer. HTML escape codes are shown in red (Firefox 3.6, Windows). The point still stands however that this is just syntax colouring and has nothing to do with how your page gets rendered by the browser, or anything to go with Google SEO.
This might be a bit off topic and of course no-brainer for you guys, but anyway:
Firefox highlights all open lines as red. If you have for example:
meta content="text...
and there is no /> at the end of the line, then Firefox makes that line appear red when you use "view page source".
Though that's not the reason for red highlight in your case.
I can view source in Firefox 11 (Win) and see bolded and non-bolded red highlighted markup. If I hover over the bolded red markup, I see a pop-up description of the problem Firefox is finding with the HTML source. For example:
Start tag seen without seeing a doctype first. Expected "<!DOCTYPE html>"
Start tag "div" seen in "table"
Stray end tag "table"
Stray end tag "div"
In non-bolded red highlighted syntax I see entities such as:
, &, >
Firefox 11 allows you to configure and use an external application to View Source. It also has several configuration values in about:config ("view_source.syntax.highlight" for example) that control how the feature is delivered.
The bolded red source highlighting in Firefox View Source may or may not cause issues with SEO. It's an indication that the browser is finding an issue with the HTML markup in the page you're viewing.
The issue of how much invalid HTML harms you with respect to SEO is debated. (And as pointed out in a separate answer, also depends on where the invalid markup appears.) This youtube video discusses HTML validation and Google SEO: http://www.youtube.com/watch?v=2XlKn6I9rSc.
I'm told anything appearing in red puts off googles seo
No. Just no. Google's SEO works on a text-basis, it ignores any colouring or formatting within a page.
The colour of the text in the source code is simply based on DreamWeaver's syntax highlighting - if you run and view your page in a browser, it shouldn't be this colour (assuming you aren't actually setting the colour of this to red).
Google will check for color on same color text and background to make sure hidden keywords aren't being used on the page. To google, white on white text is a no-no.
In Dreamweaver, syntax highlight of HTML entities does not translate into a bad 'mark' in the SEO book.
Now on the other hand, if you have key phrases in your link text that includes (>)'s, then your SEO work for the key phrase is shot because the >'s are counted as part of the key phrase.
You can probably turn red highlighting of entities off in Dreamweaver's preferences....