Danilo Bargen
Danilo Bargen
So I'd propose the following: - New readonly string field in the `Track` model called "source", defaults to either `unknown` or `default` - File and local backends use `local` -...
For many extensions we could probably directly use `Extension.ext_name`. Is that value available e.g. in a `LibraryProvider`?
Unfortunately yes, I create manual backups from time to time, but it's not yet automated. Setting up proper automated off-site backups is currently quite high on my personal priority list.
Markdown specifies backslash escapes: https://daringfireball.net/projects/markdown/syntax#backslash With that we'd arrive at the following markup spec: - Use `*` for bold - Use `**` for italic - Use `***` for bold italic...
Would we ever create hyperlinks to HTML anchors? That would conflict with the `#` syntax. If not, I like the `[text]{#ff0000}` suggestion. What exactly do you mean with hovertext? Strings...
Ah, obviously. So now we have: - Use `*` for bold - Use `**` for italic - Use `***` for bold italic - Use `\` to escape the asterisk -...
Exactly. For that you would render a string, attach an event handler on it, and then display another string resource on mouseover.
Atm I don't really have time, so if someone else has time to pick up this issue, please feel free to do so :(
There is also a unicode standard for translation strings called ICU MessageFormat: - https://github.com/unicode-org/message-format-wg - https://unicode.org/reports/tr35/tr35-messageFormat.html
@Claudio-Chies any other useful category ideas?