Online Flare HTML Output Directory
Overview
An online directory can be made available for Flare localization projects including HTML outputs, whereas the translatable topic files (.htm) and their related snippet files (.flsnp) are listed side by side.
Bearing in mind these two file types are the lion's share of any Flare project translation effort, such directory or file list is a valuable help for any linguist tackling a translation or proofreading job.
The table below is an example of an online directory
| Filename | Folder | Snippet (FLSNP) | Type | Source | Target |
|---|---|---|---|---|---|
| Application Info.htm | Admin/User Guide | EN | JA | ||
| WorkingWithApps.htm | Admin/User Guide | EN | JA | ||
| ProductNames.htm | Overview | SeeAlso_Proxy.flsnp | snippetBlock | EN | JA |
| Implement-BackEnd.htm | Overview | EN | JA | ||
| AppletInstallation.htm | Installation | EN | JA | ||
| InstallAppletsOnFrontEndMachines.htm | Installation | SeeAlso_Proxy.flsnp | snippetBlock | EN | JA |
| LP-OS-AppletInstallation.htm | Installation | EN | JA | ||
| LP-Windows-AppletInstallation.htm | Installation | SeeAlso_Proxy.flsnp | snippetBlock | EN | JA |
| OS-AppletCommands.htm | Installation | SeeAlso_Proxy.flsnp | snippetBlock | EN | JA |
| OS-InstallApplets.htm | Installation | EN | JA | ||
| OS-PostInstall.htm | Installation | EN | JA | ||
| OS-SystemRequirements.htm | Installation | EN | JA | ||
| OS-UninstallApplets.htm | Installation | MinimumRequirements.flsnp | snippetBlock | EN | JA |
| NetworkTraffic.htm | Installation | EN | JA | ||
| ProxyConfiguration.htm | Installation | EN | JA | ||
| Windows-AppletCommands.htm | Installation | EN | JA | ||
| Windows-InstallApplets.htm | Installation | EN | JA | ||
| Windows-InstallApplets-Addon.htm | Installation | EN | JA | ||
| Windows-SystemRequirements.htm | Installation | WindowsInstal.flsnp | snippetBlock | EN | JA |
| Windows-UninstallApplets.htm | Installation | SysReqMinimumFrontEndRequirements.flsnp | snippetBlock | EN | JA |
| Windows-UpgradingApplets.htm | Installation | EN | JA | ||
| Best Practices.htm | Intro | EN | JA | ||
| FAQs.htm | Intro | SeeAlso_Proxy.flsnp | snippetBlock | EN | JA |
| Home.htm | Resources/Menu | About.flsnp | EN | JA | |
| SeeAlso_Proxy.flsnp | snippetBlock | EN | JA | ||
| Search.htm | Resources/Menu | PageTiles.flsnp | snippetText | EN | JA |
| Important Notice.htm | Resources/FrontMatter | EN | JA | ||
| Bulletins.htm | Security | EN | JA | ||
| Instal Best Practices.htm | Security | EN | JA | ||
| Videos-Setup.htm | Videos | EN | JA | ||
| AdvancedPolicyDefinition.htm | WebApps | EN | JA | ||
| API Commands.htm | WebApps | EN | JA | ||
| CreatePolicy.htm | WebApps | EN | JA | ||
| DeletePolicy.htm | WebApps | EN | JA | ||
| SeeAdminAuditData.htm | WebApps | EN | JA | ||
| SeeAggregatedEvents.htm | WebApps | EN | JA | ||
| SeeComputerGroups.htm | WebApps | EN | JA | ||
| SeeComputers.htm | WebApps | EN | JA | ||
| SeeEPMVersion.htm | WebApps | EN | JA | ||
| SeePolicies.htm | WebApps | EN | JA | ||
| SeePolicyDetails.htm | WebApps | EN | JA | ||
| SeeRawEventDetails.htm | WebApps | EN | JA | ||
| SeeRawEvents.htm | WebApps | EN | JA | ||
| SeeSetsList.htm | WebApps | EN | JA |
There are different situations where such a directory can become handy. The following sections cover how an online directory can be useful:
The problem
A linguist working on a translation project tackles file translation in an out-of-context fashion — That is, when a translation project comprises more than one file, Computer-Aided Translation (CAT) tools present them in a sequential way, usually and from the translation view point, in a less-than-ideal sorting order. If the linguist needs to refer to the text being translated in context, they can select and copy the intended text and, if the reference HTML source output includes such feature, run a search to retrieve a list with all the files containing that text.
The resulting file list can be compact and a simple eye-ball browsing might suffice to pinpoint the required file. However, chances are the list is lengthy, expanding more than one page, in which case the process to locate the intended file can turn a little more complicated
The solution
Enter Online HTML Output File Directory. Having the possibility to easily locate a particular text within a Flare project greatly streamlines the chore to access the online reference topic.
Since the filename is made available to the linguist by the CAT tool, running a browser search for that filename on the online directory and clicking on the related link to access the topic content is immediate.
The directory also lists the folder path containing the project files in case they include one or more namesake files. In such cases, the file folder path can also be found in the CAT tool.
Goes without saying the Target column will be unavailable during the translation process but, once the translation is complete, this column will include a link to the target topic so the linguist or tester can conveniently switch between source and target topics.
The Online Directory in action
The following video shows how the Online HTML Output File Directory combined with Dynamic HTML Debug Output works: