Skip to content

Incorrect space between value and degree sign #86

Description

@Animyos

Using the Location: GPS (German: Standort (GPS)) experiment and the tab ‘Simple’ (‘Einfach’), Phyphox displays numerous values as follows:

Screenshot showing the ‘Simple’ tab of the *Location (GPS)* experiment. The UI language is German. Among other things, there are values for latitude, longitude, and direction in degrees.

Among other things, values for latitude (“Breitengrad”), longitude (“Längengrad”), and direction (“Richtung”) are displayed. They all have the unit degrees (°).

The issue I see here is that there is a space between the value and the degree sign. Although spaces are compulsory between values and virtually any other unit (including °C), degrees that do not indicate temperature—as well as units denoted by primes (′) or seconds/doubleprimes (″)—instead must not have a space between value and unit sign. Cf. the SI Brochure, section 5.4.3 p. 149:

The numerical value always precedes the unit and a space is always used to separate the unit from the number. […] The only exceptions to this rule are for the unit symbols for degree, minute and second for plane angle, °, ′ and ″, respectively, for which no space is left between the numerical value and the unit symbol.

(Edit: Formatting)

Activity

  1. Staacks commented on Dec 29, 2025

    @Staacks
    Member

    Well, I fully agree that this is not ideal, but fixing this could be more tricky than it might seem at first. Since all experiment configurations are defined through our XML format, we need an additional attribute in each element that uses units (graphs, value elements, edit fields (although, those have an extreme gap anyway)) to determine whether a space is required for that unit or not and we need to implement this in the Android version, the iOS version, the webinterface and the editor.

    None of this hard to implement it, but it is a surprisingly large amount of changes to remove this tiny space. Also I am not sure if we need to make this attribute "translatable". Some languages have different conventions (I think the space before a percent sign always leads to a heated debate), some might conventionally replace special characters °, %, ' or " with common abbreviations that would get a space (like deg instead of °) and I do not even have an idea how any of these look in languages with non-latin characters.

    Indeed, looking at the Chinese version, I highly suspect that their variant would require the space, so this somehow has to be part of the translation process:

    Image

    So, I will leave this issue open as your point of course is absolutely valid, but I do not yet know how and when to fix this. In some way it is similar to our naive axis labels, which follow some major international publisher guidelines, but totally fail to fit most "correct" conventions (like DIN in Germany).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions