In an environment filled with athletes willing to experiment with their nutrient intake to enhance performance and health advocates admonishing people to include fewer carbohydrate foods in their diets, a desire to more fully understand the tenets of high-performance eating prompted APRE, the nonprofit research overseer for one of the leading natural carbohydrate sources, to seek answers from experts. APRE convened a panel of sports nutrition researchers and practitioners to discuss recent science on nutritional needs for optimal physical performance and provide their collective perspectives on how dietary recommendations for athletes have changed over the years.
Nevertheless, despite the acknowledgement that athletes and resistance-trained athletes, in particular, can benefit by increasing protein intake, the experts agreed that some athletes are already consuming enough protein, roughly 1.2 to 2 g/kg per day.2 Furthermore, the recent emphasis on protein for physical performance may have clouded issues regarding the athlete's diet and, in some instances, inadvertently promoted less-than-optimal dietary practices. Athletes who overconsume protein at levels far above those recommended in the literature may cut carbohydrate intake drastically and (depending on protein sources) may consume more fat than they need. These practices can lead to suboptimal skeletal muscle glycogen levels, which, as pointed out earlier, can limit the amount of high-intensity exercise an athlete can engage in before he/she fatigues or affect how well he/she can perform during subsequent exercise bouts.
Although additional research aimed at fine-tuning the dietary needs of the physically active individual still needs to be conducted, all the experts who participated in the panel discussion endorsed the concept of consuming a majority of daily calories in the form of high-quality, high-carbohydrate whole-food sources such as potatoes as a means of improving physical performance and recovery from exercise.
The Working Group is composed of five independent experts of balanced geographical representation. Together, they investigate individual cases and produce reports and opinions in order to fulfil the mandate. They meet three times a year in Geneva.
Full row and full column references automatically take into account the cells in the larger grid size of Excel 2007 and later. This means that the reference =A:A, which refers to cells A1:A65536 in earlier versions of Excel, refers to cells A1:A1048576 in the Excel 2007 and later file format.
Converting a workbook from an earlier version of Excel to the Excel 2007 and later file format can cause problems when full row or column references are used in that workbook, and data that was not meant to be included in the references has been entered in cells that are beyond the row and column limit of the earlier version of Excel.
Also, if specific functions that count the number of cells, rows, or columns in the reference were used (such as COUNTBLANK, ROWS, and COLUMN), and these functions referenced full rows or columns, the results that these functions return might be different than expected.
If you regularly open WP files in Word XP (Word 2002), Word 2003, 2007, 2010, 2013, or 2016,please read the solution to problems with fonts when importing into Word and also see this site's macro for cleaning up typographical symbols in WP files imported into Word.
Warning: If your WP files include equations or cross-references to footnotes: When you try to print your document, your equations will be numbered, or you will see "Error! Bookmark not defined." where the cross-reference should be. To avoid this problem, immediately after importing your WP document into Word - and before trying to print - select the entire document (Ctrl-A) and unlink fields (Ctrl-Shift-F9). Then click inside a footnote (or choose Show Footnotes from the ribbon or menu), select all footnotes (Ctrl-A) and unlink fields (Ctrl-Shift-F9). Experts should be able to record these steps in a Word macro, but the macro may require editing before it works reliably.
Expert Word users may want to write a macro that will automatically perform certain operations on WordPerfect documents that are opened in Word. For example, you may want to remove or modify font or other formatting in the imported document.
The following VBA code can be adapted to detect whether a newly-opened file was created by WordPerfect; it should work in Word 2003, 2007, and 2010, but it is entirely undocumented, and it may not work in future versions. This code may be incorporated in an AutoOpen or other macro.
How to fix these problems in files opened in Word XP (Word 2002): The simplest way to fix these problems (if you have not avoided them) is to install and use the special Word macro described elsewhere on this page.
How to fix these problems in files opened in Word 2003, 2007, 2010, 2013, 2016, or later versions: The simplest way to fix these problems (if you have not avoided them) is to install and use the special Word macro described elsewhere on this page.
How to fix the problems described above when you have already opened your WP files into Word: With the help of many people more expert than I am (notably Helmut Weber, who deserves most of the credit), I have written a Word 2007 through Word 2016 macro (when you click the link, the text of the file WPSymbolConv2007.bas opens in a new window) that solves the problems of unsearchable WP characters in Word files. (For Word XP/2002 or 2003, see the next paragraph.) The macro solves the problem by tricking Word into displaying any unsearchable fields in imported WP files and then replaces those fields with native Windows characters; these replacement characters can be searched and replaced. You may install the macro in Word XP (Word 2002), Word 2003, 2007, 2010, 2013, or 2016 by following these instructions.
Note for Word XP/2002 and Word 2003 users: Please use thisalternative version of the macro for Word XP, 2002, and 2003, but otherwise follow the same instructions shown below (the downloaded file will be named WPSymbolConv.bas). This version of the symbol-converter macro is faster than the version for Word 2007 or later, but does not work reliably in Word 2007 or later. (Note: A revised version was uploaded 30 May 2007, with increased reliability.)
Important: If you fail (or refuse) to read all the instructions below and if you fail (or refuse) to follow the instructions exactly and in every detail, the macro will not work! Please do not write me an e-mail complaining that the macro does not compile or does not work unless you have read all the instructions and followed them exactly.
This macro will only work if the special WordPerfect TrueType symbol fonts are installed on your system! However, the macro only requires the specific WordPerfect font or fonts that your Word document expects to find, and typically the only one it needs is the one named WP Typographic Symbols. If you do not have the fonts on your system, and you use 32-bit Windows, you can download the full set ofWP symbol fonts from Corel's web site, and install some or all of them before trying to run the macro. (Under 64-bit Windows, download the same fonts in a ZIP archive.)
To install and run the macro, first right-click on either this link to the Word XP/2002/2003 macro file orthis link to the Word 2007/2010/2013/2016 macro file. (Select the one that matches your version of Microsoft Word!) From the menu that appears when you right-click on the link, choose Save Target As... and download the file to any convenient directory on your disk; the file is named (depending on the version) WPSymbolConv.bas or WPSymbolConv2007.bas (if your browser renames it to something like WPSymbolConv.bas.txt, rename it again to WPSymbolConv.bas or WPSymbolConv2007.bas). (Wait! What exactly does "right-click" mean?)
Then, start Microsoft Word, but File/Close (in some Word versions, Ctrl-F4 will also work) to close all documents, including the blank document that normally opens when Word is started, so that the Microsoft Word window is a plain background in which you cannot enter any text. When you are certain that Word has no document open, press Alt-F11 to bring up the Microsoft Visual Basic editor in which Word macros can be edited. Press Ctrl-R to go to the Project panel near the upper left of the window. Use the arrow keys or mouse to navigate to the bold-faced name "Normal" near the top of the panel; if your default template is named something other than "Normal" (i.e., Normal.dotm or, in older versions, Normal.dot), click on its name instead. Now, on the top-line menu, use Insert, UserForm; ignore the "form" that opens on screen; press Ctrl-F4 to close the form that you have now inserted. A UserForm must be present in your copy of Word before the macro can be installed, but you should not do anything with the form; simply let it exist.
Now, open a WP document in Word XP (Word 2002), Word 2003, 2007, 2010, 2013, or 2016. Do not modify or save the file; when you run the macro, it will make a backup copy for you! For safety reasons, the macro will not run on a file that has been saved in Word! (However, if you know what you are doing, and need to use the macro on files that have been saved in Word, see the note immediately below.) Use Tools, then Macros (or press Alt-F8), select WPSymbolConverter from the list of macros, and press Enter or click Run. The macro will tell you that it has made a backup of your file, and after you click OK on one or more warning messages, the macro will start.
Important troubleshooting message! Read this! If the macro crashes with an error message, and if you are using Word 2007, 2010, 2013, or 2016, then close your document without saving it; re-open the same document, and immediately use File/Save As..., find the "Save as type ..." field, select "Word 97-2003 document (*.doc)" from the dropdown menu, and save the file as a .doc file. Now run the macro on the saved .doc version of the file. After the macro does its work and you are satisfied with the results, you may of course save the file again in Word 2007/2010/2013/2016 format, overwriting the original copy of the file. 2b1af7f3a8