Translation Management in FOSS - The Case of GeoServer
This is a modal window.
The media could not be loaded, either because the server or network failed or because the format is not supported.
Formal Metadata
| Title |
| |
| Title of Series | ||
| Number of Parts | 156 | |
| Author | ||
| License | CC Attribution 3.0 Unported: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor. | |
| Identifiers | 10.5446/68559 (DOI) | |
| Publisher | ||
| Release Date | ||
| Language |
Content Metadata
| Subject Area | ||
| Genre | ||
| Abstract |
| |
| Keywords |
00:00
CompilerMereology
00:11
MetadataTranslation (relic)Software developerUser interfaceWeb pageWeb 2.0Rule of inferenceInternationalization and localizationMultiplication signServer (computing)GeometryCompilerAttribute grammarLevel (video gaming)Projective planeInstance (computer science)Key (cryptography)Formal languageComputer fileINTEGRALParameter (computer programming)Maschinelle ÜbersetzungSubsetSheaf (mathematics)CodeConfiguration spacePhysical systemDefault (computer science)Category of beingCASE <Informatik>Software developerMetadataSystem administratorMereologyAbstractionMathematicsStandard deviationTask (computing)Codierung <Programmierung>Equivalence relationCommunications protocolUser interfaceFunctional (mathematics)Different (Kate Ryan album)Cartesian coordinate systemASCIIIntegrated development environmentLecture/Conference
04:18
Quality of serviceLeast squaresComputer-assisted translationComputer animation
Transcript: English(auto-generated)
00:00
So I am working for come to camp and one of my hobbies, part of the GeoServer community, is taking care of the translation of the GeoServer. And so we are going to go through the translation.
00:20
There are two ways to deal with the translation in GeoServer. First, as a GeoServer user, you need sometimes to translate the metadata you broadcast with GeoServer when you have an international audience, for example. And as a GeoServer developer, you also have a task to provide a translation
00:44
for the administration user interface. So we will see in both cases what you can do with GeoServer. So for the content translation, we have the document that is generated by the Git capabilities can be translated for a lot of OGC protocols.
01:06
You can do it on all the configuration pages of the administration UI with an internationalization checkbox. And the document can be re-narrated when you provide an accept language request parameter.
01:27
You can also do some translation in styles. Only in ECLD, so in GeoCSS or a Mapbox style language is not supported. It's not part of OGC standard, it's something specific to GeoServer.
01:44
It works for title and abstract sections. And they are used in the Git legend graphic request when you provide a language parameter. You also have in SLD a language function where you can be used to get the language parameter of the request
02:02
and you can be used ever to select the good attribute in your entity to display the things on the map. And you can also use it for a rule feature when you want to change the marker, for example. For the administration UI, how it works, the text comes from properties files with a key value system.
02:28
You always have a GeoServer application.properties which contains a different language in English. Over languages are described in files with a suffix describing the language in ISO code.
02:44
You can provide partial translation, in this case you will have the default English language. And also you have to take care of the encoding of the files. You have to be something like ISO-859 or something equivalent like US-ASCII or Latin-1.
03:06
You can update the translation in a different way that you will think it in your IDE. And you provide a PR to update the next release. And you can also use the OS Geo web.late instance to suggest new translation.
03:23
You need to have a OS Geo account and after you have to ask me to register you in the project. We use web.let because two times ago we used TransFX but we have to... I have decided to move to the web.let because integration of GitHub was not working correctly.
03:46
We had to do a lot of manual exporting first to integrate the changes into GitHub. And with the TransFX automatic translation we had also a lot of changes in the existing translation we didn't want.
04:02
So now with web.let we have nice GitHub integration. We can control more of the configuration also. And since it's managed by OS Geo it's more aligned with the project in all. Thank you.