![]() So even though I don't agree that Yaml should be the "first recommended format", I completely understand people saying that it should. And what are we? Developers! What do we want? Code performant apps fast! And for this, we need simplicity. Lots of students will tell you that docs are for stupids, being arrogants (even though it's not the majority), but most of them simply don't comply with the idea reading one another pile of docs when they already have lots of books & courses to read, especially when they can just rely on a simple and readable format like Yaml.Īnd for the case of companies, just tell them this sentence and they will yell at you that customers have delay, that they just want a "Plug-and-play" solution, or that "As long as it works at first sight, don't mind me to encourage spending more time for a more complex stuff that brings no money".Įven if I agree that XLIFF is a professional and standard format, Yaml is much better for DX. I don't know if you're just a developer, lead tech or anything, but I wish you could meet tons of students learning Symfony or small & medium-class companies that use Symfony, and tell them "Don't stard coding without reading docs". or you just don't start using the Symfony without reading some docs first. You don't start coding without reading some documentation on the language. I'm totally □ to recommend Yaml for small projects, and Xliff for standards (and to avoid systematic Yaml said: Why not recommend both? Explaining when to use one or another (basically simple vs. So for 99% of all our cases at that time, Yaml was said: mo translation formats, and we just exchanged occasionnally some e-mails to warn her about new translations, she updated it, we incorporated them in the app, it was really straightforward. In my previous jobs where I developed tons of SF apps, I have never used XLIFF format, always Yaml, and it was fine.Įxcept once: the client herself wanted to pay a translator, and we provided an easy access to. We don't use any fancy XLIFF functionality in Symfony, it's pretty much still a key-value replacement, even with the said:įor my own experience, I never ever used the XLIFF format nor professional tools for translations, nor my clients did.Īnd I think it's true for most companies. If they want to customize translations from Symfony, they'll have to overwrite them with their own file anyway, ignoring the Symfony variant. With Yaml I believe that contributing is easier and it won't influence anybody who is using professional translation tools. For Symfony it should imho be very easy to contribute to translations if needed. We are contributors and developers, we love writing in tools like vim or notepad and our precious IDE, which we find superior to whatever another developer is using. However, for Symfony, the developers are not professional translators. Recommend Yaml to a company that works with professional tools, and they might look for another framework. Recommend XLIFF to new developers and they will pull their hair out. I don't really mind what Symfony recommends for developers, I feel like Symfony should promote the possibilities and their pros and cons, let the developer decide. We at PHP-translation is trying to be one of those options. Lets recommend Yaml for small apps and then recommend a few options for something cool and useful when the app is larger. At this point you do also not care what format the translation files are because you do never work with them directly. So for a real project you want to use XLIFF because your translation tools can store extra data in the XML document. ![]() You are probably aslo using extractors and a WebUI to add new translations to the translation service. You probably do not keep translations in Git because you are using a translation service. No question about it.īut, when you are doing something more than a hobby project you need to take translation more seriously. You will edit these files and regularly work with them. 2) Should we recommend using Yaml or XLIFF?įor small apps with one or two languages, sure Yaml is the way to go. I vote for keeping XLIFF but Im fine either way. Sure Yaml might be easier to read, but who reads the Symfony translation files anyways? Yaml does not give any technical benefits.XLIFF is the standard for translations. ![]() 1) Should Symfony translation files use Yaml or XLIFF?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |