Jun 062016
 

XLingPaper version 2.29.0 is now available for Windows, Mac, and Linux.

This new version of XLingPaper has a number of improvements and bug fixes.

The main highlights are:

  • Allow publisher style sheet to control whether or not sections within appendices should be included in contents.
  • Allow content control for appendixRef, exampleRef, figureRef, genericRef, sectionRef, and tablenumberedRef elements.
  • Add height and width attributes to the img element to control size of graphic in the XMLmind XML Editor.
  • Improve page-breaking of interlinear texts, especially when using automatic wrapping. In particular, the title/line number should no longer appear alone at the bottom of a page and also, longer interlinears should be split across the page boundary instead of sometimes being kept together.
  • Allow citation and abbrRef elements in content lines for all output formats and bookmarks for PDF output formats.

You can obtain an installation program for Windows, Mac or Linux at http://www.xlingpaper.org/?page_id=51.

If you have already installed XLingPaper version 2.10.0 or higher and merely want to upgrade, then you will need to download and install the XLingPaper update file. See http://www.xlingpaper.org/?page_id=107. If you have modified any of the stock publisher style sheets, please be sure to make a backup of your work before running this installer. It may overwrite your modifications.

The recent changes are:

  • 2.29.0 6 June 2016
    • Allow citation and abbrRef elements in content lines for all output formats and bookmarks for PDF output formats.
    • Add one more collection pattern to the LSAUnifiedStyleSheetForLinguisticsReferences.xml file (thanks to Kent Rasmussen).
    • Update SIL-UNDWorkPapersStylesheet per work by John Clifton.
    • For the case where collCitation and procCitation elements need to convert the names of editors of collection/proceedings volumes from a LastName, FirstName format to FirstName LastName format, we now allow one to use semi-colons between multiple editors’ names.
    • Make a citation element in an abbrDefinition element to work.
    • Update link to ISO 639-3 code site in documentation.
    • Add ability to not show a title in references if the refTitle element is empty.
    • Update SILEWPPaperAsBookStylesheet file.
    • Fix bug: when using chapterInCollection elements, there was no way to get the chapter title in a header or footer. Also added chapterInCollectionAuthor element so that one could get the author(s) of a chapter in a collection to show in a header or footer.
    • Added startSection1NumberingAtZero to the publisher style sheet documentation.
    • Allow publisher style sheet to control whether or not sections within appendices should be included in contents.
    • Allow content control for appendixRef, exampleRef, figureRef, genericRef, sectionRef, and tablenumberedRef elements.
    • Make PDF output work on Mac OS “El Capitan”.
    • Fix a typo in English error message.
    • Add height and width attributes to the img element to control size of graphic in XXE.
    • For the web page output:
      • Fix bug: when a style sheet was being used, the contents section for a part would show paragraphs, etc. in the part element.
      • If a preface, glossary, etc. item contained an index item, then the index did not show anything for the link to it.
    • For the default way of producing PDF (via XeLaTeX):
      • Improve handling of figures with their captions so that they normally, if not always, occur on the same page.
      • Improve page-breaking of interlinear texts, especially when using automatic wrapping. In particular, the title/line number should no longer appear alone at the bottom of a page and also, longer interlinears should be split across the page boundary instead of sometimes being kept together.
      • Allow a free element to have a XeLaTeXspecial attribute of ‘pagebreak’.
      • Make the options in the betweentitleandnumber attribute of the contentsLayout element work.
      • Note that cellpadding and cellspacing attributes do not work for tables using the default PDF output.
      • Fix bug: There was no way to set the default font family in a publisher style sheet to use Graphite. Now the defaultFontFamily element has a XeLaTeXSpecial attribute where one can set grapite and font-feature values.
      • Fix bug: If a document had several font-family attributes where the corresponding XeLaTeXSpecial attribute used graphite (and maybe font-feature values), any instance of that font-family also used the set of graphite/font-features of only one defined set. Now it uses each defined set in the appropriate places.
      • Fix bug: if a table had endnoteRef elements but no endnote elements, then the footnote number of the endnoteRef elements could be too high.
      • Fix bug: when a table had one or more “header” rows (i.e., a row with all th columns) and had rows with a th td+ pattern and the final row began with a td row, the header would not show.
      • Fix bug: When a style sheet has a running header or footer with both a chapter title and a section title in it, if no section occurred before a page was output, then the header or footer would contain the chapter title two times.
      • Fix bug: if the stylesheet body layout has a part and the part starts with a numberLayout, the page numbering could be wrong for the first part (and the last part of the frontMatter).
      • Fix bug: If a caption to a figure or table included an index item, then the index would list the item using the page number of the list of figures or list of tables instead of the page where the caption appeared.
      • Fix bug: if the stylesheet font size was less than 10 or more than 12, then the number in numbered lists would be too wide or too narrow, respectively.

 

 Posted by on June 6, 2016 at 11:14 am
Jan 222016
 

Last week we noted that with Mac OS X ‘El Capitan’, if one scrolled quickly through a file, the display would become scrambled.

The good news is that we have a fix for this now.  Go to the Mac install page and get the latest XXE installer for El Capitan or simply click here.

  1. After downloading this .dmg file, I suggest go to your /Applications folder and rename your current XMLEditor app to something like XMLEditorOriginal.
  2. Double-click the .dmg file after it downloads. This will open a Finder window showing the contents of the downloaded .dmg file.
  3. Drag the XMLEditor item to /Applications.

We owe a great debt of gratitude to the good folks at XMLmind for enabling us to have this fix.  They certainly had no monetary reason for helping us get this fixed.  If you are an XLingPaper user with a Mac and are using or plan to use El Capitan, please send a note of thanks to hussein at xmlmind dot com (or send a note to me at support@xlingpaper.org and I will pass it on to him).

Also, since in my opinion this whole problem is due to Apple not correctly implementing  the Java JViewport.BLIT_SCROLL_MODE properly in El Capitan, please also go to http://www.apple.com/feedback/macosx.html and report this as a bug.  Maybe Apple will fix it in a later release of El Capitan and others will benefit.

 

 

 Posted by on January 22, 2016 at 10:47 am
Jan 142016
 

While we do now have an installer for Mac OS X El Capitan, it is the case if that one scrolls quickly through a document, the content of the screen can become scrambled.  Apparently this is a Java issue.

If it is too late for you, you can try and load another file (so two files are open in XXE) and, when the screen becomes scrambled, use the keyboard to switch to the other file and then right back (Shift-Command-P two times or Shift-Command-N two times).

I will try and see what else I can learn about this issue.

 Posted by on January 14, 2016 at 2:18 pm
Nov 182015
 

Earlier we noted that the latest Mac OS X operating system (El Capitan which is version 10.11) does not work with XLingPaper.  More precisely, trying to start the XMLmind XML Editor failed.  Part of the reason is that we are using a legacy version of the XMLmind XML Editor (version 5.3.0) which requires Java version 6.  El Capitan does not come with Java 6.

We have found a fix for this for those of you who have already installed XLingPaper on your Mac.  It involves several steps.

  1. Upgrade your Mac to El Capitan.
  2. Download and install Java version 6 by going to https://support.apple.com/kb/DL1572?locale=en_US.
  3. Remove your current XMLmind XML Editor from the /Applications folder.
  4. Download and install our slightly modified version of the XMLmind XML Editor program from http://www.xlingpaper.org/wp-content/uploads/installers/macosx/XXE5-3-0ForElCapitan.dmg.
  5. Download and install the slightly changed XLingPaper configuration update for Mac at http://www.xlingpaper.org/wp-content/uploads/installers/macosx/XLingPaper-2-28-0aUpdateConfigOnlySetup.dmg.
  6. Open up a Terminal and type the following in it (or copy it from here and paste it in) and then press the return key (it will ask you for your system password):
    sudo ln -s /usr/local/texlivexlingpaper/2009basic/bin/universal-darwin /usr/local/xlingpapertexbin

You should now be set to run XLingPaper as before: you should be able to start up the XMLmind XML Editor as you used to do and open up, edit, and produce output for XLingPaper documents.

If you have any issues, please contact support@xlingpaper.org.

 

 Posted by on November 18, 2015 at 2:19 pm
Nov 102015
 

XLingPaper version 2.28.0 is now available for Windows, Mac, and Linux.

(Mac users: please do not upgrade to El Capitan yet.  We are working on a solution for why it does not work correctly with XLingPaper.)

This new version of XLingPaper has a number of improvements and bug fixes.

The main highlights are:

  • Allow an author element to have a contentType attribute (so can easily leave it out when submitting a work anonymously).
  • In the UI, change behavior of the black drop-down button on reference elements so that it invokes the SetReference command instead of showing all elements with IDs.
  • Add a special command to produce a web page of the master list of abbreviations.
  • Add ability to create a list of ISO 639-3 codes used in a document with links from the code to the list; include a language name.
  • Add glossary term capability so one can have a master list of glossary terms and then refer to them in the document. The output will show only those used in the document in a table in either a preface or a glossary element.

You can obtain an installation program for Windows, Mac or Linux at http://www.xlingpaper.org/?page_id=51.

If you have already installed XLingPaper version 2.10.0 or higher and merely want to upgrade, then you will need to download and install the XLingPaper update file. See http://www.xlingpaper.org/?page_id=107. If you have modified any of the stock publisher style sheets, please be sure to make a backup of your work before running this installer. It may overwrite your modifications.

The recent changes are:

  • 2.28.0 9 November 2015
    • Improve documentation on showLevel attribute of contents element.
    • Fix bug: if an annotation in a refWork element contained a citation element, that citation element was treated as if it were in the document proper.
    • Thanks to work by Kent Rasmussen, the Zotero to XLingPaper command now allows one to convert one or more Zotero abstracts, notes, and keywords to an XLingPaper annotation. Note that the command does expect one to have an annotatedBibliographyType element whose ID attribute is ‘atAbstract’ and one whose ID attribute is ‘atNote’.
    • Allow an author element to have a contentType attribute (so can easily leave it out when submitting a work anonymously).
    • Add info about editing referenced style sheet in publisher style sheet documentation.
    • Fix some typos in generated messages in UI.
    • Update link to vowel chart download site in the “Journal of the International Phonetic Association Illustration article, submission format” template.
    • Add a resetEndnoteNumbering attribute to the chapterLayout element in a publisher style sheet. It controls whether endnote numbering should be reset at each chapter or not.
    • Add SILEWP document template and update SILEWP publisher style sheet.
    • In the UI, change behavior of the black drop-down button on reference elements so that it invokes the SetReference command instead of showing all elements with IDs.
    • Fix bug: Publishing info material would show at the end of a book when using a style sheet.
    • Fix bug: multiple preface elements with multiple prefaceLayout elements in a style sheet did not line up according to the documentation. Same for multiple glossary elements with multiple glossaryLayout elements.
    • Fix bug: The convert gloss to abbreviation command failed to work in an embedded object and also if the gloss began with 1, 2, or 3 and the rest of the gloss was uppercase, but the abbreviation(s) for the rest of the gloss were lowercase in the abbreviation element, it failed to convert it to an abbrRef.
    • Fix some typos in the user documentation.
    • Further clarify the usecitationformatwhennumberofsharedpaperis attribute on the referencesLayout element in the publisher style sheet documentation. Also change its default value to 2.
    • Add startingPageNumberInBook attribute to publishingInfo element.
    • Add useperiodafternumber attribute to sectionTitleLayout element in publisher style sheet to control period after section numbers when there is no overt numberLayout element.
    • Add a special command to produce a web page of the master list of abbreviations.
    • In the publisher style sheet, add textafterReferenceNumber and textbeforeReferenceNumber attributes to the interlinearTextLayout element.
    • Add ignoreabbreviationsfontfamily attribute on abbreviation element to user documentation.
    • Add ability to create a list of ISO 639-3 codes used in a document with links from the code to the list; include a language name.
    • Add ability to include an interlinearSource element in a single or listSingle example.
    • Add glossary term capability so one can have a master list of glossary terms and then refer to them in the document. The output will show only those used in the document in a table in either a preface or a glossary element.
    • Add brief history description to user documentation.
    • Allow comment elements in author element (so one can keep the information while submitting a paper for anonymous review).
    • Allow a publisher style sheet to correctly place multiple preface elements or glossary elements around other frontmatter/backmatter elements.
    • Add note to documentation about problems with duplicate fonts on Windows 7 causing XXE and default PDF to not show the font correctly.
    • Add a missing collection pattern to the SIL-UNDThesisReferencesStylesheet.xml file.
    • Fix IJAL publisher style sheets to show section numbers correctly.
    • For the default way of producing PDF (via XeLaTeX):
      • Add a XeLaTeXSpecial attribute to the chapter element so one can force a page break when chapters do not necessarily begin a new page.
      • Add new attribute to the freeLayout element in a publisher style sheet: adjustIndentOfNonInitialLineBy. The value entered will be subtracted from the normal indent of second and following lines in a long free translation. This is only for the ‘automatically wrap interlinears’ case.
      • Fix bug: the indentOfNonInitialGroup attribute of the interlinearMultipleLineGroupLayout element in a publisher style sheet did not work correctly for interlinear examples when the automaticallywrapinterlinears attribute of the lingPaper element was set to ‘yes’.
      • In the style sheet, add an indentOfInitialGroup attribute on the interlinearTextLayout element. This controls how much to indent the first line of an interlinear text when using the automatic wrapping of interlinear text option.
      • Add ability to insert continuous line numbering in the PDF output. See section 2.10 ‘Add line numbers to output’ in the publisher style sheet documentation.
      • Fix bug: when a publisher style sheet was set to use double spacing and endnotes and examples are set to be singlespaced, an example in an endnote could come out in the wrong font size.
      • Fix bug: when using double spacing or space and a half and tables were not set to use single spacing, sometimes the table came out single-spaced anyway.
      • Fix bug: table captions with style sheets were not always coming out in the correct position.
      • Fix bug: an empty free element would cause the PDF to fail to be produced.
      • Fix bug: in an endnote embedded in an interlinear-text, the use of a gloss element whose language element had a font-family could cause the rest of the endnote to be formatted using that gloss’ font-family.
      • Fix bug: if one had a section title beginning a paragraph, there would be too much space between the section number and the section title.
      • Fix bug: an endnote in a table in an li element would cause the PDF not to be produced.
      • Fix bug: A non-initial paragraph in an endnote did not indent.
    • (Remove some files in the set of configuration files we are no longer using.)

 

 Posted by on November 10, 2015 at 11:29 am
