arisuchan    [ tech / cult / art ]   [ λ / Δ ]   [ psy ]   [ ru ]   [ random ]   [ meta ]   [ all ]    info / stickers     temporarily disabledtemporarily disabled

/q/ - arisuchan meta

discuss arisuchan itself. comments and questions welcome.
Name
Email
Subject
Comment

formatting options

File
Password (For file deletion.)

Help me fix this shit. https://legacy.arisuchan.jp/q/res/2703.html#2703

Kalyx ######


File: 1492437544402.jpg (161.76 KB, 278x646, crash_override.jpg)

 No.89

>no repo link anywhere

FOSS or no deal

 No.91

If this is a fork of vichan, their license forbids removing the copyright notice with the link from the bottom of the pages.

 No.139

bump.

Give us the fucking code.

 No.140

>>139
Seconded.

 No.142

File: 1492514750303.png (17.16 KB, 1000x410, GitHub_Logo.png)

>>89
The fork was just started yesterday. Changes to live have not yet been backported, but we expect to in the next few days. We will be moving LibreJS soon afterwards. The header and footer have been updated accordingly.

https://www.gnu.org/software/librejs/

 No.144

>All copyright notices and permission notices (including this file) shall be included and remain unedited in all copies or substantial portions of the Software. This explicitly includes but is not limited to the vichan copyright notices found in the footers of some template files.
You have to restore the original thing. Sadly the "built on" thing is not enough.

 No.147

>>144
I think they might have made their own templates/themes/whatever, which'd make it allowed to not have the footer in there

 No.148

>>147
No it wouldn't. Whether they made the theme or not, this is still using a "substantial portion" of vichan.

 No.149

I've noticed the [.code] tags don't cancel out the other formatting symbols. This completly destroys anything you write in C. With a repo link I'll fix it myself, otherwise please be aware that this is a fairly annoying issue.

 No.150

It's linked at the top and the bottom:
https://github.com/lainchan-jp/lainchan-jp

 No.151

>>149
They're using
highlight.js
on live. The vichan software uses
$config['markup'][] = array( );
to replace markup strings with appropriate formatting. They'd have to implement a different solution for adding formatting that is sensitive to the code blocks.

 No.169

>>149
>>151
Some improvements have been made to syntax highlighting; code blocks should prevent other tags from taking effect now. Inline monospace (with the
[m]
tag) does not use highlighting

Also, note that highlight.js has pretty bad heuristics for detecting which language is being used. I recommend specifying your language - using
[code python]...[/code]
, for example - if you give a damn.

 No.1891

>>150
for anybody stumbling into this thread and noticing that link's dead:
>>1733



[Return] [Go to top] [ Catalog ] [Post a Reply]
Delete Post [ ]