module Fluency - The complete translation enhancement suite for ProcessWire

[bernhard]

PS: Thought it might be translation cache, but just flushed the cache and I get the same (wrong) translation 😞 

[FireWire]

@bernhard That's definitely a bug. Investigating.

[bernhard]

@FireWire thank you very much!

Another little detail I just found: I wanted to translate "Telefon" to EN + CZ. For EN it's "Telephone", fine.

For CZ it seems to be "Telefon", the same as in German:

Now the problem is that if it is the same and it is saved like this, the field's value is lost:

Not sure if that is an issue with your module or rather an issue for Ryan? What do you think? I think it's more a thing that should be handled by the core. When the field is filled out and the same as the default's language value, I think it should automatically save as "+" which tells PW to use the same value as the default.

[FireWire]

@bernhard Haven't forgot about your request! The event for the organization I'm working with kicks off this week and it's been just a little hectic haha.

On 2/4/2025 at 9:53 AM, bernhard said:

Not sure if that is an issue with your module or rather an issue for Ryan? What do you think? I think it's more a thing that should be handled by the core. When the field is filled out and the same as the default's language value, I think it should automatically save as "+" which tells PW to use the same value as the default.

I just checked and the language page says to use an '=' sign to designate tell PW to use the default language.

When I entered that it saved the = sign. Am I talking about the same thing?

[bernhard]

Oh, I was always using + instead of = and it worked as well. Not sure where I picked that up.

24 minutes ago, FireWire said:

When I entered that it saved the = sign. Am I talking about the same thing?

Yes, manually entering it saves it. But the issue is that when you translate a string and the returned translation is the same (eg Telefon (DE) --> Telefon (CZ)) then fluency will fill the input with "Telefon" which will then be lost on save and the field will be marked as "blank".

I think it would be good if it turned "Telefon" into "=" on save. But I think that the core should take care of this! What do you think?

PS: No hurry.

[FireWire]

It makes sense to me that if ProcessWire will remove the value because it is the same then it might as well replace it with = .

I think it would be a nice indicator visually and to prevent extra characters being used when translating. There would be no way for Fluency to know that a blank field indicates a match. Never thought about that before, good catch!