1 |
On Fri, Oct 6, 2017 at 5:41 PM, <tuxic@××××××.de> wrote: |
2 |
> On 10/06 05:49, Andrew Tselischev wrote: |
3 |
>> On Fri, Oct 06, 2017 at 07:07:04PM +0200, tuxic@××××××.de wrote: |
4 |
>> > Hi, |
5 |
>> > |
6 |
>> > The u8g8lib, which contains libraries to drive a great amount of |
7 |
>> > displays for mainly embedded electronics has a wiki on github, which |
8 |
>> > can be oficially git-pulled as a local copy...which I did. |
9 |
>> > |
10 |
>> > Now I have tons of *.md (markdown) -files instead of html and I |
11 |
>> > dont know of any handy viewer for these. |
12 |
>> > |
13 |
>> > Since I want to update the repo from time to time |
14 |
>> > I dont want to convert them. |
15 |
>> > |
16 |
>> > Is there any recommended quick and clean way to view these files on the fly as |
17 |
>> > they would be html? |
18 |
>> > |
19 |
>> > Thanks a lot for any help in advance! |
20 |
>> > Cheers |
21 |
>> > Meino |
22 |
>> > |
23 |
>> |
24 |
>> Markdown is a markup language that was specifically designed to be readable in the source. |
25 |
>> |
26 |
>> However, if you still find it hard to read, perhaps syntax highlighting in a fancy |
27 |
>> text editor can help approximate the intended effects of the markup. |
28 |
>> |
29 |
>> Also, there are markdown-to-HTML translators. Some are even included in portage tree. |
30 |
>> |
31 |
> |
32 |
> |
33 |
> I dont want to convert the md-files to html, since I want to update |
34 |
> the repo later (see above). |
35 |
> The problem are files referencing other files. Reading the md-files |
36 |
> via vim (for example) would imply to grab all references by hand. |
37 |
> Fortheremore, tne docs are filled with graphics (for example images |
38 |
> of the fonts, which can be used), which cannot be displayed with an |
39 |
> ASCII-editor. |
40 |
> Formatting is necassary with this docs... |
41 |
> |
42 |
|
43 |
Typically what is done is you render the whole Wiki to HTML, and then |
44 |
view it in a browser. You don't edit the HTML directly. It should be |
45 |
possible to generate it incrementally. |
46 |
|
47 |
The one catch is that they might be relying on GitHub's integrated |
48 |
Wiki system. If they are, you might need to install Gollum to process |
49 |
the markdown files to HTML. |
50 |
|
51 |
Cheers, |
52 |
R0b0t1 |