mirror of
https://github.com/fergalmoran/picard.git
synced 2026-03-23 13:45:14 +00:00
Minor fixes to .md, making markdownlint happier
This commit is contained in:
@@ -4,7 +4,7 @@
|
||||
|
||||
As most of the other projects written in Python, we use the [PEP 8](https://www.python.org/dev/peps/pep-0008/). Though, we ignore some of the recommendations:
|
||||
|
||||
* E501 - Maximum line length (79 characters). The general limit we have is somewhere around 120-130.
|
||||
- E501 - Maximum line length (79 characters). The general limit we have is somewhere around 120-130.
|
||||
|
||||
*Recommended video: "[Beyond PEP 8 -- Best practices for beautiful intelligible code](https://www.youtube.com/watch?v=wf-BqAjZb8M)" by Raymond Hettinger at PyCon 2015, which talks about the famous P versus NP problem.*
|
||||
|
||||
@@ -94,7 +94,7 @@ metadata specifications and to the tag mapping tables used by various audio soft
|
||||
- [APE-Tags](http://wiki.hydrogenaud.io/index.php?title=APE_key)
|
||||
- [Matroska \| Tag Specifications](https://www.matroska.org/technical/specs/tagging/index.html)
|
||||
- [ASF / WMA](http://msdn.microsoft.com/en-us/library/ms867702.aspx)
|
||||
- MP4: See iTunes Metadata Format Specification (was available at https://developer.apple.com/, but does not seem to be available anymore)
|
||||
- MP4: See iTunes Metadata Format Specification (was available at [Apple Developer website](https://developer.apple.com/), but does not seem to be available anymore)
|
||||
- [RIFF Tags](https://exiftool.org/TagNames/RIFF.html) / [Resource Interchange File Format: INFO List Chunk](https://www.tactilemedia.com/info/MCI_Control_Info.html) / [Multimedia Programming Interface and Data Specifications 1.0](http://www-mmsp.ece.mcgill.ca/Documents/AudioFormats/WAVE/Docs/riffmci.pdf)
|
||||
- [Mutagen Spec Collection](https://mutagen-specs.readthedocs.io/en/latest/)
|
||||
|
||||
|
||||
@@ -174,9 +174,7 @@ below.
|
||||
|
||||
You can verify the signature with e.g.:
|
||||
|
||||
```
|
||||
gpg --verify picard-2.9.tar.gz.asc
|
||||
```
|
||||
gpg --verify picard-2.9.tar.gz.asc
|
||||
|
||||
Make sure the key fingerprint in the output matches the fingerprint of the
|
||||
GPG key below.
|
||||
|
||||
@@ -23,7 +23,7 @@ Their translations are handled at <https://translations.metabrainz.org/projects/
|
||||
One can update `picard.pot` using:
|
||||
|
||||
```bash
|
||||
$ python setup.py regen_pot_file
|
||||
python setup.py regen_pot_file
|
||||
```
|
||||
|
||||
Weblate will _automatically_ sync the changed `picard.pot` and update the translation files (`*.po`) with msgmerge.
|
||||
@@ -37,7 +37,7 @@ Translations for the strings from `org.musicbrainz.Picard.appdata.xml.in` and `o
|
||||
One can update `appstream/picard-appstream.pot` using:
|
||||
|
||||
```bash
|
||||
$ python setup.py regen_appdata_pot_file
|
||||
python setup.py regen_appdata_pot_file
|
||||
```
|
||||
|
||||
Weblate will _automatically_ sync the changed `picard-appstream.pot` and update the translation files (`appstream/*.po`) with msgmerge.
|
||||
@@ -61,7 +61,7 @@ Picard maintainers can regenerate `picard/const/attributes.py` and `picard/const
|
||||
|
||||
|
||||
```bash
|
||||
$ python setup.py update_constants --weblate-key={YOUR_WEBLATE_API_KEY}
|
||||
python setup.py update_constants --weblate-key={YOUR_WEBLATE_API_KEY}
|
||||
```
|
||||
|
||||
Instead of entering the Weblate API key each time you can also place a file `.weblate.ini` in the root of the repository with the following content:
|
||||
|
||||
@@ -12,8 +12,8 @@ For adding a new image into existing resources, follow these steps:
|
||||
1. Add image file (like .png) into `resources/images/` and source file (like .svg) into `resources/img-src`.
|
||||
2. Generate new .qrc file. This would automatically detect any changes in directory.
|
||||
|
||||
$ python3 makeqrc.py
|
||||
python3 makeqrc.py
|
||||
|
||||
3. Create binary of all resources which will be used by Picard.
|
||||
|
||||
$ python3 compile.py
|
||||
python3 compile.py
|
||||
|
||||
Reference in New Issue
Block a user