#How to convert footnote to endnote word 2013

[mmorgwindows]

How to convert footnote to endnote word 2013

#How to convert footnote to endnote word 2013 professional

Switch to the “References” tab on Word’s Ribbon. How to Insert Footnotes and Endnotesįire up Microsoft Word, and then open the document to which you’d like to add footnotes (or create a new document if you’re just getting started). Which one you should use in your writing depends on your personal preference or-if you’re writing for school or work-your organization’s publication standards. Endnotes, on the other hand, are added to the end of a section or document. The only difference between footnotes and endnotes is where they appear in your document.Īs the name suggests, footnotes are attached to the bottom of the page containing the sentence they correspond to. You can use footnotes and endnotes to add side comments to your work or to cite other publications like books, articles, or websites. Think of them like verbal asides, only in writing. What Are Footnotes and Endnotes?įootnotes and endnotes are both ways of adding extra bits of information to your writing outside of the main text. But don’t worry-the features and functions are the same. Depending on the version of Word you’re using, the menus we walk through in this guide may look a little different. Note: We’re using Microsoft Word 2016, but Word has supported footnotes and endnotes since at least Word 2007. Luckily, Word has useful tools for adding footnotes and endnotes to your writing. Maybe you want to make a side comment on one of your arguments, or you need to cite another author’s work without distracting from the main text.

#How to convert footnote to endnote word 2013 professional

Whether you use Microsoft Word for personal or professional writing, sometimes you may want to add supplemental notes to sections of your work.

[allyngibson]

Throughout January I worked, off and on, on something of a private project, to make an ebook of Ellery Queen’s long-out-of-print anthology, The Misadventures of Sherlock Holmes.

An anthology of Sherlock Holmes parodies, sprinkled with a few genuine pastiches and two play scripts, essentially a survey of non-Doyle Sherlock Holmes literature to mid-century, The Misadventures of Sherlock Holmes was published in 1944 then allowed to go out of print, due to legal threats from the Arthur Conan Doyle estate. Never reprinted — twenty-five years ago in The Game Is Afoot, which contains about a third of The Misadventures, editor Marvin Kaye says there was (then) movement toward a reprint, but nothing ever came of it — The Misadventures has been a kind of Holy Grail, something I’ve long sought (and once held in my hands, in a college library) that I’d never own. That’s not to say that one can’t find them for sale, but I have better things to do with my meagre income than to spend several hundred dollars on a rare book.

A decade ago, someone uploaded a scan of the entire book to the Internet along with a very rough OCR of the book’s text. I found it, pretty much by accident, one day, and downloaded the files, assuming they might quickly disappear. (Which they have not, but I won’t point you in their direction. They are quite easy to find.) Whereupon they languished on my hard drive for several years.

Around Christmas 2013, after reading an article about it in The Atlantic, I began to use the now-defunct ebook reader software Readmill. This line in Robinson Meyer’s article intrigued me: “I’m nearly certain it has the best digital typography among e-reading software today. On Readmill, digital books look like books, not text files foisted into an extensible reading environment.” I sideloaded the software onto my Kindle Fire tablet and quickly discovered that, yes, Readmill had great typography, and then I began thinking about what I wanted to read with it.

I’ve been making ebooks for myself since 2000, when Microsoft released the Reader ebook software. (Though the software has been long unsupported, to this day I regularly use Berling Antiqua, the font that came packaged with Reader.) One of the first things I did was to download Overdrive ReaderWorks, a software package for making the LIT files that Microsoft Reader used. Even then, twenty years ago, nascent ebooks were simply containers that contained HTML files, CSS files, and images — essentially, the components that drive the Internet to this day. When I got a Nook, I downloaded Calibre, an ebook management package that can convert ebooks from one format to another, even let you build them from scratch.

Making an ebook of The Misadventures, then, was a deeply intriguing idea.

The first thing I noticed when looking through the scanned PDF of The Misadventures of Sherlock Holmes was that it was a beautiful book. I fell in love with the typography, the heavy use of small caps, the old-style numerals.

