Adding Spanish as an Available Language

[totallynotdavid]

Hi there! I'm interested in contributing to this beamer template by adding support for the Spanish language. I wanted to know if the maintainers of this project would be open to accepting this contribution or if this would be more suitable as a modified version of the template.

I believe adding Spanish support would make this template more accessible to a wider audience. Please let me know your thoughts on this and how I can help move this forward.

Thank you for your time and consideration.

[LogCreative]

We welcome all contributions to this repository ☺️

Make it a plugin

I think the easiest way to contribute a translation for SJTUBeamer now is to contribute a plugin, see contrib/ dir, CONTRIBUTING.md and sjtubeamerdevguide. Or the following details:

• Fork this repository.
• Create a plugin called spanish (you can change to another name) through cd src && l3build add-contrib spanish. This will create a placeholder for your new plugin.
• Then in the contrib/spanish/sjtubeamerthemespanish.ltx, add the translation to support your language well. Besides adding the necessary packages to support your language well in this plugin file, I believe the current version of SJTUBeamer is to just redefine (\renewcommand) the following commands:
  

  SJTUBeamer/sjtucover.sty

  Line 213 in 4cec95d

  \newcommand{\bottomthanks}{Thank You}

  
  

  SJTUBeamer/sjtucover.sty

  Lines 360 to 365 in 4cec95d

  	\def\sjtubeamer@cover@partnumber{\insertromanpartnumber}
  	\def\sjtubeamer@cover@partname{\partname~\sjtubeamer@cover@partnumber}
  	\def\sjtubeamer@cover@sectionnumber{\insertsectionnumber}
  	\def\sjtubeamer@cover@sectionname{\sectionname~\sjtubeamer@cover@sectionnumber}
  	\def\sjtubeamer@cover@subsectionnumber{\insertsubsectionnumber}
  	\def\sjtubeamer@cover@subsectionname{\subsectionname~\sjtubeamer@cover@subsectionnumber}

• Write a short note in the plugin documentation contrib/spanish/spanish.tex. You could make sjtubeamerquickstart as a good reference to write your documentation.
• I think it will be a good idea to add another README_es.md to the root of this repository like it is in README_en.md.
• Make a pull request back to this repo, and the user could access your plugin by the following way:

\documentclass{beamer}
\usetheme{sjtubeamer}
\usesjtutheme{spanish}  % This will input contrib/spanish/sjtubeamerthemespanish.ltx
\begin{document}
   % the main contents
\end{document}

The plugin could also be viewed in #81.

Modify the kernel

If you are familiar with DocTeX and the internal tools we are using in the src/ directory (you probably need to read the development guide carefully), try to make a modification to the dtx files as is in src/source. You need to learn more about the communication model of this template and add nodes to each layer of this template.

SJTUBeamer/src/source/beamerthemesjtubeamer.dtx

Lines 151 to 152 in 4cec95d

	\DeclareOptionBeamer{zh}{\def\sjtubeamer@lang{zh}}
	\DeclareOptionBeamer{en}{\def\sjtubeamer@lang{en}}

SJTUBeamer/src/source/beamerinnerthemesjtubeamer.dtx

Lines 87 to 88 in 4cec95d

	\DeclareOptionBeamer{zh}{\def\sjtubeamer@inner@lang{zh}}
	\DeclareOptionBeamer{en}{\def\sjtubeamer@inner@lang{en}}

SJTUBeamer/src/source/sjtucover.dtx

Lines 39 to 40 in 4cec95d

	\DefineOption{cover}{lang}{zh}
	\DefineOption{cover}{lang}{en}

Then you can make changes to the corresponding spaces that need to be translated. Then cd src and l3build check, the root files will get updated. The resulted usage will look like this:

\documentclass{beamer} % or a language specific version of beamer
\usetheme[es]{sjtubeamer}
\begin{document}
   % the main contents
\end{document}

Since it is typically harder to add more packages to the kernel, it is less freedom compared to the previous method. But this looks better. Again it is a better idea to add a README_es.md.

You can choose the way you like to contribute.

Translating other docs

If you want to translate main.tex, the content actually doesn't belong to this repository, this document is only for demo use. You can fork tuna/thulib-latex-talk. Or you can finish the contribution above and fork this repo to translate, I think it is not necessary to translate a demo file. Put the demo inside plugin doc spanish.tex is enough.

Currently, the user manual sjtubeamer.tex is only in Simplified Chinese. Only the development guide is in English. I think you'd better not to translate those files since they are not necessary. If you choose the making the plugin method, you could write down the information in the spanish.tex. Or you could write simple hints in README_es.md.

Just fork this repo

If the methods above still sound hard for you, fork this repo directly and modify the elements to fit your need. But be aware that any graphics in this repo doesn't belong to SJTUG, they are actually belong to our university. The university limits the distribution of those files (see vi/) and you probably need to avoid distribute them publicly on other platforms. Or you could modify those artworks to fit your need if you find that as a legit option. Other than those artworks, we don't limit other parts of this repo since they are under Apache-2.0 License.