Commit 4e212f27 authored by Decorde Jeffrey's avatar Decorde Jeffrey

Merge branch 'master' of gitlab.utc.fr:crozatst/hdoc

parents d8ad2c30 de68c417
......@@ -4,7 +4,7 @@
License GPL3.0
http://www.gnu.org/licenses/gpl-3.0.txt
## Crédits
## Credits
- 2015
- Jean-Côme Douteau
- Gabrielle Rit
......@@ -17,17 +17,17 @@ This module is able to convert several [etherpad](http://etherpad.org/) files (e
## User documentation
### Running etherpad_to_hdoc.ant
1. Create an etherpad document and export it as an html file.
1. please place your html files in the `/input` folder
2. run the `run.[bat|sh]` script of your choice depending on your OS
3. and retrieve the hdoc outputs in the `/output` folder
## Running etherpad_to_hdoc.ant
1. Create an etherpad document and export it as an html file.
2. please place your html files in the `/input` folder
3. run the `run.[bat|sh]` script of your choice depending on your OS
4. and retrieve the hdoc outputs in the `/output` folder
## Unsupported
- Markdown
- Author paternity
- Etherpad timeline
- Chat
- Markdown
- Author paternity
- Etherpad timeline
- Chat
## Known bugs
- Nested lists in lists are not supported
......@@ -42,35 +42,36 @@ Example :
</li>
<ul>`
- As a consequence, etherpad indentation is not supported because it is coded as nested lists.
## TODO
- Markdown
- Markdown
## Technical notes
### Description of etherpad_to_hdoc.ant
#### Prelude
- Importation of necessary classes (antlib, htmlcleaner, jing)
- Creation of directories architecture tree
- Importation of necessary classes (antlib, htmlcleaner, jing)
- Creation of directories architecture tree
#### Transformations
- Use of htmlcleaner to transform the input file from html to xhtml. For more info, see http://htmlcleaner.sourceforge.net/index.php.
- Apply html2xhtml.xsl : this xsl extracts the content into <body> tags
- Apply html2xhtmlv1.xsl : this xsl is used as a fix and adds br tag at the end of lists (ul and ol)
- Apply html2xhtmlv2.xsl : this xsl surround text line with p tags and transforms non-hdoc tags into hdoc tags as s, u, strong tags.
- Apply html2xhtml3.xsl : this xsl is used as a fix, it deletes p tags when its child is ul or ol
- Apply xhtml2hdoc.xsl : this xsl transforms the content into hdoc structure
- Use of htmlcleaner to transform the input file from html to xhtml. For more info, see http://htmlcleaner.sourceforge.net/index.php.
- Apply html2xhtml.xsl : this xsl extracts the content into <body> tags
- Apply html2xhtmlv1.xsl : this xsl is used as a fix and adds br tag at the end of lists (ul and ol)
- Apply html2xhtmlv2.xsl : this xsl surround text line with p tags and transforms non-hdoc tags into hdoc tags as s, u, strong tags.
- Apply html2xhtml3.xsl : this xsl is used as a fix, it deletes p tags when its child is ul or ol
- Apply xhtml2hdoc.xsl : this xsl transforms the content into hdoc structure
#### Post-transformations actions
- Build hdoc structure
- Jing checks if the output file is validated with the right rng schema
- Zip the directory into hdoc archive
- Build hdoc structure
- Jing checks if the output file is validated with the right rng schema
- Zip the directory into hdoc archive
### Supported tags
html tags -> hdoc tags
- u, s, em, strong -> em
- li -> li
- ol -> ol
- br -> p
- html tags -> hdoc tags
- u, s, em, strong -> em
- li -> li
- ol -> ol
- br -> p
## Capitalisation
We learned how to use xsl sheets with text file as an input : we had to use regular expressions to extract content.
\ No newline at end of file
......@@ -4,32 +4,39 @@
## Credits
- Rit Gabrielle
- Vintache Jean
- Douteau Jean-Côme
- Fecherolle Cécile (2014)
##Presentation
- Douteau Jean-Côme
- Fecherolle Cécile (2014)
## Presentation
How to transform an etherpad document in lexique document.
Filepath in this document are relative to this file readme.
## Dependence
- Etherpad2Hdoc
- Hdoc2Lexique
## User Documentation
1. Download an etherpad document in html format.
1. Create or join an etherpad document then export it in html format (Import/Export Button) in the `/input` directory (if the directory does not exists, you have to create it).
2. Name it pad.html
2. Execute the file `/run.bat` or `/run.sh` depending on the OS. A `.scar` file is created in the directory `/output`
*If the `/input` directory contains multiple files, they won't be all treated.
*If the `/input` directory contains multiple files, they won't be all treated.*
3. Open the document with Scenari
1. Open Scenari, and choose "UTC-etu_lexique" as distant depot.
2. Go in the directory `sandBox/etherpad-to-lexique.`
3. Import your `.scar` file in the directory.
4. Open the file Main.xml created.
##Unsupported
## Unsupported
- MarkDown
- Timeline and author paternity
- Chat
##Known bugs
## Known bugs
Nested lists in lists are not supported
example :
Example :
`<ul>
<li>
<ul>
......@@ -43,29 +50,25 @@ example :
## TODO
- Work with markdown
- Correct nested lists
## Technical notes
### Description of etherpad_to_hdoc.ant
#### Prelude
- Importation of necessary classes (antlib, htmlcleaner, jing)
- Creation of directories architecture tree
- Importation of necessary classes (antlib, htmlcleaner, jing)
- Creation of directories architecture tree
#### Transformations
- Use of htmlcleaner to transform the input file from html to xhtml. For more info, see http://htmlcleaner.sourceforge.net/index.php.
- Apply html2xhtml.xsl : this xsl extracts the content into <body> tags
- Apply html2xhtmlv1.xsl : this xsl is used as a fix and adds br tag at the end of lists (ul and ol)
- Apply html2xhtmlv2.xsl : this xsl surround text line with p tags and transforms non-hdoc tags into hdoc tags as s, u, strong tags.
- Apply html2xhtml3.xsl : this xsl is used as a fix, it deletes p tags when its child is ul or ol
- Apply xhtml2hdoc.xsl : this xsl transforms the content into hdoc structure
- Use of htmlcleaner to transform the input file from html to xhtml. For more info, see http://htmlcleaner.sourceforge.net/index.php.
- Apply html2xhtml.xsl : this xsl extracts the content into <body> tags
- Apply html2xhtmlv1.xsl : this xsl is used as a fix and adds br tag at the end of lists (ul and ol)
- Apply html2xhtmlv2.xsl : this xsl surround text line with p tags and transforms non-hdoc tags into hdoc tags as s, u, strong tags.
- Apply html2xhtml3.xsl : this xsl is used as a fix, it deletes p tags when its child is ul or ol
- Apply xhtml2hdoc.xsl : this xsl transforms the content into hdoc structure
#### Post-transformations actions
- Build hdoc structure
- Jing checks if the output file is validated with the right rng schema
- Zip the directory into hdoc archive
## Capitalisation
- Build hdoc structure
- Jing checks if the output file is validated with the right rng schema
- Zip the directory into hdoc archive
## Capitalisation
\ No newline at end of file
......@@ -4,14 +4,19 @@
## Credits
- Rit Gabrielle
- Vintache Jean
- Douteau Jean-Côme
- Fecherolle Cécile (2014)
##Presentation
- Douteau Jean-Côme
- Fecherolle Cécile (2014)
## Presentation
How to transform an etherpad document in opale document.
Filepath in this document are relative to this file readme.
Filepaths in this document are relative to this readme file.
## Dependence
- Etherpad2Hdoc
- Hdoc2Opale
## User Documentation
1. Download an etherpad document in html format.
1. Create or join an etherpad document then export it in html format (Import/Export Button) in the `/input` directory (if the directory does not exists, you have to create it).
......@@ -22,13 +27,17 @@ Filepath in this document are relative to this file readme.
2. Go in the directory `sandBox/etherpad-to-opale.`
3. Import your `.scar` file in the directory.
4. Open the file Main.xml created.
##Unsupported
## Unsupported
- MarkDown
- Timeline and author paternity
- Chat
##Known bugs
Nested lists in lists are not supported
example :
## Known bugs
Nested lists in lists are not supported.
Here's an example :
`<ul>
<li>
<ul>
......@@ -42,29 +51,25 @@ example :
## TODO
- Work with markdown
- Correct nested lists
## Technical notes
### Description of etherpad_to_hdoc.ant
#### Prelude
- Importation of necessary classes (antlib, htmlcleaner, jing)
- Creation of directories architecture tree
- Importation of necessary classes (antlib, htmlcleaner, jing)
- Creation of directories architecture tree
#### Transformations
- Use of htmlcleaner to transform the input file from html to xhtml. For more info, see http://htmlcleaner.sourceforge.net/index.php.
- Apply html2xhtml.xsl : this xsl extracts the content into <body> tags
- Apply html2xhtmlv1.xsl : this xsl is used as a fix and adds br tag at the end of lists (ul and ol)
- Apply html2xhtmlv2.xsl : this xsl surround text line with p tags and transforms non-hdoc tags into hdoc tags as s, u, strong tags.
- Apply html2xhtml3.xsl : this xsl is used as a fix, it deletes p tags when its child is ul or ol
- Apply xhtml2hdoc.xsl : this xsl transforms the content into hdoc structure
- Use of htmlcleaner to transform the input file from html to xhtml. For more info, see http://htmlcleaner.sourceforge.net/index.php.
- Apply html2xhtml.xsl : this xsl extracts the content into <body> tags
- Apply html2xhtmlv1.xsl : this xsl is used as a fix and adds br tag at the end of lists (ul and ol)
- Apply html2xhtmlv2.xsl : this xsl surround text line with p tags and transforms non-hdoc tags into hdoc tags as s, u, strong tags.
- Apply html2xhtml3.xsl : this xsl is used as a fix, it deletes p tags when its child is ul or ol
- Apply xhtml2hdoc.xsl : this xsl transforms the content into hdoc structure
#### Post-transformations actions
- Build hdoc structure
- Jing checks if the output file is validated with the right rng schema
- Zip the directory into hdoc archive
## Capitalisation
- Build hdoc structure
- Jing checks if the output file is validated with the right rng schema
- Zip the directory into hdoc archive
## Capitalisation
\ No newline at end of file
......@@ -4,32 +4,40 @@
## Credits
- Rit Gabrielle
- Vintache Jean
- Douteau Jean-Côme
- Fecherolle Cécile (2014)
##Presentation
- Douteau Jean-Côme
- Fecherolle Cécile (2014)
## Presentation
How to transform an etherpad document in optim document.
Filepath in this document are relative to this file readme.
## Dependence
- Etherpad2Hdoc
- Hdoc2Optim
## User Documentation
1. Download an etherpad document in html format.
1. Create or join an etherpad document then export it in html format (Import/Export Button) in the `/input` directory (if the directory does not exists, you have to create it).
2. Name it pad.html
2. Execute the file `/run.bat` or `/run.sh` depending on the OS. A `.scar` file is created in the directory `/output`
*If the `/input` directory contains multiple files, they won't be all treated.
*If the `/input` directory contains multiple files, they won't be all treated.*
3. Open the document with Scenari
1. Open Scenari, and choose "UTC-etu_optim" as distant depot.
2. Go in the directory `sandBox/etherpad-to-otpim.`
3. Import your `.scar` file in the directory.
4. Open the file Main.xml created.
##Unsupported
## Unsupported
- MarkDown
- Timeline and author paternity
- Chat
##Known bugs
Nested lists in lists are not supported
example :
## Known bugs
Nested lists in lists are not supported.
Example :
`<ul>
<li>
<ul>
......@@ -43,29 +51,25 @@ example :
## TODO
- Work with markdown
- Correct nested lists
## Technical notes
### Description of etherpad_to_hdoc.ant
#### Prelude
- Importation of necessary classes (antlib, htmlcleaner, jing)
- Creation of directories architecture tree
- Importation of necessary classes (antlib, htmlcleaner, jing)
- Creation of directories architecture tree
#### Transformations
- Use of htmlcleaner to transform the input file from html to xhtml. For more info, see http://htmlcleaner.sourceforge.net/index.php.
- Apply html2xhtml.xsl : this xsl extracts the content into <body> tags
- Apply html2xhtmlv1.xsl : this xsl is used as a fix and adds br tag at the end of lists (ul and ol)
- Apply html2xhtmlv2.xsl : this xsl surround text line with p tags and transforms non-hdoc tags into hdoc tags as s, u, strong tags.
- Apply html2xhtml3.xsl : this xsl is used as a fix, it deletes p tags when its child is ul or ol
- Apply xhtml2hdoc.xsl : this xsl transforms the content into hdoc structure
- Use of htmlcleaner to transform the input file from html to xhtml. For more info, see http://htmlcleaner.sourceforge.net/index.php.
- Apply html2xhtml.xsl : this xsl extracts the content into <body> tags
- Apply html2xhtmlv1.xsl : this xsl is used as a fix and adds br tag at the end of lists (ul and ol)
- Apply html2xhtmlv2.xsl : this xsl surround text line with p tags and transforms non-hdoc tags into hdoc tags as s, u, strong tags.
- Apply html2xhtml3.xsl : this xsl is used as a fix, it deletes p tags when its child is ul or ol
- Apply xhtml2hdoc.xsl : this xsl transforms the content into hdoc structure
#### Post-transformations actions
- Build hdoc structure
- Jing checks if the output file is validated with the right rng schema
- Zip the directory into hdoc archive
## Capitalisation
- Build hdoc structure
- Jing checks if the output file is validated with the right rng schema
- Zip the directory into hdoc archive
## Capitalisation
\ No newline at end of file
......@@ -3,22 +3,23 @@
License GPL3.0
http://www.gnu.org/licenses/gpl-3.0.txt
##Crédits
## Crédits
Antoine Aufrechter, Estelle de Magondeaux, Marouane Hammi
##Install
## Install
In order to use this converter, follow those steps :
1. Copy your hdoc file (.scar or .zip) into the input directory. Do not put more than one file into the input directory.
2. Execute the run that correspond to your OS.
3. You will find the result into the output directory.
##User documentation
## User documentation
For each definition in the content.xml a .term is generated and for each source that is referenced in a definition the image associated (with its meta and props files) is copied into the output file with the definition.
##Known bugs
## Known bugs
>- Cannot put multiple input files
##TODO
>- Change the name of the file (.term) to the definition associated
## TODO
>- Change the name of the file (.term) to have a name without special character
>- Manage multiple input files (e.g. see lexique_to_opale)
>- list of element to convert :
>>- src url
......@@ -27,8 +28,8 @@ In order to use this converter, follow those steps :
>>- type (female, male,...) and (abbreviation, expanded,...)
>>- array
>>- multimedia
>-Do not generate the content.term or use it to generate an index instead (currently content.term is generated but useless)
##Technical notes
## Technical notes
>- The converter have to respect the same schema as the lexique_to_hdoc converter for the xslt
##Capitalisation
......@@ -22,10 +22,19 @@
<xsl:template match="h:section">
<xsl:apply-templates select="h:div"/>
<xsl:apply-templates select="h:section"/>
<xsl:apply-templates select="h:p"/>
</xsl:template>
<xsl:template match="h:div">
<xsl:apply-templates select="h:section"/>
<xsl:apply-templates select="h:p"/>
<xsl:apply-templates select="h:img"/>
<xsl:apply-templates select="h:object"/>
<xsl:apply-templates select="h:audio"/>
</xsl:template>
<xsl:template match="h:p">
<xsl:apply-templates select="h:p"/>
<xsl:apply-templates select="h:img"/>
<xsl:apply-templates select="h:object"/>
<xsl:apply-templates select="h:audio"/>
......@@ -33,17 +42,19 @@
<xsl:template match="h:img">
<xsl:variable name="src" select="@src"/>
<copy file="${srcdir}/${nameInputsId}/{$src}" tofile="${outdir}/{$src}"/>
<copy file="${{srcdir}}/${{nameInputsId}}/{$src}" tofile="${{outdir}}/{$src}"/>
<copy file="${{srcdir}}/${{nameInputsId}}/{$src}/../meta.xml" tofile="${{outdir}}/{$src}/../meta.xml"/>
<copy file="${{srcdir}}/${{nameInputsId}}/{$src}/../props.xml" tofile="${{outdir}}/{$src}/../props.xml"/>
</xsl:template>
<xsl:template match="h:object">
<xsl:variable name="data" select="@data"/>
<copy file="${srcdir}/${nameInputsId}/{$data}" tofile="${outdir}/{$data}"/>
<copy file="${{srcdir}}/${{nameInputsId}}/{$data}" tofile="${{outdir}}/{$data}"/>
</xsl:template>
<xsl:template match="h:audio">
<xsl:variable name="src" select="@src"/>
<copy file="${srcdir}/${nameInputsId}/{$src}" tofile="${outdir}/{$src}"/>
<copy file="${{srcdir}}/${{nameInputsId}}/{$src}" tofile="${{outdir}}/{$src}"/>
</xsl:template>
</xsl:stylesheet>
......
......@@ -10,54 +10,42 @@
<xsl:output method="xml" indent="yes" />
<xsl:template match="/">
<sc:item xmlns:sc="http://www.utc.fr/ics/scenari/v3/core">
<lx:term xmlns:sp="http://www.utc.fr/ics/scenari/v3/primitive" xmlns:lx="scpf.org:lexicon">
<lx:termM>
<sp:name><xsl:value-of select="hodoc:html/hodoc:body/hodoc:h2[@span='titre_def']"></xsl:value-of></sp:name>
</lx:termM>
<sp:def>
<lx:definition>
<sp:desc>
<lx:defTxt>
<xsl:apply-templates select="hodoc:html/hodoc:body/hodoc:p[@span='def_content']"></xsl:apply-templates>
</lx:defTxt>
</sp:desc>
</lx:definition>
</sp:def>
</lx:term>
</sc:item>
<xsl:apply-templates select="./hodoc:html/hodoc:body"/>
</xsl:template>
<xsl:template match="hodoc:p[@span='def_content']" >
<xsl:value-of select="."/>
<xsl:template match="hodoc:section">
<xsl:result-document href="{hodoc:header/hodoc:h1}.term" encoding="UTF-8"> <!--TODO change name of the file-->
<sc:item xmlns:sc="http://www.utc.fr/ics/scenari/v3/core"
xmlns:sp="http://www.utc.fr/ics/scenari/v3/primitive" xmlns:lx="scpf.org:lexicon"
xmlns:file="java.io.File">
<lx:term >
<lx:termM>
<sp:name><xsl:value-of select="hodoc:header/hodoc:h1"></xsl:value-of></sp:name>
</lx:termM>
<sp:def>
<lx:definition>
<sp:desc>
<lx:defTxt>
<sc:para xml:space="preserve" sc:id="t7"><xsl:apply-templates select="hodoc:div/hodoc:p[@span='def_content']/hodoc:p[@class='def_text']"></xsl:apply-templates></sc:para>
</lx:defTxt>
</sp:desc>
</lx:definition>
</sp:def>
</lx:term>
</sc:item>
</xsl:result-document>
</xsl:template>
<xsl:template match="hodoc:p[@class='def_text']" >
<xsl:value-of select="./text()"/>
<!--
<xsl:copy>
<xsl:apply-templates select="node()|@*"/>
</xsl:copy>-->
</xsl:template>
<!-- <xsl:template match="/hodoc:html/hodoc:body">
<xsl:for-each select="/hodoc:html/hodoc:body/hodoc:section">
<xsl:result-document href="section{position()}.html"> TODO change name of the file
<sc:item xmlns:sc="http://www.utc.fr/ics/scenari/v3/core">
<lx:term xmlns:sp="http://www.utc.fr/ics/scenari/v3/primitive" xmlns:lx="scpf.org:lexicon">
<lx:termM>
<sp:name><xsl:value-of select="hodoc:h2[@span='titre_def']"></xsl:value-of></sp:name>
</lx:termM>
<sp:def>
<lx:definition>
<sp:desc>
<lx:defTxt>
<xsl:apply-templates select="hodoc:p[@span='def_content']"></xsl:apply-templates>
</lx:defTxt>
</sp:desc>
</lx:definition>
</sp:def>
</lx:term>
</sc:item>
</xsl:result-document>
</xsl:for-each>
</xsl:template>-->
</xsl:stylesheet>
......@@ -11,21 +11,21 @@ Marouane Hammi
Install
In order to use this converter, follow those steps :
1. Create a dictionnary "dictionnaire.xml" which referenciate every definition you want to put ini your hdoc. This dictionnary must respect the "dictionnaire.rng" schema
2. Copy the referenciated definitions in the same current path as the dictionnary (input)
3. Your input folder must contains the dictionnary (dictionnaire.xml) and the lexique definition (**.term).
4. Execute the run that correspond to your OS. (run.sh for linux, run.bat for ubuntu)
1. Create a dictionnary "dictionnaire.xml" which referenciate every definition you want to put in your hdoc. This dictionnary must respect the "dictionnaire.rng" schema
2. Copy the referenciated definitions in the same folder than the dictionnary (input)
3. Your input folder must contain the dictionnary (dictionnaire.xml) and the lexique definitions (**.term).
4. Execute the run that corresponds to your OS. (run.sh for Linux, run.bat for Windows)
5. You will find the result into the output directory: it is named "content.xml".
Dependances
none.
User documentation
You will find a "help" directory taht contains:
- A saple of dictionnary that you neef to write and call "dictionnaire.xml".
You will find a "help" directory that contains:
- A sample of dictionnary that you need to write and call "dictionnaire.xml".
- the lexique definition that you can choose to put into your hdoc (help/available_definition folder).
The generated folder is a .xml . If you desire to see the output in you browser, you need to rename it as a .html.
If you want to create more definitions with images and tables, you will need to put this ressources in the folder naed "&". It contains all the ressources which are copy-pasted in the output folder so they can de seen in the hdoc.
If you want to create more definitions with images and tables, you will need to put this ressources in the folder named "&". It contains all the ressources which are copy-pasted in the output folder so they can e seen in the hdoc.
Unsupported
Audio and video transformation
......@@ -34,11 +34,11 @@ Known bugs
TODO
create a better transformation for the ressources. At the moment the user needs to copy the ressources in a folder named "&". The best would be tomatch the ressources in every definitions, and to call an aNT which automatically copy the ressources needed in this folder.
create a better transformation for the ressources. At the moment the user needs to copy the ressources in a folder named "&". The best would be to match the ressources in every definitions, and to call an Ant which automatically copy the ressources needed in this folder.
Create a transformation which allows every audio resources to be seen in the hdoc.
Technical notes
If folders names are changed, you will need to change the tasks of the ANT file.
If folders' names are changed, you will need to change the tasks of the ANT file.
Capitalisation
......
......@@ -11,21 +11,21 @@ Marouane Hammi
Install
In order to use this converter, follow those steps :
1. Create a dictionnary "dictionnaire.xml" which referenciate every definition you want to put ini your hdoc. This dictionnary must respect the "dictionnaire.rng" schema
2. Copy the referenciated definitions in the same current path as the dictionnary (input)
3. Copy your ressources in a folder named "&", placed in the same current path as the dictionnary (input)
4. Your input folder must contains the dictionnary (dictionnaire.xml), the lexique definition (**.term), and the ressources folder(&).
5. Execute the run that correspond to your OS. (run.sh for linux, run.bat for ubuntu)
3. You will find the result into the output directory.
1. Create a dictionnary "dictionnaire.xml" which referenciate every definition you want to put in your hdoc. This dictionnary must respect the "dictionnaire.rng" schema
2. Copy the referenciated definitions in the same folder than the dictionnary (input)
3. Your input folder must contain the dictionnary (dictionnaire.xml) and the lexique definitions (**.term).
4. Execute the run that corresponds to your OS. (run.sh for Linux, run.bat for Windows)
5. You will find the result into the output directory: it is named "content.xml".
Dependance
Dependances
none.
User documentation
You will find a "help" directory taht contains:
- A saple of dictionnary that you neef to write and call "dictionnaire.xml".
You will find a "help" directory that contains:
- A sample of dictionnary that you need to write and call "dictionnaire.xml".
- the lexique definition that you can choose to put into your hdoc (help/available_definition folder).
- a sample of the "&" folder that you need to copy in the input directory. At the moment the only 2 resources referenciated in all the definitions are there, so you can simply copy-paste this directory to the input directory.
The generated folder is a .xml . If you desire to see the output in you browser, you need to rename it as a .html.
If you want to create more definitions with images and tables, you will need to put this ressources in the folder named "&". It contains all the ressources which are copy-pasted in the output folder so they can e seen in the hdoc.
Unsupported
Audio and video transformation
......@@ -34,11 +34,12 @@ Known bugs
TODO
create a better transformation for the ressources. At the moment the user needs to copy the ressources in a folder named "&". The best would be tomatch the ressources in every definitions, and to call an aNT which automatically copy the ressources needed in this folder.
create a better transformation for the ressources. At the moment the user needs to copy the ressources in a folder named "&". The best would be to match the ressources in every definitions, and to call an Ant which automatically copy the ressources needed in this folder.
Create a transformation which allows every audio resources to be seen in the hdoc.
Technical notes
If folders names are changed, you will need to change the tasks of the ANT file.
If folders' names are changed, you will need to change the tasks of the ANT file.
Capitalisation
@echo off
set lib=lib
<<<<<<< HEAD
set ant=lexique_to_hdoc.ant
=======
set ant=lexique_to_opale.ant
>>>>>>> e6164602e4169b2cb7eaf6215434ae0ed8be47a3
set antparam=-Dprogram.param=%1
set scJarList=%lib%\*
......
......@@ -15,7 +15,7 @@ Install
In order to use this converter, follow those steps :
1. Copy your Lexique file(s) (.scar or .zip) into the input directory.
2. Execute the run that correspond to your OS.
3. You will find the result into the output directory. The name of the output files depends of the hour it was processed.
3. You will find the result into the output directory. The name of the output files depends on the hour it was processed.
Dependance
......
......@@ -14,7 +14,7 @@ Install
In order to use this converter, follow those steps :
1. Copy your Lexique file(s) (.scar or .zip) into the input directory.
2. Execute the run that correspond to your OS.
3. You will find the result into the output directory. The name of the output files depends of the hour it was processed.
3. You will find the result into the output directory. The name of the output files depends on the hour it was processed.
Dependance
......
......@@ -12,7 +12,7 @@ Install
In order to use this converter, follow those steps :
1. Copy your Lexique file(s) (.scar or .zip) into the input directory.
2. Execute the run that correspond to your OS.
3. You will find the result into the output directory. The name of the output files depends of the hour it was processed.
3. You will find the result into the output directory. The name of the output files depends on the hour it was processed.
Dependance
......
Pour réaliser votre conversion vous devez ajouter votre fichier .scar dans le dossier input. Veillez à n'en placer qu'un seul
dedans. Ensuite il suffit d'appeler le script (.bat ou .sh).
\ No newline at end of file
Converter
---------
Opale2Hdoc
License
-------
GPL 3.0
Credits
-------
Thibault Drain
Christophe Virot
Pierre Lemaire
Dependance
----------
This project can be used alone if you only want to convert a opale .scar
into a hdoc file.
User Documentation
------------------
OPALE
You have to respect the following steps :
Extract a module file from your Opale workspace
You can't export directly a web, paper or slide show support. You must extract
a module scar.
Moreover, when you extract a module, keep the default configuration :
"Include descendant network" input : checked
"keep workspaces" : unchecked
1. First, if you want to transform your
Opale publication to a Hdoc format,
you have to export a module file as a scar.
2. Then you just have to put your scar in the repository input inside the project
opale_to_hdoc.
3.
Finally, you can either launch the bash, the bat or start the ant by
taping the following instruction : ant -buildfile opale_to_hdoc
Unsupported
----------
-
- Module
Titre court
Références générales
Activité d'auto évaluation
Exercice rédactionnel
Exercice QCM
Exercice QCM graphique
Exercice QCU