#gallery-0-16 { margin: auto; } #gallery-0-16 .gallery-item { float: left; margin-top: 10px; text-align: center; width: 25%; } #gallery-0-16 img { border: 2px solid #cfcfcf; } #gallery-0-16 .gallery-caption { margin-left: 0; } /* see gallery_shortcode() in wp-includes/media.php */

It was a book I wanted to look at and savor, not only because of its words but because of its beauty. I wanted to recreate, as much as possible, the look and feel of the original book, and I wanted my ebook to be just as beautiful.

I worked intently for about two weeks in early 2014. I would go to the text file — which was very, very bad — and copy out a story and paste it into Notepad. Then, comparing it to a printout from the PDF, I would correct the errors and lay my HTML tags. I even created CSS code so the story introductions would be formatted correctly.

Then, in mid-January, after completing a clean-up of about a third of the book, I stopped. To this day, I don’t know why. Did I lose passion for the project? Was I overwhelmed at work? Whatever happened, my working files sat, unwanted and unloved, in a directory on my desktop, and at some point I moved them off of my desktop, out of sight and out of mind. I’d think about The Misadventures from time to time, and do nothing.

Around Christmas, I said to myself, “Dude, why don’t you finish it?” And a few days after New Year’s, I picked it up again.

I had new ideas. I’m a big fan of Standard Ebooks, a project that makes free, professional-quality ebooks from public domain texts. Their books look great, they’re coded well, the CSS produces beautiful typography. Essentially, they made exactly what I wanted my ebook of The Misadventures of Sherlock Holmes to be, so, using Calibre, I took a Standard Ebooks book apart and decided to use its code as my foundation, adding my chapters and my CSS code on top of the basic CSS typography.

I started with what I’d done six years earlier — the introduction and dozen stories I’d cleaned up — and added them to the Calibre project. Most stories started with a block at the top that indicated its detective and its narrator, side by side on the opposite sides of the page. I experimented with CSS code to make that work — I settled on using two SPANs and floating the text left or right — but most of it was fairly straightforward. The advantage to working in Calibre in this way was that, as I finished proofing and polishing a story, I could add it to the ebook file and see how it worked, building the book one story at a time.

There were challenges. Footnotes don’t work in ebooks, so I moved all of the footnotes in The Misadventures to an Endnotes section. There’s an index, which I wanted to keep, so I coded internal hyperlinks to the stories or, in some cases, endnotes that the original index would have. In so doing, I discovered one entry in the index that actually wasn’t in Ellery Queen’s manuscript, and there were two Wastonian characters that should have been in Queen’s index that weren’t. These I silently corrected.

#gallery-0-17 { margin: auto; } #gallery-0-17 .gallery-item { float: left; margin-top: 10px; text-align: center; width: 25%; } #gallery-0-17 img { border: 2px solid #cfcfcf; } #gallery-0-17 .gallery-caption { margin-left: 0; } /* see gallery_shortcode() in wp-includes/media.php */

One thing I was keen to do was to retain the illustrations by Frederic Dorr Steele. Sidney Paget is considered the definitive Sherlock Holmes artist, but I have a distinct preference for Steele.

#gallery-0-18 { margin: auto; } #gallery-0-18 .gallery-item { float: left; margin-top: 10px; text-align: center; width: 33%; } #gallery-0-18 img { border: 2px solid #cfcfcf; } #gallery-0-18 .gallery-caption { margin-left: 0; } /* see gallery_shortcode() in wp-includes/media.php */

One thing I did not do was to retain the dropcaps that led off each story. Dropcaps don’t work well in ebooks. But I did retain the way the original book began each story with a few words done in small caps.

It took about two weeks of work to complete the book. The two play scripts were probably the most difficult part of the book to format correctly. After assembling the finished book, I did a proofread on my Kindle, highlighting things that looked like they were wrong, comparing those highlights to the manuscript, and editing my files to make corrections. Doing so, I believe I’ve fixed a couple of typos from the original book. There was one howler of a fact error in a single story that I silently corrected by changing a single word, and I thought about adding one note to explain the reference to “32mos” in John Kendrick Bangs’ The Adventures of Shylock Homes, as that’s a term I don’t believe I have ever encountered (it’s an old publishing term, today we’d call it a “trade paperback”), but that I left alone.

Whether it looks the way I want it to is due to the ebook readers software, not my work. Different ebook readers implement the CSS3 spec incompletely or inconsistently. I thought the finished ebook would look fantastic in Moon+, which is considered one of the best ebook reader apps out there, but there were parts of my CSS that it simply ignored in favor of its own way of formatting. Small caps and old-style numerals are, shall we say, edge cases that aren’t always implemented. I tried various epub plugins for Chrome in Vivaldi and got exactly what I wanted in a desktop browser. On a phone or tablet, Gitden Reader did the best, but it’s not a particularly user-friendly piece of software.

Readmill did well with it. I discovered that I had implemented the detective/narrator block leading off each story badly. When I replaced the SPAN tags with P tags and a display: inline; rule in the CSS, they formatted correctly. But it can’t do the small caps or old-style numerals at all. Six years ago I might have driven myself mad trying to figure out why it wasn’t doing those things. Now I understand that it’s not Readmill, it’s simply how ebook readers work.

My decade-old Nook Simple Touch, poor thing, did better than I thought it would. The Nook has a well-known problem with centering images — it can’t handle the simple CSS rule margin-left: auto; margin-right: auto; display: block; at all — nor does it do the small caps and the old-style numerals.

My Kindle Fire and the Kindle app on my phone do very well with it, as you can see from the screenshots above. It does the small caps correctly, but for old-style numerals I need to use the Georgia font instead of my preferred Palatino.

It’s unfortunate that The Misadventures has been out of print for the last seventy-five years as it’s rather entertaining and provides a nice overview of the state of Sherlock Holmes literature at the time of its publication. There’s an Arsène Lupin story (“Holmlock Shears Arrives Too Late,” the first meeting of Lupin and “Shears”/”Sholmes,” which you can read in Standard Ebooks’ Arsène Lupin collection), Vincent Starrett’s classic “The Unique Hamlet” makes an appearance, as does Mark Twain’s A Double-Barrelled Detective Story. There’s a Solar Pons story from August Derleth, there’s a story that a serious Raffles story and a Holmes parody at the same time, there are stories from Anthony Boucher and Manly Wade Wellman that place Holmes in a World War II setting, there’s even two stories about Sherlock Holmes’ children, one played for humor (his three year-old son is even better at deduction than his father, but with the maturity and discretion of a three year-old), one a serious mystery (with a Joan Watson, no less!). Many of the pieces are parodies and burlesques that poke fun, sometimes gently, sometimes savagely, on Sherlock Holmes. The script from The Adventures of Ellery Queen radio show with a Sherlock Holmes theme is really the only self-indulgent inclusion, but the story introductions by the Queen gestalt are fascinating, warm, and chatty in their own right. It’s a nice collection, one that, if someone brought back into print, I’d happily add to my bookshelf.

In spite of the limitations of the ebook reader software, I achieved what I set out to do. I created an ebook of Ellery Queen’s The Misadventures of Sherlock Holmes, one that looks professionally produced and maintains, as much as possible, the formatting of the book as originally published in 1944. Sometimes I will open the book on my Kindle, just to flip through and look at it. It’s a good looking book, an attractive book, and I’m glad I spent the time, picked up the project again, and finished it.

The Misadventures of Sherlock Holmes Throughout January I worked, off and on, on something of a private project, to make an ebook of Ellery Queen's long-out-of-print anthology, The Misadventures of Sherlock Holmes.

[compunetss]

How to edit PDFs in Microsoft Word

Working with PDFs has become as common as working with Word docs, but to get the full editing capabilities in Adobe Acrobat you must shell out more than $400 for the Professional version. While there are plenty of less expensive alternatives, the simplest solution might be a tool you already use:

Microsoft Word 2013.

