Đỗ Thành Long soiqualang

Advanced Formatting in GitHub Markdown

GitHub Flavored Markdown lets you create useful documents in GitHub and GitHub Enterprise using .md files. Like other varieties of markdown, GitHub Markdown tries to be as readable as possible in its raw form, resulting in an intentionally limited set of formatting options. However, these options can feel restrictive when dealing with complex content.

Although GitHub Markdown strips out most HTML tags, here are a few tricks that can give you more flexibility when formatting your documents. These advanced formatting options can make your documents more useable, but they come at the expense of plain text readability, so use with caution.

html/index.php

<?php

phpinfo();

docker/Dockerfile

How do I dropdown?

This is how you dropdown.

<details>
<summary>How do I dropdown?</summary>
<br>
This is how you dropdown.

	"""
	A simple proxy server, based on original by gear11:
	https://gist.github.com/gear11/8006132

	Modified from original to support both GET and POST, status code passthrough, header and form data passthrough.

	Usage: http://hostname:port/p/(URL to be proxied, minus protocol)
	For example: http://localhost:5000/p/www.google.com
	"""
	import re

	Function UniConvert(Text As String, InputMethod As String) As String
	Dim VNI_Type, Telex_Type, CharCode, Temp, i As Long
	UniConvert = Text
	VNI_Type = Array("a81", "a82", "a83", "a84", "a85", "a61", "a62", "a63", "a64", "a65", "e61", _
	"e62", "e63", "e64", "e65", "o61", "o62", "o63", "o64", "o65", "o71", "o72", "o73", "o74", _
	"o75", "u71", "u72", "u73", "u74", "u75", "a1", "a2", "a3", "a4", "a5", "a8", "a6", "d9", _
	"e1", "e2", "e3", "e4", "e5", "e6", "i1", "i2", "i3", "i4", "i5", "o1", "o2", "o3", "o4", _
	"o5", "o6", "o7", "u1", "u2", "u3", "u4", "u5", "u7", "y1", "y2", "y3", "y4", "y5")
	Telex_Type = Array("aws", "awf", "awr", "awx", "awj", "aas", "aaf", "aar", "aax", "aaj", "ees", _
	"eef", "eer", "eex", "eej", "oos", "oof", "oor", "oox", "ooj", "ows", "owf", "owr", "owx", _

	import numpy as np
	from osgeo import gdal, gdal_array, osr

	def npmatrix_to_geotiff (filepath, matrices, gdal_type, transform = None, projection = None, nodata = None):
	(y_res, x_res) = matrices[0].shape
	driver = gdal.GetDriverByName('GTiff')
	image = driver.Create(filepath, x_res, y_res, len(matrices), gdal_type)
	if transform is not None:
	image.SetGeoTransform(transform)
	if projection is not None:

	<!DOCTYPE html>
	<html>
	<head>
	<title>Seed tool</title>
	<style>
	.seed-status {
	display: inline-block;
	padding; 2px;
	background: #ccc;
	}

	<html>
	<head>
	<!--
	@tag hta:application

	@attribute ApplicationName Sets the name of the HTA.

	@attribute Border [Thick]\|Thin\|None
	@attribute BorderStyle [Normal]\|Raised\|Sunken\|Complex\|Static
	@attribute Caption [Yes]\|No

	// check version
	node -v \|\| node --version

	// list locally installed versions of node
	nvm ls

	// list remove available versions of node
	nvm ls-remote

	// install specific version of node

	# export mysql database into shapefile
	ogr2ogr out_shapes MYSQL:gis,user=root,password=password

	# import shapefile into mysql
	ogr2ogr -f MySQL MySQL:database_name,user=root,password=password my_shapefile.shp -nln table_name -a_srs EPSG:4326 -update -overwrite -lco engine=MYISAM

	# reproject spatial reference from WGS 84 UTM 48S to Geographic Lattitide/Longitude Coordinate System
	ogr2ogr -f "ESRI Shapefile" target_file.shp source_file.shp -s_srs EPSG:32748 -t_srs EPSG:4326