Oct 052015
 

Steve Marlett reports that he tried to upgrade hid Mac Operating System to El Capitan and then could not get the XMLmind XML Editor version we use to run:

Warning to others: I upgraded to the El Capitan operating system on my Macbook and then was unable to get XMLMind to launch. I have now downgraded to Yosemite and am able to work again. So beware!

So if you are a Mac user, please do not upgrade your OS until we find out what the problem was.

 Posted by on October 5, 2015 at 9:07 am
Jul 252015
 

Recently, there have been two cases reported where a font was not displaying correctly in the XMLmind XML Editor and in the default PDF output. In both cases it was on Windows 7 and in both cases the user had installed a new version of the font in question. It turned out that there were duplicate instances of that font installed. (Why Windows 7 allowed duplicates, I have no idea.)

The solution was to get a tool like TypoGraf to see what fonts are truly installed, find the duplicates, delete them, and re-install the one version of the font desired. TypoGraf can be obtained from http://www.neuber.com/typograph/index.html. Please note that it is *crucial* that you run TypoGraf as Administrator when you try and delete a duplicate font. If you do not, it will look like the font is deleted but it will not be.

 Posted by on July 25, 2015 at 9:47 am
Jul 082015
 

XLingPaper version 2.27.0 is now available for Windows, Mac, and Linux.

This new version of XLingPaper has a number of improvements and bug fixes.

The main highlights are:

  • Allow abbrRef elements wherever “embedded” elements can go, not just in the limited places allowed before.
  • Allow more than one email address for a given author.

You can obtain an installation program for Windows, Mac or Linux at http://www.xlingpaper.org/?page_id=51.

If you have already installed XLingPaper version 2.10.0 or higher and merely want to upgrade, then you will need to download and install the XLingPaper update file. See http://www.xlingpaper.org/?page_id=107. If you have modified any of the stock publisher style sheets, please be sure to make a backup of your work before running this installer. It may overwrite your modifications.

