Wrong string count when HTTP request encoding is different from default server encoding about multilingual_field HOT 13 CLOSED

@6ui11em This issue has been bugging me since a long time now... And I did not came across anything better than the suggested fix above. Would you consider integrating it ?? Thanks.

from multilingual_field.

With the next update we will extend the Texbox Field extension and we will use all his original methods, then could be a good moment to check this.

from multilingual_field.

Nice. But the textfield has the same problem with different counts with differents text enconding. See my other comment on extending the textfield...

from multilingual_field.

then if this is a problem is present in the Textbox Field extension the issue may be fixed there, the idea of the next release of multilingual text field is to extends the parent extension and use his methods. Textbox Field extension will be required to use multilingual textfield.

from multilingual_field.

Are you talking about Symphony core fields ??? Or the other extension ?

from multilingual_field.

Multilingual Text field es based on Texbox Field from Rowan Lewis:

https://github.com/rowan-lewis/textboxfield/

from multilingual_field.

AAAAA I got confuse again !!!

from multilingual_field.

Just like Multilingual Entry URL Field extends Entery URL Field so it can take advantage of it's functions and not re-invent the wheel, so will Multilingual Field extend the Text Box Field.

Btw, @6ui11em , shouldn't this be renamed to Multilingual Text Box Field?

from multilingual_field.

Good point, I will considere it when re-write the extension,

from multilingual_field.

I would agree on that rename.... And I would consider coding a 'facade' extenstion (just like nil's stage librairy) for multilingual extensions. We code now build multilingual extension really simply !

from multilingual_field.

@6ui11em

Frontend Localisation 1.4 is out. It now encloses Frontend Language management => no more language redirect dependency.

It supplies FLang information and some assets for multilingual components (eg: the UI multilingual tabs).

Here's an example implementation from multilingual_image_upload (and other places where I'm using the tabs, eg: Page LHandles, multilingual_*, Frontend Localisation, a future Section LHandles ;) ):

1. Load Frontend Localisation assets. Recommended from your driver.
2. The wrapper must have a class .field-multilingual.
3. Build the tabs as usual.

Frontend Localisation initializes the language tabs wherever it finds a .field-multilingual class.

Can you please give an ETA for when multilingual text will be updated?

Thank you.

from multilingual_field.

@vlad-ghita

Great!

I'm in the middle of a project and I'm so busy but I will try to find some time to update the extension. Maybe next week I could do something.

@vlad-ghita, @nitriques

I pushed the Multilingual Tag Field:

https://github.com/6ui11em/multilingual_tag_field

I used it in small project, I would like to do more tests before release it to the community but now I don't have this time. Maybe you could test the extension and give me some feedback and I will try to publish it next week with the multilingual text field update. This extension was based on your upload fiels so I think is adapted to the new multilingual fields dependecies.

All your comments are welcome.

from multilingual_field.

I pushed the Multilingual Tag Field

Cool stuff !

I'll have a look.

from multilingual_field.