![]() The *easiest* way is to i)Įmail me a sample data file and ii) the subroutine you used to write it,Īnd I will happily create a data read for your file format.Ĭommand line options : - p fileprefix : change prefix to ALL settings files read / written by splash - d defaultsfile : change name of defaults file read / written by splash - l limitsfile : change name of limits file read / written by splash - e, - ev : use default options best suited to ascii evolution files ( ie. If this does not work, point to the location of your fits libraries with FITS_DIR=/path/to/fits.įurther details on writing your own subroutine are given inĪppendix Data reads and command line options. Compile splash with H5PART_DIR=/path/to/h5part/. Compile splash with PBOB_DIR=/path/to/pbob/. Table 2 Other supported file formats that require external libraries ¶ splash Command Will recognise that the file dump_000.h5 is in the HDF5 format, and will automatically select the correct read_data routine.īelow is a list of other formats supported, but have additional library requirements. ![]() h5, the suffix _hdf5 from the splash command can be removed. Reads tracer particle output from the FLASH code. Reads HDF5 format from the AMUSE framework. Reads HDF5 format from the gadget code (automatically recognised) Table 1 Supported HDF5 data formats ¶ splash Command Other supported formats are listed in Other supported file formats that require external libraries, but these require additional libraries.īelow is a list of the supported data formats that require HDF5. If splash is compiled with HDF5=yes, the formats listed in Supported HDF5 data formats will also be available in the splash binary. Lines 18-26 is where you can define them.Ĭomments, complains, requests are always welcome, either here or at SF.Alias asplash = 'splash ' # Alias for ascii splash alias ssplash = 'splash -f phantom ' alias gsplash = 'splash -f gadget ' alias vsplash = 'splash -f vine ' alias nsplash = 'splash -f ndspmhd ' alias rsplash = 'splash -f srosph ' alias dsplash = 'splash -f dragon ' alias srsplash = 'splash -f seren ' alias tsplash = 'splash -f tipsy ' alias tsplash = 'splash -f tipsy ' alias msplash = 'splash -f mhutch ' HTML output is not CSS-enabled, but you can fairly easy change colors in the script itself. Context is colored differently, and the actual text is highlighted. String contents = table_file.getText('UTF-8')Ĭontents = contents.replaceAll(/\\s+\\\.*\\Ĭonsole.println "$count segments written to $table_file"Īs you see in the screenshot, there will be none or more tables that show filename, segment number, text of the note on yellow background, and source and target text of the current segment surrounded by the respective context (if available). Target = painttag(target, curtagbg, tagfg) ![]() Target = StaticUtils.makeValidXML(target).replaceAll(/zzznullzzz/, //) Source = painttag(source, curtagbg, tagfg) Source = StaticUtils.makeValidXML(source) Table_file = new File(folder + projname + '_notes.html')ĭef painttag = Projname = new File(prop.getProjectRoot()).getName() ShowMessageDialog null, msg, title, INFORMATION_MESSAGEĭef folder = prop.projectRoot+'script_output/' * tagbg = '#E5E4E2' //tag background in contextĭef tagfg = 'green' //tag foreground in contextĭef contxtfg = 'darkgray' //font foreground in contextĭef curtagbg = '#BCC6DD' //tag background in segment's textĭef curtagfg = 'green' //tag foreground in segment's textĭef curtxtbg = '#BCC6CC' //font background in segment's textĭef filenmbg = 'lightgray' //cell background for filenameĭef thbg = 'gray' //table heading cells backgroundįinal def msg = 'Please try again after you open a project.' * number, text of the note, source and target text (with text from prev. * heading, then for each segment with a note there is a row with segment * is exported to a separate table that has the name of the file as its * #Files: Writes 'NAME_notes.html' in the 'script_output' subfolder * #Purpose:Ğxport the project's notes into a HTML table * THIS SCRIPT HAS BEEN SPONSORED BY TRANSLATION AGENCY VELIOR Here’s the listing, and the script title is linked to SF.net where you can download it. When the script is invoked, it will create a file named PROJECTNAME_notes.html in /script_output subfolder of the current project root (the subfolder will be created if it doesn’t exist, and PROJECTNAME is the actual name, of course). ![]() It may help you to discuss different translation issues with the client/editor/your spiritual guru or review your own translation if you use notes for yourself. Here’s a new script that lets you export OmegaT project notes to a HTML table.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |