At my place of work we were doing translations with json files and key value pairs.
eg. en-US.json
{
"this_key": "Translates to this"
}
/** | |
* Recursively searches the startObject for the given value. | |
* | |
* All matches are displayed in the browser console and stored in the global variable "gsResults" | |
* The function tries to simplify DOM element names by using their ID, when possible. | |
* | |
* Usage samples: | |
* | |
* globalSearch( document, 'someValue' ); // Search entire DOM document for the string value. | |
* globalSearch( document, '^start' ); // Simple regex search (function recognizes prefix/suffix patterns: "^..." or "...$"). |
# A little list of aliases for weeb developers | |
# nya | Opens a file for edition | |
alias nya='nano' | |
# neko | Prints a file on terminal | |
alias neko='cat' | |
# onegai | Execute the previous command as sudo | |
alias onegai='echo sudo $(fc -ln -1) ; sudo $(fc -ln -1)' |
alias subs=subs | |
function subs() { | |
movie="${1}" | |
filename="${1%.*}" | |
mappings=`ffprobe -loglevel error -select_streams s -show_entries stream=index:stream_tags=language -of csv=p=0 "${movie}"` | |
OLDIFS=$IFS | |
IFS=, | |
( while read idx lang | |
do |
At my place of work we were doing translations with json files and key value pairs.
eg. en-US.json
{
"this_key": "Translates to this"
}
This explains how to setup for GitHub projects which automatically generates Doxygen code documentation and publishes the documentation to the gh-pages
branch using Travis CI.
This way only the source files need to be pushed to GitHub and the gh-pages branch is automatically updated with the generated Doxygen documentation.
Get an account at Travis CI. Turn on Travis for your repository in question, using the Travis control panel.
To create a clean gh-pages
branch, with no commit history, from the master branch enter the code below in the Git Shell. This will create a gh-pages branch with one file, the README.md
in it. It doesn't really matter what file is uploaded in it since it will be overwritten when the automatically generated documentation is published to th
#!/usr/bin/env php | |
<?php | |
/******************************************************************************************************************* | |
* ProFinder v1.0 * | |
* http://forum.xda-developers.com/android/software/profinder-proguard-obfuscation-tracker-t3183647 * | |
******************************************************************************************************************* | |
* Copyright 2015 Kevin Mark * | |
* * | |
* Licensed under the Apache License, Version 2.0 (the "License"); * | |
* you may not use this file except in compliance with the License. * |