translations.txt: update allowed values for 'table_name' field

[felixguendling]

Summary

Allowed value for table_name: add all tables that have translatable fields.

Describe the Problem

According to the current reference, Fares v2 and Flex v2 are not translatable.

I think this happened through an oversight when adding Fares and Flex without updating the translations table.

Use Cases

It would be valuable to be able to translate the following fields:

• rider_categories.rider_category_name
• rider_categories.eligibility_url
• fare_media.fare_media_name
• fare_media.fare_media_type
• fare_media.fare_product_name
• areas.area_name
• networks.network_name
• location_groups.location_group_name
• locations.location_stop_name
• locations.location_stop_desc
• booking_rules.message
• booking_rules.pickup_message
• booking_rules.drop_off_message
• booking_rules.phone_number
• booking_rules.info_url
• booking_rules.booking_url

Proposed Solution

Extend the list of translatable values by:

• rider_categories
• fare_media
• fare_products
• areas
• networks
• pathways
• levels
• location_groups
• locations
• booking_rules

Type of change

GTFS Schedule

• Functional Change
• Non-Functional Change
• Documentation Maintenance

GTFS Realtime

• Specification Change
• Specification Change (Experimental Field)

Additional Information

Another solution could be to use a more general wording that's not prone to this problem. Something like

Allowed values are all GTFS tables containing translatable fields (see field_name description for allowed field types).

Proposed Discussion Period

I would hope that everyone agrees that also Flex and Fares should be translatable.
However, since holiday season is approaching, it's probably better to give it 2 months.

Testing Details

I'm working on MOTIS translation support and MOTIS will support translating Fares and Flex values as well from the beginning.

Proposal Update Tracker

Date	Update Description
2025-12-13	Initial proposal

[isabelle-dr]

Related issue: #424