This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| usage:faq [2020/04/01 12:44] – Links for FAQs flywire | usage:faq [2026/09/09 06:29] (current) – fixed Forum link lordofbikes | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| ===== Did you check the documentation ? ===== | ===== Did you check the documentation ? ===== | ||
| - | Please have a look at the [[https:// | + | Please have a look at the [[https:// |
| ===== FAQ sections ===== | ===== FAQ sections ===== | ||
| - | Below you will find some of most frequent questions asked on forum organized by topics. If you do not find the answer to you issue, you can ask for support on the [[http://forum.librecad.org/ | + | Below you will find some of most frequent questions asked on forum organized by topics. If you do not find the answer to you issue, you can ask for support on the [[https://discourse.librecad.org/ |
| **[[usage: | **[[usage: | ||
| Line 78: | Line 78: | ||
| === 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://forum.librecad.org/ | + | 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 [[https://discourse.librecad.org/ |
| === Open Design Alliance File Converter === | === Open Design Alliance File Converter === | ||
| Line 126: | Line 126: | ||
| === Can I easily 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. | + | **Yes**, with a simple //pull request// |
| - | * 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. | + | * Click the **pencil** button, search for text near the location, make any edits you want then preview them to confirm |
| - | * If you're reading this you won't have write access to the repository so GitHub will create a copy of the repository | + | * If you're reading this you won't have write access to the repository |
| - | * Give the //Pull Request// a description and add any comments then click **Create pull request**. | + | * 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. | + | **Hints** |
| - | Each contribution should have its own branch so just start again. If you missed something in the //pull request// just open up your repository | + | Many GitHub files are in a special format, for example, the User Manual uses reStructuredText. Codes are used to format the document so a simple search in the browser will only find text formatted the same (and Chrome would search the file but Firefox would only search the screen). If the change is simple you might be able to stay within existing formatting, try a blank line before/ |
| + | |||
| + | Each contribution should have its own branch so just start again. If you missed something in the //pull request// just open up your repository 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. | 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:// | [[https:// | ||