This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
usage:faq [2020/02/14 03:29] – Host User Manual Locally flywire | usage:faq [2020/03/24 06:27] – ODA Online Converter flywire | ||
---|---|---|---|
Line 44: | Line 44: | ||
**The DXF import process failed, why?**\\ | **The DXF import process failed, why?**\\ | ||
- | LibreCAD does not support all features of Autodesk DXF format. Currently only the following DXF formats are supported : R12, R14, 2000, 2004 and 2007. If you have issues to import some DXF files, please report them on the [[http:// | + | LibreCAD does not support all features of Autodesk DXF format. Currently, only the following DXF formats are supported: R12, R14, 2000, 2004 and 2007. If you have issues to import some DXF files, please report them on the [[http:// |
+ | **Open Design Alliance File Converter**\\ | ||
+ | Try the [[https:// | ||
==== Printing/ | ==== Printing/ | ||
**Why does exporting a PDF produce a blank page?**\\ | **Why does exporting a PDF produce a blank page?**\\ | ||
Line 58: | Line 59: | ||
**Where can I find the upcoming release of LibreCAD? | **Where can I find the upcoming release of LibreCAD? | ||
- | For most OS, it is possible to build the release under development with this [[https:// | ||
- | |||
For most OS, it is possible to build the release under development with this [[https:// | For most OS, it is possible to build the release under development with this [[https:// | ||
Line 68: | Line 67: | ||
**Purpose: | **Purpose: | ||
- | * Allow Read the Docs files to be hosted locally and viewed | + | * Allow Read the Docs files to be viewed |
* Make edits to the docs themselves and render them locally so you can inspect changes before pushing back to the fork | * Make edits to the docs themselves and render them locally so you can inspect changes before pushing back to the fork | ||
Line 83: | Line 82: | ||
* In your browser enter http:// | * In your browser enter http:// | ||
- | If you make any changes to the User Manual files they will be updated in the browser. | + | If you make any changes to the local User Manual files they will be updated in the browser. |
+ | |||
+ | |||
+ | ==== Contribute on GitHub ==== | ||
+ | |||
+ | **Can I easily contribute on GitHub?** | ||
+ | |||
+ | **Yes**, with a simple //pull request//. You will need to register a GitHub account, login then go to the page. For example, click the //Edit on GitHub// link in the top right-hand corner of any User Manual page to go to the page. | ||
+ | |||
+ | * Click the **pencil** button, make any edits you want and preview them to confirm. Give the proposed change a description up to 50 characters and optionally an extended description then click the **Propose file Change** button. | ||
+ | * If you're reading this you won't have write access to the repository so GitHub will create a copy of the repository as a branch of a fork in your account. Click the **Create pull request** button. | ||
+ | * Give the //Pull Request// a description and add any comments then click **Create pull request**. | ||
+ | |||
+ | Many GitHub files are in a special format, for example, the User Manual uses reStructuredText. If the change is simple you might be able to stay within existing formatting or perhaps copy a similar formatted section from elsewhere and change it. If you mess it up get help or submit it anyway and let the repository owner fix it. | ||
+ | |||
+ | Each contribution should have its own branch so just start again. If you missed something in the //pull request// just open up your repository fork branch, change it and commit a new change. | ||
+ | |||
+ | This process will only work for one file and you can repeat it for two. Complex Pull Requests involving multiple files should be submitted using Git. | ||
+ | [[https:// |