![]() |
Localized Version |
Post Reply ![]() |
Author | |
Steve Halpern ![]() Admin Group ![]() Joined: January-25-2003 Points: 3919 |
![]() ![]() ![]() ![]() ![]() Posted: May-25-2023 at 3:41pm |
Hi, Because making a localized version means a lot of under the hood text-to-speech system changes, the version 1.0.1.9 version is marked as a beta. This new version allows full customization of all TTS phrases. You could change the language, to French for example, change the order of the vocabulary, or even modify the English to what you want. In the Flight1 Agent you will see the beta as a dropdown option. Give it a try if you like the idea of customizing TTS voices and report any issues here. You now save the language in the .voice configuration. There is more info in the manual, but the left side column is the default command, and the right side is what you can customize using the text box below. To reach this screen, you select the Customize option in the Voice Designer... I know, many windows... ![]() You can even test all commands in the screen. ![]() |
|
Steve
![]() |
|
![]() |
|
1l2p ![]() New Member ![]() Joined: May-20-2023 Location: France Points: 26 |
![]() ![]() ![]() ![]() ![]() |
Nice GUI... It just works!
Still need to tweak a little bit as we need to restart the app and as .voice save link is not very obvious. But that was a good way to get a full functional release in few hours. Congratulations! One comment regarding distance spelling. It would be nice if the ".0" string could be removed from integer non decimal values "3.0" before sending them to TTS. Also in French TTS, it would be great to send numbers with a comma and not a decimal point (1,4km and not 1.4). We say "un virgule quatre" (one comma four) and not "un point quatre" in French. Don't know if can upload and link a txt file here, so I put my French.lng translation as is. -------- maintain_hdg=Maintenez votre cap actuel. maintain_hdg_dest=Maintenez votre cap actuel pour atteindre [DESTINATION]. clear_pattern_turn=Après avoir quitté le circuit, prenez un cap au # pour atteindre [DESTINATION]. maintain_adequate=Maintenez une altitude suffisante au-dessus du relief. approaching_dest=En approche de [DESTINATION]. air_approaching_dest=Avion à l'approche de [DESTINATION]. turn_to=Tournez au <#/>. climb_to=Montez à # pieds. descend_to=Descendez à # pieds. for_cmd=pour and_cmd=et miles=mille nautical_miles=mille nautique kilometers=kilomètres location_ahead=[LOCATION] est devant vous à [DISTANCE]. location_ahead_clock=[LOCATION] est à # heures [DISTANCE] devant vous. location_ahead_lr_clock=[LOCATION] est [DISTANCE] à [LEFT-RIGHT] à # heures ahead_at_dist_is_dest=Devant vous, à [DISTANCE], se trouve [DESTINATION]. ahead_clock_dest=Devant vous à # heures, se trouve [DESTINATION]. ahead_clock_dist_dest=[DISTANCE] devant vous à # heures, se trouve [DESTINATION]. just_flew_over=Vous venez de passer au-dessus de [DESTINATION]. left_cmd=gauche right_cmd=droite to_left_right_clock=À votre [LEFT-RIGHT] à # heures, se trouve [LOCATION]. to_left_right_clock_dist=[DISTANCE] à votre [LEFT-RIGHT] à # heures, se trouve [LOCATION]. flying_near=Vous volez à proximité de [LOCATION]. prepare_for_arrival=Vous arrivez à destination de [DESTINATION]. |
|
![]() |
|
Steve Halpern ![]() Admin Group ![]() Joined: January-25-2003 Points: 3919 |
![]() ![]() ![]() ![]() ![]() |
About the commas... that should be able to be "switched". It would only be in the [DISTANCE] tag. Maybe an alternate tag, such as [DISTANCEC] where the [C] would convert it to a comma. Good idea about the 1.0. Found the issue on the French lat/lon data. Some would be correct, and some not. Alternate parsing was required on that data and I found the error. Thanks for the translation! I will post here when the next beta is uploaded with the fixes. Using French also showed that I needed to account for extended ASCII (UTF-8). The data is loading incorrectly. "Après avoir quitté le circuit" does not show correctly when I load it. The next build should have these fixes.
|
|
Steve
![]() |
|
![]() |
|
1l2p ![]() New Member ![]() Joined: May-20-2023 Location: France Points: 26 |
![]() ![]() ![]() ![]() ![]() |
Alt tag [DISTANCEC] will be a good way to proceed.
Just saw a strange display when restarting the app. I now also have the french data on the left ant UTF issues with accents. ![]() |
|
![]() |
|
Steve Halpern ![]() Admin Group ![]() Joined: January-25-2003 Points: 3919 |
![]() ![]() ![]() ![]() ![]() |
Hi, The new 1.0.2.0 beta was uploaded. I found a better way than using [DISTANCEC]. I added "point" to the vocabulary. So now you can change it to "virgule" ![]() I downloaded Microsoft Hortense (French) and I could not understand her, so maybe that is a good thing. Also, re-download the French database. It has the corrected LAT-LON points. I discovered we will have to add more phrases to the languages, primarily related to the end of the adventure when scoring is presented... but we can start testing with where it is at now and add that later. ![]() |
|
Steve
![]() |
|
![]() |
|
1l2p ![]() New Member ![]() Joined: May-20-2023 Location: France Points: 26 |
![]() ![]() ![]() ![]() ![]() |
Hi,
Thanks for the 1.0.2.0 update. I flew with Suzanne Cere, and not Hortense but it was great. ;-) "Point to Virgule" feature is ok and the trip was very smooth. I had some trouble installing the new FR-WikiData.bin file as it was always locked by the app itself. I set Wikipedia back to English, exited the app and manually deleted the previous .bin file. Then the new one could be downloaded. In general, taking new settings into account is not always obvious. To be sure, I systematically restart the application after any settings update. Adding new sentences will be fine. It could also be interesting to be able to create several versions of the same phrase which would then be played randomly to have more variations in flight. Have a nice week-end, Philippe. |
|
![]() |
|
Steve Halpern ![]() Admin Group ![]() Joined: January-25-2003 Points: 3919 |
![]() ![]() ![]() ![]() ![]() |
I will check the opening and closing of the data to make sure it is not held open in that instance. Thanks for the testing! The way the language system is constructed, adding varied phrases would not be too difficult. It could be accomplished in several ways. You could likely add several phrases with a delimiter (separator) on a given line and it would randomly pick from them. A good feature to add! |
|
Steve
![]() |
|
![]() |
|
1l2p ![]() New Member ![]() Joined: May-20-2023 Location: France Points: 26 |
![]() ![]() ![]() ![]() ![]() |
That sounds good!
![]() Filtering Wikipedia entries could also be useful. Using Wikipedia types (another new Window ;-) ), or maybe better just with a list of blacklisted strings matching entries titles. For example, I found that there were a lot of articles on train or subway stations. In some cases, it was one in two entries. So filtering based on keywords list may help. |
|
![]() |
|
Steve Halpern ![]() Admin Group ![]() Joined: January-25-2003 Points: 3919 |
![]() ![]() ![]() ![]() ![]() |
Hi, The latest beta should have the final vocabulary for now. You can actually load your existing file and see the new entries. The Exclude option can be saved to presets when Wikipedia data is used.
|
|
Steve
![]() |
|
![]() |
|
1l2p ![]() New Member ![]() Joined: May-20-2023 Location: France Points: 26 |
![]() ![]() ![]() ![]() ![]() |
Thanks for this release Steve.
It works great with the random sentences and really feels much more realistic. We need to check that the language template is really saved with the selected voice profile. I think that the link had been lost when installing the last release. The Geo Window does not come back anymore automatically to the list view. We now have to right click on the last active Wikipedia text to display it again. I can confirm that a keywords blacklist option might be helpful to filter unwanted Wikipedia inputs. I'm not sure that I understood what you wrote regarding the "Exclude option" and the presets. Is it related? Also got an idea to clean and to avoid complex manual parsing of Wikipedia data. I do not really use ChatGPT, but I tried to ask it to summarize the raw Wikipedia data. The result was impressive, with a clean and intelligent text, with fully filtered strings containing no special chars or values. A kind of perfect input to feed the T2S. I don't know how the ChatGPT API works and I think access should be paid. But the added value is spectacular. Thanks again, Philippe. --- Here is an updated French .lng file with multiple inputs. maintain_hdg=Maintenez votre cap actuel.$nConservez votre cap actuel.$nGardez votre cap actuel.$nMaintenez votre cap.$nConservez votre cap.$nGardez votre cap. maintain_hdg_dest=Maintenez votre cap actuel pour atteindre [DESTINATION].$nGardez votre cap actuel pour atteindre [DESTINATION].$nMaintenez votre cap pour atteindre [DESTINATION].$nGardez votre cap pour atteindre [DESTINATION]. clear_pattern_turn=Après avoir quitté le circuit, prenez un cap au # pour atteindre [DESTINATION]. maintain_adequate=Maintenez une altitude suffisante au-dessus du relief.$nConservez une altitude suffisante au-dessus du relief. approaching_dest=En approche de [DESTINATION].$nVous vous approchez de [DESTINATION].$nVous arrivez à [DESTINATION]. air_approaching_dest=Avion à l'approche de [DESTINATION].$nAvion en approche de [DESTINATION].$nVotre avion arrive à [DESTINATION]. turn_to=Tournez au <#/>.$nPrenez au <#/>.$nDirigez-vous au <#/>. climb_to=Montez à # pieds. descend_to=Descendez à # pieds. for_cmd=pour and_cmd=et miles=mille nautical_miles=mille nautique kilometers=kilomètres point=virgule location_ahead=[LOCATION] est devant vous à [DISTANCE].$n[LOCATION] se trouve devant vous à [DISTANCE].$n[LOCATION] se situe devant vous à [DISTANCE].$n[LOCATION] est à [DISTANCE] devant vous.$n[LOCATION] se trouve à [DISTANCE] devant vous.$n[LOCATION] se situe à [DISTANCE] devant vous. location_ahead_clock=[LOCATION] est à # heures [DISTANCE] devant vous.$n[LOCATION] se situe à # heures [DISTANCE] devant vous.$n[LOCATION] se trouve à # heures [DISTANCE] devant vous.$nDevant vous [DISTANCE] à # heures se trouve [LOCATION].$nDevant vous [DISTANCE] à # heures se situe [LOCATION]. location_ahead_lr_clock=[LOCATION] est [DISTANCE] à [LEFT-RIGHT] à # heures$n[LOCATION] se trouve [DISTANCE] à [LEFT-RIGHT] à # heures$n[LOCATION] se situe [DISTANCE] à [LEFT-RIGHT] à # heures ahead_at_dist_is_dest=Devant vous, à [DISTANCE], se trouve [DESTINATION].$nDevant vous, à [DISTANCE], se situe [DESTINATION]. ahead_clock_dest=Devant vous à # heures, se trouve [DESTINATION].$nDevant vous à # heures, se situe [DESTINATION]. ahead_clock_dist_dest=[DISTANCE] devant vous à # heures, se trouve [DESTINATION].$n[DISTANCE] devant vous à # heures, se situe [DESTINATION]. just_flew_over=Vous venez de passer au-dessus de [DESTINATION].$nVous êtes passé au-dessus de [DESTINATION]. left_cmd=gauche right_cmd=droite to_left_right_clock=À votre [LEFT-RIGHT] à # heures, se trouve [LOCATION].$nÀ votre [LEFT-RIGHT] à # heures, se situe [LOCATION].$nÀ # heures à votre [LEFT-RIGHT], se trouve [LOCATION].$nÀ # heures à votre [LEFT-RIGHT], se situe [LOCATION]. to_left_right_clock_dist=[DISTANCE] à votre [LEFT-RIGHT] à # heures, se trouve [LOCATION].$n[DISTANCE] à votre [LEFT-RIGHT] à # heures, se situe [LOCATION].$n[DISTANCE] à votre [LEFT-RIGHT] dans vos # heures, se trouve [LOCATION].$n[DISTANCE] à votre [LEFT-RIGHT] dans vos # heures, se situe [LOCATION]. flying_near=Vous volez à proximité de [LOCATION].$nVous passez à proximité de [LOCATION].$nVous êtes à proximité de [LOCATION].$nVous volez près de [LOCATION].$nVous passez près de [LOCATION].$nVous êtes près de [LOCATION]. prepare_for_arrival=Vous arrivez à destination de [DESTINATION].$nVous arrivez à [DESTINATION]. you_have_reached=Vous avez atteint la destination de votre aventure. Vous pouvez parquer votre avion. adventure_statistics=Statistiques de l'aventure distance_travelled=Distance parcourue flight_time=Temps de vol$nDurée du vol places_visited=Lieux visités excellent=Excellent$nTrès bien$nParfait good=Bien fair=Pas trop mal$nPas mal$nCorrect poor=Pas terrible$nPas génial$nFaible hours=Heures minutes=Minutes seconds=Secondes takeoff=Décollage landing=Atterrissage invalid_takeoff_count=Nombre de décollages invalide invalid_landing_count=Nombre d'atterrissages invalide lateral_navigation=Guidage latéral vertical_navigation=Guidage vertical your_total_score=Votre score total pour ce vol est flight_evaluation=Evaluation du vol calculated_expected=Ce vol a un score estimé de #. Les valeurs les plus basses sont les meilleures. click_adv_to_close=Cliquez sur ADV dans le menu pour terminer l'aventure. you_have_completed=Vous avez terminé votre aventure. |
|
![]() |
|
Steve Halpern ![]() Admin Group ![]() Joined: January-25-2003 Points: 3919 |
![]() ![]() ![]() ![]() ![]() |
Hi Philippe, Thanks for the French template! I tested the assigning of the language template. It seemed to save. But if the Geo window is already loaded you would have to close and re-open it for it to be assigned. Make sure the language file is selected and highlighted in blue before saving the voice preset. I added an Exclude option in the Map window. When you select Wikipedia, it would exclude a search term. Note it is not in the Geo window yet... See if it works on the filter items you want to exclude. See "Station" below. ![]() The newer data and version pulls directly from Wikipedia in real time, with better flexibility to add extended information. You will see the option for extended data in Settings of the beta version... But that is interesting about ChatGPT!
|
|
Steve
![]() |
|
![]() |
|
1l2p ![]() New Member ![]() Joined: May-20-2023 Location: France Points: 26 |
![]() ![]() ![]() ![]() ![]() |
I got it now. Exclude option is currently only implemented in the Map Window.
Search and display were ok with a single keyword. Did you already set a "separator" to handle multiple keywords?
|
|
![]() |
|
Steve Halpern ![]() Admin Group ![]() Joined: January-25-2003 Points: 3919 |
![]() ![]() ![]() ![]() ![]() |
Yes, comma separated... no spaces needed. The test version I have now implements it in the Geo Window. It will be in the next beta!
|
|
Steve
![]() |
|
![]() |
|
1l2p ![]() New Member ![]() Joined: May-20-2023 Location: France Points: 26 |
![]() ![]() ![]() ![]() ![]() |
I tried the 1.0.2.3 but was not able to understand how to activate filtering in Geo Window.
What Database mode should be kept? Do we need to activate or link some Presets ? ![]() |
|
![]() |
|
Steve Halpern ![]() Admin Group ![]() Joined: January-25-2003 Points: 3919 |
![]() ![]() ![]() ![]() ![]() |
It appears you have it correct. Let's say your preset includes Wikipedia, and the grayed box is FR, and you saved "station" as an exclude name. When you open the Geo Windows, you will not see any entry with station in the title. As a test, start without a filter. Jump to a populated area and note the list of entries. Find a word that is common to a few locations. Close the Geo Window, edit the preset with that exclude word and set it as active (Wiki Exclude), then load the Geo Window. They should now be missing.
|
|
Steve
![]() |
|
![]() |
|
1l2p ![]() New Member ![]() Joined: May-20-2023 Location: France Points: 26 |
![]() ![]() ![]() ![]() ![]() |
That's what I did last night. Maybe did I missed something. Filtering works well in the Map/Presets windows. Even with multiple keywords and they are not case sensitive. I just tried again few minutes ago. (I reset the cfg meanwhile) ![]() It seems to be ok now. "Gare" is not anymore in the liste. But can you confirm that in this "preset" mode only the Wikipedia Titles are sent to T2S? ![]() |
|
![]() |
|
Steve Halpern ![]() Admin Group ![]() Joined: January-25-2003 Points: 3919 |
![]() ![]() ![]() ![]() ![]() |
You should have the full Wikipedia excerpt. If not, see if your have the Disable Wikipedia Information box checked. It should be unchecked in voice settings. ![]() |
|
Steve
![]() |
|
![]() |
|
1l2p ![]() New Member ![]() Joined: May-20-2023 Location: France Points: 26 |
![]() ![]() ![]() ![]() ![]() |
Everything is like your screencap.
But I do not clearly understand where the exclude filter mechanism applies. If it's only on "Preset" database option and not on "Wikipedia" we then need to select "Preset" radio to activate it. But what is now the purpose of the "Wikipedia" radio button option with langage and extended check box? I'm quite lost ;-) ![]() |
|
![]() |
|
Steve Halpern ![]() Admin Group ![]() Joined: January-25-2003 Points: 3919 |
![]() ![]() ![]() ![]() ![]() |
The product is even complex for me and I put the settings there! ![]() It is only Preset, and that needs to be ticked. Your Wiki Exclude name works and helps you identify it is Wiki. A preset can use any of the databases. The Wikipedia/Language/Extended will carryover however when Preset is selected, and you are using a Wikipedia database. Technically, they could be left enabled for BOTH the Wikipedia and Preset tick boxes. Maybe it is best do do that to not cause confusion. Like this: ![]() But you still should have had an extract for that location... however, if the Wikipedia server was momentarily unreachable, maybe that is why you got that? See if you get others that have extracts.
|
|
Steve
![]() |
|
![]() |
Post Reply ![]() |
|
Tweet |
Forum Jump | Forum Permissions ![]() You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |