uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marshall Schor (JIRA)" <...@uima.apache.org>
Subject [jira] Commented: (UIMA-1051) doc build not working on Linux
Date Wed, 02 Jun 2010 00:11:36 GMT

    [ https://issues.apache.org/jira/browse/UIMA-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874328#action_12874328
] 

Marshall Schor commented on UIMA-1051:
--------------------------------------

I agree.  The absolute paths (to windows palaitino fonts) only work on Windows, and perhaps
not on more recent versions... 

Alternatives:

* give up on the special Palatino font, and just use something commonly available.
* use OS - triggered profiles to select Palatino on Windows platform, and something more or
less equivalent on (most?) (all?) other platforms (Linux & Mac).

The downside to switching fonts based on platforms is that the page layout may change, and
the PDFs generated may have different page numbers.  This may make the olink databases (which
record page numbers, among other things, for PDFs) dependent on the platform.  

It may also be the case that even if we went with a commonly available font, such as Times
Roman, that the fonts for that on different platforms may be slightly different, so the above
problem may be there in any case.

My feeling at this point is to drop the special Palatino font, and go with the most common
default variable spacing PDF font (probably Times Roman), on all platforms.  Other opinions?



> doc build not working on Linux
> ------------------------------
>
>                 Key: UIMA-1051
>                 URL: https://issues.apache.org/jira/browse/UIMA-1051
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout, Documentation
>    Affects Versions: 2.2.2AS, 2.2.2, 2.3
>            Reporter: Marshall Schor
>            Priority: Minor
>
> The document build on Linux for UIMA-AS (and  for base UIMA too) fails to properly make
the olink (cross document reference database system) work, because of differing file naming
conventions between linux and windows.
> The document build also fails to handle the font selection - that code was built just
for Windows.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message