Task #1221
RCP: X.X, copy txm.css when import is done
Status: | New | Start date: | 01/07/2015 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% |
|
Category: | Import | Spent time: | - | |
Target version: | TXM X.X |
Description
Currently every edition page declares the "txm.css" stylesheet, but no "txm.css" file is added to the binary corpus directory by any import process (pager).
To help users style their editions, we should help them provide a CSS stylesheet file to the pager.
solution¶
- If an import process creates an edition and succesfully ends
- And a "txm.css" file is available in the
$HOME/TXM/css
directory - Then it must be copied into the
$TXM/corpora/$CORPUS/HTML/$CORPUS/default
directory (the directory may change see ticket about css link for portal corpus SH???)
History
#1 Updated by Matthieu Decorde over 8 years ago
- Description updated (diff)
#2 Updated by Serge Heiden over 8 years ago
- Description updated (diff)
#3 Updated by Serge Heiden over 8 years ago
- Description updated (diff)
#4 Updated by Serge Heiden over 8 years ago
- Description updated (diff)
#5 Updated by Serge Heiden over 8 years ago
- Description updated (diff)
#6 Updated by Serge Heiden over 8 years ago
- Description updated (diff)
#7 Updated by Matthieu Decorde over 7 years ago
- Target version changed from TXM 0.7.8 to TXM 0.8.0a (split/restructuration)
#8 Updated by Sebastien Jacquot about 6 years ago
Other way:
Add "CSS" file choice to "Editions" section of XTZ import form.
#9 Updated by Serge Heiden about 6 years ago
Sebastien Jacquot a écrit :
Other way:
Add "CSS" file choice to "Editions" section of XTZ import form.
Currently the XTZ module copies recursively the content of any 'xsl', 'css' and 'dtd' directories if present in the source directory (this behavior is not documented yet). So any css file present in the css directory can be accessed by html code.
#10 Updated by Sebastien Jacquot about 6 years ago
SJ: Thanks I found the doc here: https://groupes.renater.fr/wiki/txm-info/public/specs_import_xtz_docu
Maybe it would be more precise to show these information in the import form. eg. if "css", etc. directory is present, fill a "CSS browse" input text with its path otherwise leave empty and let the user browses to a path if he wants?
SH: For XTZ we must also consider all the possible XSL stylesheets available in the 4 different XSL steps source directories: 1-split-merge, 2-front, 3-posttok and 4-edition. In the XML/w+CSV module, there was an input parameter UI available for the xsl-front XSL stylesheet parameter choice. It was removed in the design of the new form for XTZ when we added 3 new xsl directories. We must redesign the UI of the form where 4 different xsl steps (sets of xsls) allow to select various xsl files or directories.
#11 Updated by Sebastien Jacquot almost 5 years ago
- Target version changed from TXM 0.8.0a (split/restructuration) to TXM 0.8.0
#12 Updated by Matthieu Decorde about 4 years ago
- Target version changed from TXM 0.8.0 to TXM X.X