Full Hebrew Support for Form 104 (Right-to-Left Input Rendering)

Eyalredler65

Hi,

In Israel Search and Rescue operations we frequently use the Form 104 within SARTopo. At the moment, Hebrew text is not displayed correctly in the form - right-to-left input appears in the wrong order, which makes it very difficult to use during real missions.

I’d like to request:

  1. Proper right-to-left (RTL) rendering support for Hebrew in all Form 104 fields.

  2. Correct handling of Hebrew characters, punctuation, and mixed Hebrew/English text.

  3. Ideally, full RTL support in any printable/exported version of the form as well.

This improvement would be extremely helpful for Search and Rescue teams in Israel who rely on SARTopo as an operational tool, especially in fast-moving missions where forms need to be completed accurately and quickly.

Thanks in advance for considering this enhancement - it would make a meaningful difference for Hebrew-speaking SAR units.

0

Comments

2 comments

Date Votes
  • Comment author
    Eyalredler65

    Additional note:
    It would also be very helpful if the same Hebrew right-to-left rendering fix could be applied to the printed map output. At the moment, Hebrew labels and annotations on printed maps also appear in the wrong order, which makes them difficult to use during field operations. Proper RTL support in map printouts would make a big difference for teams working with Hebrew materials.

     
     
    0
  • Comment author
    Matt Jacobs

    Unfortunately the map viewer, printed maps and SAR forms all use different rendering stacks, which require independent solutions.  Of those, printed maps are probably the hardest - there's a lot of custom logic we built in-house for rendering labels along lines, and adding RTL support to that is likely going to be tricky.

    I'm unsure what's involved with forms.  Can you download a copy of the original 104 at https://drive.google.com/file/d/0B_6IcXP9zKKMLVd3TlJpQ0lRZkNUaGtyeUFpSHhMdw/view?resourcekey=0-XZHhpN_nFif0q0xtb3jOPg, fill it out with some sample Hebrew, and send it to help@caltopo.com along with a reference to this forum post?

    I'll take a look at what's going on internally in a properly filled out PDF vs the one we generate, but no promises.  Overall, we're trying to move towards data being fully encompassed within the app and paper forms being less relevant.  For example the forthcoming UI we have up at preview.caltopo.com will finally allow people without edit access to an assignment to still view its details within the app, which should greatly reduce the need for paper assignment forms.

    Locally, we are using and recommending pre-printed, 4-part, half-sheet 104 forms that hold a segment letter, team ID and team members' information, but none of the other information such as assignment details.  Everything that's on the map stays on the map, and the paper just helps us keep track of who is on which team, and which team is doing which assignment.  We've found that's much simpler to manage, than trying to print paperwork from CalTopo, fill in missing fields, and then only have a single copy of the paper.

    0

Please sign in to leave a comment.