While previous versions of Word let you save a document as a PDF, Word 2013 allows you to open an Adobe formatted file, modify it and then resave it back to the PDF format without using Acrobat. Microsoft calls this new feature PDF Reflow, and here we’ll show how it works with a file containing text and an image.

Open PDFs

Open Word 2013. Select File > Open, then Browse to the folder that contains your PDFs. Select a file and click the Open button. Notice the selected file appears in the View window on the right. For this example, select a file with text and graphics.

[ Further reading: Your new PC needs these 15 free, excellent programs ]

Once you click Open, the following dialog box appears:

Note the message warns that large files take longer to load, and the layout in Word may not look exactly like the original PDF. That’s because margins, columns, tables, page breaks, footnotes, endnotes, frames, track changes, and special format options such as font effects (among other things) may differ between the original software used to create the PDF file (such as InDesign, WordPerfect, Microsoft Publisher, Photoshop, etc.) and Word.

Microsoft suggests that text documents transfer and reflow better than documents heavily laden with charts and graphics, tags, bookmarks, footnotes, and/or track changes. These additional text blocks often land in the middle of paragraphs or tagged on to the end. Be aware of these limitations so you can plan for the outcome and make adjustments as needed.

Many of the layout attributes, however, are compatible and transfer from the PDF directly into Word with no problems. For example, the following image is a copy of the original PDF we opened in Word 2013.

Modify PDFs in Word

You can easily add new paragraphs and edit and delete data, and the document reformats automatically as you type. You can even remove, replace, or reposition the graphics, and the text-wrap feature re-wraps the paragraphs around the image at its new location. You can also change the page size, the margins, the line spacing, the font and font size plus all the font attributes, and much more.

In the “edited” version of this document, the font and font size in the title, subtitle, first, and last paragraphs were all changed. In addition, the yellow paragraph was added and the image was moved from top right to bottom left, all without any problems.

In fact, Word 2013’s PDF compatibility is so good, you can right-click the image and view an entire list of editable graphic options including cropping, sizing, formatting, positioning, adding captions, and even attaching hyperlinks.

With all these new features, you can now use Word 2013 as a desktop publisher, save the finished product as a compiled/condensed PDF, then ship it directly to the printer for mass production. This is a real plus for small offices and home businesses who can’t afford to purchase another software program for every special function that occurs.

The real benefit for everyone else is the convenience of copying data from one document to another that previously originated within incompatible file formats. PDFs are smaller, easier to email, and much more efficient for printing because the format is portable, therefore, all the necessary elements to produce the finished product are collected into a single file.

The downside of Word’s Reflow feature is that some companies use the PDF format to ensure some measure of copyright protection on the documents they distribute. There is a solution for these groups as well. Password-protect the document in Acrobat for Read Only, so the file cannot be copied or converted.

Save or export to PDF

Once the document is altered to your satisfaction, choose File > SaveAs, navigate to the appropriate folder, then choose PDF from the Save as Type dropdown list.

Immediately, the system displays the following PDF file type screen. Choose: Optimize for Standard (publishing online and printing) and check the box for Open File After Publishing, then click Save.

Another option for saving or resaving a document as a PDF file is to export it. Choose File>Export, select Create PDF/XPS Document in the left column, then click the button with the same name.

Again, the system displays the following PDF file type screen. Choose: Optimize for Standard (publishing online and printing) and check the box for Open File After Publishing if you want the PDF to open after it’s saved. Then click the Publish button and your new PDF is created.

Repairing errors

If you find errors in the republished/resaved PDF documents, you may have to go back and reformat the pages. Text will likely re-flow with no problems, but the graphics using text-wrap may disrupt the text flow. If that happens, break up the paragraphs so that one text box ends before the image, then another, new text box begins again after the image. Once that’s accomplished, hard-code the position of the graphic box.

Right click the image, choose Wrap Text>More Layout Options, and the following screen appears:

If your text is moved and rearranged in your new PDF, you may want to choose a Relative horizontal and vertical position. This allows the image to move with the text. If you want the image to remain absolutely at the bottom-left side of page one, then choose an Absolute horizontal and vertical position. You don’t have to locate or guess the position, just move the image and the new position coordinates appear in the above box. All you have to do is click Absolute or Relative, then click OK.

Once these decisions are settled, repeat the steps above to re-save or re-export the file to a new PDF.

[file-formats-programming]

Word 2013 Documents Support & Variables Support in LINQ Reporting Engine in .NET Apps

What's New in this Release?

Aspose development team is happy to announce the monthly release of Aspose.Words for Java & .NET 17.3.0. This month’s release contains over 67 useful new features, enhancements and bug fixes. Please see the release notes for more detail. Here is a look at just a few of the biggest features and API changes in this month’s release; Full support for Word 2013 documents (roundtrip to/from DOCX), variables support and more new features are introduced in LINQ Reporting Engine, New Public OfficeMath properties: MathObjectType, Justification, DisplayType, Font substitution mechanism improved. Now Aspose.Words evaluates all related fields in FontInfo (Panose, Sig etc) and finds the closest match among the available font sources, Asian font rendering improved (more precise metrics calculation), Stroke weight is now taken into account while rendering auto-sized Textboxes, Implemented next round of improvements in table grid algorithm, Improved table breaking logic in compatibility mode for tables with header rows, Improved table breaking logic for tables with nested tables in a cell with bottom margin set, Improved tables breaking logic for tables with vertically merged cells having horizontal borders and Implemented fitText option for table cells. Starting from this release, Aspose team has added the full support of MS Word 2013 documents. The full support of roundtrip to/from DOCX is available in this Aspose.Words version. Previously, Aspose.Words performed font substitution only in cases when FontInfo in the document for the missing font doesn’t contain the PANOSE. Now Aspose.Words evaluates all related fields in FontInfo (Panose, Sig etc) and finds the closest match among the available font sources. In case of font substitution the warning is issued with text. Please note that now font substitution mechanism will override the FontSettings.DefaultFontName in cases when FontInfo for the missing font is available in the document. FontSettings.DefaultFontName will be used only in cases when there are no FontInfo for the missing font. Moreover, please note that font substitution algorithm in MS Word is not documented so, the result of Aspose.Words font substitution may not match MS Word choice. Aspose team has introduced new property in this release that allows user to get type MathObjectType of this Office Math object. The MathObjectType enumeration is added in Aspose.Words 17.3 to specify type of an Office Math object. It has introduced new option in that removes empty rows that contain mail merge regions from the document. It has also added new public properties Justification and DisplayType into the OfficeMath class. It has also added new public property Field.LocaleId in this release that allows user to get/set field’s locale.  It has also added new paramerter -fitSizeLim for image tag to change the size of the textbox according to the size of the image without increasing the size of the textbox. It has also added support for variables in Aspose.Words 17.3 LINQ Reporting Engine that enables users to use variables in template documents. Variables are useful when users need to calculate an expensive value just once and access it multiple times in a template. The list of new and improved features added in this release are given below

New public OfficeMath properties: MathObjectType, Justification, DisplayType

Full support for Word 2013 documents (roundtrip to/from DOCX)

Variables support and more new features are introduced in LINQ Reporting Engine.

Font substitution mechanism improved. Now Aspose.Words evaluates all related fields in FontInfo (Panose, Sig etc) and finds the closest match among the available font sources.

Asian font rendering improved (more precise metrics calculation).

Stroke weight is now taken into account while rendering auto-sized Textboxes.

Implemented next round of improvements in table grid algorithm.

Improved table breaking logic in compatibility mode for tables with header rows.

Improved table breaking logic for tables with nested tables in a cell with bottom margin set.

Improved tables breaking logic for tables with vertically merged cells having horizontal borders.

Implemented fitText option for table cells.

Add MailMergeCleanupOptions option to remove empty row

Cell's content are warped incorrectly in output Pdf

PDF output is incorrect for 2 text columns

Add feature to set background color of table row using Linq Reporting Engine

Insert image dynamically using Linq without change size of textbox

