No reviews yetBe the first to leave a review for AutoI18n
Maker
📌
When I was developing with nextjs, I realised that I, like everyone else, was spending too much time maintaining multi-language related code while writing the project code, especially when there are a lot of pages, which takes a lot of time, this is something that should be automated (at least in my opinion) and we should have more time to do business related things, what if I created a desktop tool to do this in one click?
That's how the project came about, it took me 3 months to complete, I consulted a lot of resources, I had to be busy with work during the day while taking time to develop it at night, I spent I don't know how many nights debugging and testing it, and so far it works great and it's helped a few of my friends finish their own products as well.
I invite you to take a look at the product, it's free, what features do you think are missing from this tool when you first look at it? Please let me know in the comments section, thanks!
This sounds like a game changer for Next.js developers! @kamjin, I'm curious about the desktop tool's automation capabilities. How does it handle different language formats or custom translations? In your experience, what was the most challenging aspect of the development process? Would love to hear more!
Report
Maker
@awesomeyang, thank you very much! Let me try to answer some questions:
When we talk about making a project multilingual, it's usually reflected at the code level. Different languages are extracted into separate JSON files, each with the same keys. The program then packages these files and, depending on the access routes, references the correct language. The code remains the same for different languages—for example, using the t function to reference the same key in different languages. The tool handles this process automatically during runtime, so we just need to enjoy the results.
As for custom translations, the tool doesn’t directly support them in the traditional sense. Custom translations usually involve manually searching the code and modifying the specific language file. This process doesn’t affect other languages or future updates, unless you make changes to the default language text. If you only want to change the program's text content, this can be done efficiently through the tool's JSON editor. I recommend giving it a try!
The main challenge: I created this tool because debugging in JavaScript, especially in cross-platform desktop software development, can be quite cumbersome. It significantly reduces development efficiency, often requiring extensive log printing for debugging. This process demands focused attention, and any interruptions can lead to bugs.
I will continue to work on improving the tool to make it more useful and practical. Thanks again for your support!
Report
Congrats on the launch, @kamjin! It's awesome to see a tool that automates i18n for Next.js projects. The time savings on multi-language maintenance will be huge for many developers.
Report
Maker
@blankwebdev You are right that we should use our time to do more efficient things rather than boring things, but while proving that, the next thing I need to think about is how to make multilingual translation results more satisfying, thank you!
Report
Congratulations on the launch of AutoI18n. In this fast-paced environment, people increasingly need to use these software to save work efficiency. Thank you very much for having such a software to assist with work.
Report
Maker
@nancy_zhou_klee You're welcome. It feels good to bring convenience to others and I enjoy it!
Report
Wow, it's what I'm looking for. Looks promising! I'll check it out. Congrats on the launch!
Great initiative, @kamjin! I can totally relate to the pain of handling multi-language setups in Next.js. Your desktop tool sounds like a game-changer for automating this tedious process. I appreciate the effort and time you've invested to help the dev community. Looking forward to testing it out! As for features, perhaps integrating more visual previews of translations could be useful? Let's keep the feedback coming!
#Makers #Nextjs #i18n
Report
Maker
@boyso I am very grateful to you for your useful suggestion ‘Integrate more visual translation previews’! This feature sounds great and useful, it should solve the need to adjust the translation again if you are not satisfied with the result, but I haven't thought about more interface features and effects yet, and I lack some inspiration. Can we talk more about this?
Report
Congrates!I am preparing to learn next.js recently. Is it friendly to beginners?
favicon.run