如何将 .nfo 文件转换为 .fff 文件

Question

我有一个信息库文件，我想将其转换为 HTML。我正在尝试使用以下库对其进行转换：https://github.com/imazen/folioxml它附带一个配置文件，其中一部分如下所示

myconfig:
....
 
  infobases:
    - id: info_a
      path: "files/info_a.FFF"
      aliases:
        - 'C:\files\info_a.NFO'
    - id: info_b
      path: "files/info_b.FFF"
      aliases:
        - 'C:\files\info_b.NFO
...

我能够使用给定的命令构建并运行该工具

• mvn clean 编译程序集：single -U -B -fae
• java -jar commandline/target/folioxml-commandline-jar-with-dependency.jar -config core/folioxml/resources/test.yaml -export folio_help

但是它失败并出现错误，因为它需要上面配置中指定的 FFF 文件

在阅读上述存储库中的自述文件后，他们指定了一些将 .NFO 导出到 .FFF 的方法，他们建议使用 Folio Views 或 Folio Builder，但我无法找到有关这些工具的更多信息

有人可以提供有关上述工具的更多信息，例如在哪里可以找到它们，或者告诉我有关将 .NFO 文件导出到 .FFF 的任何其他方法

感谢您的帮助

Answer 1

遗憾的是，“Folio Views”等被出售了好几次*，而我上次检查时，它的所有者是一家不积极出售它的公司。

“Folio Builder”是一款单独出售的工具，用于“打包”由 Folio Views 创建的信息库并将其发布到 CD。我记得 Folio Builder 相当昂贵。这就是创建 FFF 文件（平面文件）的工具。

Folio Views 可以创建影子文件，但我认为它与平面文件不同。

我认为 Folio Views 信息库有一个免费查看器，您可以询问 Lilith River 是否有（以及是否有帮助）。仅供参考：还有一个名为 Folio Integrator 的 SDK/API，它的价格甚至更贵。

也许你可以找到现在的主人，看看他们是否愿意提供帮助。当我尝试联系他们时，他们没有回应，也许你会运气更好。

*这么好的产品，卖给了微软，然后微软又卖了。

Answer 2

我也有一个平面文件（.FFF）及其定义文件（.DEF）。但是当我使用该包时，将其转换为 .HTML/.XML 文件时遇到一些错误。 当我按照自述文件中提到的过程操作时，会生成这两个文件。

在日志文件中显示以下错误：-

导出资源... 线程“main”中出现异常 java.io.IOException：Infobase CPACHB 存在于集合中，但 lucene 索引中缺少根记录。 在 folioxml.export.plugins.ResolveHyperlinks.loadAnalyzerFromLucene（ResolveHyperlinks.java:53） 在 folioxml.export.plugins.ResolveHyperlinks.loadAnalyzers（ResolveHyperlinks.java:59） 在 folioxml.export.plugins.ResolveHyperlinks.beginInfobaseSet（ResolveHyperlinks.java:87） 在 folioxml.export.InfobaseSetVisitor.complete（InfobaseSetVisitor.java:69） 在 folioxml.export.ExportRunner.Export(ExportRunner.java:130) 在 folioxml.command.Main.run(Main.java:70) 在 folioxml.command.Main.main(Main.java:40) 在 highslide 文件夹中生成这些文件，如下图所示：-

我已附上我的 config.yaml 文件

myconfig:
export_xml: true #Creates a single XML file with all the content (excluding the 
stylesheet, images, and logs)  (default=true)
skip_normal_records: false # affects xml only - only writes out hierarchy
affecting levels, in order to make a shorter file. (default=false)
nest_file_elements: true # affects XML only - Disables nested syntax for <file> 
elements in xml, uses flat structure. Nesting uses same hierarchy as folio. 
(default=true)
indent_xml: true #Indentation can introduce undesired visual 
artificacts/spacing, and should only be used for human consumption. 
(default=true)

export_inventory: true # Lowers performance - tracks unique elements in memory, 
generates a textual report at the end. (default=true)

