You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -221,22 +219,4 @@ After checking out the required version, build and run the app as described abov
221
219
222
220
## Release Process
223
221
224
-
Releasing _Tuner_ comprises cutting a release of the code in [tuner github](https://github.com/tuner-app/tuner) and then updating the [flathub repo](https://github.com/flathub/com.github.louis77.tuner) which will automatically have the flatpak generated and rolled to Flathub for distribution.
225
-
226
-
### Beta Releases
227
-
228
-
Beta releases should be tagged from the Tuner _development_ branch in with a version number format of _v1.\*.\*-beta.\*_
229
-
230
-
Once a beta release has been tagged, the Flathub _beta_ branch can be updated via a pull request with the _beta_ tag going into the manifest _.json_, and any patches and documentation updated as needed. The pull request will trigger a flathub build, but will not merge the pull request - pull requests should be merged only if they result in a successful build.
231
-
232
-
Once the beta is successfully built by flathub it will be available for installation and testing within the user community.
233
-
234
-
Once a beta roll is deamed a success its pull request can be merged, and a production release can be rolled.
235
-
236
-
### Production Releases
237
-
238
-
Production releases are generated from _development_ pull requests into _main_. The updated _main_ branch should be tagged with a version number format of _v1.\*.\*_
239
-
240
-
Once a release has been tagged, the [flathub repo](https://github.com/flathub/com.github.louis77.tuner)_main_ branch can be updated with the _release_ tag going into the manifest _.json_, and any patches and documentation updated as needed. Updates from the _main_ branch should be copied in from a direct _pull request_ of the _main_ branch. The _main_ branch **should not** come from a merge _beta_ branch to avoid triggering subsequent builds in _beta_ .
241
-
242
-
Once the main production release is built by flathub it will be available for installation and automatically distributed to user community.
222
+
Cutting a releasing **Tuner** on [github](https://github.com/tuner-labs/tuner) and packaging and pushing out a new **Flathub** distribution are covered in the [release doc](RELEASE.md)
Copy file name to clipboardExpand all lines: I18N.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
1
# Internationalization
2
2
3
-
**Tuner** uses [Gnome *i18n*](https://developer.gnome.org/documentation/guidelines/localization.html) for internationalization. This system specifies target files and extracts identified strings for translation in the source, the target languages, and during the build process compiles translated strings into package which. The appropriate translated strings are then used by the host system when running **Tuner**.
3
+
**Tuner** uses [Gnome *i18n*](https://developer.gnome.org/documentation/guidelines/localization.html) for internationalization. This system and library specifies source files (*POTFILES*) from which to extract identified strings for translation (the *.pot* file) and the target languages (*LINGUAS*). During the build process translated strings (*.po* files) are package and the included library uses the appropriate translated strings are then used by the host system when running **Tuner**.
4
4
5
-
Translations are managed and applied by[Weblate](https://hosted.weblate.org/projects/tuner/) as two different components:
5
+
Translations are creted, managed and applied via[Weblate](https://hosted.weblate.org/projects/tuner/) as two different components:
6
6
7
7
* The application [UI](https://hosted.weblate.org/projects/tuner/tuner-ui/)
8
8
* The flatpak [Desktop](https://hosted.weblate.org/projects/tuner/tuner-desktop/) metadata
@@ -39,4 +39,4 @@ This:
39
39
* Builds the **main***.pot* file that relates to the UI
40
40
* Builds the **extra***.pot* file that relates to the Desktop metadata
41
41
42
-
Updates to the *.pot*, *LINGUAS* and *POTFILES* files *pushed* to the development branch will be picked up by Weblate and can be worked on on the Weblate **Tuner** page.
42
+
Updates to the *.pot*, *LINGUAS* and *POTFILES* files *pushed* to the development branch will be picked up by Weblate and can be worked on the Weblate **Tuner** page. Weblate then generates the *.po* translation files and opens a github pull request to have them included in **Tuner**
The **flathub** packaging for **Tuner** is documented in <RELEASE.md>
4
4
5
-
Building Tuner localy is described in the [development doc](DEVELOP.md).
5
+
Other packaged versions of Tuner maybe available, but are maintained outside of Tuner itself; Versions may be out of date.
6
6
7
-
## Packages for other platforms and distos
7
+
If you are packaging **Tuner** please contribute to this page.
8
8
9
-
Other packed versions of Tuner are available, but are maintained outside of Tuner itself: Versions may be out of date.
10
-
11
-
### Arch Linux / AUR
9
+
## Arch Linux / AUR
12
10
13
11
Arch-based GNU/Linux users can find `Tuner` under the name [tuner-git](https://aur.archlinux.org/packages/tuner-git/) in the **AUR**:
14
12
@@ -18,15 +16,17 @@ yay -S tuner-git
18
16
19
17
Thanks to [@btd1377](https://github.com/btd1337) for supporting Tuner on Arch Linux!
20
18
21
-
###MX Linux
19
+
## MX Linux
22
20
23
21
MX Linux users can find `Tuner` by using the MX Package Installer (currently under the MX Test Repo tab for MX-19 and the Stable Repo for MX-21)
24
22
25
23
Thanks to SwampRabbit for packaging Tuner for MX Linux!
26
24
27
-
### Pacstall
25
+
## Pacstall
26
+
27
+
Pacstall is a totally new package manager for Ubuntu that provides an AUR-like community-driven repo for package builds.
28
28
29
-
Pacstall is a totally new package manager for Ubuntu that provides an AUR-like community-driven repo for package builds. If you already use `pacstall` you can install Tuner:
29
+
If you already use `pacstall` you can install Tuner:
30
30
31
31
```bash
32
32
pacstall -I tuner
@@ -35,63 +35,3 @@ pacstall -I tuner
35
35
If you have Ubuntu and want a clean build of Tuner on your system, consider using `pacstall` instead of Flatpak if you don't feat beta software. Get `pacstall` here:
36
36
37
37
<https://pacstall.dev>
38
-
39
-
## General
40
-
41
-
### Desktop Menu
42
-
43
-
The desktop file must be validated using this command:
44
-
45
-
```bash
46
-
desktop-file-validate [name-of-desktop-file]
47
-
```
48
-
49
-
### AppData
50
-
51
-
The AppData.xml must be validated using this command:
52
-
53
-
```bash
54
-
flatpak run org.freedesktop.appstream-glib validate [path-to-xml]
Copy file name to clipboardExpand all lines: README.md
+15-14Lines changed: 15 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,18 +14,24 @@ Minimalist radio station player - **Tuner** Version 2
14
14
15
15
## Features
16
16
17
-
-Play ever changing stations found in [radio-browser.info](https://www.radio-browser.info/) radio station index
18
-
- See the top selections of stations (random, top, trending) from the index
19
-
-See the different station content genres and subgeneres from the index
17
+
-Explore ever changing radio stations indexed in [radio-browser.info](https://www.radio-browser.info/)
18
+
- See the top selections of listened to and saved stations from the index
19
+
-Find different station content genres and subgeneres from the index
20
20
- Jukebox - Play a new random station every ten minutes
21
21
- Save your favourite stations
22
-
- Search for stations and content
22
+
- Search for stations and content by keyword
23
23
- Save your favorite station searches
24
24
- Export your favorite stations to _m3u_ playlists
25
25
- DBus integration to pause/resume playing and show station info in Wingpanel
26
26
- Updates station click count at station index on station play
27
27
- Updates station vote count at station index when you star a station
28
28
29
+
### Internationalization & Translation
30
+
31
+
**Tuner** is Internationalized, and is available in various languges. Translations are hosted on [Weblate](https://hosted.weblate.org/engage/tuner/). Please help by [translating Tuner into your language or fix any translation issues](I18N.md) you find.
32
+
33
+
Thanks to the Weblate team for generously hosting **Tuner** for free!
34
+
29
35
### Recent Updates
30
36
31
37
_December 2025_ all things **Tuner** have become a _Github Organization_ called [**tuner_labs**](https://github.com/tuner-labs) to ensure **Tuner** continues to be available and we invite you to participate in keeping it a great source of music discovery and Internet Radio player.
@@ -36,22 +42,17 @@ _January 2025_ Version 2 released with major new features and performance improv
36
42
37
43
**Tuner** is primarily [developed](DEVELOP.md) and distributed as a Flatpak on [Flathub](https://flathub.org/apps/details/com.github.louis77.tuner).
38
44
39
-
It can also be built and [distributed via other platforms and distos](PACKAGING.md). Make **Tuner** work on your favorite Disto/Package.
40
-
41
-
## Translation
45
+
It can also be built and [distributed via other platforms and distos](PACKAGING.md).
46
+
Please help make **Tuner** work on your favorite Disto/Package.
42
47
43
-
**Tuner** is Internationalized, and is available in various languges. Translations are hosted on [Weblate](https://hosted.weblate.org/engage/tuner/). Please help by [translating Tuner into your language or fix any translation issues](I18N.md) you find.
48
+
## Status and Support
44
49
45
-
Thanks to the Weblate team for generously hosting **Tuner** for free!
50
+
Join in or start [discussion about tuner](https://github.com/orgs/tuner-labs/discussions)... Feature request, observations and Issues can be documented with tickets on [Github](https://github.com/tuner-labs/tuner/issues)
46
51
47
-
## Build, Maintance and Development of Tuner
52
+
###Build, Maintance and Development of Tuner
48
53
49
54
Building, developing and maintianing **Tuner** is detailed seperately and in detail in the [DEVELOP](DEVELOP.md) markdown.
50
55
51
-
## Status and Support
52
-
53
-
Feature request, observations and Issues can be documented with tickets on [Github](https://github.com/tuner-labs/tuner/issues)
54
-
55
56
### Known Issues
56
57
57
58
#### If AAC/AAC+ streams don't play (found on Elementary OS 6) install the following dependency
The AppData.xml must be validated using this command:
23
+
24
+
```bash
25
+
flatpak run org.freedesktop.appstream-glib validate [path-to-xml]
26
+
27
+
```
28
+
29
+
### Test different languages
30
+
31
+
```bash
32
+
LANGUAGE=de_DE ./com.github.louis77.tuner
33
+
```
34
+
35
+
## Flatpak
36
+
37
+
Releasing *Tuner* comprises cutting a release of the code in [tuner github](https://github.com/tuner-app/tuner) and then updating the [flathub repo](https://github.com/flathub/com.github.louis77.tuner) which will automatically have the flatpak generated and rolled to Flathub for distribution.
38
+
39
+
## Flathub Builds
40
+
41
+
**flathub** builds can be monitored at <https://flathub.org/en/builds>
42
+
43
+
### Beta Releases
44
+
45
+
Beta releases should be tagged from [github](https://github.com/tuner-labs/tuner/releases/new) using the Tuner *development* branch - the *meson* buildfile should have the same version number - the beta format is *v2\*.\*-beta.\**
46
+
47
+
Once a beta release has been tagged, the Flathub *beta* branch can be updated via a pull request with the *beta* tag going into the manifest *.json*, and any patches and documentation updated as needed. The pull request will trigger a flathub build, but will not merge the pull request - pull requests should be merged only if they result in a successful build.
48
+
49
+
Once the beta is successfully built by flathub it will be available for installation and testing within the user community.
50
+
51
+
Once a beta roll is deemed a success its pull request can be merged, and a production release can be rolled.
52
+
53
+
### Production Releases
54
+
55
+
Production releases are generated from *development* pull requests into *main*. The updated *main* branch should be tagged with a version number format of *v2.\*.\**
56
+
57
+
Once a release has been tagged, the [flathub repo](https://github.com/flathub/com.github.louis77.tuner)*main* branch can be updated with the *release* tag going into the manifest *.json*, and any patches and documentation updated as needed. Updates from the *main* branch should be copied in from a direct *pull request* of the *main* branch. The *main* branch **should not** come from a merge *beta* branch to avoid triggering subsequent builds in *beta*.
58
+
59
+
Once the main production release is built by flathub it will be available for installation and automatically distributed to user community.
0 commit comments