The recent changes are:

  • 2.27.0 8 June 2015
    • Allow br elements in appendix, chapter, part, and section titles but not in table of contents (i.e., remove them from table of contents).
    • Allow abbrRef elements wherever “embedded” elements can go, not just in the limited places allowed before.
    • Insert section 6.1.4 in the user documentation on how to create a table with its own footnotes.
    • Change documentation to use support@xlingpaper.org email address.
    • Fix bug: the firstParagraphHasIndent attribute of the chapterInCollectionLayout element was ignored.
    • The SIL International publisher style sheet for manuscript references needed a space after the colon after the location.
    • Add documentation on how to center an image using a table.
    • Add ability to control vertical spacing between interlinear text units (via the spaceBetweenUnits attribute on the new interlinearTextLayout element).
    • Fix some link typos in the user documentation.
    • Make Set Reference for exampleRef elements show only examples within a framedUnit when the exampleRef is in a framedUnit. Conversely, Set Reference for exampleRef elements outside of a
      framedUnit do not show any examples within a framedUnit.
    • Add a command ShowExampleNumberAndIds which when run on an exampleRef element will show projected example numbers as well as the example IDs.
    • Add defaultGlossLanguage and defaultVernacularLanguage attributes to lingPaper element.
    • When changing default gloss and vernacular languages, add note in documentation that need to restart XXE for the changes to take effect.
    • Allow more than one email address for a given author.
    • Allow a hanging indent to occur within a chart (especially for an example which is a dictionary entry).
    • For publisher style sheet, fix bug which kept section number from showing in running headers in papers.
    • Add schematron check for a table cell width attribute which has just a space in it.
    • Fix bug in web page output with a publisher style sheet: the indexLinkLayout information was ignored.
    • Added figureRefLinkLayout and tablenumberedRefLinkLayout to new publisher style sheet templates.
    • For the default way of producing PDF (via XeLaTeX):
      • Undo “Enable PDF bookmarks for book documents to show three levels (and not just two)” from 2.26.2: it broke starting on odd pages.
      • Fix bug: if the basic point size was different than 10pt, 11pt, or 12pt and one was using double or space-and-a-half, then if the contents were to be single spaced, they would come
        out in the LaTeX document class size (10, 11, or 12).
      • Fix bug: The PDF would fail to be produced if a caption in a table not in a tablenumbered contained a br element.
      • Add a note in documentation that using index IDs containing underscores may cause the page numbers to not come out.
      • Add needspace command for word emedded within word examples.
      • Revise how needspace command is done to avoid some bad page breaks which have no work-around.
      • Fix bug: a table with 1000+ rows would cause the PDF to fail (buf_size limit met). Inserted a “%nl” at the end of each row to prevent this.
      • Fix bug: a non-initial endnoteRef in an interlinear-text which referred to an endnote in an interlinear-text earlier in the file had an incorrect footnote number.
      • Fix bug: When a publisher style sheet has acknowledgementsLayout with showAsFootnoteAtEndOfAbstract set to yes, it would use a footnote even when there was no acknowledgements
        element and it would use a footnote after every pc element.
      • Add XeLaTeXSpecial attribute to lingPaper element; have it use “overfullhbox=’5pt'”. This will output a 5pt black box on any line that is too long (but not for tables).
      • Make the version element be centered when there is no publisher style sheet.
      • Fix bug: within a definition element, if one changed font family, the scope of that font family continued on when it should not have. Ths also happened in an endnote within an
        example.
      • Fix bug: a free translation could show up on top of the final line of a lineGroup when in an interlinear example, no heading, and there was another lineGroup before it.
      • Fix bug: within a definition element, if one changed font family, the scope of that font family continued on when it should not have. Ths also happened in an endnote within an
        example.
      • Fix bug: when using an index along with content control, the text from the content control names was showing up at the end of the index.
      • Fix bug: some listInterlinears with an interlinearSource did not align the source information at the right edge correctly when the source came after the free.
      • Fix bug: the PDF would fail to be produced if one said the document was in a particular language.
      • Fix bug: the PDF would fail to be produced if using the default (no style sheet) output and one had a language id used in a free that contained a hyphen.
      • A chart with an image could mess up a following paragraph’s indent if the chart was at the top level.
      • Fix bug: when a publisher style sheet had a figureRefLinkLayout or a tablenumberedRefLinkLayout, any color or decoration did not show in the PDF.
  •  Posted by on July 8, 2015 at 3:57 pm