export_hidden_text: true # Halves performance. Writes out a log of text that 
would be hidden by the generated CSS (either via display:none or zero-contrast 
coloring). (default=true)

resolve_jump_links: false # Disable fixing up jump links (default=true)
resolve_query_links: false # Disable simulating queries and linking them to the 
first result. If this and resolve_jump_links are false, no Lucene index is 
required. (default=true)

export_html: true # Exports lots of browsable HTML files according to the 
splitting and naming rules. (default=true)
use_highslide: true #affects both XML and HTML. Required for popups/notes to 
keep working. (default=true)
add_nav_links: true #html only # Adds prev/next links at the beginning and end 
of each HTML generated. (default=true)

faux_tabs: false # Enable faux tabs (default=false)
faux_tabs_window_min: 80 # We have to deal with centered and right-aligned 
tabs.
faux_tabs_window_max: 120 # These provide the default and maximum (character 
count) bounds with which to simulate them.

# Here we can manually map broken URLs (and cross-infobase links) to new places
# link_mapper:
#   urls:
#     'C:\Files\Data.pdf': "https://othersite/data"

#   infobases:
#     'C:\Files\Other.NFO': "http://othersite/other"
#     'C:\Files\Other2.NFO': "http://othersite/other2"

#This is how we trash stuff we don't care about
# pull: # log_pulled_elements.txt and log_dropped_elements.txt are created
#   program_links: true
#   menu_links: true
#   drop_notes: false # It can be cleaner to drop notes/popups than preserve 
them with highslide & javascript. Dropped data is logged.
#   drop_popups: false # When use_highslide is false, the popups would 
otherwise be invalid HTML
#   ole_objects: false
#   metafile_objects: false
#   links_to_infobases:
#     - 'C:\Files\Obsolete.NFO'
#     - 'C:\Files\Obsolete2.NFO'

#You must convert all your infobases that link to each other at once, otherwise 
those links will not be preserved.
#In addition, unique IDs will overlap between infobases converted separately, 
causing potential issues in your final data store.
infobases:
- id: CPACHB
  path: "files/CPACHB.FFF"
  # aliases:
  #   - 'C:\files\CPACHB.NFO'
# - id: info_b
#   path: "files/info_b.FFF"
#   aliases:
#     - 'C:\files\info_b.NFO'

#Structure affects how we split the infobase into parts and identify those 
parts.
# We can specify a custom provider class

structure_class: "folioxml.export.structure.IdSlugProvider"
structure_class_params: ["null", "null", 0, 0, 1]

#structure_class_params: String levelRegex, String splitOnFieldName, Integer 
idKind, Integer root_index, Integer start_index

# levelRegex lets us split based on predefined folio levels like "Heading 
1|Heading 2"
# splitOnFieldName lets us split whenever a record contains the given field.
# idKind values
# 0 (heading-based slugs), 1 (integers), 2 (nested integers 2.3.1), 3 (guids), 
or 4 (folio IDs). Schemes 5-9 use the contents of splitOnFieldName and fall 
back to 0-4 if missing or non-unique.
# root_index and start_index are used for idKinds 2 and 3 (as well as 7 and 8, 
of course).

asset_start_index: 1 #What index do we start with for asset IDs.

#Only set this to true if you also set export_locations: images: url to a 
template that can respond based on numeric ID instead of filename. See 
AssetInventory.xml
asset_use_index_in_url: false

export_locations:
default:
  path: "files/export/{id}-{stamp}/{input}" #Used for text, xml files, css, and 
logs
image:
  path: files/export/{input} #Adjust this to represent the absolute path where 
the static images will be stored. Control {input} with asset_use_index_in_url
luceneindex:
  path: "files/indexes/myconfig/" #Just a temp directory.
html:
  path: "files/export/{id}-{stamp}/html/{input}.html" #Adjust this to represent 
the final hosted location of your HTML pages, as an absolute path. Adjust 
idKind to change {input}

请帮我将这些文件转换为 XML/HTML 对开平面文件夹