Justification of OfficeMath object

Obtain type of the MathObject

Add feature to define variables in LINQ Reporting template

Provide ability to specify locale at Field level

Implement reading of themes for RTF format.

Support of MS Word 2013 documents (WORDSNET-7741 and WORDSNET-7964)

/table grid/ Cell's content is rendering a few inches to the right in PDF

Table header should be pushed to the next page if no rows fit below header in 2013 mode

Table header row orphaned in 2013 mode

Mail Recipient is lost after re-saving Doc

Add/remove document settings if OptimizeFor is called for a document

Incorrect Asian font metrics

Saving resources when converting Words documents to HTML

Fonts substitution // Improve font substitution rules.

Paragraph formatting is lost after re-saving Docx

Underline/strikethrough formatting is applied to revisions imported from HTML

/tcFitText/ Conversion of table creates new line inside table

Compare and Reject feature do not mimic Microsoft Word's behavior

/nested row break height/Text moves to previous pages after conversion from Docx to Pdf

/fitText/ Chinese text render on next line in HtmlFixed

/table break header row/ Converting from .docx to .pdf loses table header

/table break header row/ Table is rendered on previous page after conversion form Docx to Pdf

Table header moves to previous page bottom in PDF

EndnoteOptions are not saved if the document does contain endnotes

/table break/ All pages show some content from next page at bottom in PDF

Paragraph's spacing is changed when InsertDocument is used with UseDestinationStyles mode

Hebrew date field renders incorrectly in Pdf

Incorrect formatting of 'Normal (Web)' after import from another document

Text in image is missing when exporting to HTML

More vertical spacing between lines added when exporting to HTML

Output Docx is not opened in MS Word after performing mail merge

Bookmark entries are not entirely merged after mail merge

Z-order is incorrect after conversion docx to odt.

Some table rows render on the previous page of PDF

Bullet list is changed to numbered list after conversion from bytes to Docx

ShapeAttr.LineFillBlipName attribute returns invalid value

A strange Box appears near certain images in PDF

TTFontMetrics.BoldSimulationScale is not too accurate for MS Gothic

Hyperlink encoded twice in PDF

Aspose.Words ignores stroke weight for autosized textboxes

Shape with caps is not rendered correctly

Docx to Pdf conversion issue with StructuredDocumentTag rendering

List label size differs in layout.

Content of StructuredDocumentTag is lost in output Pdf/Doc

Docx to Html conversion issue with chart's axis bounds

Ref field generates error code after conversion from FlatOpc to Doc

TOC update does not see format revision changes.

Position of AutoShape is changed after Appending.

Fonts substitution // Measurements: Spacing of text lines in PDF is different to when viewed in MS Word

Fonts substitution // Incorrect fonts rendering.

Docx to HtmlFixed conversion issue with fonts

/advanced typography/ Arabic text is incorrectly rendered to PDF

WordArt // Multiline // Watermark shape is not rendering correctly in PDF

Contents position is changed after conversion from Doc to Pdf

Table's contents move to next page after conversion from Doc to Pdf

Other most recent bug fixes are also included in this release

Newly added documentation pages and articles

Some new tips and articles have now been added into Aspose.Words for .NET documentation that may guide users briefly how to use Aspose.Words for performing different tasks like the followings.

Inserting Images Dynamically

Setting Text Background Color Dynamically

Overview: Aspose.Words

Aspose.Words is a word processing component that enables .NET, Java & Android applications to read, write and modify Word documents without using Microsoft Word. Other useful features include document creation, content and formatting manipulation, mail merge abilities, reporting features, TOC updated/rebuilt, Embedded OOXML, Footnotes rendering and support of DOCX, DOC, WordprocessingML, HTML, XHTML, TXT and PDF formats (requires Aspose.Pdf). It supports both 32-bit and 64-bit operating systems. You can even use Aspose.Words for .NET to build applications with Mono.

More about Aspose.Words

Homepage Aspose.Words for .NET

Download Aspose.Words for .NET

Online documentation of Aspose.Words